Re: [gentoo-user] Init Scripts Not Starting
On Wed, Jan 04, 2012 at 07:10:07PM -0800, Dan Cowsill wrote: On Wed, Jan 4, 2012 at 8:53 AM, Neil Bothwick n...@digimed.co.uk wrote: On Wed, 4 Jan 2012 06:53:18 -0800, Dan Cowsill wrote: Running rc or rc default returns immediately. I am sure I am starting into the default runlevel because ntp-client runs on default and it starts no problem. Have you enabled logging in rc.conf? What does /var/log/rc.log show? I have indeed. The logs show that everything but xdm and virtualbox-guest-additions start normally. The logs do not show any attempt to start either of those. It seems this system is full of lies. Did you check the file permissions on those scripts? I have. Permissions in the /etc/init.d folder are consistent across the board. If anything else, you can try running 'strace -e trace=file' on rc-status and rc-update show and might notice something there that would explain while those two tools come up with different sets of scripts... I've attached the strace results from rc-status, rc-update show and rc itself. If you guys can make any sense of them, I'd be grateful. Seems that rc-status sees the xdm initscript... but why doesn't it show it then... no idea... My advice would be to submit a bug, the inconsistent output from rc-status vs rc-update is suspicious enough... You might also try to re-emerge the packages that installs /etc/init.d/xdm to see if that doesn't help... (should be x11-base/xorg-server) yoyo
Re: [gentoo-user] Init Scripts Not Starting
On Jan 4, 2012 9:56 PM, Dan Cowsill danthe...@gmail.com wrote: On Wed, Jan 4, 2012 at 3:17 AM, YoYo Siska y...@gl.ksp.sk wrote: On Tue, Jan 03, 2012 at 08:31:08PM -0800, Dan Cowsill wrote: Hey list, A little while after I compiled Gnome and got things running, I lost the ability to add scripts to the default runlevel. I can run rc-update add xdm default, for example, and the xdm symlink will appear in /etc/runlevels/default, and that symlink will indeed point to /etc/init.d/xdm, but xdm will not start. Further to that, there's no evidence to indicate that RC is even trying to start it. No errors, no logs, no nothing. Same goes for virtualbox-guest-additions and sysklogd. I tried logging rc and got absolutely nowhere. There's nothing overt in dmesg either. The really fun part is these scripts function perfectly if I run them after boot. Since there's no evidence of this problem in any logs or during the startup process, I assume there is no problem and I am doing it wrong. Is it possible that you are booting into a different runlevel that default ? (there's a softlevel=... kernel cmdline parameter) What happens if (after boot) you just run rc (should start all service in the current runlevel, that are not started yet) or rc default (should swithc to 'default' runlevel and start all services) ? Could you post the output of rc-status -a ? And maybe also grep rc /etc/inittab ? For xdm there is one additional thing to check: xdm can be disabled through a 'nox' kernel cmdline option or an /etc/.noxdm file... But in that case the initscript itself should start and just print a message, that it is not starting the DM. yoyo Hey, thanks for the reply. Running rc or rc default returns immediately. I am sure I am starting into the default runlevel because ntp-client runs on default and it starts no problem. Output from grep rc /etc/inittab: si::sysinit:/sbin/rc sysinit rc::bootwait:/sbin/rc boot l0:0:wait:/sbin/rc shutdown l1:1:wait:/sbin/rc single l2:2:wait:/sbin/rc nonetwork l3:3:wait:/sbin/rc default l4:4:wait:/sbin/rc default l5:5:wait:/sbin/rc default l6:6:wait:/sbin/rc reboot su0:S:wait:/sbin/rc single Output from rc-status -a: Runlevel: default net.eth1 [ started ] dbus [ started ] net.eth0 [ started ] netmount [ started ] ntp-client[ started ] sshd [ started ] udev-postmount[ started ] local [ started ] Runlevel: sysinit dmesg [ started ] udev [ started ] devfs [ started ] Runlevel: boot hwclock [ started ] modules [ started ] fsck [ started ] root [ started ] mtab [ started ] localmount[ started ] sysctl[ started ] bootmisc [ started ] urandom [ started ] net.lo[ started ] termencoding [ started ] swap [ started ] keymaps [ started ] hostname [ started ] procfs[ started ] Runlevel: shutdown killprocs [ stopped ] savecache [ stopped ] mount-ro [ stopped ] Dynamic Runlevel: hotplugged Dynamic Runlevel: needed sysfs [ started ] Dynamic Runlevel: manual Output from rc-update show: bootmisc | boot dbus | default devfs |
Re: [gentoo-user] Init Scripts Not Starting
On Jan 6, 2012 2:09 AM, Pandu Poluan pa...@poluan.info wrote: On Jan 4, 2012 9:56 PM, Dan Cowsill danthe...@gmail.com wrote: - 8 snippage That's strange... it looks as if the /etc seen by rc during boot is different from the /etc seen after entering runlevel default... Try bind mounting root separately, e. g. : mkdir -p /mnt/root mount -o bind / /mnt/root then compare the relevant subdirectories under /etc and /mnt/root/etc Rgds,
Re: [gentoo-user] Init Scripts Not Starting
On Tue, Jan 03, 2012 at 08:31:08PM -0800, Dan Cowsill wrote: Hey list, A little while after I compiled Gnome and got things running, I lost the ability to add scripts to the default runlevel. I can run rc-update add xdm default, for example, and the xdm symlink will appear in /etc/runlevels/default, and that symlink will indeed point to /etc/init.d/xdm, but xdm will not start. Further to that, there's no evidence to indicate that RC is even trying to start it. No errors, no logs, no nothing. Same goes for virtualbox-guest-additions and sysklogd. I tried logging rc and got absolutely nowhere. There's nothing overt in dmesg either. The really fun part is these scripts function perfectly if I run them after boot. Since there's no evidence of this problem in any logs or during the startup process, I assume there is no problem and I am doing it wrong. Is it possible that you are booting into a different runlevel that default ? (there's a softlevel=... kernel cmdline parameter) What happens if (after boot) you just run rc (should start all service in the current runlevel, that are not started yet) or rc default (should swithc to 'default' runlevel and start all services) ? Could you post the output of rc-status -a ? And maybe also grep rc /etc/inittab ? For xdm there is one additional thing to check: xdm can be disabled through a 'nox' kernel cmdline option or an /etc/.noxdm file... But in that case the initscript itself should start and just print a message, that it is not starting the DM. yoyo
Re: [gentoo-user] Init Scripts Not Starting
On Wed, Jan 4, 2012 at 3:17 AM, YoYo Siska y...@gl.ksp.sk wrote: On Tue, Jan 03, 2012 at 08:31:08PM -0800, Dan Cowsill wrote: Hey list, A little while after I compiled Gnome and got things running, I lost the ability to add scripts to the default runlevel. I can run rc-update add xdm default, for example, and the xdm symlink will appear in /etc/runlevels/default, and that symlink will indeed point to /etc/init.d/xdm, but xdm will not start. Further to that, there's no evidence to indicate that RC is even trying to start it. No errors, no logs, no nothing. Same goes for virtualbox-guest-additions and sysklogd. I tried logging rc and got absolutely nowhere. There's nothing overt in dmesg either. The really fun part is these scripts function perfectly if I run them after boot. Since there's no evidence of this problem in any logs or during the startup process, I assume there is no problem and I am doing it wrong. Is it possible that you are booting into a different runlevel that default ? (there's a softlevel=... kernel cmdline parameter) What happens if (after boot) you just run rc (should start all service in the current runlevel, that are not started yet) or rc default (should swithc to 'default' runlevel and start all services) ? Could you post the output of rc-status -a ? And maybe also grep rc /etc/inittab ? For xdm there is one additional thing to check: xdm can be disabled through a 'nox' kernel cmdline option or an /etc/.noxdm file... But in that case the initscript itself should start and just print a message, that it is not starting the DM. yoyo Hey, thanks for the reply. Running rc or rc default returns immediately. I am sure I am starting into the default runlevel because ntp-client runs on default and it starts no problem. Output from grep rc /etc/inittab: si::sysinit:/sbin/rc sysinit rc::bootwait:/sbin/rc boot l0:0:wait:/sbin/rc shutdown l1:1:wait:/sbin/rc single l2:2:wait:/sbin/rc nonetwork l3:3:wait:/sbin/rc default l4:4:wait:/sbin/rc default l5:5:wait:/sbin/rc default l6:6:wait:/sbin/rc reboot su0:S:wait:/sbin/rc single Output from rc-status -a: Runlevel: default net.eth1 [ started ] dbus [ started ] net.eth0 [ started ] netmount [ started ] ntp-client[ started ] sshd [ started ] udev-postmount[ started ] local [ started ] Runlevel: sysinit dmesg [ started ] udev [ started ] devfs [ started ] Runlevel: boot hwclock [ started ] modules [ started ] fsck [ started ] root [ started ] mtab [ started ] localmount[ started ] sysctl[ started ] bootmisc [ started ] urandom [ started ] net.lo[ started ] termencoding [ started ] swap [ started ] keymaps [ started ] hostname [ started ] procfs[ started ] Runlevel: shutdown killprocs [ stopped ] savecache [ stopped ] mount-ro [ stopped ] Dynamic Runlevel: hotplugged Dynamic Runlevel: needed sysfs [ started ] Dynamic Runlevel: manual Output from rc-update show: bootmisc | boot dbus | default devfs | sysinit dmesg | sysinit fsck | boot
Re: [gentoo-user] Init Scripts Not Starting
On Wed, 4 Jan 2012 06:53:18 -0800, Dan Cowsill wrote: Running rc or rc default returns immediately. I am sure I am starting into the default runlevel because ntp-client runs on default and it starts no problem. Have you enabled logging in rc.conf? What does /var/log/rc.log show? -- Neil Bothwick Eat shit - 50 million flies can't be wrong Use Microsoft . . . . . signature.asc Description: PGP signature
Re: [gentoo-user] Init Scripts Not Starting
On Wed, Jan 04, 2012 at 06:53:18AM -0800, Dan Cowsill wrote: On Wed, Jan 4, 2012 at 3:17 AM, YoYo Siska y...@gl.ksp.sk wrote: On Tue, Jan 03, 2012 at 08:31:08PM -0800, Dan Cowsill wrote: Hey list, A little while after I compiled Gnome and got things running, I lost the ability to add scripts to the default runlevel. I can run rc-update add xdm default, for example, and the xdm symlink will appear in /etc/runlevels/default, and that symlink will indeed point to /etc/init.d/xdm, but xdm will not start. Further to that, there's no evidence to indicate that RC is even trying to start it. No errors, no logs, no nothing. Same goes for virtualbox-guest-additions and sysklogd. I tried logging rc and got absolutely nowhere. There's nothing overt in dmesg either. The really fun part is these scripts function perfectly if I run them after boot. Since there's no evidence of this problem in any logs or during the startup process, I assume there is no problem and I am doing it wrong. Is it possible that you are booting into a different runlevel that default ? (there's a softlevel=... kernel cmdline parameter) What happens if (after boot) you just run rc (should start all service in the current runlevel, that are not started yet) or rc default (should swithc to 'default' runlevel and start all services) ? Could you post the output of rc-status -a ? And maybe also grep rc /etc/inittab ? For xdm there is one additional thing to check: xdm can be disabled through a 'nox' kernel cmdline option or an /etc/.noxdm file... But in that case the initscript itself should start and just print a message, that it is not starting the DM. yoyo Hey, thanks for the reply. Running rc or rc default returns immediately. I am sure I am starting into the default runlevel because ntp-client runs on default and it starts no problem. Hmm, the weird thing is that 'rc-status -a' and 'rc-update show' show different things (no xdm and virtualbox-... in the first one) but I have no idea what might be causing that... Few random thoughts: Did you check the file permissions on those scripts? Any pending etc-update stuff (esp. in /etc/init.d) ? (not that it should affect this in any way...) If anything else, you can try running 'strace -e trace=file' on rc-status and rc-update show and might notice something there that would explain while those two tools come up with different sets of scripts... You can also look around the dirs/files in /lib/rc/init.d/ to se a more complete state of the rc system... (/lib/rc/init.d/softlevel should show the current runlevel) yoyo Output from grep rc /etc/inittab: si::sysinit:/sbin/rc sysinit rc::bootwait:/sbin/rc boot l0:0:wait:/sbin/rc shutdown l1:1:wait:/sbin/rc single l2:2:wait:/sbin/rc nonetwork l3:3:wait:/sbin/rc default l4:4:wait:/sbin/rc default l5:5:wait:/sbin/rc default l6:6:wait:/sbin/rc reboot su0:S:wait:/sbin/rc single Output from rc-status -a: Runlevel: default net.eth1 [ started ] dbus [ started ] net.eth0 [ started ] netmount [ started ] ntp-client[ started ] sshd [ started ] udev-postmount[ started ] local [ started ] Runlevel: sysinit dmesg [ started ] udev [ started ] devfs [ started ] Runlevel: boot hwclock [ started ] modules [ started ] fsck [ started ] root [ started ] mtab [ started ] localmount[ started ] sysctl[ started ] bootmisc [ started ] urandom [ started ] net.lo[ started ] termencoding [ started ] swap [
