If I’m logged into the Supermon and use the button “AST STOP” it stops the Asterisk manager as expected. Then I use “AST START” I see that it runs the command “/bin/sh /usr/sbin/safe_asterisk” at which point the Supermon become non responsive.
If I look at httpd:
asterisk]# systemctl status httpd
- httpd.service - Apache Web Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)
Active: active (running) since Mon 2023-11-27 12:49:45 EST; 9min ago
Main PID: 294 (httpd)
Tasks: 59 (limit: 512)
CGroup: /system.slice/httpd.service
|- 294 /usr/bin/httpd -k start -DFOREGROUND
|- 320 /usr/bin/httpd -k start -DFOREGROUND
|- 321 /usr/bin/httpd -k start -DFOREGROUND
|- 322 /usr/bin/httpd -k start -DFOREGROUND
|- 323 /usr/bin/httpd -k start -DFOREGROUND
|- 324 /usr/bin/httpd -k start -DFOREGROUND
|- 772 /usr/bin/httpd -k start -DFOREGROUND
|- 832 /usr/bin/httpd -k start -DFOREGROUND
|- 874 /usr/bin/httpd -k start -DFOREGROUND
|-1795 /usr/bin/httpd -k start -DFOREGROUND
|-1796 /usr/bin/httpd -k start -DFOREGROUND
|-1797 /usr/bin/httpd -k start -DFOREGROUND
|-1969 /bin/sh /usr/sbin/safe_asterisk
`-1971 /usr/local/hamvoip-asterisk/sbin/asterisk -f -vvvg -c
If I kill the process for safe_asterisk everything returns to normal.
It seems that safe_asterisk keeps running and causes things to lock up, Supermon web interface will not load until I kill the save_asterisk process.
This happens anytime I attempt to start or restart the AST process via the supermon interface.
3 posts - 2 participants