Project

General

Profile

Bug #20731

Yum update gone wrong - some services failed

Added by Kent Knudsen over 4 years ago. Updated almost 4 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Installer
Target version:
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Katello 3.3.2 / Foreman 1.14.2

Yesterday I performed a yum update on our katello box that completed OK. Today after even after a reboot I can't access the webpage.

Doing a 'katello-service status' I see some services are not started e.g. smart_proxy_dynflow_core and httpd. Output of command is attached.

Any chance of finding out why this happened and/or how to start the unstarted services?

/Thanks

service_status.txt service_status.txt 16.3 KB Kent Knudsen, 08/24/2017 09:30 AM

History

#1 Updated by Kent Knudsen over 4 years ago

  • Tracker changed from Support to Bug

#2 Updated by John Mitsch over 4 years ago

  • Status changed from New to Need more information

If you haven't already, can you run foreman-installer --upgrade?

#3 Updated by Kent Knudsen over 4 years ago

John Mitsch wrote:

If you haven't already, can you run foreman-installer --upgrade?

HI John,

I ran this a couple days ago and got an error than I can't remember today.

After a reboot yesterday I got the smart_proxy_dynflow_core service started but still not the httpd service.

Yesterday I found the solution for the unstartable httpd service on a Bugzilla page for Satellite 6.2 - https://bugzilla.redhat.com/show_bug.cgi?id=1336365#c10

Editing the /etc/httpd/conf/ports.conf by commenting out the "Listen 443" I was able to start the apache service.

After that I was able to complete the upgrade to Katello 3.4.5 / Foreman 1.15.3 and all services started correctly.

Don't know if above workaround should have been fixed, but apperently this is related to the Foreman bug: http://projects.theforeman.org/issues/16972

#4 Updated by Justin Sherrill over 4 years ago

  • Category set to Installer
  • Status changed from Need more information to Rejected
  • Legacy Backlogs Release (now unused) set to 166

We've not been able to reproduce this, going ahead and closing. If anyone else is seeing this or can provide some reproducer insight, please let us know.

Also available in: Atom PDF