- Joined
- Aug 30, 2018
- Messages
- 32
- Reaction score
- 2
I have a handful of Linux based 3CX instances (all on-prem at the customer location) that I am looking to upgrade to v18 within the next 1-2 weeks.
Here is my concern - all of the 3CX instances that I am managing we're all stood up using the non-3CX Debian installer (this was fully driven based on the hardware that I was using, I was unable to get the official 3CX Debian version to install; the install would get to the very end and then just bomb out/stall - this occurred multiple times using different 3CX installers on different hardware). Note: I have been able to use the official 3CX Debian based on v18 on 'new' installs and it seems to work without issue.
My question is this: is it a sure fire guarantee that the v18 automated upgrade will fail on these systems? Please note that the Debian version that was used for these installs was the 'base' version only (I did add SSH services to it but that is all). There are no other 3rd party add-ons and or features enabled on any of these systems.
What is the best way to handle this type of scenario?
Here is my concern - all of the 3CX instances that I am managing we're all stood up using the non-3CX Debian installer (this was fully driven based on the hardware that I was using, I was unable to get the official 3CX Debian version to install; the install would get to the very end and then just bomb out/stall - this occurred multiple times using different 3CX installers on different hardware). Note: I have been able to use the official 3CX Debian based on v18 on 'new' installs and it seems to work without issue.
My question is this: is it a sure fire guarantee that the v18 automated upgrade will fail on these systems? Please note that the Debian version that was used for these installs was the 'base' version only (I did add SSH services to it but that is all). There are no other 3rd party add-ons and or features enabled on any of these systems.
What is the best way to handle this type of scenario?