Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionPradeep Kumar Surisetty
2016-04-11 15:39:35 UTC
Description of problem:
To monitor few latest failures, archived all the data /var/log/* and restarted katello services. mongod, httpd, foreman-proxy fails to restart
[root@satserver log]# ls
old.tgz
[root@satserver log]# katello-service restart
---
<snip>
Redirecting to /bin/systemctl stop mongod.service
Success!
Redirecting to /bin/systemctl start mongod.service
Job for mongod.service failed because the control process exited with error code. See "systemctl status mongod.service" and "journalctl -xe" for details.
Redirecting to /bin/systemctl start postgresql.service
Redirecting to /bin/systemctl start qpidd.service
Redirecting to /bin/systemctl start qdrouterd.service
Redirecting to /bin/systemctl start tomcat.service
Redirecting to /bin/systemctl start foreman-proxy.service
Job for foreman-proxy.service failed because the control process exited with error code. See "systemctl status foreman-proxy.service" and "journalctl -xe" for details.
Redirecting to /bin/systemctl start pulp_celerybeat.service
Redirecting to /bin/systemctl start pulp_resource_manager.service
Redirecting to /bin/systemctl start pulp_workers.service
Redirecting to /bin/systemctl start httpd.service
Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details.
Redirecting to /bin/systemctl start foreman-tasks.service
Job for foreman-tasks.service failed because the control process exited with error code. See "systemctl status foreman-tasks.service" and "journalctl -xe" for details.
Some services failed to start: mongod,foreman-proxy,httpd,foreman-tasks
---
untarring this helps to restart again.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Archive /var/log/* data
[root@satserver log]# ls
old.tgz
2. restart katello services
katello-service restart
3. Some services failed to start: mongod,foreman-proxy,httpd,foreman-tasks
Actual results:
Few services fails to start
Expected results:
All services should start
Additional info:
Description of problem: To monitor few latest failures, archived all the data /var/log/* and restarted katello services. mongod, httpd, foreman-proxy fails to restart [root@satserver log]# ls old.tgz [root@satserver log]# katello-service restart --- <snip> Redirecting to /bin/systemctl stop mongod.service Success! Redirecting to /bin/systemctl start mongod.service Job for mongod.service failed because the control process exited with error code. See "systemctl status mongod.service" and "journalctl -xe" for details. Redirecting to /bin/systemctl start postgresql.service Redirecting to /bin/systemctl start qpidd.service Redirecting to /bin/systemctl start qdrouterd.service Redirecting to /bin/systemctl start tomcat.service Redirecting to /bin/systemctl start foreman-proxy.service Job for foreman-proxy.service failed because the control process exited with error code. See "systemctl status foreman-proxy.service" and "journalctl -xe" for details. Redirecting to /bin/systemctl start pulp_celerybeat.service Redirecting to /bin/systemctl start pulp_resource_manager.service Redirecting to /bin/systemctl start pulp_workers.service Redirecting to /bin/systemctl start httpd.service Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details. Redirecting to /bin/systemctl start foreman-tasks.service Job for foreman-tasks.service failed because the control process exited with error code. See "systemctl status foreman-tasks.service" and "journalctl -xe" for details. Some services failed to start: mongod,foreman-proxy,httpd,foreman-tasks --- untarring this helps to restart again. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Archive /var/log/* data [root@satserver log]# ls old.tgz 2. restart katello services katello-service restart 3. Some services failed to start: mongod,foreman-proxy,httpd,foreman-tasks Actual results: Few services fails to start Expected results: All services should start Additional info: