1. Home
  2. pfSense® Software
  3. HA/CARP/VIPs
  4. CARP : MASTER -> BACKUP (more frequent advertisement received)

CARP : MASTER -> BACKUP (more frequent advertisement received)

  • G

    Hello,
    I have a problem with my pfSense cluster.
    From time to time a have a message

    
carp: VHID 2@em3: MASTER -> BACKUP (more frequent advertisement received)
carp: VHID 2@em3: BACKUP -> MASTER (master down)
ovpns1: link state changed to DOWN
ovpns4: link state changed to DOWN
ovpns1: link state changed to UP
ovpns4: link state changed to UP

    After this, my OpenVPN tunnels are reconnected. Its very annoying.

    I already tried to changed network card - from build it - Broadcom to Intel Quad  PRO/1000 (It's DELL R710 Server) but doesn't help me.

    Also I tunned my cofing

    
kern.cam.boot_delay=10000
kern.ipc.nmbclusters="1000000"
hw.bce.tso_enable=0
hw.pci.enable_msix=0

    Another thing was connect network card directly to Internet Router , without switch. I don't have disconnection for 5 days, but yesterday I got this same error message :/

    In my configuration I have 8 network in Carp and only one : WAN2 is problematic.

    Any idea what to do?

    
Jan 10 23:26:59	kernel: carp: VHID 2@em3: MASTER -> BACKUP (more frequent advertisement received)
Jan 10 23:26:59	check_reload_status: Carp backup event
Jan 10 23:27:00	php-fpm: /rc.carpbackup: Carp cluster member "176.xx.xx.90 - WAN2 CARP VIP (2@em3)" has resumed the state "BACKUP" for vhid 2@em3
Jan 10 23:27:02	kernel: carp: VHID 2@em3: BACKUP -> MASTER (master down)
Jan 10 23:27:02	check_reload_status: Carp master event
Jan 10 23:27:03	php-fpm: /rc.carpmaster: Carp cluster member "176.xx.xx.90 - WAN2 CARP VIP (2@em3)" has resumed the state "MASTER" for vhid 2@em3
Jan 10 23:27:03	php-fpm: /rc.carpmaster: Starting OpenVPN instance on 176.xx.xx.90 - WAN2 CARP VIP because of transition to CARP master.
Jan 10 23:27:03	kernel: ovpns1: link state changed to DOWN
Jan 10 23:27:03	check_reload_status: Reloading filter
Jan 10 23:27:04	check_reload_status: Reloading filter
Jan 10 23:27:04	php-fpm: /rc.carpmaster: Starting OpenVPN instance on 176.xx.xx.90 - WAN2 CARP VIP because of transition to CARP master.
Jan 10 23:27:04	kernel: ovpns4: link state changed to DOWN
Jan 10 23:27:04	kernel: ovpns1: link state changed to UP
Jan 10 23:27:04	check_reload_status: rc.newwanip starting ovpns1
Jan 10 23:27:04	kernel: ovpns4: link state changed to UP
Jan 10 23:27:04	check_reload_status: rc.newwanip starting ovpns4
Jan 10 23:27:05	php-fpm[39493]: /rc.newwanip: rc.newwanip: Info: starting on ovpns1.
Jan 10 23:27:05	php-fpm[39493]: /rc.newwanip: rc.newwanip: on (IP address: 172.31.55.1) (interface: []) (real interface: ovpns1).
Jan 10 23:27:05	check_reload_status: Reloading filter
Jan 10 23:27:05	php-fpm[39493]: /rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - -> 172.31.55.1 - Restarting packages.
Jan 10 23:27:05	check_reload_status: Starting packages
Jan 10 23:27:05	php-fpm[39493]: /rc.newwanip: rc.newwanip: Info: starting on ovpns4.
Jan 10 23:27:05	php-fpm[39493]: /rc.newwanip: rc.newwanip: on (IP address: 172.31.65.1) (interface: []) (real interface: ovpns4).
Jan 10 23:27:05	php-fpm[39493]: /rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - -> 172.31.65.1 - Restarting packages.
Jan 10 23:27:05	check_reload_status: Starting packages
Jan 10 23:27:06	php-fpm: /rc.start_packages: Restarting/Starting all packages.
Jan 10 23:27:06	php-fpm[39493]: /rc.start_packages: Restarting/Starting all packages.
Jan 10 23:27:06	php-fpm[39493]: /rc.start_packages: Reloading syslog-ng for configuration sync
Jan 10 23:27:06	php-fpm: /rc.start_packages: Reloading syslog-ng for configuration sync
Jan 10 23:27:06	supervise/syslog-ng[43434]: Daemon exited gracefully, not restarting; exitcode='0'
Jan 10 23:27:11	php-fpm[39493]: /rc.start_packages: The command '/usr/local/etc/rc.d/syslog-ng.sh stop' returned exit code '1', the output was ''
Jan 10 23:27:11	php-fpm: /rc.start_packages: The command '/usr/local/etc/rc.d/syslog-ng.sh stop' returned exit code '1', the output was ''
Jan 10 23:27:13	check_reload_status: Syncing firewall
Jan 10 23:27:13	check_reload_status: Reloading filter
Jan 10 23:27:13	php-fpm: /rc.start_packages: Reloading syslog-ng for configuration sync
Jan 10 23:27:13	supervise/syslog-ng[59756]: Daemon exited gracefully, not restarting; exitcode='0'
Jan 10 23:27:13	check_reload_status: Syncing firewall
Jan 10 23:27:13	check_reload_status: Reloading filter
Jan 10 23:27:13	php-fpm[39493]: /rc.start_packages: Starting syslog-ng
Jan 10 23:27:14	php-fpm: /rc.filter_synchronize: Beginning XMLRPC sync to https://172.16.1.3:443.
Jan 10 23:27:14	check_reload_status: Syncing firewall
Jan 10 23:27:14	check_reload_status: Reloading filter
Jan 10 23:27:14	php-fpm[39493]: /rc.start_packages: Checked cron job for /bin/kill -HUP `cat /var/run/bandwidthd.pid`, no change needed
Jan 10 23:27:14	bandwidthd: Monitoring subnet 255.255.255.0 with netmask 255.255.255.0
Jan 10 23:27:14	bandwidthd: Monitoring subnet 255.255.255.224 with netmask 255.255.255.224
Jan 10 23:27:14	bandwidthd: Monitoring subnet 255.255.255.0 with netmask 255.255.255.0
Jan 10 23:27:14	bandwidthd: Monitoring subnet 255.255.255.0 with netmask 255.255.255.0
Jan 10 23:27:14	bandwidthd: Monitoring subnet 255.255.255.0 with netmask 255.255.255.0
Jan 10 23:27:14	bandwidthd: Monitoring subnet 255.255.255.0 with netmask 255.255.255.0
Jan 10 23:27:14	bandwidthd: Monitoring subnet 255.255.255.224 with netmask 255.255.255.224
Jan 10 23:27:14	bandwidthd: Monitoring subnet 255.255.255.0 with netmask 255.255.255.0
Jan 10 23:27:14	bandwidthd: Monitoring subnet 255.255.255.0 with netmask 255.255.255.0
Jan 10 23:27:14	bandwidthd: Monitoring subnet 255.255.255.0 with netmask 255.255.255.0
Jan 10 23:27:14	bandwidthd: Monitoring subnet 255.255.255.224 with netmask 255.255.255.224
Jan 10 23:27:14	bandwidthd: Monitoring subnet 255.255.255.0 with netmask 255.255.255.0
Jan 10 23:27:14	bandwidthd: Monitoring subnet 255.255.255.0 with netmask 255.255.255.0
Jan 10 23:27:14	bandwidthd: Monitoring subnet 255.255.255.0 with netmask 255.255.255.0
Jan 10 23:27:14	bandwidthd: Monitoring subnet 255.255.255.0 with netmask 255.255.255.0
Jan 10 23:27:14	bandwidthd: Monitoring subnet 255.255.255.224 with netmask 255.255.255.224
Jan 10 23:27:14	bandwidthd: Monitoring subnet 255.255.255.0 with netmask 255.255.255.0
Jan 10 23:27:14	bandwidthd: Monitoring subnet 255.255.255.0 with netmask 255.255.255.0
Jan 10 23:27:14	bandwidthd: Recovering from log.1.2.cdf
Jan 10 23:27:14	php-fpm: /rc.filter_synchronize: XMLRPC sync successfully completed with https://172.16.1.3:443.
Jan 10 23:27:14	bandwidthd: Recovering from log.2.1.cdf
Jan 10 23:27:14	bandwidthd: Recovering from log.3.0.cdf
Jan 10 23:27:14	bandwidthd: Recovering from log.4.0.cdf
Jan 10 23:27:14	bandwidthd: Finished recovering 248 records
Jan 10 23:27:14	bandwidthd: Opening bce3
Jan 10 23:27:14	bandwidthd: Recovering from log.2.1.cdf
Jan 10 23:27:14	bandwidthd: Packet Encoding: Ethernet
Jan 10 23:27:14	bandwidthd: Drawing initial graphs
Jan 10 23:27:14	bandwidthd: Recovering from log.3.0.cdf
Jan 10 23:27:14	bandwidthd: Recovering from log.4.0.cdf
Jan 10 23:27:14	bandwidthd: Recovering from log.1.2.cdf
Jan 10 23:27:14	bandwidthd: Finished recovering 248 records
Jan 10 23:27:14	bandwidthd: Opening bce3
Jan 10 23:27:14	bandwidthd: Packet Encoding: Ethernet
Jan 10 23:27:14	bandwidthd: Drawing initial graphs
Jan 10 23:27:14	bandwidthd: Finished recovering 2910 records
Jan 10 23:27:14	bandwidthd: Opening bce3
Jan 10 23:27:14	bandwidthd: Packet Encoding: Ethernet
Jan 10 23:27:14	bandwidthd: Drawing initial graphs
Jan 10 23:27:14	bandwidthd: Finished recovering 6393 records
Jan 10 23:27:14	bandwidthd: Recovering from log.1.1.cdf
Jan 10 23:27:14	bandwidthd: Finished recovering 2910 records
Jan 10 23:27:14	bandwidthd: Opening bce3
Jan 10 23:27:14	bandwidthd: Packet Encoding: Ethernet
Jan 10 23:27:14	bandwidthd: Drawing initial graphs
Jan 10 23:27:14	bandwidthd: Finished recovering 6393 records
Jan 10 23:27:14	bandwidthd: Recovering from log.1.1.cdf
Jan 10 23:27:14	bandwidthd: Finished recovering 6116 records
Jan 10 23:27:14	bandwidthd: Recovering from log.1.0.cdf
Jan 10 23:27:14	bandwidthd: Finished recovering 10224 records
Jan 10 23:27:14	bandwidthd: Recovering from log.2.0.cdf
Jan 10 23:27:14	bandwidthd: Finished recovering 10224 records
Jan 10 23:27:14	bandwidthd: Recovering from log.2.0.cdf
Jan 10 23:27:14	bandwidthd: Finished recovering 6116 records
Jan 10 23:27:14	bandwidthd: Recovering from log.1.0.cdf
Jan 10 23:27:14	bandwidthd: Finished recovering 4150 records
Jan 10 23:27:14	bandwidthd: Opening bce3
Jan 10 23:27:14	bandwidthd: Packet Encoding: Ethernet
Jan 10 23:27:14	bandwidthd: Drawing initial graphs
Jan 10 23:27:14	bandwidthd: Finished recovering 5958 records
Jan 10 23:27:14	bandwidthd: Opening bce3
Jan 10 23:27:14	bandwidthd: Packet Encoding: Ethernet
Jan 10 23:27:14	bandwidthd: Drawing initial graphs
Jan 10 23:27:14	bandwidthd: Finished recovering 4150 records
Jan 10 23:27:14	bandwidthd: Opening bce3
Jan 10 23:27:14	bandwidthd: Packet Encoding: Ethernet
Jan 10 23:27:14	bandwidthd: Drawing initial graphs
Jan 10 23:27:14	bandwidthd: Finished recovering 5958 records
Jan 10 23:27:14	bandwidthd: Opening bce3
Jan 10 23:27:14	bandwidthd: Packet Encoding: Ethernet
Jan 10 23:27:14	bandwidthd: Drawing initial graphs
Jan 10 23:27:19	check_reload_status: Syncing firewall
Jan 10 23:27:19	check_reload_status: Reloading filter
Jan 10 23:27:25	php-fpm: /rc.filter_synchronize: Filter sync successfully completed with https://172.16.1.3:443.
Jan 10 23:27:25	php-fpm[79431]: /rc.filter_synchronize: Beginning XMLRPC sync to https://172.16.1.3:443.
Jan 10 23:27:25	php-fpm[79431]: /rc.filter_synchronize: XMLRPC sync successfully completed with https://172.16.1.3:443.
Jan 10 23:27:36	php-fpm[79431]: /rc.filter_synchronize: Filter sync successfully completed with https://172.16.1.3:443.
    0
Log in to reply
 

Products

Services

Support

News

Resources

Company

Our Mission

We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

Subscribe to our Newsletter

Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

© 2020 Rubicon Communications, LLC | Privacy Policy