Actions
Bug #19998
openCommand rudder server node-to-relay fails with curl error about proxy on debian
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
Description
It seems to be due to the correction to #18968: on debian 9 with scale-out-relay 6.2-1.6 which contains the fix, I get the error:
root@server:/home/vagrant# rudder server node-to-relay 44a6d856-1f6c-4900-b70b-17a5c0eac34e Rudder relay installation script starting, using UUID 44a6d856-1f6c-4900-b70b-17a5c0eac34e. curl: (5) Could not resolve proxy: '' Failed to promote 44a6d856-1f6c-4900-b70b-17a5c0eac34e to relay. Code 5
And the correction was:
Workaround:
- edit /opt/rudder/share/commands/server-node-to-relay
- replace --proxy ''
by --noproxy '*'
Files
Updated by François ARMAND about 3 years ago
- Subject changed from Command rudder server node-to-relay may fail with curl error about proxy to Command rudder server node-to-relay fails with curl error about proxy on debian
- Description updated (diff)
Updated by François ARMAND about 3 years ago
- Related to Bug #18968: Command rudder server node-to-relay may fail with curl error added
Updated by Nicolas CHARLES almost 3 years ago
- Related to Bug #20287: Command rudder server node-to-relay fails to execute added
Updated by Vincent MEMBRÉ over 1 year ago
- Target version changed from 6.1-1.5 to 7.2
Updated by Alexis Mousset about 1 year ago
- Target version changed from 7.2 to 7.3
Actions