- Joined
- Apr 3, 2024
- Messages
- 2
- Reaction score
- 0
Morning.
I have three clients who, this morning, all have the same symptoms. PBX will not function at all. No voice, no extensions, no calls in/out, no Web interface - nothing.
All hosted on Google Cloud, deployed using Marketplace. All PBXs are over a year old and are set up to receive automatic updates on Sunday. All PBXs are on V20.
From SSH console, when running sudo 3CXStartServices, I receive the following error:
Job for 3CXEventNotificationManager.service failed because a fatal signal was delivered causing the control process to dump core.
(and then several lines of errors showing the remaining services failing to start due to dependence on the first service)
I can't start any of the services manually, they fail with A dependency job for [servicename] failed. See 'journalctl -xe' for details.
Any assistance is appreciated. A full dump of the journal entry is below:
Oct 14 12:12:53 tcx-phone-system-3-vm systemd[1]: Starting 3CXEventNotificationManager.service - 3CX Event Notification Manager...
░░ Subject: A start job for unit 3CXEventNotificationManager.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit 3CXEventNotificationManager.service has begun execution.
░░
░░ The job identifier is 5066.
Oct 14 12:12:55 tcx-phone-system-3-vm systemd[1]: 3CXEventNotificationManager.service: Main process exited, code=dumped, status=6/ABRT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit 3CXEventNotificationManager.service has exited.
░░
░░ The process' exit code is 'dumped' and its exit status is 6.
Oct 14 12:12:55 tcx-phone-system-3-vm systemd[1]: 3CXEventNotificationManager.service: Failed with result 'core-dump'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit 3CXEventNotificationManager.service has entered the 'failed' state with result 'core-dump'.
Oct 14 12:12:55 tcx-phone-system-3-vm systemd[1]: Failed to start 3CXEventNotificationManager.service - 3CX Event Notification Manager.
░░ Subject: A start job for unit 3CXEventNotificationManager.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit 3CXEventNotificationManager.service has finished with a failure.
░░
░░ The job identifier is 5066 and the job result is failed.
Oct 14 12:12:55 tcx-phone-system-3-vm systemd[1]: 3CXEventNotificationManager.service: Consumed 1.322s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit 3CXEventNotificationManager.service completed and consumed the indicated resources.
I have three clients who, this morning, all have the same symptoms. PBX will not function at all. No voice, no extensions, no calls in/out, no Web interface - nothing.
All hosted on Google Cloud, deployed using Marketplace. All PBXs are over a year old and are set up to receive automatic updates on Sunday. All PBXs are on V20.
From SSH console, when running sudo 3CXStartServices, I receive the following error:
Job for 3CXEventNotificationManager.service failed because a fatal signal was delivered causing the control process to dump core.
(and then several lines of errors showing the remaining services failing to start due to dependence on the first service)
I can't start any of the services manually, they fail with A dependency job for [servicename] failed. See 'journalctl -xe' for details.
Any assistance is appreciated. A full dump of the journal entry is below:
Oct 14 12:12:53 tcx-phone-system-3-vm systemd[1]: Starting 3CXEventNotificationManager.service - 3CX Event Notification Manager...
░░ Subject: A start job for unit 3CXEventNotificationManager.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit 3CXEventNotificationManager.service has begun execution.
░░
░░ The job identifier is 5066.
Oct 14 12:12:55 tcx-phone-system-3-vm systemd[1]: 3CXEventNotificationManager.service: Main process exited, code=dumped, status=6/ABRT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit 3CXEventNotificationManager.service has exited.
░░
░░ The process' exit code is 'dumped' and its exit status is 6.
Oct 14 12:12:55 tcx-phone-system-3-vm systemd[1]: 3CXEventNotificationManager.service: Failed with result 'core-dump'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit 3CXEventNotificationManager.service has entered the 'failed' state with result 'core-dump'.
Oct 14 12:12:55 tcx-phone-system-3-vm systemd[1]: Failed to start 3CXEventNotificationManager.service - 3CX Event Notification Manager.
░░ Subject: A start job for unit 3CXEventNotificationManager.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit 3CXEventNotificationManager.service has finished with a failure.
░░
░░ The job identifier is 5066 and the job result is failed.
Oct 14 12:12:55 tcx-phone-system-3-vm systemd[1]: 3CXEventNotificationManager.service: Consumed 1.322s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit 3CXEventNotificationManager.service completed and consumed the indicated resources.