RouteD daemon might crash on cluster member when PIM Sparse Mode multicast is configured and multicast traffic arrives from peer cluster member
||R75.40, R75.40VS, R75.45, R75.46, R75.47, R76, R77, R77.10, R77.20
|Platform / Model
RouteD daemon might crash on cluster member when PIM Sparse Mode multicast is configured and multicast traffic arrives from peer cluster member.
After enabling generation of core dump files per sk92764, core dump files for 'RouteD' process were generated in the /var/log/dump/usermode/ directory.
If the state of ClusterXL Standby member is administratively changed to "Down" with "clusterXL_admin down" command (refer to sk55081) and then changed back to "Up" with "clusterXL_admin up" command, it is possible that the RouteD on the Standby member will crash with core dump file.
During such issue, the output of "cphaprob -ia list" command will show that the Critical Device "routed" reports its status as "problem".
RouteD core dump file contains the following stack:
Core was generated by `/bin/routed -i 1 -f /etc/routed1.conf -h 1'.
Program terminated with signal 6, Aborted.
#0 0x... in __kernel_vsyscall ()
#1 0x... in __kernel_vsyscall ()
#1 0x... in raise () from /lib/libc.so.6
#2 0x... in abort () from /lib/libc.so.6
#3 0x... in task_quit ()
#4 0x... in task_assert ()
#5 0x... in ptree_insert ()
#6 0x... in pim_cluster_sm_recv_sg_state ()
#7 0x... in pim_cluster_sm_recv ()
#8 0x... in pim_cluster_recv ()
#9 0x... in ipsrd_cluster_process_recvd_app_msgs ()
#10 0x... in task_timer_dispatch ()
#11 0x... in main ()
PIM-SM during transitional stages might receive sync information before system has fully initialized.
Note: To view this solution you need to