Regarding Saucy, it looks like a timing issue that make the problem
disapear as I'm able to reproduce the same problem on Debian/Sid.
Adding a debugging "lsof -i @127.0.0.1:8443" in /etc/init.d/stud in
do_start just prior to the start-stop-daemon shows :
# invoke-rc.d stud restart
* Restarting stud stud
[Stop: stud.conf] COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
stud 1851 _stud 3u IPv4 10480 0t0 TCP localhost:8445 (LISTEN)
stud 1852 _stud 3u IPv4 10480 0t0 TCP localhost:8445 (LISTEN)
stud 1853 _stud 3u IPv4 10480 0t0 TCP localhost:8445 (LISTEN)
stud 1854 _stud 3u IPv4 10480 0t0 TCP localhost:8445 (LISTEN)
[Started: stud.conf] ...done.
root@ubuntu:~/precise/stud-0.3# ps aux | grep stud
root 1888 0.0 0.0 8108 896 pts/1 S+ 09:45 0:00 grep
--color=auto stud
So my diagnostic is that stud's children are not yet terminated when
do_start runs, which leads to failure to start.
This should be caught by this test :
if ! start-stop-daemon --start --quiet --pidfile
$PIDFILE \
--exec $DAEMON --test ; then
echo -n "[Already running: ${BASE}] "
but for some reason, the use of --pidfile mask the presence of children.
I need to investigate this one further.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1123950
Title:
/etc/init.d/stud restart does not start the daemon
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/stud/+bug/1123950/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
