Update to v8 failed

[Andriy]

Dear community

I have two installations of 3CX on two separate AWS instances
One updated to v8 without any problems and the other gives UPDATE FAILED error every time.

Could you please guide me hw do I troubleshoot this? I cant find anything that is wrong with my installation or server
here is the log I am getting:

Hit:1 http://security.debian.org/debian-security stretch/updates InRelease
Ign:2 http://cdn-aws.deb.debian.org/debian stretch InRelease
Hit:3 http://cdn-aws.deb.debian.org/debian stretch-updates InRelease
Hit:4 http://cdn-aws.deb.debian.org/debian stretch Release
Hit:5 http://ftp.debian.org/debian stable InRelease
Hit:7 http://downloads-global.3cx.com/downloads/debian stretch-testing InRelease
Ign:8 http://ftp.de.debian.org/debian jessie InRelease
Hit:9 http://downloads-global.3cx.com/downloads/debian stretch InRelease
Hit:10 http://ftp.de.debian.org/debian jessie Release
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
3cxpbx : Depends: libfreeimage3 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
Rollback to 16.0.7.930...
Reading package lists...
Building dependency tree...
Reading state information...
3cxpbx is already the newest version (16.0.7.930).
0 upgraded, 0 newly installed, 0 to remove and 216 not upgraded.

 

[ChrisC_3CX]

From the info you provided it seems you are using both Jessie and Stretch repositories, what is the actual OS 3CX is running on? How was this machine deployed in AWS, did you use the PBXExpress?

Since there seem to be missing dependencies, instead of trying to fix the issue on this specific machine, I would highly recommend taking a backup of 3CX and then restore it to a newly deployed Debian 9 machine to ensure that you do not have similar issues in the future.

 

[Andriy]

Hello Chris

Thank you for suggestion
I think i will do that.

My Actual OS is Debian and I used PBXExpress to install. I also used same thing for my other installation but it installed correctly without problems.

Distributor ID Debian
Description Debian GNU/Linux 9.5 (stretch)
Release:9.5
Codename:stretch

For future - Could you please let me know what are Jessie and Stretch repositories and what is the problem with using them both?

 

[NickD_3CX]

For future - Could you please let me know what are Jessie and Stretch repositories and what is the problem with using them both?

If you install using PBX Express or the 3CX ISO, then you should never have to worry about these.

As you asked though, Jessie and Stretch are Debian version codenames. Jessie refers to Debian 8, Stretch to Debian 9, and now Buster is Debian 10.
The repositories are where Linux downloads its applications from, so if you are running Debian 9, you shouldn't have any Debian 8 repositories.

 

[Andriy]

Thank you very much for your explanation.
i will build a new Debian 10 server and move everything there or maybe move to PBX Express which seems to be much easier option.

I only moved to AWS because there was a short period when 3CX stopped providing PBX express and asked to move to Google or AWS after one year of use.

Thank you

 

[Saqqara]

I would use pbx express, as the setting up of 3cx is taken care off using method

 

[Andriy]

Good to know. I will move to PBXexpress then. I think it uses AWS anywa and will make things easier.

 

[NickD_3CX]

Good to know. I will move to PBXexpress then. I think it uses AWS anywa and will make things easier.

Deploying from PBX Express is your best option in my opinion.
You can find the instructions here: https://www.3cx.com/docs/cloud-pbx-amazon-aws/

After you have created your “Access Key ID”/“Secret Access Key” and “Key Pairs” once as per the guide, deploying new instances will be a breeze, just don't lose these files so you can re-use them.

 

[Andriy]

Hello Nick

Sorry, it has been some time.
Actually, this installation was deployed by PBXexpress. So PBX express has created an AWS instance for me. I only provided “Access Key ID”/“Secret Access Key”

Now I believe i need to reinstall the OS and restore backup. But i am not sure how to do that if I want to keep my original IP address.

Can I ask PBXExpress to reinstall 3CX into the same AWS instance as before?

 

[ChrisC_3CX]

You cannot allocate an IP through PBXExpress, you will have to check if that is possible to do via AWS's Control Panel.

Also, do note that PBX Express deploys a completely new machine with Debian 9 OS already installed and also completes the 3CX Installation. That said, since you used PBXExpress, you should now have a fuld Debian 9 machine that is already running 3CX, you will not need to reinstall anything.

 

[Andriy]

I would leave it as it is, but I as per my first post the update fails all the time.


Hit:1 http://security.debian.org/debian-security stretch/updates InRelease
Ign:2 http://cdn-aws.deb.debian.org/debian stretch InRelease
Hit:3 http://cdn-aws.deb.debian.org/debian stretch-updates InRelease
Hit:4 http://cdn-aws.deb.debian.org/debian stretch Release
Hit:5 http://ftp.debian.org/debian stable InRelease
Hit:7 http://downloads-global.3cx.com/downloads/debian stretch-testing InRelease
Ign:8 http://ftp.de.debian.org/debian jessie InRelease
Hit:9 http://downloads-global.3cx.com/downloads/debian stretch InRelease
Hit:10 http://ftp.de.debian.org/debian jessie Release
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
3cxpbx : Depends: libfreeimage3 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
Rollback to 16.0.7.930...
Reading package lists...
Building dependency tree...
Reading state information...
3cxpbx is already the newest version (16.0.7.930).
0 upgraded, 0 newly installed, 0 to remove and 216 not upgraded.

 

[ChrisC_3CX]

Alright, you could do the following:

1. Go into the Management Console of your current instance. Click on "Backup & Restore >> Backup".

2. Select everything to create a full backup and click on OK.

3. Once the backup is complete, download it to your PC. (an email will be sent to the administrator account once the backup has been completed)

4. Go into AWS and find the instance you are using, shut it down. (do not delete just yet)

5. Access the 3CX customer Portal and go to Keys >> Select a Key >> Self Host. Follow the PBX Express to deploy your new machine on AWS using the same License Key. Note: This will create a brand new VM running 3CX.

6. Upload the backup you created to your FTP, sFTP or Google Bucket Storage space.

7. Access the new 3CX Instance Management Console and go to Backup & Restore >> Location. Configure the FTP, sFTP or Google Bucket Storage space and make sure the backup you uploaded appeared in the backups list.

8. Select the backup and restore.

9. Once you have confirmed everything is in working order, you may proceed with deleting the old VM which you shut down previously.

 

[Andriy]

Thanks for suggestion. I will try it if I can not find a different way to keep my IP address.

My SIP trunk is locked to my current IP address and they say it takes week to change it.

 

[ChrisC_3CX]

I see, in that case I recommend first figuring out if allocating the desired IP to a machine is possible via AWS and if yes, how. Once you know how to do that, you'll be ready to proceed with the procedure I provided previously.

 

[Andriy]

Thank you very much for great advice. I will try that.