Take the 2-minute tour ×
Raspberry Pi Stack Exchange is a question and answer site for users and developers of hardware and software for Raspberry Pi. It's 100% free, no registration required.

I've switched from sysvinit to upstart but get the below message whenever I attempt to start a service:

Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused

Upstart does execute all the old sysvinit scripts at startup so it is safe to switch. But Upstart scripts don't seem to work for me.

Does anyone know what may be causing the above error message? The only reference to it I've come across is in relation to running within a chroot or a virtual machine, neither apply.

share|improve this question
2  
Have you rebooted the Pi? serverfault.com/questions/236667/upstart-does-not-work –  Steve Robillard Jul 24 '12 at 2:42
    
@SteveRobillard Wow. I felt sure I must have already done that... I guess I didn't though as restarting has sorted it. Thanks. –  peterstrapp Jul 24 '12 at 17:00
    
Glad I could help. –  Steve Robillard Jul 24 '12 at 17:04
    
I've just had a very similar problem. I assumed I would need to reboot my after. I found that sudo reboot wont actually reboot the system. This is probobaly due to the reboot needing to be done by sysvinit but upstart is now installed instead. –  couling Sep 15 '12 at 10:10
add comment

1 Answer

up vote 3 down vote accepted

Have you rebooted the Pi? serverfault.com/q/236667/upstart-does-not-work
- Steve Robillard on July 24 at 2:42

Basically, the link says that you should try rebooting the system. Thanks Steve!

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.