https://bugzilla.novell.com/show_bug.cgi?id=680332 https://bugzilla.novell.com/show_bug.cgi?id=680332#c0 Summary: blogd crashes on boot and "kills" the runlevel initialisation Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: colAflash@gmx.net QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b12) Gecko/20110222 Firefox/4.0b12 After updating to 11.4 (x86_64 - from 11.3) on a AMD Phenom II pc I got this error at the end of the boot-log: blogd:Can not read from fd 0: Input/output error Seems like blogd crashes. And by doing this, it stops the system from entering the correct runlevel. "fd 0" seems to be the filehandle 0. But I'm not shure that this is the meaning of "fd 0". There are no messages about the services that should be startet in that runlevel. And for example the X-Server doesn't comes up in runlevel 5 (so no XDM, KDM or XOrg shows up). If I log in after boot-up, and type "runlevel" it tells "N 5". For debugging, I put some code into /etc/init.d/boot.local, which checked the filehandles of blogd. The result: ls -lA /proc/`pidof blogd`/fd/ total 0 lrwx------ 1 root root 64 Mar 16 23:34 0 -> /dev/ptmx l-wx------ 1 root root 64 Mar 16 23:34 1 -> /dev/tty1 l-wx------ 1 root root 64 Mar 16 23:34 2 -> /dev/tty1 lrwx------ 1 root root 64 Mar 16 23:34 3 -> /dev/blog l-wx------ 1 root root 64 Mar 16 23:34 4 -> /var/log/boot.msg The permissions of /dev/ptmx are: crw-rw-rw- 1 root tty 5, 2 17. Mär 00:07 /dev/ptmx Renaming /sbin/blogd to /sbin/blogd.disable seems to be a workaround. After doing this, my system initializes the runlevel as it should. I found just 2 similar problems using Google: http://forums.opensuse.org/english/get-technical-help-here/hardware/455513-o... http://linux.derkeiler.com/Mailing-Lists/SuSE/2011-02/msg00490.html Reproducible: Couldn't Reproduce Steps to Reproduce: Difficult to reproduce. I did the pretty same update procedure on my notebook - but there everything's working fine. Actual Results: Any service of the choosen runlevel comes up. No xdm, kdm, xorg. Expected Results: Runlevel should initialise correctly and blogd should be able to do whatever it should do. Workaround: Rename or delete /sbin/blogd (for example into /sbin/blogd.disable) 2 similar problems: http://forums.opensuse.org/english/get-technical-help-here/hardware/455513-o... http://linux.derkeiler.com/Mailing-Lists/SuSE/2011-02/msg00490.html -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.