Upstart issues - Revision history

Jan.pekar at 10:29, 20 April 2015

2015-04-20T10:29:22Z

92.238.217.145: /* Running Ubuntu Lucid */ added note about making the postinit script executable

2012-10-30T19:01:10Z

‎Running Ubuntu Lucid: added note about making the postinit script executable

118.93.14.98: Remove broken links (use page history to recover if necessary)

2012-07-19T03:03:38Z

Remove broken links (use page history to recover if necessary)

118.93.14.98 at 02:55, 19 July 2012

2012-07-19T02:55:53Z

85.183.6.49: /* Remove console outputs */

2012-01-25T08:46:54Z

‎Remove console outputs

Glenn: +cat

2011-10-21T19:20:39Z

+cat

112.206.153.7: /* Running an upstart based guest */ fix mixup between guest and host

2011-05-05T12:13:55Z

‎Running an upstart based guest: fix mixup between guest and host

78.54.175.76: /* Notes for debugging */

2010-11-28T00:44:49Z

‎Notes for debugging

Jakobsg: /* Running Ubuntu Lucid */

2010-11-01T11:50:58Z

‎Running Ubuntu Lucid

Faxioman: /* Running Ubuntu Lucid */

2010-10-22T13:18:26Z

‎Running Ubuntu Lucid

@@ Line 47: / Line 47: @@
   tty6.conf
   upstart-udev-bridge.conf
 In Ubuntu 10.04 you also want to remove:
@@ Line 72: / Line 73: @@
          chown root:utmp /var/run/utmp
          chmod 664 /var/run/utmp
-         initctl emit virtual-filesystems
+         initctl emit --no-wait virtual-filesystems
-         initctl emit local-filesystems
+         initctl emit --no-wait local-filesystems
-         initctl emit remote-filesystems
+         initctl emit --no-wait remote-filesystems
-         initctl emit filesystem
+         initctl emit --no-wait filesystem
   end script

@@ Line 2: / Line 2: @@
 There's an inipost-file (http://capa-support.mikrov.dk/downloads/initpost) that can be used when creating hosts, so there's no need for manual tweaking.
-Put it in <code>/usr/lib/util-vserver/distributions/lucid</code>. Install the vserver with <code>--initstyle plain</code>.
+Put it in <code>/usr/lib/util-vserver/distributions/lucid</code> and make it executable. Install the vserver with <code>--initstyle plain</code>.
 You will still need to look over services when installing since we're tweaking Upstart's normal <code>emit</code> directives.

@@ Line 1: / Line 1: @@
 == Running Ubuntu Lucid ==
-There's an inipost-file (http://static.thedudes.org/initpost) that can be used when creating hosts, so there's no need for manual tweaking.
+There's an inipost-file (http://capa-support.mikrov.dk/downloads/initpost) that can be used when creating hosts, so there's no need for manual tweaking.
-Put it in <code>/usr/lib/util-vserver/distributions/lucid</code>. Install the vserver with <code>--initstyle plain</code>. You still need to look over services when installing since we're tweaking Upstarts normal emits.
+Put it in <code>/usr/lib/util-vserver/distributions/lucid</code>. Install the vserver with <code>--initstyle plain</code>.
-!! Note !! The inipost-file is missing. You can temporarily download it from: http://dl.dropbox.com/u/1171189/initpost
+You will still need to look over services when installing since we're tweaking Upstart's normal <code>emit</code> directives.
-−
-And more permanently here: http://capa-support.mikrov.dk/downloads/initpost
 You can also have a look at http://wiki.raceme.org/dokuwiki/tof:computer:vserver:upstart_ubuntu_lucid for a manual procedure.

@@ Line 1: / Line 1: @@
 == Running Ubuntu Lucid ==
