3.3 upgrade from 3.2.12p1 on single instance: upgrade.php exits early

Hi,
Just trying to run the 3.3 upgrade on my single server, and the installer appears to exit early after the backup phase:

Code:

# php -q update.php


--------------------------------------------------------------------------------
 _____ ___________   _____              __ _         ____
|_   _/  ___| ___ \ /  __ \            / _(_)       /__  \
  | | \ `--.| |_/ / | /  \/ ___  _ __ | |_ _  __ _    _/ /
  | |  `--. \  __/  | |    / _ \| '_ \|  _| |/ _` |  |_ |
 _| |_/\__/ / |     | \__/\ (_) | | | | | | | (_| | ___\ \
 \___/\____/\_|      \____/\___/|_| |_|_| |_|\__, | \____/
                                              __/ |
                                             |___/ 
--------------------------------------------------------------------------------


>> Update 

Operating System: Debian 12.0 (Bookworm) or compatible

This application will update ISPConfig 3 on your server.

Shall the script create a ISPConfig backup in /var/backup/ now? (yes,no) [yes]: 

Creating backup of "/usr/local/ispconfig" directory...
Creating backup of "/etc" directory...
Creating backup of "/root/.acme.sh" directory...
Creating backup of "/etc/letsencrypt" directory...
root@ispconfig:/tmp/ispconfig3_install/install# 

Code:

##### SERVER #####
IP-address (as per hostname): ***.***.***.***
[WARN] could not determine server's ip address by ifconfig
[INFO] OS version is Debian GNU/Linux 12 (bookworm)

[INFO] uptime:  11:00:28 up 10 days,  9:00,  2 users,  load average: 0.84, 0.77, 0.78

[INFO] memory:
               total        used        free      shared  buff/cache   available
Mem:           895Mi       556Mi        76Mi        86Mi       528Mi       338Mi
Swap:          974Mi       245Mi       729Mi

[INFO] systemd failed services status:
  UNIT LOAD ACTIVE SUB DESCRIPTION
0 loaded units listed.

[INFO] ISPConfig is installed.

##### ISPCONFIG #####
ISPConfig version is 3.2.12p1

Not so great w/ php so as to run the script in debug mode to show why it exits. I can debug if more info is provided though

Cheers

 

Already tried `no` to backup.

Plenty of space:

Code:

# df /
Filesystem     1K-blocks    Used Available Use% Mounted on
/dev/sda1       31861548 6251856  23965660  21% /

Not many changes on PHP since original ISPC install: https://pastebin.com/7tzTswQG

 

I think it could be due to the available free memory.
I also had in a local Debian 12 dev VM the problem to run through the ISPConfig update.
Maybe it helps to not automatically backup ISPConfig when the Updater asks if it should perform the backup.

 

Thanks for your replies.
I upped the RAM (it's a VM) and this didn't help. Also, verified the db host and passwords in
/usr/local/ispconfig/interface/lib/config.inc.php and
/usr/local/ispconfig/server/lib/config.inc.php

I can also log into the db from the VM with `mysql -h <db host> -u <db user> -p` using those values and can log in no probs.
I did previous 3.2.x point upgrades in this VM without issues, so this is only occurring with the 3.3. update

 

Ok, got it: I'd tightened permissions in the db and didn't have permission for the db root from the ispc host. Now adjusted and it's working.
Thanks for your help