Incorrect system time after deployment to Google cloud

Status
Not open for further replies.

LiscardGP

Customer
Basic Certified
Joined
Sep 29, 2011
Messages
73
Reaction score
1
I have recently moved our PBX from a local Windows 10 machine into Google cloud running on debian.

Since completing the migration our incoming calls have not been directed appropriately.

I have discoverd that the debian system time is running 20 minutes behind the time zone (London) specified during the migration proedure.

I have two questions:-

1) Did I do something wrong as I do not recollect time settings being a consideration following the 3CX migration procedures using PBX express?

2) What's the best way to correct the time and ensure it stays accurate.

Thanks in advance for any replies.

3CX 8 seat Professional
Google cloud - debian 9 installed using 3CX PBX express
 
Hi Liscard,

On Debian-based installs, we control the PBX and OS timezone via the PBX settings page, if you deployed using our ISO.

If not, then you will have to look into the Debian side of things and manage time by yourself. This is more of a Debian related question than a 3CX question and that's the best direction to ask your question.
 
Hi

Thank you for the prompt reply.

I deployed using the 3CX IOS as I am not an expert in Debian.

So this is a 3CX problem. Any solutions please?
 
I would say that this is not a 3CX issue if the time is off by 20 mins.

You will have to look into learning some basic Debian management, or get someone who is familiar to help you check the machine's time and ensure that it can reach an NTP to automatically keep it's own time updated.
 
OK . That's a brush off as clearly this is a 3CX issue as I have simply followed the 3CX instructions :)

There was no variation from the standard 3CX instructions.

Does anyone else have something helpful to add before I start learning debian? :)
 
No it is not a brush off Liscard, the VM keeps the time via the OS.

The OS passes the time on to applications

3CX is an application, not an OS.

Hence, a good starting point is to check the VM time, and update it using the tools the OS provides.

To clarify, 3CX will manage the timezone for you, but it will not fix the actual clock for you.

I hope the above was more clear :)
 
OK JohnS_3CX. Try not to be quite so condesending please.:(

I have used linux and windows platforms and I am fully aware of the differnce between 3CX and an OS!

I have also been using 3CX for about 10 years so I think I have a resonable knowledge base and I am dissapointed by concesending comments like " 3CX is an application, not a OS"! I am also fully aware 3CX gets gets the time form the system clock.

To be clear. The debian OS ships with the 3CX install package. I presume it has been fine tuned to support the 3CX application and it is not clear whether it is "locked down" in any way by 3CX. Can I just SSH into my google instance and expect it to respond like standard Debian 9?

As such 3CX should accept some responsibility when the package it provides does not result in a satisfactory deployment.

In this case the 3CX debian based package has installed with an incorrect system time. I failthfully followed the 3CX instructions and it took me some time to track down the cause of the problems this has caused running my PBX. Having alerted 3CX to the issue, I would have thought 3CX might want to investigate the issue at least to ascertain the inteity of the debian install package.

So if anyone has a helpful answer it would be most appreciated. I promise to treat all responses with respet and careful consideration.

For now I am simply going to reboot the instance when my buisness is closed. Hopefully that will solve the problem.

If that does not work I will SSH into the instance and check out the NTP settings.

Any other helpful advice would be appreciated.
 
SOLVED

I decide to take path of least resistance.

1) backed up PBX
2) released FQDN
3) deleted cloud instance
4) Deployed for second time to google cloud
5) restored backup

System time correct and 3CX working correctly.

Who knows why it happened. I just hope it does not recur!
 
  • Like
Reactions: Evolute IT
Hi Liscard,

For the record, I made no assumptions about your level of knowledge, since I often respond to members that have anything from zero experience all the way up to members who are SIP and Linux gurus.

I was sorry to hear you got that impression, sometimes text replies may come across as wrong in a less than personal medium such as a web forum.

I'm also very glad to hear that the issue has been resolved, and if it happens again I will be glad to share any additional resources and knowledge I have on the subject.
 
  • Like
Reactions: MidiTélécom
Status
Not open for further replies.

Forum statistics

Threads
111,856
Messages
589,404
Members
164,693
Latest member
FLCC