Asterisk got abruptly closed the transport ports but asterisk runs actively

Hi everyone,

I currently saw in Asterisk version 16.25.3. where asterisk abrtuply stops listening to the port 5060 in both TCP and UDP

Check the status of the asterisk in systemctl it was in active status

systemctl status asterisk
● asterisk.service - LSB: Asterisk PBX
Loaded: loaded (/etc/init.d/asterisk; generated)
Active: active (exited) since Thu 2026-03-05 11:00:46 IST; 2 weeks 5 days ago
Docs: man:systemd-sysv-generator(8)
CPU: 7h 13min 11.426s

Mar 05 11:00:46  systemd[1]: Starting LSB: Asterisk PBX…
Mar 05 11:00:46 asterisk[64951]:  * Starting Asterisk PBX: asterisk
Mar 05 11:00:46 asterisk[64951]:    …done.
Mar 05 11:00:46 systemd[1]: Started LSB: Asterisk PBX.
Mar 05 11:00:48 asterisk[64964]: radcli: rc_read_config: rc_read_config: can’t open /etc/radiusclient-ng/radiusclient.conf: No such file or directory
Mar 05 11:00:48 asterisk[64964]: radcli: rc_read_config: rc_read_config: can’t open /etc/radiusclient-ng/radiusclient.conf: No such file or directory 

but while looking the port using netstat -tulpn | grep “5060”

~# netstat -tulpn | grep “5060”

it was empty.so we can conclude that asterisk didn’t listening to the ports

I also tried access the Asterisk CLI but this was the output given below:

asterisk -rvvvvvv
Unable to connect to remote asterisk (does /var/run/asterisk/asterisk.ctl exist?)

I wanted to know the root cause of this issue and how to prevent the asterisk from stop closing the port 5060 abruptly ?