Solved On-prem v18.0 (build 31) to v20 upgrade failed

[Suri]

Hello,

This is our system info:

• Annual Pro v18.0 (Build 31)
• Debian 10
• On-premise

We tried upgrading to v20 yesterday via management console but it failed due to the attached error. I assume this is the part that errored:

"/bin/sed: can't read /etc/apt/sources.list.d/*: No such file or directory"

Is there any extra step needed to be done before upgrading?

Thank you

 

[Guillaume Bourgeois]

https://www.3cx.com/ordering/pricing/pricelist/

Note to myself, when I say "here is the link," I need to actually include the link. LOL

 

[Guillaume Bourgeois]

Thanks Nicholas , So if i go with Fresh installation and use the backup and restore i wont get any issues and it will work perfectly ???

The likelihood that this solution will resolve your issue is very high. However, if it does not solve your problem or if other issues arise, 3CX cannot be held responsible. Nevertheless, the 3CX support team is excellent and will do everything necessary to assist you through technical support tickets, provided you follow the recommended guidelines.. Alternatively, you can post on the forum, where the community and support staff will make their best efforts to help you.

Tip:
If possible, access the 3CX Dashboard, export your list of users, and take screenshots of your "Phone" tab. Should any issues occur during restore, you'll be relieved to have at least the user list, including their MAC addresses. The Phone tab will help you identify the local IP addresses (if they are local to the PBX) and see which phones are actually online. This information makes it easier to manage if you need to reinstall from scratch, which is a last resort and unlikely to be necessary.

 

[Suri]

Can you please check if there is also the log file under /var/lib/3cxpbx ?

Hi TheodorosG,

Sorry for the late response. This is the content of the log file in /var/lib/3cxpbx

"{ "result": "aborted", "time": "06-08-2024 18:22:45", "title": "File ownership problem", "message": "There are files under /var/lib/3cxpbx/Bin/nginx/conf with the wrong user and/or group ownership. Please make sure the files are owner by the user: phonesystem" }"

I then checked the permissions for nginx directory and below is the output:

"root@3cx:/var/lib/3cxpbx/Bin/nginx# ls -l
total 4
drwxr-xr-x 4 phonesystem phonesystem 4096 Jul 24 04:04 conf
root@3cx:/var/lib/3cxpbx/Bin/nginx# cd conf/
root@3cx:/var/lib/3cxpbx/Bin/nginx/conf# ls -l
total 24
drwxr-xr-x 4 phonesystem phonesystem 4096 May 27 11:23 Instance1
-rw-r--r-- 1 phonesystem phonesystem 1647 Apr 25 00:19 lets-encrypt-x3-cross-signed.pem
-rw-r--r-- 1 phonesystem phonesystem 5916 Jul 24 04:04 nginx.conf
-rw-r--r-- 1 phonesystem phonesystem 812 Apr 25 00:19 shared-headers.conf"

 

[Agathocles Prodromou]

The output seems incomplete. Can you please post the result of

ls -laR /var/lib/3cxpbx/Bin/nginx/conf

 

[Suri]

The output seems incomplete. Can you please post the result of

ls -laR /var/lib/3cxpbx/Bin/nginx/conf

Hi Agathocles,

Sorry about that, please find the result in the attachment. Is is because of the ssl file permissions?

 

[Agathocles Prodromou]

Hi @Suri ,

Yes, there are files owned by root. Thus the error you receive when you attempt to upgrade is correct.

All files under the conf directory need to be owned by the phonesystem user/group. Once you do that, you may proceed with the upgrade. (as always, take an offside backup or a VM snapshot prior proceeding)

P.S I have removed the log file as it contained your FQDN.

 

[Suri]

Hi @Suri ,

Yes, there are files owned by root. Thus the error you receive when you attempt to upgrade is correct.

All files under the conf directory need to be owned by the phonesystem user/group. Once you do that, you may proceed with the upgrade.

P.S I have removed the log file as it contained your FQDN.

Thank you so much Agathocles, for both the solution and removing the file. I checked the file I attached again and realized it was not picked up by replace due to different structure.

I will try making the changes sometime early next week and re-try the upgrade. Can we please leave this thread open till then? I will update it if the upgrade goes through or if there are any other issues.

 

[Suri]

Hi @Suri ,

Yes, there are files owned by root. Thus the error you receive when you attempt to upgrade is correct.

All files under the conf directory need to be owned by the phonesystem user/group. Once you do that, you may proceed with the upgrade. (as always, take an offside backup or a VM snapshot prior proceeding)

P.S I have removed the log file as it contained your FQDN.

Hi,

I changed folder permissions today and tried the upgrade, it went through successfully. Thank you for your help. This thread can now be closed.

 

[Agathocles Prodromou]

Hi,

I changed folder permissions today and tried the upgrade, it went through successfully. Thank you for your help. This thread can now be closed.

Hi there,

Glad to hear everything went smoothly! Enjoy V20