Suddenly start_daemon does not fork the new pid, hangs the script
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lsb (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: lsb
Suddenly software which uses start_daemon to launch a daemon process in the background caused an Ubuntu Server 8.10 not to completely reboot. The package that utilizes start_daemon is ooRexx: Open Object Rexx.
The startup script for the rxapid daemon does various checks to determine which way to launch the daemon. On 8.10, it selects start_daemon as that is available.
The script successfully launches the ooRexx rxapid daemon, as I can successfully interact with the daemon.
However, the script never ends, and that causes the server to never get to a login prompt on tty1.
I am successfully using /etc/rc.local to start rxapid, and have removed the service using: update-rc.d -f rxapid remove
This server used to boot normally. A kernel update caused me to need to reboot the server, thus I discovered this problem.
I was able to recreate this problem in a VirtualBox test environment.
Steps to recreate this situation:
1) Install Ubuntu Server 9.10 downloads. sourceforge. net/project/ oorexx/ oorexx/ 4.0.0/ooRexx- 4.0.0.i586. deb?use_ mirror= cdnetworks- us-1 4.0.0.i586. deb
2) Apply all available updates
3) Reboot
4) Add openssh-server
5) ssh to the VM test server
6) use wget to DL the latest ooRexx for Ubuntu:
wget http://
7) Install said package:
sudo dpkg -i ooRexx-
8) Reboot
9) The rxapid process never forks, system will not complete booting on tty1
I also opened a bug report about this at the ooRexx project site:
"rxapid service suddenly not forking on Ubuntu Server 9.10" /sourceforge. net/tracker/ ?func=detail& atid=684731& aid=2963828& group_id= 119701
https:/
As ooRexx 4.0 has been out for a while, it must be something in one of the latest Ubuntu updates as the package of ooRexx has not changed since it was last working correctly.