Apologies for the duplication , I forgot to include a
subject in the previous message.
At the bottom of /var/log/messages I see
Jul 1 07:35:01 home kernel: imklog 3.18.6, log source = /proc/kmsg started.
Jul 1 07:35:01 home rsyslogd: [origin software="rsyslogd"
swVersion="3.18.6" x-pid="2103" x-info="http://www.rsyslog.com"]
restart
Jul 1 07:35:01 home kernel: imklog 3.18.6, log source = /proc/kmsg started.
Jul 1 07:35:01 home rsyslogd: [origin software="rsyslogd"
swVersion="3.18.6" x-pid="2103" x-info="http://www.rsyslog.com"]
restart
(Some wraparound may have occurred in the above)
The same pair of messages is repeated. First time I notice such a
thing. In /var/log/kern.log I see at the bottom
Jul 1 07:35:01 home kernel: imklog 3.18.6, log source = /proc/kmsg started.
Jul 1 07:35:01 home kernel: imklog 3.18.6, log source = /proc/kmsg started.
Once again a duplication.
Is there any legitimate reason this might have happened or is it a
kernel bug ? Neither file has anything else I haven't seen before.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/BANLkTikSv=EU3jTPnxzqpq...@mail.gmail.com
> [Please preserve the CC]
Sorry but I can't.
> At the bottom of /var/log/messages I see
>
> Jul 1 07:35:01 home kernel: imklog 3.18.6, log source = /proc/kmsg started.
> Jul 1 07:35:01 home rsyslogd: [origin software="rsyslogd" swVersion="3.18.6" x-pid="2103" x-info="http://www.rsyslog.com"] restart
> Jul 1 07:35:01 home kernel: imklog 3.18.6, log source = /proc/kmsg started.
> Jul 1 07:35:01 home rsyslogd: [origin software="rsyslogd" swVersion="3.18.6" x-pid="2103" x-info="http://www.rsyslog.com"] restart
(...)
> The same pair of messages is repeated. First time I notice such a thing.
> In /var/log/kern.log I see at the bottom
>
> Jul 1 07:35:01 home kernel: imklog 3.18.6, log source = /proc/kmsg
> started. Jul 1 07:35:01 home kernel: imklog 3.18.6, log source =
> /proc/kmsg started.
>
> Once again a duplication.
JFYI, I also get them:
stt008:~# grep -i -e imk -e rsyslog /var/log/syslog*
/var/log/syslog:Jul 1 07:52:00 stt008 kernel: imklog 3.18.6, log source = /proc/kmsg started.
/var/log/syslog:Jul 1 07:52:00 stt008 rsyslogd: [origin software="rsyslogd" swVersion="3.18.6" x-pid="2616" x-info="http://www.rsyslog.com"] restart
/var/log/syslog.1:Jul 1 07:38:58 stt008 kernel: imklog 3.18.6, log source = /proc/kmsg started.
/var/log/syslog.1:Jul 1 07:38:58 stt008 rsyslogd: [origin software="rsyslogd" swVersion="3.18.6" x-pid="2616" x-info="http://www.rsyslog.com"] restart
> Is there any legitimate reason this might have happened or is it a
> kernel bug ? Neither file has anything else I haven't seen before.
Dunno, but I hope yes, there should be a good reason for starting rsyslog
service and imklog module twice.
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
How many instances of rsyslog or comparable daemons are running on
your system? Do you use logrotate or something similiar that restarts
logging daemons? Check crontab -l and /etc/crontab for the tasks that
usually run at 07:35, and then check either these tasks, or, if it is
something like cron-daily, check /etc/cron.daily.
If you indeed use logrotate, check /etc/logrotate.d
and /etc/logrotate.conf if you have two lines saying that rsyslog
should be restarted (maybe grep for rsyslog in the above-mentioned
directories).
Best regards,
Claudius
--
New systems generate new problems.
Please use GPG: ECB0C2C7 4A4C4046 446ADF86 C08112E5 D72CDBA4
http://chubig.net/ http://nightfall.org
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/20110701193...@ares.home.chubig.net