-There's a inipost-file ( http://static.thedudes.org/initpost ) that can be used when creating hosts, so there's no need for manual tweaking.
+There's an inipost-file (http://static.thedudes.org/initpost) that can be used when creating hosts, so there's no need for manual tweaking.
-Put it in <pre>/usr/lib/util-vserver/distributions/lucid</pre> Install the vserver with --initstyle plain. You still need to look over services when installing since we're tweaking Upstarts normal emits.
+Put it in <code>/usr/lib/util-vserver/distributions/lucid</code>. Install the vserver with <code>--initstyle plain</code>. You still need to look over services when installing since we're tweaking Upstarts normal emits.
-!! Note !! The inipost-file is missing. You can temporarely download it from: http://dl.dropbox.com/u/1171189/initpost
+!! Note !! The inipost-file is missing. You can temporarily download it from: http://dl.dropbox.com/u/1171189/initpost
 And more permanently here: http://capa-support.mikrov.dk/downloads/initpost
@@ Line 12: / Line 12: @@
 == Running an upstart based guest ==
-currently upstart based guests need some manual tweaking to make them work inside a vserver host.
+Currently upstart based guests need some manual tweaking to make them work inside a vserver host.
 === Prepare the host ===
@@ Line 18: / Line 18: @@
   # echo plain > /etc/vservers/<vservername>/apps/init/style
-Or use '--initstyle plain' when creating the host.
+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
@@ Line 26: / Line 26: @@
 === 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 beeing able to open <code>/dev/console</code> or failing to start the udev system).
+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.
@@ Line 54: / Line 54: @@
 === Services you want to look over ===
-There are files in the /etc/init dir that you want to check the startup line of.
+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 happend since it is in a VServer and thus never start.
+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.
+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 doesn't start from scratch:
+Jobs that don't start from scratch:
   mysql-server-5.1 (mysql.conf)
@@ Line 80: / Line 80: @@
   end script
-The utmp stuff is needed if you mount <code>/var/run</code> as tmpfs and you don't create utmp anywhere else.
+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 ===
@@ Line 108: / Line 108: @@
 === 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:<br/>
+This depends on net-device-up IFACE=lo, remove this from the start line so that it reads:
-<code>start on filesystem</code>
+ start on filesystem
 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 --debug flag,
+First, you need to run Upstart with the <code>--debug</code> flag;
-one way of doing it is inserting
+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)
- "--debug"
+so it reads
-in INITCMD_START under the xplain-clause inside /usr/lib/util-vserver/vserver.functions (row 316 here)
+ INITCMD_START=( /sbin/init --debug )
-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
+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/*
@@ Line 128: / Line 128: @@
   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 a Upstart job you'll find on http://upstart.ubuntu.com/wiki/Debugging.
+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.
@@ Line 145: / Line 145: @@
 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 to be PID 1. It is linked against NPTL (in contrast to sysvinit), which has a bug in it's 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:
+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
@@ Line 172: / Line 172: @@
 === 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 same error that I did.
+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 following line in /etc/init/ssh.conf:
+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
-to
    # replaces SSHD_OOM_ADJUST in /etc/default/ssh
    #oom never

← Older revision		Revision as of 08:46, 25 January 2012
Line 101:		Line 101:

	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.		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 ===		=== Adapt /etc/init/rc-sysinit.conf inside the guest ===

← Older revision		Revision as of 19:20, 21 October 2011
Line 184:		Line 184:

	sudo aptitude install dbus		sudo aptitude install dbus
		+
		+	[[Category:Documentation]]

← Older revision		Revision as of 11:50, 1 November 2010
Line 5:		Line 5:

	!! Note !! The inipost-file is missing. You can temporarely download it from: http://dl.dropbox.com/u/1171189/initpost		!! Note !! The inipost-file is missing. You can temporarely download it from: http://dl.dropbox.com/u/1171189/initpost
		+
		+	And more permanently here: http://capa-support.mikrov.dk/downloads/initpost

	You can also have a look at http://wiki.raceme.org/dokuwiki/tof:computer:vserver:upstart_ubuntu_lucid for a manual procedure.		You can also have a look at http://wiki.raceme.org/dokuwiki/tof:computer:vserver:upstart_ubuntu_lucid for a manual procedure.