I get some ERRORS after upgrading to ISPConfig 3.2

Can you go through these steps for the server your databases are on: https://www.faqforge.com/linux/debugging-ispconfig-3-server-actions-in-case-of-a-failure/
After disabling the cronjob and enabling debug logging, can you delete one of the database backups and then run the server.sh script?

 

Actually, i misread your note. I just checked on one of my servers and see the same error. I made a bug report: https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5866

 

But for your first issue we still have to figure out what's wrong exactly... Can you spot a difference between the working and non working sites in the config / names? Maybe a special character in the domain name? Different compression formats?

 

Alright, and if you try switching back to the default format, does it work then?

 

This is the interesting part:

Code:

25.10.2020-12:10 - DEBUG - Triggered backup routine for domain id 67, action name backup_web_files
25.10.2020-12:10 - DEBUG - Performing web files backup of /var/www/clients/client20/web67 in format zip, mode userzip
25.10.2020-12:10 - DEBUG - safe_exec cmd: cd '/var/www/clients/client20/web67' && zip  -b '/tmp' --exclude='./backup\*' --exclude=./bin --exclude=./dev --exclude=./etc --exclude=./lib --exclude=./lib32 --exclude=./lib64 --exclude=./opt --exclude=./sys --exclude=./usr --exclude=./var --exclude=./proc --exclude=./run --exclude=./tmp --exclude=./log --symlinks -r '/media/mybackupdrive/backup_all_webs/web67/manual-web67_2020-10-25_12-10.zip' * .* -x "../*" - return code: 18
25.10.2020-12:10 - ERROR - Backup of web files for domain drgordi.com failed using path /var/www/clients/client20/web67 failed.
25.10.2020-12:10 - DEBUG - Remove Lock: /usr/local/ispconfig/server/temp/.ispconfig_lock

Could it be that there is something wrong with the permissions of these webs? run

Code:

ls -l /var/www/example.com/web

to view the permissions of the web folder

 

My bad, missed adding -a to the command so hidden files are listed aswell. Can you run it again just for sure?

Code:

ls -la /var/www/example.com/web

 

On this exact problem, no. I'll forward it to the person that wrote the new code.

There are 2 other database backup errors known that will be fixed in 3.2.1:
https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5866
https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5867

 

Weird, and you are updated to 3.2? Every 3.2 system should have bug #5866, only systems with the db on a different server than the web should have #5867

 

I made a issue on our GitLab for this now: https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5878

Could you all share your OS, PHP version (that's used for the CLI), and backup settings for the domain(s) that fail in one comment here or directly on GitLab?

Find your OS version:

Code:

cat /etc/os-release

Find your PHP version:

Code:

php --version