After a disastrous attempt to upgrade v18 to v20 last year, I thought I'd try again. Even though v18 is working perfectly, it feels like I'm being pushed to upgrade to v20.
This time it gives up rather than doing a bad upgrade, which I suppose is an improvement.
The first 'fail' I find in the log file I get emailed is
Reading package lists...
[33m====== [11:29:30] Preparation: Upgreadability status seems OK[39m
[33m====== [11:29:30] Preparation: Checking locales[39m
[33m====== [11:29:30] Workaround: Unholding packages to avoid issues during the upgrade[39m
[33m====== [11:29:30] Upgrade Result: *******************************************[39m
{
"result": "aborted",
"time": "28-01-2025 11:29:30",
"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"
}
[31m[11:29] aborted: File ownership problem - 0[39m
So, that's complaining about a 'file ownership' problem. If I ssh onto the server and look in that directory, everything looks OK:
root@3cx:/# cd /var/lib/3cxpbx/Bin/nginx/conf/
root@3cx:/var/lib/3cxpbx/Bin/nginx/conf# ls -la
total 32
drwxr-xr-x 4 phonesystem phonesystem 4096 Jan 26 04:00 .
drwxr-xr-x 3 phonesystem phonesystem 4096 Dec 17 2021 ..
drwxr-xr-x 3 phonesystem phonesystem 4096 Dec 3 10:48 Instance1
-rw-r--r-- 1 phonesystem phonesystem 1647 Nov 13 09:05 lets-encrypt-x3-cross-signed.pem
-rw-r--r-- 1 phonesystem phonesystem 5910 Jan 26 04:00 nginx.conf
-rw-r--r-- 1 phonesystem phonesystem 812 Nov 13 09:05 shared-headers.conf
drwxr-xr-x 2 phonesystem phonesystem 4096 Jan 26 04:00 snippets
Any ideas?
As the upgrade process seems a bit flaky, is it possible to do a fresh install of v20 and copy my configuration into it?
This time it gives up rather than doing a bad upgrade, which I suppose is an improvement.
The first 'fail' I find in the log file I get emailed is
Reading package lists...
[33m====== [11:29:30] Preparation: Upgreadability status seems OK[39m
[33m====== [11:29:30] Preparation: Checking locales[39m
[33m====== [11:29:30] Workaround: Unholding packages to avoid issues during the upgrade[39m
[33m====== [11:29:30] Upgrade Result: *******************************************[39m
{
"result": "aborted",
"time": "28-01-2025 11:29:30",
"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"
}
[31m[11:29] aborted: File ownership problem - 0[39m
So, that's complaining about a 'file ownership' problem. If I ssh onto the server and look in that directory, everything looks OK:
root@3cx:/# cd /var/lib/3cxpbx/Bin/nginx/conf/
root@3cx:/var/lib/3cxpbx/Bin/nginx/conf# ls -la
total 32
drwxr-xr-x 4 phonesystem phonesystem 4096 Jan 26 04:00 .
drwxr-xr-x 3 phonesystem phonesystem 4096 Dec 17 2021 ..
drwxr-xr-x 3 phonesystem phonesystem 4096 Dec 3 10:48 Instance1
-rw-r--r-- 1 phonesystem phonesystem 1647 Nov 13 09:05 lets-encrypt-x3-cross-signed.pem
-rw-r--r-- 1 phonesystem phonesystem 5910 Jan 26 04:00 nginx.conf
-rw-r--r-- 1 phonesystem phonesystem 812 Nov 13 09:05 shared-headers.conf
drwxr-xr-x 2 phonesystem phonesystem 4096 Jan 26 04:00 snippets
Any ideas?
As the upgrade process seems a bit flaky, is it possible to do a fresh install of v20 and copy my configuration into it?
