Editing
Upstart issues
(section)
From Linix VServer
Jump to navigation
Jump to search
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== Running an upstart based guest == Currently upstart based guests need some manual tweaking to make them work inside a vserver host. === Prepare the host === First of all you need to set the init style of your vserver to plain # echo plain > /etc/vservers/<vservername>/apps/init/style Or use <code>--initstyle plain</code> when creating the host. I'd also strongly recommend to mount <code>/var/run</code> and <code>/var/lock</code> of the guest as tmpfs. So add the following lines to <code>/etc/vservers/<vservername>/fstab</code> none /var/run tmpfs size=16m,nosuid,mode=0755 0 0 none /var/lock tmpfs size=16m,noexec,nosuid,nodev 0 0 === Remove low level services inside the guest === Then you need to get rid of anything in <code>/etc/init/</code> that tries to fiddle with your Server's Hardware or other low-level Stuff that's already handled by your host's kernel/system. Having one such scriptlet still enabled might cause the whole upstart system to fail (like not being able to open <code>/dev/console</code> or failing to start the udev system). Just remove these scriptlets, move them out of the way or rename them to something not ending in <code>.conf</code>. Be aware that upstart also parses subfolders of <code>/etc/init/</code> for <code>.conf</code> files. This is what I deleted on a basic Ubuntu 9.10 guest: dmesg.conf hostname.conf hwclock-save.conf hwclock.conf mountall-net.conf mountall-reboot.conf mountall-shell.conf mountall.conf network-interface.conf networking.conf procps.conf rsyslog-kmsg.conf tty1.conf tty2.conf tty3.conf tty4.conf tty5.conf tty6.conf upstart-udev-bridge.conf acpid.conf In Ubuntu 10.04 you also want to remove: console-setup.conf === Services you want to look over === There are files in the <code>/etc/init</code> dir that you want to check the startup line of. It could be waiting for something that will never happen in a VServer, and thus never start. For example mysql.conf needs a 'net-device-up'-emit also. By running vserver <name> exec initctl emit net-device-up it will come up like a charm. Either put this in vserver.conf or remove in from mysql.conf. Jobs that don't start from scratch: mysql-server-5.1 (mysql.conf) === Fake low level events inside the guest === Finally you need to fake emit the events that some of these scripts would do during regular boot. Probably the cleanest approach is to add a scriptlet <code>vserver.conf</code> to <code>/etc/init/</code> with this content: start on startup script touch /var/run/utmp chown root:utmp /var/run/utmp chmod 664 /var/run/utmp initctl emit --no-wait virtual-filesystems initctl emit --no-wait local-filesystems initctl emit --no-wait remote-filesystems initctl emit --no-wait filesystem initctl emit --no-wait static-network-up initctl emit --no-wait net-device-up end script The <code>utmp</code> stuff is needed if you mount <code>/var/run</code> as <code>tmpfs</code> and you don't create <code>utmp</code> anywhere else. === Remove console outputs === If your VServer hangs on the command vserver <name> stop and puts out A timeout occured while waiting for the vserver to finish and it will be killed by sending a SIGKILL signal. The following process list might be useful for finding out the reason of this behavior: ---------------------------------------------------------------------- <pid> <context> <name> ? Ss 0:00 /sbin/init <pid> <context> <name> ? Ss 0:00 /sbin/init ---------------------------------------------------------------------- you should run sed -i 's/^\(console output\)$/#\1/1' /etc/vservers/$name/vdir/etc/init/* which will disable all lines with 'console output', and Upstart won't try output to it. Which is a good thing since it doesn't exist. Another reason might be that you removed control-alt-delete.conf from /etc/init/ - which is used for a proper shutdown of the vserver: 20:00 <@Bertl> util-vserver does not execute stuff inside the guest, it simply sends a signal to init (inside the guest) 20:01 <@Bertl> (the singnal is SIGINT, and this equals to the CTRL-ALT-DEL action) === Adapt /etc/init/rc-sysinit.conf inside the guest === This depends on net-device-up IFACE=lo, remove this from the start line so that it reads: start on filesystem This scriptlet tries to parse <code>/proc/cmdline</code> which will not work and probably isn't needed inside a vserver. Simply comment out or delete the whole <code>for ARG in $(cat /proc/cmdline) do...done</code> loop. === Notes for debugging === First, you need to run Upstart with the <code>--debug</code> flag; one way of doing it is inserting <code>--debug</code> in <code>INITCMD_START</code> under the xplain-clause inside <code>/usr/lib/util-vserver/vserver.functions</code> (row 316 here) so it reads INITCMD_START=( /sbin/init --debug ) Second, you should enable console output in the rc-files inside /etc/init. If you had commented them out before, you could do sed -i 's/#^\(console output\)$/\1/1' /etc/vservers/$name/vdir/etc/init/* Third you need a device to act as console, I used tty0. cp -a /dev/tty0 /etc/vservers/$name/vdir/dev/console If you do things at a console of the machine it will now print out detailed information. More on how to debug an Upstart job you'll find on http://upstart.ubuntu.com/wiki/Debugging. Notice that if one fails they all fail. === Notes for older kernels === If you encounter upstart errors like this: $ vserver foo start init: missing runlevel Try `init --help' for more information. or $ vserver foo start telinit: Failed to connect to socket /com/ubuntu/upstart: Connection refused then you're probably running the current stable version <code>2.6.22.19-vs2.2.0.7</code>. Upstart's <code>/sbin/init</code> implementation requires it to be PID 1. It is linked against NPTL (in contrast to sysvinit), which has a bug in its caching <code>getpid(2)</code> wrapper. With this kernel version <code>getpid(2)</code> returns the cached PID to init, resulting in init replacing itself with telinit. You can fix this by upgrading to a <code>2.6.26+</code> kernel and a newer vserver patch, or by patching upstart: diff --git a/init/main.c b/init/main.c index bfcd528..c6c9304 100644 --- a/init/main.c +++ b/init/main.c @@ -37,6 +37,7 @@ #include <string.h> #include <syslog.h> #include <unistd.h> +#include <syscall.h> #include <linux/kd.h> @@ -131,7 +132,7 @@ main (int argc, } /* Check we're process #1 */ - if (getpid () > 1) { + if (syscall(SYS_getpid) > 1) { execv (TELINIT, argv); /* Ignore failure, probably just that telinit doesn't exist */ For more information see the man pages of <code>getpid(2)</code> (NOTES) and <code>clone(2)</code> (BUGS). === Init procedure doesn't complete === ==== SSH ==== If you've completed all above steps and some init scripts doesn't get invoked at all (most notably old SYSV init scripts) you might have encountered the same error that I did. In Lucid guest I had to comment out (or remove) the <code>oom never</code> line in <code>/etc/init/ssh.conf</code>: # replaces SSHD_OOM_ADJUST in /etc/default/ssh #oom never After commenting out this line initialization completed successfully. ==== D-BUS ==== When creating guest as chroot some packages you might expect are missing. One of these is D-BUS. Strangely enough the /etc/init/dbus.conf gets installed which prevents Upstart to finish its starting sequence. Solution: install dbus package sudo aptitude install dbus [[Category:Documentation]]
Summary:
Please note that all contributions to Linix VServer may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Linix VServer:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Navigation menu
Page actions
Page
Discussion
Read
Edit
History
Page actions
Page
Discussion
More
Tools
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
About
Overview
Paper
News
Developers
Donations
Search
Getting Started
Downloads
FAQs
Documentation
Support
Participate
How to participate
Report a Bug
Communicate
Teams/Projects
Hall of Fame
Resources
Archives
Recent Wiki Changes
Pastebin
Related Projects
VServer Hosting
Happy VServer Users
Tools
What links here
Related changes
Special pages
Page information