Actions
Bug #20632
closed
Trigger run button fails to contact the API
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Priority:
48
Name check:
To do
Fix check:
To do
Regression:
Description
In a 6.2.12, sometimes, the trigger run button in the node reports webpage fails to connect to the underlying API. It displays an error with:
Error when trying to contact internal remote-run API: Read timed out
The apache error log gives:
[Mon Jan 24 09:47:57.969847 2022] [proxy:error] [pid 118776:tid 139952943769344] (111)Connection refused: AH00957: HTTP: attempt to connect to 127.0.0.1:8080 (localhost) failed
The remote-run cli is working fine, and an apache restart fix the issue.
Updated by Alexis Mousset about 2 years ago
It is really strange as the problem seems to be in the webapp (which listens on 8080), so restarting apache does not seem linked...
Updated by Vincent MEMBRÉ about 2 years ago
- Target version changed from 6.2.13 to 6.2.14
- Priority changed from 50 to 49
Updated by Vincent MEMBRÉ almost 2 years ago
- Target version changed from 6.2.14 to 6.2.15
- Priority changed from 49 to 48
Updated by Alexis Mousset almost 2 years ago
Relayd has changed significantly between Rudder 6 and 7. Closing for now, please reopen with relayd logs if it still occurs on 7.X.
Updated by Alexis Mousset almost 2 years ago
- Status changed from New to Rejected
Actions