Project

General

Profile

Bug #2152

foreman-proxy in foreground mode prevents server from booting

Added by Callum Scott over 6 years ago. Updated about 1 year ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Packaging
Target version:
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

Having ":daemon: false" set in /etc/foreman-proxy/settings.yaml prevents the server coming back up in the event of a reboot.

I was able to telnet to the server on port 8433 but as the smart-proxy starts before openssh I was unable to ssh onto the server.

I was unable to get to a command prompt on the console, and had to recover by booting into a live environment and mounting the HDD to edit the yaml file and daemonize the proxy.

If the the proxy is set not to daemonize then it shouldn't be started at boot time.


Related issues

Has duplicate Smart Proxy - Bug #2208: Init script hangs forever when daemonize is set to falseClosed2013-02-13

History

#1 Updated by Dominic Cleal over 6 years ago

  • Project changed from Foreman to Smart Proxy

#2 Updated by Greg Sutcliffe over 6 years ago

This is a packaging problem - the proxy can't tell if it's a boot-start or not, so it needs to be handled in the initscripts. The Sys-V init scripts would be easy enough to alter, but the Systemd ones might be harder, as they don't contain the same arbitrary logic.

#3 Updated by Greg Sutcliffe over 6 years ago

  • Category set to Packaging
  • Assignee set to Greg Sutcliffe

#4 Updated by Dominic Cleal over 6 years ago

  • Status changed from New to Ready For Testing
  • Assignee changed from Greg Sutcliffe to Dominic Cleal
  • Target version set to 26

#5 Updated by Dominic Cleal over 6 years ago

  • Status changed from Ready For Testing to Resolved

merged

#6 Updated by Dominic Cleal over 6 years ago

  • Target version changed from 26 to 1.2.0

#7 Updated by Greg Sutcliffe about 1 year ago

  • Target version deleted (1.2.0)

Also available in: Atom PDF