Bug #10645
closedProxy error when accepting 500 inventories at the same time
Description
When accepting 500 inventories at the same time, I get the following error:
Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request POST /rudder/secure/nodeManager/manageNewNode. Reason: Error reading from remote server
Things are going well in backstages, but still, this is confusing
Updated by Nicolas CHARLES over 7 years ago
actually, it may have broken things (it may be the cause of #10646)
Updated by Nicolas CHARLES over 7 years ago
- Related to Bug #10646: "SocketException(message='Socket closed'" error at the end of generation with 500 nodes added
Updated by Jonathan CLARKE over 7 years ago
- Severity set to Minor - inconvenience | misleading | easy workaround
- Priority changed from 0 to 6
Assuming this is working well in the backend as you suggest, this would be a Minor severity ticket. If this does break something, either merge it with #10646, or increase the severity.
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 4.1.2 to 4.1.3
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 4.1.3 to 4.1.4
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 4.1.4 to 4.1.5
Updated by Alexis Mousset over 7 years ago
- Target version changed from 4.1.5 to 4.1.6
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 4.1.6 to 4.1.7
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 4.1.7 to 4.1.8
Updated by Vincent MEMBRÉ almost 7 years ago
- Target version changed from 4.1.8 to 4.1.9
- Priority changed from 21 to 20
Updated by Vincent MEMBRÉ almost 7 years ago
- Target version changed from 4.1.9 to 4.1.10
- Priority changed from 20 to 19
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.10 to 4.1.11
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.11 to 4.1.12
- Priority changed from 19 to 18
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.12 to 4.1.13
Updated by Vincent MEMBRÉ about 6 years ago
- Target version changed from 4.1.13 to 4.1.14
Updated by Benoît PECCATTE about 6 years ago
- Target version changed from 4.1.14 to 4.1.15
Updated by Vincent MEMBRÉ almost 6 years ago
- Target version changed from 4.1.15 to 4.1.16
Updated by Vincent MEMBRÉ almost 6 years ago
- Target version changed from 4.1.16 to 4.1.17
Updated by Vincent MEMBRÉ almost 6 years ago
- Target version changed from 4.1.17 to 4.1.18
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 4.1.18 to 4.1.19
Updated by Alexis Mousset over 5 years ago
- Target version changed from 4.1.19 to 4.1.20
Updated by François ARMAND over 5 years ago
- Target version changed from 4.1.20 to 4.1.21
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 4.1.21 to 4.1.22
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 4.1.22 to 4.1.23
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 4.1.23 to 4.1.24
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 4.1.24 to 588
Updated by Benoît PECCATTE about 5 years ago
- Target version changed from 588 to 5.0.13
Updated by Vincent MEMBRÉ about 5 years ago
- Target version changed from 5.0.13 to 5.0.14
Updated by Nicolas CHARLES about 5 years ago
This still happens. I think it's because the process to accept 500 nodes is too slow, and the action is not async - so it fails
Updated by Nicolas CHARLES about 5 years ago
plus generation kicks in while the process goes on
Updated by Nicolas CHARLES about 5 years ago
i got one error75d7-4df6-941e-c0ae3115e7e0.xml'. You can safely ignore that warning if the The connection is not established.
file was already existing in Git and was not modified by that archive.
[2019-09-02 20:08:32] ERROR nodes.pending - Error when trying to accept node f886ece3-165c-42f3-ba55-d840a86b3499. Rollbacking. <
[2019-09-02 20:08:32] ERROR nodes.pending - Unit acceptor error for node NodeId(f886ece3-165c-42f3-ba55-d840a86b3499) <- Error when trying to accept node f886ece3-165c-42f3-ba55-d840a86b3499 <- The connection is not established.
Updated by Vincent MEMBRÉ about 5 years ago
- Target version changed from 5.0.14 to 5.0.15
Updated by Vincent MEMBRÉ almost 5 years ago
- Target version changed from 5.0.15 to 5.0.16
Updated by Alexis Mousset over 4 years ago
- Target version changed from 5.0.16 to 5.0.17
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 5.0.17 to 5.0.18
Updated by Vincent MEMBRÉ about 4 years ago
- Target version changed from 5.0.18 to 5.0.19
- Priority changed from 18 to 19
Updated by Vincent MEMBRÉ about 4 years ago
- Target version changed from 5.0.19 to 5.0.20
Updated by Vincent MEMBRÉ almost 4 years ago
- Target version changed from 5.0.20 to 797
Updated by Nicolas CHARLES over 3 years ago
- Priority changed from 19 to 20
i reproduced it on a very memory coonstraint system.
could be a memory issue
Updated by Benoît PECCATTE over 3 years ago
- Target version changed from 797 to 6.1.14
Updated by Vincent MEMBRÉ about 3 years ago
- Target version changed from 6.1.14 to 6.1.15
Updated by Vincent MEMBRÉ about 3 years ago
- Target version changed from 6.1.15 to 6.1.16
Updated by Vincent MEMBRÉ about 3 years ago
- Target version changed from 6.1.16 to 6.1.17
- Priority changed from 20 to 21
Updated by Vincent MEMBRÉ almost 3 years ago
- Target version changed from 6.1.17 to 6.1.18
Updated by Vincent MEMBRÉ almost 3 years ago
- Target version changed from 6.1.18 to 6.1.19
Updated by François ARMAND over 2 years ago
- Is duplicate of Architecture #5367: Make node acceptance process asynchronous added
Updated by François ARMAND over 2 years ago
- Status changed from New to Rejected
I'm closing that issue as a duplicate of #5367