Symptom

A cluster of three vManage instances running version 20.15.4 in a multitenant environment is experiencing increased crash frequency resulting in reboot of system due to ?Software initiated - vdaemon-1 got signal 11? errors. show reboot history REBOOT DATE TIME REBOOT REASON ------------------------------------------------------------------------- 2025-11-11T16:04:45+00:00 Initiated by user - activate 20.15.4 2025-11-17T16:20:03+00:00 Software initiated - vdaemon-1 got signal 11 2025-11-17T16:54:49+00:00 Software initiated - vdaemon-1 got signal 11 2025-11-17T17:33:11+00:00 Software initiated - vdaemon-1 got signal 11 2025-11-17T17:41:46+00:00 Software initiated - vdaemon-1 got signal 11 2025-11-17T18:07:11+00:00 Software initiated - vdaemon-3 got signal 11 The crash files are missing from all the three nodes vmanage01# show crash % No entries found. vmanage01# vshell vmanage01:~$ cd /opt/data/crash/ vmanage01:/opt/data/crash$ ls -l total 0 vmanage02# show crash % No entries found. vmanage02# vshel vmanage02:~$ cd /opt/data/crash/ vmanage02:/opt/data/crash$ ls -l total 0 vmanage03#show crash % No entries found. vmanage03# vshell vmanage03:~$ cd /opt/data/crash/ vmanage03:/opt/data/crash$ ls -l total 0 Following error reported under /var/log/vdebug Nov 17 19:03:42 vmanage01 VDAEMON_3[1774]: vdaemon_json_get_string_value[334]: [VDAEMON_DBG_PKT-3] json_object_get failed for managementSystemIP Nov 17 19:03:42 vmanage01 kernel: vdaemon[1774]: segfault at 0 ip 00007f020ad1fc5b sp 00007ffeaa8544d8 error 4 in libc.so.6[7f020ac3e000+158000] Nov 17 19:03:42 vmanage01 kernel: Code: 48 8d 7c 24 f8 49 39 fa 0f 83 d9 00 00 00 81 f9 ff 00 00 00 0f 87 d3 00 00 00 80 fa 2e 75 6f 41 89 0a 48 83 c0 01 4d 8d 52 04 38 30 0f 84 5c ff ff ff 41 b9 00 00 00 00 bf 0a 00 00 00 0f b6 Nov 17 19:03:43 vmanage01 vScript: trap_cleanup_1: Clean up requested for an invalid dir Nov 17 19:03:43 vmanage01 vScript: trap_cleanup_2: Cleaning up umask Nov 17 19:03:44 vmanage01 vScript: %%Viptela-KERNEL-0-000000: Core file generated /var/crash/core.vdaemon.vmanage01.1774.1763402622 Nov 17 19:03:45 vmanage01 vScript: %%Viptela-KERNEL-0-000000: /var/crash/core.vdaemon.vmanage01.1774.1763402622: Compressing core file done

Conditions

- vDaemon process crashes on in Multitenant vManage Cluster of 3 Instances running version 20.15.4 - Following error reported under /var/log/vdebug prior to crash Nov 17 19:03:42 vmanage01 VDAEMON_3[1774]: vdaemon_json_get_string_value[334]: [VDAEMON_DBG_PKT-3] json_object_get failed for managementSystemIP Nov 17 19:03:42 vmanage01 kernel: vdaemon[1774]: segfault at 0 ip 00007f020ad1fc5b sp 00007ffeaa8544d8 error 4 in libc.so.6[7f020ac3e000+158000] Nov 17 19:03:42 vmanage01 kernel: Code: 48 8d 7c 24 f8 49 39 fa 0f 83 d9 00 00 00 81 f9 ff 00 00 00 0f 87 d3 00 00 00 80 fa 2e 75 6f 41 89 0a 48 83 c0 01 4d 8d 52 04 38 30 0f 84 5c ff ff ff 41 b9 00 00 00 00 bf 0a 00 00 00 0f b6 - The system will then goes into reboot state vmanage01 SYSMGR[1049]: get_reboot_reason[1428]: %SYSMGR_DBG_MAIN-1: Reboot reason: Software initiated - vdaemon-3 got signal 11

Workaround

None

Further Problem Description