Subject: Re: [vserver] Upstart advice for Ubuntu Precise
From: Herbert Poetzl <herbert@13thfloor.at>
Date: Thu, 9 May 2013 16:55:04 +0200

On Thu, May 09, 2013 at 09:15:49AM -0400, Phil Daws wrote:
> Hello all,

> am attempting to create a vserver guest, using Ubuntu Precise,
> but receiving a lot of errors surrounding upstart:

>  * Stopping domain name service... bind9 waiting for pid 16494
>  to die [ OK ]

> initctl: Unable to connect to Upstart: Failed to connect to
> socket /com/ubuntu/upstart: Connection refused
>  * Asking all remaining processes to terminate...                                
                                                                   [ OK ] 
> initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart:
Connection refused
> initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart:
Connection refused
>  * All processes ended within 1 seconds....                                      
                                                                   [ OK ] 
> initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart:
Connection refused
> initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart:
Connection refused
>  * Unmounting temporary filesystems...                                           
                                                                   [ OK ] 
>  * Deactivating swap...                                                          
                                                                          swapoff: Not
superuser.
>                                                                                  
                                                                   [fail]
this looks like upstart isn't running at all
(i.e. sysv init style)

> umount: /var/run: not mounted
> mount: permission denied
>  * Will now restart
> /usr/bin/find: `var/lock': No such file or directory
>  * Starting domain name service... bind9
>    ...done.
> 
> 
> I have followed the guide
> http://linux-vserver.org/Upstart_issues but that did not seem
> to resolve the issues; well it got rid of the error messages
> but then the bind9 service would not start. 

IIRC, the wiki suggests to switch to plain
init style, which means that upstart is now
started inside the guest (thus no messages
on startup/shutdown from the runlevel changes)
which also means, that upstart is supposed to
start whatever services you'd like to get
started, and you have to check the upstart
related log files for reasons why they aren't
started.

But if bind9 is all you want to run inside
your guest, I'd use the sysv runlevel script
for that and just get rid of all the upstart
related crap, e.g. by replacing the initctl
link with a link to /bin/true.

HTH,
Herbert

> I installed vserver from the repo psand and this is the current
> list of packages:

> ii  libvserver0                       0.30.216-pre3038-1                dynamic libraries
for util-vserver
> ii  linux-headers-vserver-3.2-beng    3.2.42-2.3.2.16+precise1          A metapackage
which installs the latest Linux-Vserver patched 3.2 linux-headers pa
> ii  linux-image-vserver-3.2-beng      3.2.42-2.3.2.16+precise1          A metapackage
which installs the latest Linux-Vserver patched 3.2 linux-image pack
> ii  util-vserver                      0.30.216-pre3038-1                utilities
for managing Linux-VServer guests
> ii  util-vserver-build                0.30.216-pre3038-1                tools which
can be used to build vservers
> ii  util-vserver-core                 0.30.216-pre3038-1                core utilities
of util-vserver
> ri  util-vserver-sysv                 0.30.216-pre3038-1                initscripts
for util-vserver

> Any help would be gratefully appreciated.

> Thank you.