Dual-WAN, MONITOR spamming system, causing 504: Bad Gateway
-
I just noticed with 3.2.3-Release, dual wan functionality does not work very well. When a link goes down, the system log is spammed with the following messages and when accessing the config interface, it is soo slow and gets 504: Bad Gateway.
I am getting these almost every second:
Aug 30 17:38:12 php-fpm 99842 /rc.newwanip: MONITOR: WAN2_DHCP is down, omitting from routing group WAN2_GATORLINK Aug 30 17:38:12 php-fpm 99842 /rc.newwanip: MONITOR: WAN2_DHCP is down, omitting from routing group FAIL_OVER Aug 30 17:38:12 php-fpm 99842 /rc.newwanip: MONITOR: WAN2_DHCP is down, omitting from routing group Transmission Aug 30 17:38:12 php-fpm 99842 /rc.newwanip: MONITOR: WAN2_DHCP is down, omitting from routing group WAN2_WAN Aug 30 17:38:12 php-fpm 99842 /rc.newwanip: MONITOR: WAN2_DHCP is down, omitting from routing group WAN_WAN2 Aug 30 17:38:12 php-fpm 99842 /rc.newwanip: MONITOR: WAN2_DHCP is down, omitting from routing group LOADBALANCE Aug 30 17:38:12 php-fpm 99842 /rc.newwanip: Dynamic DNS (xxx): running get_failover_interface for opt1\. found igb1 Aug 30 17:38:12 php-fpm 99842 /rc.newwanip: Dynamic DNS dynodes (xxx): xxx extracted from local system. Aug 30 17:38:12 php-fpm 99842 /rc.newwanip: MONITOR: WAN2_DHCP is down, omitting from routing group WAN2_GATORLINK Aug 30 17:38:12 php-fpm 99842 /rc.newwanip: MONITOR: WAN2_DHCP is down, omitting from routing group FAIL_OVER Aug 30 17:38:12 php-fpm 99842 /rc.newwanip: MONITOR: WAN2_DHCP is down, omitting from routing group Transmission Aug 30 17:38:12 php-fpm 99842 /rc.newwanip: MONITOR: WAN2_DHCP is down, omitting from routing group WAN2_WAN Aug 30 17:38:12 php-fpm 99842 /rc.newwanip: MONITOR: WAN2_DHCP is down, omitting from routing group WAN_WAN2 Aug 30 17:38:12 php-fpm 99842 /rc.newwanip: MONITOR: WAN2_DHCP is down, omitting from routing group LOADBALANCE Aug 30 17:38:12 php-fpm 99842 /rc.newwanip: Dynamic DNS: updatedns() starting Aug 30 17:38:12 php-fpm 99842 /rc.newwanip: MONITOR: WAN2_DHCP is down, omitting from routing group WAN2_GATORLINK Aug 30 17:38:12 php-fpm 99842 /rc.newwanip: MONITOR: WAN2_DHCP is down, omitting from routing group FAIL_OVER Aug 30 17:38:12 php-fpm 99842 /rc.newwanip: MONITOR: WAN2_DHCP is down, omitting from routing group Transmission Aug 30 17:38:12 php-fpm 99842 /rc.newwanip: MONITOR: WAN2_DHCP is down, omitting from routing group WAN2_WAN Aug 30 17:38:12 php-fpm 99842 /rc.newwanip: MONITOR: WAN2_DHCP is down, omitting from routing group WAN_WAN2 Aug 30 17:38:12 php-fpm 99842 /rc.newwanip: MONITOR: WAN2_DHCP is down, omitting from routing group LOADBALANCE -
On 2.3.2 64-bit. Similar problem as GoldServe. Whenever Wan1/2 failover occurs I get hit with 3 pairs of the same log messages in succession. Any way to have PfSense log just one entry pair? Does it log for every gateway with monitoring enabled even though it's not included in the failover tiers?
2016-09-28 16:07:53 Daemon.Error pfsense Sep 28 16:07:53 php-fpm[51147]: /rc.dyndns.update: MONITOR: WAN2GW is down, omitting from routing group Wan1Failover
2016-09-28 16:07:53 Daemon.Error pfsense Sep 28 16:07:53 php-fpm[51147]: /rc.dyndns.update: MONITOR: WAN2GW is down, omitting from routing group Wan2Failover
2016-09-28 16:07:53 Daemon.Error pfsense Sep 28 16:07:53 php-fpm[51147]: /rc.dyndns.update: MONITOR: WAN2GW is down, omitting from routing group Wan1Failover
2016-09-28 16:07:53 Daemon.Error pfsense Sep 28 16:07:53 php-fpm[51147]: /rc.dyndns.update: MONITOR: WAN2GW is down, omitting from routing group Wan2Failover
2016-09-28 16:07:53 Daemon.Error pfsense Sep 28 16:07:53 php-fpm[51147]: /rc.dyndns.update: MONITOR: WAN2GW is down, omitting from routing group Wan1Failover
2016-09-28 16:07:53 Daemon.Error pfsense Sep 28 16:07:53 php-fpm[51147]: /rc.dyndns.update: MONITOR: WAN2GW is down, omitting from routing group Wan2Failover