This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Failed to start message bus: Failed to bind socket "/var/run/dbus/system_bus_socket": No such file or directory dbus.

Dear Ti E2E Community,

For boot time optimization,  I have renamed rc5.d & started invoking the scripts in backgroundas shown below, now as of now only rcS.d is being invoked

root@lifeline:/etc# ls -la rcS.d/


lrwxrwxrwx 1 root root 21 Feb 17 2014 S03mountall.sh -> ../init.d/mountall.sh
lrwxrwxrwx 1 root root 14 Jan 1 2000 S04udev -> ../init.d/init

vi /etc/init.d/init

/etc/init.d/udev start &
/etc/init.d/udev-cache &
/etc/init.d/ifplugd.sh &
/etc/init.d/dbus-1 start
/etc/init.d/dropbear start &
/etc/init.d/ntpdate.sh start &
/etc/init.d/hwclock.sh start &
/etc/init.d/syslog.busybox start &
/etc/init.d/alsa-state start &
/etc/init.d/gpio.sh &
/opt/tunstall/scripts/startup.sh

Am seeing the below error message during boot, could you please let me know why am seeing the below error message, any service or scripts needs to be run or am I missing anything??

Starting system message bus: [ 2.599961] random: dbus-daemon urandom read with 65 bits of entropy available
Failed to start message bus: Failed to bind socket "/var/run/dbus/system_bus_socket": No such file or directory
dbus.

Kindly do the needful as early as possible

Many Thanks in advance