Issues Installing Satellite 6 BETA 2 installation issue
Getting the following during installation
this might be the root cause
Jun 16 14:43:21 satellite-name systemd[1]: Starting Pulp Celery Workers...
-- Subject: Unit pulp_workers.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit pulp_workers.service has begun starting up.
Jun 16 14:43:21 satellite-name systemd[18716]: Failed at step CHDIR spawning /usr/bin/python: No such file or directory
-- Subject: Process /usr/bin/python could not be executed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- The process /usr/bin/python could not be executed and failed.
Installing Notice: /Stage[main]/Candlepin::Service/Service[to [99%] [.......................................................................... ]
Could not start Service[pulp_workers]: Execution of '/usr/share/katello-installer-base/modules/service_wait/bin/service-wait start pulp_workers' returned 1: Redirecting to /bin/systemctl start pulp_workers.service
/Stage[main]/Pulp::Service/Service[pulp_workers]/ensure: change from stopped to running failed: Could not start Service[pulp_workers]: Execution of '/usr/share/katello-installer-base/modules/service_wait/bin/service-wait start pulp_workers' returned 1: Redirecting to /bin/systemctl start pulp_workers.service
/Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]: Failed to call refresh: /usr/sbin/foreman-rake db:seed returned 1 instead of one of [0]
/Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]: /usr/sbin/foreman-rake db:seed returned 1 instead of one of [0]
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[satellite-name]: Failed to call refresh: Proxy satellite-name cannot be registered (Could not load data from https://satellite-name
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[satellite-name]: Proxy satellite-name cannot be registered (Could not load data from https://satellite-name
Installing Done [100%] [..........................................................................]
Something went wrong! Check the log for ERROR-level output
The full log is at /var/log/foreman-installer/satellite.log
Responses
Expert
929 points
Oh this won't be pretty. Rebooted the server and executed the installer script and it went through the installation fine.
Not a warm fuzzy feeling there.
Red Hat
Active Contributor
191 points
Will, Can we a foreman-debug archive mailed to satellite6-beta@redhat.com so we can diagnose further?
Expert
929 points
Hey Mike So I'm installing Satellite 6.2 GA and I got the same thing (felt like bad dejavu) ; run the installer, get the error same as above (can't find /usr/bin/python) Reboot the server and re-execute the install script and all goes through as planned.
I can reproduce this anytime by reverting to the snapshot from my base build and executing the installation script..
Installation goes basically like this: Build from Kickstart (I can provide to you in private)
- Register system to Red Hat
subscription-manager register
- List Subscriptions
subscription-manager list --available --all
- Attach a subscription
subscription-manager subscribe --pool=#Satellite Pool ID
subscription-manager subscribe --pool=#Red_Hat_Enterprise_Linux_Pool_Id
subscription-manager subscribe --pool=#Red_Hat_Enterprise_Linux_Software_Collections_Pool_Id
- Disable existing repos
subscription-manager repos --disable "*"
- Enable the Satellite and RHEL repos
subscription-manager repos --enable rhel-7-server-rpms --enable rhel-server-rhscl-7-rpms --enable rhel-7-server-optional-rpms
subscription-manager repos --enable rhel-7-server-satellite-6.2-rpms
- Update any installed packages on the system and reboot
yum -y update && systemctl restart
- Install satellite
yum install satellite
- Install Satellite
satellite-installer --scenario satellite\
--foreman-initial-organization "Enterprise_Unix_Engineering" \
--foreman-initial-location "viennaLab" \
--foreman-admin-username <user>\
--foreman-admin-password <password>\
--certs-server-cert "/root/ssl-temp/<certfile>"\
--certs-server-cert-req "/root/ssl-temp/<csr>"\
--certs-server-key "/root/ssl-temp/<key>"\
--certs-server-ca-cert "/root/ssl-temp/<rootca>"\
--foreman-proxy-dns false \
--foreman-proxy-dhcp false \
--foreman-proxy-tftp false
Community Member
26 points
I have the same problem, please help resolve. Thanks.
Logs: [31m Could not start Service[foreman-proxy]: Execution of '/usr/share/katello-installer-base/modules/service_wait/bin/service-wait start foreman-proxy' returned 1: Redirecting to /bin/systemctl start foreman-proxy.service [0mError: Could not start Service[foreman-proxy]: Exe: 765/766, 99%, 0.0/s, elapsed: 00:18:39 [31m /Stage[main]/Foreman_proxy::Service/Service[foreman-proxy]/ensure: change from stopped to running failed: Could not start Service[foreman-proxy]: Execution of '/usr/share/katello-installer-base/modules/service_wait/bin/service-wait start foreman-proxy' returned 1: Redirecting to /bin/systemctl start foreman-proxy.service [0mCould not load : no implicit conversion of nil int: 765/766, 99%, 0.0/s, elapsed: 00:19:08 [31m /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[ipas-pvm-112-077.purescale.raleigh.ibm.com]: Failed to call refresh: Proxy ipas-pvm-112-077.purescale.raleigh.ibm.com cannot be registered (ApipieBindings::MissingArgumentsError: id): N/A [0m[31m /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[ipas-pvm-112-077.purescale.raleigh.ibm.com]: Proxy ipas-pvm-112-077.purescale.raleigh.ibm.com cannot be registered (ApipieBindings::MissingArgumentsError: id): N/A [0m[32mDone [0m: 766/766, 100%, 0.0/s, elapsed: 00:19:12 [32mDone [0m: 766/766, 100%, 0.0/s, elapsed: 00:19:12 [1m[31mSomething went wrong![0m Check the log for ERROR-level output
Expert
929 points
I never did get a solution to this from Red Hat. This has happened since, but it was sporadic, and only happened when I was doing installs of Satellite. I finally had to move on. The solution in my case, was to patch the server, then reboot it before installing Satellite. The reboot being the key part here, which would be advisable for any Red Hat Application installation.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.