[systemd-devel] Custom systemctl service issue
Ricardo
mcgrathricardol at gmail.com
Sun Mar 10 20:14:39 UTC 2024
On a custom systemctl service, when start service it seems starting without
any message, but when it check by journalctl command it reporter as Failure.
But if manually run service program it starts without any problem and
message.
The bellow is program to execute as service, which have work without any
problems on previous linux service.
# asterisk
# asterisk -rx "core stop now"
# systemctl start asterisk.service
#
# journalctl -xe |grep asterisk
-- Subject: Unit asterisk.service has finished start-up
-- Unit asterisk.service has finished starting up.
Mar 10 10:20:15 localhost.localdomain asterisk[1536]: ASTdb initialization
failed. ASTERISK EXITING!
Mar 10 10:20:15 localhost.localdomain asterisk[1536]: Unable to open
Asterisk database '/var/lib/asterisk/astdb.sqlite3': unable to open
database file
Mar 10 10:20:15 localhost.localdomain systemd[1]: asterisk.service: main
process exited, code=exited, status=1/FAILURE
Mar 10 10:20:15 localhost.localdomain systemd[1]: Unit asterisk.service
entered failed state.
Mar 10 10:20:15 localhost.localdomain systemd[1]: asterisk.service failed.
Tks
Ricardo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20240310/c8d22bbc/attachment.htm>
More information about the systemd-devel
mailing list