Solved Upgrade to version 18 failed

Status
Not open for further replies.

rubendebeuze

Free User
Joined
Apr 15, 2022
Messages
8
Reaction score
1
Hello,

When i want to update to version 18 from gui i get an error mail: 3CX attempted to update your 3CX Debian OS at ******.my3cx.nl from Debian 9 to 10 and failed.

When i open the log i see this sudo: a password is required i have cli acces trough this machine does anyone have the update command for the debian migration and upgrade? I guess it is a script that is called when you push the upgrade button in gui.

I have my 3cx hosted in Azure
 
Hi!

How did you initially installed your 3CX system? Was using PBX Express/Configuration Wizard, or marketplace image?

Also how did you initialize the OS upgrade, was it from the Management Console?

Can you also attach the update.log attached to the email you receive so we can have a look?
 
Hi Nick,

Initially installed 3CX form marketplace image. Ater that did al the updates trough the gui.
 
OK, can you also attach the update.log attached to the email you receive so we can have a look?
 
Only this rule is in the attached log file

sudo: a password is required
 
Have you ever made any changes to the /etc/sudoers file?
This is as if the "phonesystem" user cannot run the script to upgrade the OS as "sudo".
 
No not to the sudoers file only once i have lost the ssh password and reset it trough reset password section in the azure VM
 
Then I'm not sure what has caused this, but at this point it may be faster and easier to just create a new instance.

If your full backup is <1GB, what you could do is:
  1. Take a full backup and download it to your local PC
  2. Power down this instance
  3. Re-deploy a new instance in Azure using our Configuration Wizard:
    https://www.3cx.com/docs/hosting-pbx-phone-system-microsoft-azure/
  4. Restore the backup during the process
 
  • Like
Reactions: Evolute IT
Oke Thankyou is will do that. Thans for the quick support!
 
  • Like
Reactions: NickD_3CX
Sure thing!

I'll leave the thread unlocked in case you run into anything else you want to ask. :)
 
Enployment goes well even the restore of the backup. But is roll out in a other resource group and other virtual network can i choose fot that before enrollement as well? I need the same virtual network and same ip because of my ip sec tunnel
 
Unfortunately from the deployment wizard you can't select resource groups, but alternatively you can re-create you instance using the marketplace image.

Instructions for this are here:
https://www.3cx.com/docs/pbx-azure-marketplace/

You can still restore your backup this way.
 
Ok did it and machine work but i didn't get any gui when go to the external or internal ip of the machine. I can ping the local ip and can ssh in it but didn't get it to work in browser.
 
Ok did it and machine work but i didn't get any gui when go to the external or internal ip of the machine. I can ping the local ip and can ssh in it but didn't get it to work in browser.
After you follow the instructions in the guide, did you follow the last 2 steps:
  1. Copy the “Public IP address” for your new VM and open it followed by port 5015 in a browser, e.g.
    http://8.8.8.8:5015
    .
  2. Use the First Time Configuration Wizard guide for step by step instructions on configuring your 3CX PBX.

Also, make sure you do the instructions pointed out in this note:

Note: Due to a restriction of Azure on waagent and cloud-init on marketplace images, the swap file must be created manually after creation of the machine. SSH to your machine and proceed as explained here.
 
Not sure what the problem was delete the vm and roll out a new one form market place and it works!

So now i have restored the backup and full online with version 18!

Thankyou very much for your support!
 
Excellent, glad you got everything up and running!

I'll mark this one as 'Solved'.
 
Status
Not open for further replies.

Forum statistics

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