Update Failed ID 10010 > 18.0.8.939 to 18.0.9.20 18.0 (Build 20)

Status
Not open for further replies.

dean_fc

Premier Customer
Joined
Oct 16, 2023
Messages
2
Reaction score
0
We have a self-hosted 3CX system on an AWS Linux server which failed to update and we need to determine the root cause.

We were using version 18.0.8.939 and the system detected that a new version was available.
The services received a signal to stop and was then unresponsive.

We manually rebooted the server and manually restarted the services, which generated the following event in the logs

3CX failed to update.

3CX Phone System Management Console ID: 10010

We ran the following command
sudo dpkg -- configure

Which caused the update to finish successfully.

Unfortunately, our phone system was unavailable for approx 12 hours due to the failed update and we are required to investigate the root cause to ensure it does not occur again.

We have not received an email describing the update failure.

How do we determine the root cause?
 
You didn't receive an emailed log?
I have seen similar and received emailed log file which clearly showed it stopped the upgrade due to insufficient system resources which makes sense because that instance runs on a 1GB and 1vCPU AWS lightsail instance and the upgrade needs at least 2GB and 2 vCPU's per 3CX.

Other systems with sufficient system resources have been fine.
 
  • Like
Reactions: N_G
Hi Aarond,

Thanks for your reply. No, we did not receive an emailed log file.

Our system uses a t3.medium on AWS which has 2 CPUs and 4GB of RAM so we don't suspect that insufficient resources are the cause.
 
Status
Not open for further replies.

Forum statistics

Threads
111,974
Messages
590,081
Members
164,899
Latest member
mazet