Hi Adam, you give me the right hint to find the solution and your first idea was the right one...
[2016-11-22 14:38:01.861 #119088] ERROR -- action: SSL_connect returned=1 errno=0 state=SSLv3 read server session ticket A: tlsv1 alert unknown ca (OpenSSL::SSL::SSLError) /opt/rh/rh-ruby22/root/usr/share/ruby/net/http.rb:923:in `connect' /opt/rh/rh-ruby22/root/usr/share/ruby/net/http.rb:923:in `block in connect' /opt/rh/rh-ruby22/root/usr/share/ruby/timeout.rb:74:in `timeout' /opt/rh/rh-ruby22/root/usr/share/ruby/net/http.rb:923:in `connect' .... [2016-11-22 15:08:54.849 #2491] FATAL -- SIGTERM [2016-11-22 15:08:54.877 #2491] ERROR -- dynflow: ... core terminated. i already had that problem once with the unknown ca error. i had to update the crl-File for the ca to fix that behavior. I already done this on the other Foreman Installations to be able to import the facts from our puppet server. Thx for the help and the final hint. Susanne On Tuesday, November 22, 2016 at 10:10:35 AM UTC+1, Adam Ruzicka wrote: > > Hello, > it seems that when the proxy is making a callback to Foreman, it doesn't > reach Foreman at all. Could you please set set log_level to DEBUG in > /etc/smart_proxy_dynflow_core/settings.yml, watch the log > in /var/log/foreman-proxy/smart_proxy_dynflow_core.log and try to rerun the > job? Some useful information might show up there. > > Adam > > -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
