Fixing broken dbus from Ubuntu 11.04 to 11.10 dist-upgrade

#Written by: Michael Wood
#Date 11-29-2011

Well it looks like dbus is broken on my Ubuntu 11.10 server after doing a dist-upgrade. Possibly due to a third party script that didn't execute correctly.

Upon startup I get a message stating:
"Waiting for network configuration..."
"Waiting an additional 60 seconds for network"
"System will be booted without full network support"

Taking a look at /var/log/dmesg I can see the errors at the end of the file:
[17.029623] init: dbus main process (696) terminated with status 1
[17.029649] init: dbus main process ended, respawning
[17.030584] init: Unable to connect to the system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused
[17.057128] init: plymouth-upstart-bridge main process (702) terminated with status 1

Running an "ifconfig" command should only show you the local loopback interface (lo).  No ethernet interface (eth0) is present.

Taking a look at /var/run/dbus I noticed the init script is not removing the following lines:
pid
system_bus_socket|

Run this command:
sudo /var/run/dbus rm -f pid system_bus_socket|

Also, it seems during this dist-upgrade the contents of /var/run and /var/lock were supposed to be transistioned to /run and /run/lock
First thing you need to do is create these directories (mine were already created, but check first):
sudo mkdir /run
sudo mkdir /run/lock

Next copy the contents of /var/run to /run like this:
sudo mv /var/run/* /run

Copy the contents from /var/lock to /run/lock:
sudo mv /var/lock/* /run/lock

It's possible there may be a special mount point in use by the system.  If you get any error messages trying to copy from those directories, try this:
sudo rm -f <filename>

If the above command doesn't work, try unmounting the file:
sudo umount -fl <filename>
Now try to remove the file(s) again.

Delete the following directories:
sudo rm -rf /var/run /var/lock

Now time to create symbolic links:
sudo ln -s /run /var
sudo ln -s /run/lock /var

Restart the machine:
sudo shutdown -r now

If all went as planned everything should be working correctly now.