log files to look at when 3cx v18 freezes

[ray gershon]

I am self hosting on AWS Lightsail. My pbx froze last night at 10:42pm. I couldn't even get to the webpage for the management consoIe. (webpage not found) Rebooting my instance on Lightsail brought everything back up. . What log file would be best to look at to see what might have happened?

 

[VasilisV_3CX]

Hi @ray gershon,

Would it be that the the OS froze or only the PBX?

 

[ray gershon]

That is a good question. The lightsail instance was showing up and running so I assumed the OS was ok. (Im still new to all this so forgive me). If I connect to the instance using SSH is there anything I should look for?

 

[VasilisV_3CX]

Hi @ray gershon,

I'd have a look for any 3CX services not running at the time. If one is down, restart the service. Let's see if that works.

 

[ray gershon]

All services are up right now. I couldn't get to the management console webpage when the pbx was down. Url was not found. That's why I had to restart the aws lightsail instance. I wonder if an update was released last night that might have caused everything to hang.
Updates are checked daily between 10 and 11pm on my system.

 

[VasilisV_3CX]

I'd say monitor this and if it happens again, first check if you have SSH access and check the services. Let me know if anything else goes down this weekend.

 

[ray gershon]

Sounds good. Thank you. Just to verify, the Linux command to check services is "service 3cx* status" ?

 

[VasilisV_3CX]

Hi @ray gershon,

I'd use "service 3* status" to ensure it catches everything.

 

[ray gershon]

Thanks

 

[Alphabetic]

If its the first time I would ignore but but if it happened again then start the troubleshooting.

You should also check disk space.

 

[ray gershon]

I was going through the logs and it looks like there was an unattended upgrade at the moment the system froze.
Log started: 2021-10-28 22:42:04
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 36688 files and directories currently installed.)
Preparing to unpack .../libdns-export1104_1%3a9.11.5.P4+dfsg-5.1+deb10u6_amd64.deb ...
Unpacking libdns-export1104 (1:9.11.5.P4+dfsg-5.1+deb10u6) over (1:9.11.5.P4+dfsg-5.1+deb10u5) ...
Setting up libdns-export1104 (1:9.11.5.P4+dfsg-5.1+deb10u6) ...
Processing triggers for libc-bin (2.28-10) ...
Log ended: 2021-10-28 22:42:06

Log started: 2021-10-28 22:42:06
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 36688 files and directories currently installed.)
Preparing to unpack .../libisc-export1100_1%3a9.11.5.P4+dfsg-5.1+deb10u6_amd64.deb ...
Unpacking libisc-export1100:amd64 (1:9.11.5.P4+dfsg-5.1+deb10u6) over (1:9.11.5.P4+dfsg-5.1+deb10u5) ...
Setting up libisc-export1100:amd64 (1:9.11.5.P4+dfsg-5.1+deb10u6) ...
Processing triggers for libc-bin (2.28-10) ...
Log ended: 2021-10-28 22:42:07

 

[VasilisV_3CX]

Hi @ray gershon,

Are you sure that the PBX was down at the time or was the OS itself down during the update?

If you navigate to /var/log you'll find all the logs you'll need to investigate further. Note that it keeps a 7 day record, so you're still in luck right now. You could have a look at the syslog.3.gz file which should contain Friday's logs. I'd suggest copying the entire folder so you don't lose anything you may need.