Null cache in statis_cache : segfault

Hi Team,

we are using asterisk 13 and at one of our customers we are experiencing the segfault in non calling hours.
As checked from the core dump file created at that time we can see that the cache was null at that time :
backtracre and other details checked :
(gdb) bt
#0 0x00000000005e0950 in stasis_cache_dump_by_eid ()
#1 0x00000000005e099a in stasis_cache_dump ()
#2 0x00000000004d8a9f in handle_chanlist ()
#3 0x00000000004df062 in ast_cli_command_full ()
#4 0x00000000004df1c6 in ast_cli_command_multiple_full ()
#5 0x00000000004564cd in netconsole ()
#6 0x000000000060cb70 in dummy_start ()
#7 0x00007fd11440add5 in start_thread () from /lib64/
#8 0x00007fd1137afead in clone () from /lib64/
(gdb) frame 0
#0 0x00000000005e0950 in stasis_cache_dump_by_eid ()
(gdb) p cache
$1 = 0
(gdb) p *cache
Cannot access memory at address 0x0

In messages :
May 10 05:30:34] ERROR[36921] manager.c: Unable to process manager action ‘Ping’. Asterisk is shutting down.
[May 10 05:30:47] Asterisk certified/13.21 built by root @ cbm on a x86_64 running Linux on 2020-06-15 17:14:24 UTC

Can you please help us in knowing that in which all possible scenarios this cache can be null ?

It’s likely NULL because Asterisk is shutting down and the resources were freed during that process. Why it is shutting down, no idea.

Thanks @jcolp for your input.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.