[opensuse-factory] eth0 and dbus problems after upgrade to 12.1
Already sent to opensuse list with no reply yet. I updated via 12.1 x86_64 dvd and because I maintain multimedia, I included a few build service repos in thye upgrade. I used zypper dup from 11.3 to 11.4 without problems but this time there are problems which I assume stem from /var/run being a tempfs. I've searched threads on this list and factory list and googling only brought up similar Ubuntu problems but no real help. First problem was having to manually "ifup eth0" to get my network going, I've fixed that with adding "ifup eth0" to "/etc/init.d/boot.local" but the other problem has me stumped. As kde is starting it halts on a message box stating a similar message to this syslog one, clicking ok continues to desktop : pam_systemd(xdm-np:session): Failed to connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory Thinking that this was caused by the tempfs I also created the dbus directory in boot.local but it doesn't fix anything. I'm surprised that no one has reported a bug and it seems I'm the only one to have this problem, it's maybe leftover from my 11.4 kernel getting mangled when I recompiled with certain extra cdc_phonenet options and then when I updated my non openSUSE VirtualBox-4.1 to 4.1.8 my network died. I fixed this with the 11.4 tumbleweed kernel. Please help, here's a section of my /var/log/messages with lots of the above error message and my boot.msg is at http://pastebin.com/Zpn9AnTp , I'm a bit nervous using pastebin for this so it expires after one day. : Mar 7 10:56:02 Arbuthnot kdm: :0[2184]: pam_systemd(xdm-np:session): Failed to connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory Mar 7 10:56:04 Arbuthnot checkproc: checkproc: can not get session id for process 2396! Mar 7 10:56:50 Arbuthnot kernel: [ 5373.607165] fuse init (API version 7.17) Mar 7 10:56:50 Arbuthnot mount[3411]: mount: fusectl already mounted or /sys/fs/fuse/connections busy Mar 7 10:56:50 Arbuthnot mount[3411]: mount: according to mtab, fusectl is already mounted on /sys/fs/fuse/connections Mar 7 10:56:50 Arbuthnot systemd[1]: sys-fs-fuse-connections.mount mount process exited, code=exited status=32 Mar 7 10:57:14 Arbuthnot sudo: davepl : TTY=pts/2 ; PWD=/home/davepl ; USER=root ; COMMAND=/usr/bin/tailf /var/log/messages Mar 7 10:57:15 Arbuthnot sudo: pam_systemd(sudo:session): Failed to connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory Mar 7 10:57:14 Arbuthnot sudo: davepl : TTY=pts/2 ; PWD=/home/davepl ; USER=root ; COMMAND=/usr/bin/tailf /var/log/messages Mar 7 10:57:15 Arbuthnot sudo: pam_systemd(sudo:session): Failed to connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory Mar 7 10:57:40 Arbuthnot su: (to root) davepl on /dev/pts/1 Mar 7 10:57:40 Arbuthnot su: pam_systemd(su:session): Failed to connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory Mar 7 11:15:09 Arbuthnot logrotate: ALERT exited abnormally with [1] Mar 7 11:15:09 Arbuthnot logrotate: error: "/var/log/atftpd" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file. Mar 7 11:15:09 Arbuthnot logrotate: error: "/var/lib/mailman/logs" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file. Mar 7 11:15:09 logrotate: last message repeated 11 times Mar 7 11:15:09 Arbuthnot logrotate: error: "/var/lib/privoxy/log" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file. Mar 7 11:15:09 Arbuthnot logrotate: error: "/var/lib/privoxy/log" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file. Mar 7 11:15:09 Arbuthnot logrotate: error: "/var/log/quagga" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file. Mar 7 11:15:09 logrotate: last message repeated 5 times Mar 7 11:15:09 Arbuthnot logrotate: error: "/var/log/squid" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file. Mar 7 11:15:09 logrotate: last message repeated 2 times Mar 7 11:15:09 Arbuthnot logrotate: error: "/var/log/squidGuard" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file. Mar 7 11:15:09 Arbuthnot logrotate: error: "/var/log/news" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file. Mar 7 11:15:09 logrotate: last message repeated 2 times Mar 7 11:15:09 Arbuthnot run-crons[3889]: logrotate: OK Mar 7 11:15:09 Arbuthnot run-crons[3889]: suse-clean_catman: OK Mar 7 11:15:19 Arbuthnot run-crons[3889]: suse-do_mandb: OK Mar 7 11:16:05 Arbuthnot run-crons[3889]: suse-texlive: OK Mar 7 11:16:06 Arbuthnot su: (to nobody) root on none Mar 7 11:16:06 Arbuthnot su: pam_systemd(su:session): Failed to connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory Mar 7 11:16:06 Arbuthnot su: (to nobody) root on none Mar 7 11:16:06 Arbuthnot su: pam_systemd(su:session): Failed to connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory Mar 7 11:16:06 Arbuthnot su: (to nobody) root on none Mar 7 11:16:06 Arbuthnot su: pam_systemd(su:session): Failed to connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory Mar 7 11:22:22 Arbuthnot run-crons[3889]: suse-updatedb: OK Mar 7 11:22:22 Arbuthnot run-crons[3889]: suse.cron-sa-update: OK Mar 7 11:22:25 Arbuthnot run-crons[3889]: suse.de-backup-rc.config: OK Mar 7 11:22:48 Arbuthnot run-crons[3889]: suse.de-backup-rpmdb: OK Mar 7 11:22:49 Arbuthnot run-crons[3889]: suse.de-check-battery: OK Mar 7 11:22:49 Arbuthnot run-crons[3889]: suse.de-clean-tmp: OK Mar 7 11:22:49 Arbuthnot run-crons[3889]: suse.de-cron-local: OK Mar 7 11:26:40 Arbuthnot run-crons[3889]: suse.de-rkhunter: OK Mar 7 11:26:40 Arbuthnot run-crons[3889]: suse.de-snapper: OK Mar 7 11:26:44 Arbuthnot run-crons[3889]: tmpwatch: OK Mar 7 11:30:01 Arbuthnot run-crons[18484]: suse.de-snapper: OK Thanks in advance for any help Dave P -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le mercredi 07 mars 2012 à 15:58 +0200, Dave Plater a écrit :
Already sent to opensuse list with no reply yet.
Bug report would be much better for your issue.
Anyway, the first thing would be to install ALL 12.1 updates, which are
fixing a lot of the issues related to systemd and network.
--
Frederic Crozat
On 03/07/2012 07:30 PM, Frederic Crozat wrote:
Le mercredi 07 mars 2012 à 15:58 +0200, Dave Plater a écrit :
Already sent to opensuse list with no reply yet.
Bug report would be much better for your issue.
Anyway, the first thing would be to install ALL 12.1 updates, which are fixing a lot of the issues related to systemd and network.
I'm fully up to date, first thing I did, ubuntu seemed to have a big problem with this and offered the solution of linking /var/run to /run but that caused the same blank screen problem the ubuntu users experienced and I had to edit boot.local with a rescue system. This is almost certainly caused by a file left behind in 11.4, somebody must know what files could cause this. Maybe if I weed out my orphaned packages..... Thanks Dave P -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (2)
-
Dave Plater
-
Frederic Crozat