Arch Linux

Weegee

Member

Registered: 2010-08-06

Posts: 62

[✓] udev upgrade and unclean shutdown: gdm and syslog-ng won't start

After running a udev upgrade (161-1 → 161-2) I had to reset my PC because VirtualBox caused a full system freeze (even rebooting using the SysRq key didn't work). So the system started to boot, and the first error message I got was that /sbin/syslog-ng couldn't start due to a bus error, though other daemons were able to start without any problems. The next error message I received was init: Id "x" respawning too fast: disabled for 5 minutes. which obviously came from GDM (which gets started by using /etc/inittab). However I was still able to login, start the xserver via startx and execute gnome-session.

Up to now, everything works as usual. Programs start und run flawlessly, there are no error messages or anything related. So it seems like only GDM and syslog-ng were affected by the upgrade/unclean shutdown. I've already tried to downgrade udev, reinstall the upgrade, reinstall gdm and syslog-ng, run a file system check (via shutdown -rF) - nothing has changed. I've also checked the log files within /var/log, but I haven't found any file containing a warning about a bus error (except some files which are about 2 or 3 days old).

I have no idea what I should do now. Another option would be to reinstall Arch Linux - which is what I don't really want to do.

Last edited by Weegee (2010-09-01 13:41:15)

---

~

vacant

Member

From: downstairs

Registered: 2004-11-05

Posts: 816

Re: [✓] udev upgrade and unclean shutdown: gdm and syslog-ng won't start

I had a problem this morning which I suspect may be udev related.

Stuck a sata hard drive into a USB port to do my monthly backup and nada, zilch.  I saw the light on the caddy flicker from green (idle) to amber and back to green but nothing in dmesg and nothing in messages.log. No /dev/sdbX created.

I restarted hal and dbus, unplugged the caddy but got nothing until I typed "udevadm trigger" as root, then all was fine. On reboot it recognised the drive.

I'm still not sure if it was that command that fixed it. Did the trigger rewrite some database?

Weegee

Member

Registered: 2010-08-06

Posts: 62

Re: [✓] udev upgrade and unclean shutdown: gdm and syslog-ng won't start

I really don't know why, but GDM started to work again after I compiled and reinstallied it (I wanted to create a full backtrace via gdb, so I had to recompile GDM with --enable-debug). Now I'll also compile and reinstall the syslog-ng package.

... strange

---

~