Bug 700429

+++ This bug was initially created to detach the dbus-related issue from Bug #693873 +++

Description of problem:
A dbus connection message is printed on the console when rebooting/halting the system.

Version-Release number of selected component (if applicable):
ypbind-1.32-8.fc15

How reproducible:
sometimes

Steps to Reproduce:
see the comments bellow
  
Actual results:
ypbind[...]: Connection to D-BUS system message bus failed: Failed to connect
to socket /var/run/dbus/system_bus_socket: Connection refused

Expected results:
No messages.

Additional info:
Conversation log from Bug #693873 related to this one:

Severin Gehwolf 2011-04-08 10:50:43 EDT

Remember that I'm using NIS + /home on NFS + NetworkManager now. Another
(minor?) problem I have been seeing is that in some cases when I reboot/halt
the machine, I get on the console:

ypbind[...]: Connection to D-BUS system message bus failed: Failed to connect
to socket /var/run/dbus/system_bus_socket: Connection refused.

Unfortunately, I cannot always reproduce. I'll follow up should I be able to.
However, when it occurrs, I get the above message over and over again. The
shutdown process stalls for 2 minutes or so, only printing this message until
it finally continues. I cannot interrupt this (ctrl+c).

----------------------------------------

Comment 23 Jan Horak 2011-04-12 04:03:35 EDT

(In reply to comment #21)
> ypbind[...]: Connection to D-BUS system message bus failed: Failed to connect
> to socket /var/run/dbus/system_bus_socket: Connection refused.
> 
> Unfortunately, I cannot always reproduce. I'll follow up should I be able to.
> However, when it occurrs, I get the above message over and over again. The
> shutdown process stalls for 2 minutes or so, only printing this message until
> it finally continues. I cannot interrupt this (ctrl+c).

Does it happen even in ypbind-1.32-7.fc15? There is no correct LSB header in
previous versions, so this could have been caused by massive parallelism of
tasks during boot up. However, the LSB header is defined now, so it should be
OK in this new update.

----------------------------------------

Comment 24 Severin Gehwolf 2011-04-13 18:18:08 EDT

(In reply to comment #23)
> (In reply to comment #21)
> > ypbind[...]: Connection to D-BUS system message bus failed: Failed to connect
> > to socket /var/run/dbus/system_bus_socket: Connection refused.
> > 
> > Unfortunately, I cannot always reproduce. I'll follow up should I be able to.
> > However, when it occurrs, I get the above message over and over again. The
> > shutdown process stalls for 2 minutes or so, only printing this message until
> > it finally continues. I cannot interrupt this (ctrl+c).
> 
> Does it happen even in ypbind-1.32-7.fc15? There is no correct LSB header in
> previous versions, so this could have been caused by massive parallelism of
> tasks during boot up. However, the LSB header is defined now, so it should be
> OK in this new update.

To be honest, I'm not sure. I can't remember when I switched to ypbind with LSB
headers in init scripts, so it's hard to tell. So far it didn't happen again
and I don't consider this an issue anymore. Should it happen again, I'll report
it here. Thanks!

----------------------------------------

Comment 26 Severin Gehwolf 2011-04-14 09:35:15 EDT

(In reply to comment #24)
> (In reply to comment #23)
> > (In reply to comment #21)
> > > ypbind[...]: Connection to D-BUS system message bus failed: Failed to connect
> > > to socket /var/run/dbus/system_bus_socket: Connection refused.
> > > 
> > > Unfortunately, I cannot always reproduce. I'll follow up should I be able to.
> > > However, when it occurrs, I get the above message over and over again. The
> > > shutdown process stalls for 2 minutes or so, only printing this message until
> > > it finally continues. I cannot interrupt this (ctrl+c).
> > 
> > Does it happen even in ypbind-1.32-7.fc15? There is no correct LSB header in
> > previous versions, so this could have been caused by massive parallelism of
> > tasks during boot up. However, the LSB header is defined now, so it should be
> > OK in this new update.

$ rpm -q ypbind
ypbind-1.32-7.fc16.x86_64

I am using this for a while now, and yesterday I was able to reproduce the
system_bus_socket: Connection refused problem. It doesn't seem to be entirely
fixed yet. This is just a FYI. I'm not overly concerned about this and I'm
still foggy about how to reliably reproduce. Thanks!

----------------------------------------

Comment 27 Jan Horak 2011-04-14 09:46:51 EDT

(In reply to comment #26)
> $ rpm -q ypbind
> ypbind-1.32-7.fc16.x86_64
> 
> I am using this for a while now, and yesterday I was able to reproduce the
> system_bus_socket: Connection refused problem. It doesn't seem to be entirely
> fixed yet. This is just a FYI. I'm not overly concerned about this and I'm
> still foggy about how to reliably reproduce. Thanks!

I realized that ypbind-1.32-7-fc15 misses $rpcbind in its LSB header, which
hypothetically can cause problems such that. I've prepared a new package
ypbind-1.32-8.fc15 (see comment #25), which has a correct LSB header, so you
can give it a try and see, if something changes.

----------------------------------------

Comment 28 Severin Gehwolf 2011-04-15 10:47:50 EDT

(In reply to comment #23)
> (In reply to comment #21)
> > ypbind[...]: Connection to D-BUS system message bus failed: Failed to connect
> > to socket /var/run/dbus/system_bus_socket: Connection refused.

Elaborating a bit more about this problem. I've noticed that _IF_ I see this
problem, the immediately preceeding message printed to the console is something
along the lines of:

pam_systemd(...): Failed to get user data <NIS-UID>
pam_su(...) ---> not sure about this

I'm not sure if this is related. Maybe this is only happening after I've su'ed
to root from a NIS user, but that doesn't seem to be the entire story since I
can't reliably reproduce using just those two steps. Hmmm.

Let me know when you've got a build with the $rpcbind in the LSB header ready.
Thanks!

----------------------------------------

Comment 30 Severin Gehwolf 2011-04-26 09:22:29 EDT

(In reply to comment #27)
> (In reply to comment #26)
> > $ rpm -q ypbind
> > ypbind-1.32-7.fc16.x86_64
> > 
> > I am using this for a while now, and yesterday I was able to reproduce the
> > system_bus_socket: Connection refused problem. It doesn't seem to be entirely
> > fixed yet. This is just a FYI. I'm not overly concerned about this and I'm
> > still foggy about how to reliably reproduce. Thanks!
> 
> I realized that ypbind-1.32-7-fc15 misses $rpcbind in its LSB header, which
> hypothetically can cause problems such that. I've prepared a new package
> ypbind-1.32-8.fc15 (see comment #25), which has a correct LSB header, so you
> can give it a try and see, if something changes.

FWIW: I have ypbind-1.32-8.fc15 here and still have seen the system_bus_socket:
Connection refused problem :(

----------------------------------------

Comment 31 Jan Horak 2011-04-27 10:05:01 EDT

You can try to add also messagebus to LSB header and see if it helps:

-# Required-Start: $local_fs $remote_fs $network $rpcbind
-# Required-Stop: $local_fs $remote_fs $network $rpcbind
+# Required-Start: $local_fs $remote_fs $network $rpcbind messagebus
+# Required-Stop: $local_fs $remote_fs $network $rpcbind messagebus

What version of NetworkManager do you use?