Good day Team,
I am attempting to migrate from centos to alma.
Running a container on proxmox and situation is, Asterisk does not want to start with systemd.
If I manual start asterisk with asterisk -cccvvvvvvddddd, it starts in 3 seconds.
But if I do systemctl start asterisk.service, it hangs till it times out.
After 4 auto restart asterisk comes alive.
journalctl -xeu asterisk.service,
Just shows attempt to restarts and failing.
There’s nothing being poppulated into logs for the timeout or delay, how would you troubleshoot this? Any suggestions are welcome.
Thanks.
Hi @techjaymindave!
Post the contents of /etc/systemd/system/asterisk.service (or where it’s defined).
Pay special attention to:
- Type = if it’s set to simple, try switching to forking or vice versa depending on how Asterisk behaves.
- ExecStart = make sure it matches your manual command.
- TimeoutStartSec = increase it temporarily to see if that affects behavior.
- StandardOutput = and StandardError = redirect to journal or log files to catch hidden errors.
journalctl -u asterisk.service --since "5 minutes ago"
journalctl -b
Run this in a second shell right after starting the service:
watch 'ps aux | grep asterisk'
All the best! 
hello
I recommend checking /var/log/messages as a starting point, but for systemd services on AlmaLinux, using journalctl -u asterisk.service -b will often provide more detailed error messages. Additionally, check the service unit file for misconfigurations, verify Asterisk’s own logs in /var/log/asterisk/, and consider SELinux status. This combined approach usually helps pinpoint startup issues.