- Joined
- Mar 18, 2015
- Messages
- 52
- Reaction score
- 11
hi
:
Dec 3 16:15:01 debian3cx CRON[22060]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Dec 3 16:17:01 debian3cx CRON[22089]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Dec 3 16:20:18 debian3cx systemd[1]: 3CXPhoneSystem01.service: Main process exited, code=killed, status=6/ABRT
Dec 3 16:20:18 debian3cx systemd[1]: 3CXPhoneSystem01.service: Unit entered failed state.
Dec 3 16:20:18 debian3cx systemd[1]: 3CXPhoneSystem01.service: Failed with result 'signal'.
Dec 3 16:21:48 debian3cx systemd[1]: Starting Flush Journal to Persistent Storage...
may it caused by this cron task ?
Thank for helping troobleshooting
- 3CX Version, e.g. Standard Annual 16.0.8.9
- Server OS, e.g. Debian 9
- Is the 3CX Server On-premises
- IP Phone Make/Model/Firmware version, e.g. SNOM
- Provisioning Method: Local
- Trunk Provider OpenIP
- Has the Firewall Checker passed: YES
- Are custom Phone Templates being used: NO
:
Dec 3 16:15:01 debian3cx CRON[22060]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Dec 3 16:17:01 debian3cx CRON[22089]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Dec 3 16:20:18 debian3cx systemd[1]: 3CXPhoneSystem01.service: Main process exited, code=killed, status=6/ABRT
Dec 3 16:20:18 debian3cx systemd[1]: 3CXPhoneSystem01.service: Unit entered failed state.
Dec 3 16:20:18 debian3cx systemd[1]: 3CXPhoneSystem01.service: Failed with result 'signal'.
Dec 3 16:21:48 debian3cx systemd[1]: Starting Flush Journal to Persistent Storage...
may it caused by this cron task ?
Thank for helping troobleshooting
