Support #23136
closedERROR -- action: Connection refused - connect(2) for "127.0.0.1" port 3000 (Errno::ECONNREFUSED)
Description
Hi,
when I run a job, it fails with this error :
ERROR -- action: Connection refused - connect(2) for "127.0.0.1" port 3000 (Errno::ECONNREFUSED)
in smart_proxy_dynflow_core.log
I have :
- Endpoint for reverse communication
:foreman_url: 'https://foreman.my.domain'
and I can't find anywhere with 127.0.0.1 port 3000
Do you know where I can change this ?
Thanks
Updated by Adam Ruzicka over 6 years ago
Try looking at foreman_url key in /etc/smart_proxy_dynflow_core/settings.yml . Also don't forget to restart the smart_proxy_dynflow_core service after changing that file.
Updated by Sebastien LAMY over 6 years ago
Adam Ruzicka wrote:
Try looking at foreman_url key in /etc/smart_proxy_dynflow_core/settings.yml . Also don't forget to restart the smart_proxy_dynflow_core service after changing that file.
- ll /etc/smart_proxy_dynflow_core/settings.yml
ls: cannot access /etc/smart_proxy_dynflow_core/settings.yml: No such file or directory
I don't have other files names settings.xml
only /etc/foreman-proxy/settings.yml
Updated by Adam Ruzicka over 6 years ago
Ok, on what platform are you? What versions of packages (foreman, REX, smart_proxy_dynflow) do you have?
Updated by Sebastien LAMY over 6 years ago
Adam Ruzicka wrote:
Ok, on what platform are you? What versions of packages (foreman, REX, smart_proxy_dynflow) do you have?
Centos 7
Foreman 1.16.0
katello 3.5.1
smart_proxy_dynflow_core 0.1.8
Updated by Sebastien LAMY over 6 years ago
Hi,
I recreated the settings.yml file, and now I have another error :
[2018-04-10 11:15:03.392 #13829] DEBUG -- dynflow: Step 28333c6c-360f-4d32-8846-c7503831d326: 5 running >> error in phase Run SmartProxyDynflowCore::Callback::Action
[2018-04-10 11:15:03.392 #13829] ERROR -- action: SSL_connect returned=1 errno=0 state=SSLv3 read server session ticket A: sslv3 alert unsupported certificate (OpenSSL::SSL::SSLError)
but my cert seems to be ok
How can I test if the certificate should work ?
Updated by Sebastien LAMY over 6 years ago
No I have
ERROR -- action: 403 Forbidden (RestClient::Forbidden)
the job works, but the Rest Callback does not work
Updated by Adam Ruzicka over 3 years ago
- Status changed from New to Closed
Last movement here was 3 years ago. Closing.