• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved Cron logrotate warning: initctl: Unable to connect to Upstart

VLopez

New Pleskian
Hi people.
Debian 7 server updated recently from 12.0 Plesk to 12.5 Plesk. So far so good but...

We're having a email per day from Cron Daemon

Cron <root@hosting> test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )

/etc/cron.daily/logrotate:
initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused

There's no other issue by now and all seems to be working properly.
Searched for cron jobs at /etc/cron.daily regarding this messages but found no clue who's orginating this messages.
Before upgrade this issue was nonexistent.
Probably nothing to care much about, but i do prefer havin messages when needed.

Any hint?

Thanks in advance.
 
Hi VLopez,

first of all, pls. be informed, that on Debian/Ubuntu - based systems, the cron - crontabs can be investigated/modified/edited/deleted at "/etc/crontab". The depending log - rotation - configuration for your "upstart" can be found "/etc/logrotate.d/upstart".

Consider to add at crontab - commands the optional string " >/dev/null 2>&1", to avoid getting eMails.
 
Hi again.

We've found that doing an apt-get upgrade throws the error when restarting some services during upgrade proccess.

{....}
Setting up bind9-host (1:9.8.4.dfsg.P1-6+nmu2+deb7u11) ...
Setting up dnsutils (1:9.8.4.dfsg.P1-6+nmu2+deb7u11) ...
Setting up bind9utils (1:9.8.4.dfsg.P1-6+nmu2+deb7u11) ...
Setting up bind9 (1:9.8.4.dfsg.P1-6+nmu2+deb7u11) ...
initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
[....] Stopping domain name service...: bind9waiting for pid 29918 to die

. ok
[ ok ] Starting domain name service...: bind9.
Setting up openssl (1.0.1t-1+deb7u1) ...
{.....}​

So we belive this issue is not directly related to Plesk but with operating system itself, so we think it's better to mark this thread as resolved by now in order to not confuse any other people.
We will search for any resolution on Debian forums.
P.S.: We will post here any solution we find.

Anyway, if anyone has any clue will be welcome.

Thanks all.
 
Back
Top