Sorry, fat finger send. Will update presently. ------ The most dangerous phrase in the language is, "We've always done it this way."
- Grace Hopper On 15 February 2017 at 10:51, Lachlan Musicman <[email protected]> wrote: > After a seemingly successful - if traumatic - upgrading of puppet from 3.x > to 4.x as per https://www.theforeman.org/plugins/katello/3.2/upgrade/puppe > t.html I find that neither Candlepin nor pulp are starting. > > CentOS 7.3, Katello 3.2, Foreman 1.13 > > [root@vmpr-res-utils etc]# hammer ping > candlepin: > Status: FAIL > Server Response: > candlepin_auth: > Status: FAIL > Server Response: > pulp: > Status: FAIL > Server Response: > foreman_tasks: > Status: ok > Server Response: Duration: 12ms > > Well, actually, systemctl has pulp-* as working (status = active (running) > except the normal active(exited) for pulp_workers.service ) > > The Katello Administration/About page show me > > > Backend System Status Component Status Message > candlepin FAIL Connection refused - connect(2) for " > vmpr-res-utils.unix.petermac.org.au" port 8443 > candlepin_auth FAIL A backend service [ Candlepin ] is unreachable > foreman_tasks OK pulp FAIL 404 Resource Not Found pulp_auth FAIL Skipped > pulp_auth check after failed pulp check > > > [main] > enabled=1 > latency=1 > > [messaging] > url= > uuid= > cacert=/etc/rhsm/ca/candlepin-local.pem > clientcert=/etc/pki/consumer/bundle.pem > > > > > > > > ------ > The most dangerous phrase in the language is, "We've always done it this > way." > > - Grace Hopper > -- 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.
