Hourly : apinger: SIGHUP received, reloading configuration



  • Hi,

    Some strange behaviour which I can't get solved.

    Gateways.log :

    Jul 25 21:13:25 pfsense apinger: SIGHUP received, reloading configuration.
    Jul 25 22:13:25 pfsense apinger: SIGHUP received, reloading configuration.
    Jul 25 23:13:25 pfsense apinger: SIGHUP received, reloading configuration.
    Jul 26 00:13:25 pfsense apinger: SIGHUP received, reloading configuration.
    Jul 26 01:13:25 pfsense apinger: SIGHUP received, reloading configuration.
    Jul 26 02:13:25 pfsense apinger: SIGHUP received, reloading configuration.
    Jul 26 03:13:25 pfsense apinger: SIGHUP received, reloading configuration.
    Jul 26 04:13:25 pfsense apinger: SIGHUP received, reloading configuration.
    Jul 26 05:13:25 pfsense apinger: SIGHUP received, reloading configuration.
    Jul 26 06:13:25 pfsense apinger: SIGHUP received, reloading configuration.
    Jul 26 07:13:25 pfsense apinger: SIGHUP received, reloading configuration.
    Jul 26 08:13:25 pfsense apinger: SIGHUP received, reloading configuration.
    Jul 26 09:13:25 pfsense apinger: SIGHUP received, reloading configuration.

    Wan connection isn't lost at all.
    But a lot of services get reloaded after this message (also racoon etc) , so a lot of connections are lost hourly

    Don''t wan't to disable gateway monitoring , because this functionality is needed when there is a real loss of wan connection.

    Found a workaround , just testing it : disabled "State Killing on Gateway Failure" (advanced->Miscellaneous ->Gateway monitoring)

    Just wan't to know what is happening here.

    Whenever somebody knows which logging/debugging or else needs to be checked , please give a reply to this message.

    Kind regards,

    Roel



  • Hi,

    disabling "State Killing on Gateway Failure" , doesn't change this behaviour.

    Even more.. it seems that not apinger is reloading anything hourly.
    as far as i can see , also apinger IS restarted hourly.

    Currently i'm investigating radvd logs (routing.log)
    As i'm running ipv6 prefix delegation.

    Jul 26 09:13:25 pfsense radvd[40496]: resuming normal operation
    Jul 26 10:13:23 pfsense radvd[40496]: attempting to reread config file
    Jul 26 10:13:23 pfsense radvd[40496]: resuming normal operation
    Jul 26 10:13:24 pfsense radvd[40496]: attempting to reread config file
    Jul 26 10:13:24 pfsense radvd[40496]: resuming normal operation
    Jul 26 10:13:25 pfsense radvd[40496]: attempting to reread config file
    Jul 26 10:13:25 pfsense radvd[40496]: resuming normal operation
    Jul 26 11:13:23 pfsense radvd[40496]: attempting to reread config file
    Jul 26 11:13:23 pfsense radvd[40496]: resuming normal operation
    Jul 26 11:13:24 pfsense radvd[40496]: attempting to reread config file
    Jul 26 11:13:24 pfsense radvd[40496]: resuming normal operation
    Jul 26 11:13:25 pfsense radvd[40496]: attempting to reread config file
    Jul 26 11:13:25 pfsense radvd[40496]: resuming normal operation

    is it possible that this has someting to do with this BSD option :

    net.inet6.ip6.rtexpire: 3600

    Any help would be appreciated

    Kind regards,

    Roel