Sorry I forgot, I did a snapshot of our production server (running kali 2023.2 like my test one), tried the update, same result

Upstream updated the database.
If gvm was already installed, you will have to migrate the database with the command:
sudo runuser -u _gvm -- gvmd --migrate

(gvm-check-setup would have identified the problem)

Hi sbrun, I also did that but still no web interface (rebooted in between)

sudo runuser -u _gvm -- gvmd --migrate

systemctl daemon-reload && systemctl restart gvmd.service gsad.service

systemctl status gvmd
● gvmd.service - Greenbone Vulnerability Manager daemon (gvmd)
Loaded: loaded (/lib/systemd/system/gvmd.service; enabled; preset: disabled)
Active: active (running) since Fri 2023-07-21 11:15:26 CEST; 5s ago
Docs: man:gvmd(8)
Process: 4221 ExecStart=/usr/sbin/gvmd --osp-vt-update=/run/ospd/ospd.sock --listen-group=_gvm (code=exited, status=0/SUCCESS)
Main PID: 4225 (gvmd)
Tasks: 1 (limit: 9315)
Memory: 180.2M
CPU: 1.722s
CGroup: /system.slice/gvmd.service
└─4225 "gvmd: gvmd: Wa" --osp-vt-update=/run/ospd/ospd.sock --listen-group=_gvm

Jul 21 11:15:23 kali systemd[1]: Starting gvmd.service - Greenbone Vulnerability Manager daemon (gvmd)...
Jul 21 11:15:23 kali systemd[1]: gvmd.service: Can't open PID file /run/gvmd/gvmd.pid (yet?) after start: No such file or directory
Jul 21 11:15:26 kali systemd[1]: Started gvmd.service - Greenbone Vulnerability Manager daemon (gvmd).

In case this helps:

gvm-check-setup

gvm-check-setup 22.5.0
Test completeness and readiness of GVM-22.5.0
Step 1: Checking OpenVAS (Scanner)...
OK: OpenVAS Scanner is present in version 22.7.3.
OK: Notus Scanner is present in version 22.5.0.
OK: Server CA Certificate is present as /var/lib/gvm/CA/servercert.pem.
Checking permissions of /var/lib/openvas/gnupg/*
OK: _gvm owns all files in /var/lib/openvas/gnupg
OK: redis-server is present.
OK: scanner (db_address setting) is configured properly using the redis-server socket: /var/run/redis-openvas/redis-server.sock
OK: the mqtt_server_uri is defined in /etc/openvas/openvas.conf
OK: _gvm owns all files in /var/lib/openvas/plugins
OK: NVT collection in /var/lib/openvas/plugins contains 85973 NVTs.
OK: The notus directory /var/lib/notus/products contains 434 NVTs.
Checking that the obsolete redis database has been removed
OK: No old Redis DB
OK: ospd-openvas service is active.
OK: ospd-OpenVAS is present in version 22.5.3.
Step 2: Checking GVMD Manager ...
OK: GVM Manager (gvmd) is present in version 22.5.5.
Step 3: Checking Certificates ...
OK: GVM client certificate is valid and present as /var/lib/gvm/CA/clientcert.pem.
OK: Your GVM certificate infrastructure passed validation.
Step 4: Checking data ...
OK: SCAP data found in /var/lib/gvm/scap-data.
OK: CERT data found in /var/lib/gvm/cert-data.
Step 5: Checking Postgresql DB and user ...
OK: Postgresql version and default port are OK.
gvmd | _gvm | UTF8 | en_US.UTF-8 | en_US.UTF-8 | | libc |
16435|pg-gvm|10|2200|f|22.5||
OK: At least one user exists.
Step 6: Checking Greenbone Security Assistant (GSA) ...
OK: Greenbone Security Assistant is present in version 22.05.1~git.
Step 7: Checking if GVM services are up and running ...
OK: gvmd service is active.
OK: gsad service is active.
Step 8: Checking few other requirements...
OK: nmap is present.
OK: ssh-keygen found, LSC credential generation for GNU/Linux targets is likely to work.
OK: nsis found, LSC credential package generation for Microsoft Windows targets is likely to work.
OK: xsltproc found.
WARNING: Your password policy is empty.
SUGGEST: Edit the /etc/gvm/pwpolicy.conf file to set a password policy.
Step 9: Checking greenbone-security-assistant...
OK: greenbone-security-assistant is installed

It seems like your GVM-22.5.0 installation is OK.

Update:

• gvmd is working fine, I still have fun .pid logs

  systemctl status gvmd

  ● gvmd.service - Greenbone Vulnerability Manager daemon (gvmd)
  Loaded: loaded (/lib/systemd/system/gvmd.service; enabled; preset: disabled)
  Active: active (running) since Wed 2023-07-26 14:52:51 CEST; 3min 58s ago
  Docs: man:gvmd(8)
  Process: 1241 ExecStart=/usr/sbin/gvmd --osp-vt-update=/run/ospd/ospd.sock --listen-group=_gvm (code=exited, status=0/SUCCESS)
  Main PID: 1242 (gvmd)
  Tasks: 1 (limit: 9315)
  Memory: 178.1M
  CPU: 5.736s
  CGroup: /system.slice/gvmd.service
  └─1242 "gvmd: gvmd: Wa" --osp-vt-update=/run/ospd/ospd.sock --listen-group=_gvm

Jul 26 14:52:47 kali systemd[1]: Starting gvmd.service - Greenbone Vulnerability Manager daemon (gvmd)...
Jul 26 14:52:47 kali systemd[1]: gvmd.service: Can't open PID file /run/gvmd/gvmd.pid (yet?) after start: No such file or directory
Jul 26 14:52:51 kali systemd[1]: Started gvmd.service - Greenbone Vulnerability Manager daemon (gvmd).

Greenbone assistant is working fine once I realised the /lib/systemd/system/greenbone-security-assistant.service was overwritten :-)