Syslog console messages every midnight

[Rilo Ravestein]

Hello,

I noticed that i am getting Syslog-ng messages in the console every midnight. Is that normal?

Code:

Feb 10 00:00:00 nas syslog-ng[1926]: Configuration reload request received, reloading configuration;
Feb 11 00:00:00 nas syslog-ng[1926]: Configuration reload request received, reloading configuration;
Feb 12 00:00:00 nas syslog-ng[1926]: Configuration reload request received, reloading configuration;
Feb 13 00:00:00 nas syslog-ng[1926]: Configuration reload request received, reloading configuration;
Feb 14 00:00:00 nas syslog-ng[1926]: Configuration reload request received, reloading configuration;
Feb 15 00:00:00 nas syslog-ng[1926]: Configuration reload request received, reloading configuration;
Feb 16 00:00:00 nas syslog-ng[1926]: Configuration reload request received, reloading configuration;
Feb 17 00:00:00 nas syslog-ng[1926]: Configuration reload request received, reloading configuration;

 

[Bidule0hm]

I have them too, I guess it's normal ;)

 

[DrKK]

Yep, normal. Everyone has them.

 

[Rilo Ravestein]

Ok, great. Thanks

 

[DrKK]

To be fair, just because it's "normal" doesn't mean it's not a "bug". Why would the configuration have to be reloaded every midnight?

:)

 

[Rilo Ravestein]

To be fair, just because it's "normal" doesn't mean it's not a "bug". Why would the configuration have to be reloaded every midnight
:)

I agree. Maybe someone can shed a light on this

 

[Mirfster]

Does that also show in dmesg?

 

[Rilo Ravestein]

Does that also show in dmesg?

Nope.
In the console (GUI):

Code:

Feb 18 00:00:00 nas syslog-ng[1896]: Configuration reload request received, reloading configuration;

Part of the output of dmesg -a:

Code:

epair2a: promiscuous mode enabled
ng_ether_ifnet_arrival_event: can't re-name node epair2b
Feb 17 17:32:50 nas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair2b
Feb 18 03:01:12 vbox sm-mta[13045]: u1I21CZr013045: SYSERR(root): hash map "Alias0": missing map file /etc/mail/aliases.db: No such file or directory

17:32 entry was from restarting a jail if i'm correct
03:01 entry I have fixed ;)
Anyway, nothing at 00:00

 

[Peter Czanik]

I think, it is due to log rotation.

 

[PhilZJ81]

I started seeing these messages when I did a fresh install to 9.10. My old setup on 9.3 didn't show them.
I'm currently running "FreeNAS-9.10-STABLE-201605240427" and I see those messages at the the same time as the OP.

Are we still in agreement that it's not an issue?

thanks!

 

[Peter Czanik]

I just checked /etc/crontab and I was right:

# Rotate log files only at midnight.
0 0 * * * root newsyslog > /dev/null 2>&1

So, it's normal, even if annoying.