Your message dated Mon, 11 Jan 2016 05:26:57 +0000 with message-id <[email protected]> and subject line Bug#808289: Removed package(s) from unstable has caused the Debian Bug report #582745, regarding upstart: Upstart jobs get stuck when "expect daemon" or "expect fork" is wrong. to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 582745: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582745 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: upstart Version: 0.6.3-1 Severity: normal While trying to write some upstart /etc/init .conf files, I noticed that if I got the "expect daemon/fork" line incorrect then init would get in a messed up state, causing any subsequent "initctl start" or "initctl stop" commands to hang on the .conf file in question, even after the bug was fixed. The only solution I could find was to rename the script. I suspect rebooting would work to but I'm in a position to reboot right now. Clearly it was my fault that I got the "expect" line wrong, but even so I don't think upstart should hang when talking about that job for then on. There needs to be some way to reset it or not let it get in that state at all. Here's a small test case I made. I was unable to get it to hang with just an "exec" line. I had to put it in a "script" and then call an external program. cat > fail.conf <<EOF expect fork script /bin/true sleep 10& end script EOF If I try to start the job now it prints a PID that doesn't match up with the correct PID. On my system I got: # initctl start fail fail start/running, process 20121 # ps aux | grep sleep root 20122 0.0 0.0 3804 480 ? S 03:07 0:00 sleep 10 At this point any attempt to "initctl stop fail" will hang. If I Control-C a hung "stop" and try again it will say it's already stopped, but the state doesn't show up correctly: # initctl status fail fail stop/killed, process 20121 Attempting to start it again also hangs. I couldn't find any way out of this state except to reboot, or rename the fail.conf file to fail1.conf and continue testing under that name. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.33-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages upstart depends on: ii initscripts 2.87dsf-10 scripts for initializing and shutt ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib ii libdbus-1-3 1.2.24-1 simple interprocess messaging syst ii sysv-rc 2.87dsf-10 System-V-like runlevel change mech ii sysvinit-utils 2.87dsf-10 System-V-like utilities upstart recommends no packages. upstart suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Version: 1.11-5+rm Dear submitter, as the package upstart has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/808289 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
