Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- root@host ~]# foreman-installer --enable-foreman-plugin-ansible --enable-foreman-proxy-plugin-ansible
- Resetting puppet server version param...
- Systemd start for foreman-proxy failed!
- journalctl log for foreman-proxy:
- -- Logs begin at Tue 2019-03-12 11:38:52 CET, end at Tue 2019-03-12 11:41:18 CET. --
- Mar 12 11:39:03 host.domain01.domaincorp.lan systemd[1]: Starting Foreman Proxy...
- Mar 12 11:39:13 host.domain01.domaincorp.lan smart-proxy[7304]: Errors detected on startup, see log for details. Exiting: uninitialized constant Dynflow
- Mar 12 11:39:13 host.domain01.domaincorp.lan systemd[1]: foreman-proxy.service: main process exited, code=exited, status=1/FAILURE
- Mar 12 11:39:13 host.domain01.domaincorp.lan systemd[1]: Failed to start Foreman Proxy.
- Mar 12 11:39:13 host.domain01.domaincorp.lan systemd[1]: Unit foreman-proxy.service entered failed state.
- Mar 12 11:39:13 host.domain01.domaincorp.lan systemd[1]: foreman-proxy.service failed.
- Mar 12 11:41:17 host.domain01.domaincorp.lan systemd[1]: Starting Foreman Proxy...
- Mar 12 11:41:18 host.domain01.domaincorp.lan smart-proxy[10472]: Errors detected on startup, see log for details. Exiting: uninitialized constant Dynflow
- Mar 12 11:41:18 host.domain01.domaincorp.lan systemd[1]: foreman-proxy.service: main process exited, code=exited, status=1/FAILURE
- Mar 12 11:41:18 host.domain01.domaincorp.lan systemd[1]: Failed to start Foreman Proxy.
- Mar 12 11:41:18 host.domain01.domaincorp.lan systemd[1]: Unit foreman-proxy.service entered failed state.
- Mar 12 11:41:18 host.domain01.domaincorp.lan systemd[1]: foreman-proxy.service failed.
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/service/systemd.rb:167:in `rescue in start'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/service/systemd.rb:164:in `start'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type/service.rb:103:in `block (3 levels) in <module:Puppet>'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/property.rb:487:in `set'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/property.rb:561:in `sync'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type/service.rb:114:in `sync'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:236:in `sync'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:134:in `sync_if_needed'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:80:in `perform_changes'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:21:in `evaluate'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:233:in `apply'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:249:in `eval_resource'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:163:in `call'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:163:in `block (2 levels) in evaluate'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:507:in `block in thinmark'
- /opt/puppetlabs/puppet/lib/ruby/2.1.0/benchmark.rb:294:in `realtime'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:506:in `thinmark'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:163:in `block in evaluate'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:118:in `traverse'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:154:in `evaluate'
- /usr/share/gems/gems/kafo-2.1.0/modules/kafo_configure/lib/puppet/parser/functions/add_progress.rb:30:in `evaluate_with_trigger'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:222:in `block in apply'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/log.rb:155:in `with_destination'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/report.rb:146:in `as_logging_destination'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:221:in `apply'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:171:in `block in apply_catalog'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:224:in `block in benchmark'
- /opt/puppetlabs/puppet/lib/ruby/2.1.0/benchmark.rb:294:in `realtime'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:223:in `benchmark'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:170:in `apply_catalog'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:343:in `run_internal'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:221:in `block in run'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/context.rb:65:in `override'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:306:in `override'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:195:in `run'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/apply.rb:348:in `apply_catalog'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/apply.rb:274:in `block in main'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/context.rb:65:in `override'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:306:in `override'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/apply.rb:225:in `main'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/apply.rb:170:in `run_command'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:375:in `block in run'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:662:in `exit_on_fail'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:375:in `run'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:132:in `run'
- /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute'
- /opt/puppetlabs/puppet/bin/puppet:5:in `<main>'
- /Stage[main]/Foreman_proxy::Service/Service[foreman-proxy]/ensure: change from stopped to running failed: Systemd start for foreman-proxy failed!
- journalctl log for foreman-proxy:
- -- Logs begin at Tue 2019-03-12 11:38:52 CET, end at Tue 2019-03-12 11:41:18 CET. --
- Mar 12 11:39:03 host.domain01.domaincorp.lan systemd[1]: Starting Foreman Proxy...
- Mar 12 11:39:13 host.domain01.domaincorp.lan smart-proxy[7304]: Errors detected on startup, see log for details. Exiting: uninitialized constant Dynflow
- Mar 12 11:39:13 host.domain01.domaincorp.lan systemd[1]: foreman-proxy.service: main process exited, code=exited, status=1/FAILURE
- Mar 12 11:39:13 host.domain01.domaincorp.lan systemd[1]: Failed to start Foreman Proxy.
- Mar 12 11:39:13 host.domain01.domaincorp.lan systemd[1]: Unit foreman-proxy.service entered failed state.
- Mar 12 11:39:13 host.domain01.domaincorp.lan systemd[1]: foreman-proxy.service failed.
- Mar 12 11:41:17 host.domain01.domaincorp.lan systemd[1]: Starting Foreman Proxy...
- Mar 12 11:41:18 host.domain01.domaincorp.lan smart-proxy[10472]: Errors detected on startup, see log for details. Exiting: uninitialized constant Dynflow
- Mar 12 11:41:18 host.domain01.domaincorp.lan systemd[1]: foreman-proxy.service: main process exited, code=exited, status=1/FAILURE
- Mar 12 11:41:18 host.domain01.domaincorp.lan systemd[1]: Failed to start Foreman Proxy.
- Mar 12 11:41:18 host.domain01.domaincorp.lan systemd[1]: Unit foreman-proxy.service entered failed state.
- Mar 12 11:41:18 host.domain01.domaincorp.lan systemd[1]: foreman-proxy.service failed.
- Installing Done [100%] [..........................................................................................................................................................]
- Something went wrong! Check the log for ERROR-level output
- The full log is at /var/log/foreman-installer/katello.log
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement