Unable to connect to Upstart

[Michael Heuberger]

$ sudo restart smbd
restart: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused

Happens after upgrading Ubuntu from 14.10 to 15.04 and also causes nmbd unable to start via cron.

Attached info should reveal my whole setup and help locating the issue.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: samba 2:4.1.13+dfsg-4ubuntu3
ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
Uname: Linux 3.19.0-26-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.17.2-0ubuntu1.3
Architecture: amd64
BothFailedConnect: Yes
Date: Mon Aug 24 22:57:40 2015
InstallationDate: Installed on 2014-10-31 (297 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
NmbdLog:

SambaServerRegression: Yes
SmbConfIncluded: Yes
SmbLog:
 STATUS=daemon 'smbd' finished starting up and ready to serve connectionsFailed to delete pidfile /var/run/samba/smbd.pid. Error was No such file or directory
   STATUS=daemon 'smbd' finished starting up and ready to serve connectionsFailed to delete pidfile /var/run/samba/smbd.pid. Error was No such file or directory
   STATUS=daemon 'smbd' finished starting up and ready to serve connectionsFailed to delete pidfile /var/run/samba/smbd.pid. Error was No such file or directory
   STATUS=daemon 'smbd' finished starting up and ready to serve connectionsFailed to delete pidfile /var/run/samba/smbd.pid. Error was No such file or directory
   STATUS=daemon 'smbd' finished starting up and ready to serve connectionsFailed to delete pidfile /var/run/samba/smbd.pid. Error was No such file or directory
SourcePackage: samba
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.cron.daily.samba: [deleted]
mtime.conffile..etc.logrotate.d.samba: 2014-12-28T13:03:29.219447

[Michael Heuberger (michael.heuberger)]

i think the duplicate status is wrong. the other bug has NO apport information. this one ticket has more information

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.