Comment 10 for bug 703993

No it doesn't, there should be further logs indicating that rsyslog
actually responded to the signal, shut down and exited - or if not,
15s, Upstart followed up with SIGKILL

On Tue, Jan 25, 2011 at 5:02 PM, Clint Byrum <email address hidden> wrote:
> robs, it makes sense that all logs would stop when rsyslog was killed..
> so maybe thats not what does it.
>
> Maybe add a task
>
> # rsyslog-stopped
> start on stopped rsyslog
> task
>
> script
>  initctl list > /list.after.rsyslog.stopped
> end script
>
>
> That should record that rsyslog actually stopped. Maybe also there is more information on the console. I'm not sure how to get to the console on linux v-server but it may offer some clues since you're running in debug mode.
>
> --
> You received this bug notification because you are a member of Upstart
> Developers, which is subscribed to upstart .
> https://bugs.launchpad.net/bugs/703993
>
> Title:
>  start and stop hang when run inside a 10.04 Vserver guest
>
> Status in Upstart:
>  New
>
> Bug description:
>  I configured a host machine with Ubuntu Lucid 10.04 amd64, then I
>  installed:
>
>  ii  linux-headers-2.6.32-27-vserver   2.6.32-27.49~ppa3
>  ii  linux-headers-vserver                    2.6.32.27.29~ppa1
>  ii  linux-image-2.6.32-27-vserver      2.6.32-27.49~ppa3
>  ii  linux-image-vserver                      2.6.32.27.29~ppa1
>  ii  util-vserver                                    0.30.216~r2842-2ubuntu2
>
>  I followed http://linux-vserver.org/Upstart_issues to successfully build a guest system.
>  The guest boots and halt fine, but if the stop and start commands are executed from the console, they simply hang.
>
>  This doesn't allow apt-get upgrades to run smoothly, as post-inst
>  scripts often call restart "servicename"
>
>  I attach the Upstart debug I get from stop dbus .. seems fine to me ? :
>  init: Connection from private client
>  init: job_class_register: Registered job /com/ubuntu/Upstart/jobs/rc
>  init: job_class_register: Registered job /com/ubuntu/Upstart/jobs/screen_2dcleanup
>  init: job_class_register: Registered job /com/ubuntu/Upstart/jobs/dbus
>  init: job_register: Registered instance /com/ubuntu/Upstart/jobs/dbus/_
>  init: job_class_register: Registered job /com/ubuntu/Upstart/jobs/ssh
>  init: job_register: Registered instance /com/ubuntu/Upstart/jobs/ssh/_
>  init: job_class_register: Registered job /com/ubuntu/Upstart/jobs/control_2dalt_2ddelete
>  init: job_class_register: Registered job /com/ubuntu/Upstart/jobs/vserver
>  init: job_class_register: Registered job /com/ubuntu/Upstart/jobs/mounted_2dvarrun
>  init: job_class_register: Registered job /com/ubuntu/Upstart/jobs/rc_2dsysinit
>  init: job_class_register: Registered job /com/ubuntu/Upstart/jobs/mounted_2ddev
>  init: job_class_register: Registered job /com/ubuntu/Upstart/jobs/mysql
>  init: job_register: Registered instance /com/ubuntu/Upstart/jobs/mysql/_
>  init: job_class_register: Registered job /com/ubuntu/Upstart/jobs/mounted_2dtmp
>  init: dbus goal changed from start to stop
>  init: dbus state changed from running to pre-stop
>  init: dbus state changed from pre-stop to stopping
>  init: event_new: Pending stopping event
>  init: Handling stopping event
>  init: event_finished: Finished stopping event
>  init: dbus state changed from stopping to killed
>  init: Sending TERM signal to dbus main process (16657)
>  init: Disconnected from system bus
>  init: Sending KILL signal to dbus main process (16657)
>
>  A similar problem (the same ?) is reported here:
>  http://www.freak-search.com/de/thread/2643371/vserver_problems_installing_ubuntu_10.10_as_a_guest_of_a_debian_host
>
>
>  Thanks,
>  Roberto Sebastiano
>
>
>