Thank you for checking the Problem, i will try to fix it. Strange, i used most default settings and it still provides problems.
Am Mittwoch, 13. Juli 2016 09:03:19 UTC+2 schrieb Ivan Necas: > > The proxy.log says: > > E, [2016-07-12T11:32:41.033559 #1475] ERROR -- : Error during startup, > terminating. Address already in use - bind(2) > > and the netstat shows there is 1/systemd listening on port 9090, which > is probably the reason why this happens. > I also looked more closely at the s_connect output you provided and it > confirms the cert is completely different > from what foreman expects. > > -- Ivan > > On Tue, Jul 12, 2016 at 9:45 PM, 'Denis Müller' via Foreman users > <[email protected] <javascript:>> wrote: > > i disabled selinux and started the installation again, but no luck. Im > > providing foreman-debug archiv. > > > > Am Dienstag, 12. Juli 2016 13:02:40 UTC+2 schrieb Ivan Necas: > >> > >> I was not able to see any issues in the output. I forklifted > >> the 3.0 in my environment and was not able to reproduce the issue > either. > >> > >> Anything interesting in /var/log/foreman-proxy/proxy.log. > >> > >> Just to complete the info, is it selinux enforcing or permissive? > >> > >> Ideally, > >> using the foreman-debug to upload the tar to out support storage > >> and sharing the link here would move us forward. > >> > >> -- Ivan > >> > >> On Tue, Jul 12, 2016 at 9:26 AM, 'Denis Müller' via Foreman users > >> <[email protected]> wrote: > >> > Hello Ivan, > >> > > >> > thank you for reply. I send you the output of that commands: > >> > > >> > > >> > > >> > Am Dienstag, 12. Juli 2016 09:00:27 UTC+2 schrieb Ivan Necas: > >> >> > >> >> Hi, > >> >> > >> >> Would you mind sharing the output of the following commands: > >> >> > >> >> openssl x509 -in /etc/foreman-proxy/ssl_cert.pem -text -noout > >> >> openssl s_client -connect $(hostname):9090 > >> >> openssl verify -CAfile /etc/foreman/proxy_ca.pem > >> >> /etc/foreman-proxy/ssl_cert.pem > >> >> > >> >> What I'm looking for especially is if the CN is matching the host > fqdn > >> >> and if the corresponding > >> >> ca verifies it. > >> >> > >> >> -- Ivan > >> >> > >> >> On Tue, Jul 12, 2016 at 7:54 AM, 'Denis Müller' via Foreman users > >> >> <[email protected]> wrote: > >> >> > I had custom repositories of Epel and so on. So after replacing it > >> >> > with > >> >> > default repos it worked, im able to install katello. BUT if i run > >> >> > "foreman-installer --scenario katello" it fails all the time. > >> >> > The OS is CentOS 7.1 and it is fresh installed system. > >> >> > ^C[root@katello ~]# foreman-installer --scenario katello > >> >> > Proxy katello.nodes.rto.de cannot be registered (422 > Unprocessable > >> >> > Entity): > >> >> > Unable to communicate with the proxy: ERF12-2530 > >> >> > [ProxyAPI::ProxyException]: > >> >> > Unable to detect features ([OpenSSL::SSL::SSLError]: SSL_connect > >> >> > returned=1 > >> >> > errno=0 state=SSLv3 read server certificate B: certificate > verif...) > >> >> > for > >> >> > proxy https://katello.nodes.rto.de:9090/features Please check the > >> >> > proxy > >> >> > is > >> >> > configured and running on the host. > >> >> > > >> >> > > >> >> > > >> >> > /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[ > katello.nodes.rto.de]/ensure: > >> >> > change from absent to present failed: Proxy katello.nodes.rto.de > >> >> > cannot > >> >> > be > >> >> > registered (422 Unprocessable Entity): Unable to communicate with > the > >> >> > proxy: > >> >> > ERF12-2530 [ProxyAPI::ProxyException]: Unable to detect features > >> >> > ([OpenSSL::SSL::SSLError]: SSL_connect returned=1 errno=0 > state=SSLv3 > >> >> > read > >> >> > server certificate B: certificate verif...) for proxy > >> >> > https://katello.nodes.rto.de:9090/features Please check the proxy > is > >> >> > configured and running on the host. > >> >> > > >> >> > > >> >> > > >> >> > /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[ > katello.nodes.rto.de]: > >> >> > Failed to call refresh: Proxy katello.nodes.rto.de cannot be > >> >> > registered > >> >> > (ApipieBindings::MissingArgumentsError: id): N/A > >> >> > > >> >> > > >> >> > > >> >> > /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[ > katello.nodes.rto.de]: > >> >> > Proxy katello.nodes.rto.de cannot be registered > >> >> > (ApipieBindings::MissingArgumentsError: id): N/A > >> >> > Installing Done > >> >> > [100%] > >> >> > > >> >> > > >> >> > > [...............................................................................................................................] > > > >> >> > Something went wrong! Check the log for ERROR-level output > >> >> > The full log is at /var/log/foreman-installer/katello.log > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > Am Freitag, 8. Juli 2016 11:21:38 UTC+2 schrieb Marvin Beckers: > >> >> >> > >> >> >> Hello Denis, > >> >> >> > >> >> >> it might be helpful to provide logfiles in English since that's > the > >> >> >> language most people on this mailing list have in common. Not > >> >> >> everyone > >> >> >> speaks German. What command exactly are you running? Is that the > >> >> >> output > >> >> >> of > >> >> >> `yum install katello`? What repositories have you configured? > >> >> >> > >> >> >> Marvin > >> >> >> > >> >> >> Am Freitag, 8. Juli 2016 10:41:22 UTC+2 schrieb Denis Müller: > >> >> >>> > >> >> >>> Hi, > >> >> >>> > >> >> >>> i was trying to install "katello.noarch 0:3.0.0-9.el7" but no > luck > >> >> >>> here. > >> >> >>> Installation can not resolve all dependencies, is it a bug? See > >> >> >>> install.log. > >> >> >>> I would appreciate any help. > >> >> >>> > >> >> >>> Best regards, > >> >> >>> > >> >> >>> Denis > >> >> > > >> >> > -- > >> >> > 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. > >> > > >> > -- > >> > 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. > > > > -- > > 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] <javascript:>. > > To post to this group, send email to [email protected] > <javascript:>. > > Visit this group at https://groups.google.com/group/foreman-users. > > For more options, visit https://groups.google.com/d/optout. > -- 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.
