Check_reload_status: Reloading filter - timestamp jumping around ???



  • Hi y'all.
    I've got pfSense 2.0.1 2g nano-bsd running on a Netgate FW-7535 and for the most part, all is well.  Something I've noticed though, is that there appear to be, every few minutes some entries being put in the syslog that say

    check_reload_status: Reloading filter

    I don't know what these entries signify, but they are  a bit worrisome, additionally because the timestamp on the entries seems to be +0400 from the "real" system clock and so it looks out of sequence, see below screenshot

    any ideas on how to further troubleshoot this or why it's happening??
    thank you to anyone who replies



  • @luckman212:

    the timestamp on the entries seems to be +0400 from the "real" system clock

    What time zone has been configured on the pfSense box? GMT+4 hours? GMT-4 hours?

    On my system running 2.0.1-RELEASE I see in the system log:

    Jun  7 09:07:14 pfsense apinger: ALARM: WAN(121.50.212.9)  *** down ***
    Jun  7 09:07:14 pfsense apinger: alarm canceled: WAN(121.50.212.9)  *** down ***
    Jun  7 09:07:24 pfsense check_reload_status: Reloading filter
    Jun  7 09:07:24 pfsense check_reload_status: Reloading filter
    Jun  7 09:12:24 pfsense apinger: ALARM: WAN(121.50.212.9)  *** down ***
    Jun  7 09:12:24 pfsense apinger: alarm canceled: WAN(121.50.212.9)  *** down ***
    Jun  7 09:12:34 pfsense check_reload_status: Reloading filter
    Jun  7 09:12:34 pfsense check_reload_status: Reloading filter

    What is the build reported on the pfSense home page? If I recall correctly, some time ago (but I can't recall how long ago) the system logs seemed to be timestamping some events with local time and some with GMT.



  • Some processes use the system time at the time of process startup, and some use the current system time. When you see that it's generally because you changed the system from GMT to your actual timezone (or otherwise changed the timezone) after the system booted. No easy way to get all those consistent short of rebooting now that you have the desired timezone set.



  • @cmb:

    Some processes use the system time at the time of process startup, and some use the current system time. When you see that it's generally because you changed the system from GMT to your actual timezone […] after the system booted

    Ah ha!  Yes that makes sense, I am pretty sure I did do that, and I haven't rebooted the pfSense since I set it up.  I'll try rebooting tonight and see if that eliminates the discrepancy.  Thanks cmb!



  • Yep that seems to have done the trick for the strange timestamps  ;)
    cheers


Locked