Support Center > Search Results > SecureKnowledge Details
RouteD daemon crashes several minutes after shutting down an interface on the Active ClusterXL member Technical Level
Symptoms
  • RouteD daemon crashes several minutes after shutting down an interface on the Active ClusterXL member:

    • Scenario 1:
      1. Configure ClusterXL as "Primary Up" ('Switch to higher priority Cluster Member').
      2. Shut down an interface on the Active member.
      3. Wait for failover to complete.
      4. After several minutes, the RouteD daemon crashes.


    • Scenario 2:
      1. Configure ClusterXL as "Primary Up" ('Switch to higher priority Cluster Member').
      2. Shut down an interface on the Active member.
      3. Wait for failover to complete.
      4. Reboot the member with the shut down interface.
      5. After the rebooted member goes up it becomes Active, and the RouteD daemon crashes.


  • RouteD core dump file shows the following stack:

    Core was generated by `/bin/routed -i default -f /etc/routed0.conf -h 1'.
    Program terminated with signal 11, Segmentation fault.

    #0 0x... in cpcl_vrf_master_send_vrf_finish ()
    (gdb) bt
    #0 0x... in cpcl_vrf_master_send_vrf_finish ()
    #1 0x... in task_timer_dispatch ()
    #2 0x... in main ()
    (gdb)
Cause

When the cluster peer is unstable, it keeps on resetting connections to TCP port 2010. The problem occurs because member is waiting for timer to fire to send out the VRF number, but meanwhile the peer resets. Therefore, pointer to the peer becomes invalid.


Solution
 Note: To view this solution you need to Sign In .