xxx.az.3cx.us DNS is offline

[Bob Denny]

Thanks so much! As you may have concluded from my writing, I do enjoy learning new things. I also do already have a fresh full backup including license on my GDrive - one of V15.5 SP6 which also now shows the correct expiry date on my recently renewed license (it was a year out of date). I may try to have a go at fixing the Jessie deps.

I just wonder how my Debian got into such bad shape in the first place (the multiple issues we overcame thanks to your help!!). This system has automatically updated itself all the way from the original new GCloud instance -> PBX Express 15.0 SP5 (8 auto updates) through 15.5 SP4, hands-off, as far as I can tell. What happened? I haven't even SSH-logged into that system for ages.

By the way, the PBX Express is really well done.

WIth my switch running, I will likely defer the OS upgrade to the weekend.

PS the Stackexchange article looks spot on, thanks for that also. There are a couple of others linked from there, one on SuperUser. I ought to be able to get things going with that info.

 

[NickD_3CX]

The problems you had were mainly focus around 3 areas:

• The 3CX repository being wrong: that I am not sure how it got there, but we'll skip this one
• The Google SDK repository throwing an error: this is related due to the fact that you had created the instance a long time ago: https://cloud.google.com/compute/docs/troubleshooting/known-issues#keyexpired
  Google has since fixed newer ISOs so this doesn't happen any more.
• Some other repositories are failing: this is not your fault, they existing Debian repositories have just changed as mentioned in the link I sent you. The only thing you could have done is upgraded to Debian 9 Stretch sooner.

 

[Bob Denny]

I'm starting to see the light. Your script had the rug pulled out from under it by the move of the backport repos. I'm going to see if I can get this to work. Thanks for all of the help! Both of you have been so helpful, and on a short turnaround.

Looks like I missed it by only a few weeks!

https://superuser.com/a/1417656/21840

 

[Bob Denny]

I'm hoping to do the Debian 9 thing sometime soon, but the spectre of a dead phone system is too much. It's running now without problems. Some things about Linux are so aggravating.

 

[BrenttG]

It really isnt as hard as it sounds, the majority of it is all wizard based. And like was said, do a new VM, dont install over the old one, so that if you fail, you can just turn the old one back on, if you succeed, then just delete the old one. always a way back to operational, we always roll VMs this way, or do snapshots.

 

[Bob Denny]

Sumething about I have to sudo-edit indexes and lists because components used by the Debian 8-9 script have been moved from one place in the cloud to another (to an "archive" location)? It seems I wanted too long to upgrade, and the Debian devs/admins moved stuff offline. See Nick's reply above, and the preceding messages in this thread. Clicking this button fails every time:



The upgrade failed left and right for me but miraculously during my failed attempts the 3CX switch itself upgraded to its current version so I got my FQDN back seemingly magically. So here I am on Debian 8 with a running 3CX. I'm tempted to just wait till it dies for some other reason before risking scorching the Linux instance. Again I am no way any sort of Linux sysadmin expert.