Debian 13 Trixie is OUT

Chat
1
3 Likes
2

And Proxmox 9 Too :smiley:

4 Likes
3

the way memebers of this commmunity love proxmox


4

Tried to update an old NS8 Debian VM but failed.

After apt upgrade exim was installed and cluster-admin not working, traefik isn’t starting.
Need to investigate


At least there will be a newer podman version:

root@debianns8test:~# podman --version
podman version 5.4.2

EDIT:

Errors after upgrade:

Aug 19 10:23:04 debianns8test (it-ready)[2234]: redis.service: Failed at step EXEC spawning /usr/local/bin/redis-wait-ready: No such file or directory
Aug 19 10:23:04 debianns8test (acl-load)[2242]: redis.service: Failed to execute /usr/local/bin/acl-load: No such file or directory
Aug 19 10:30:49 debianns8test (runagent)[2348]: promtail.service: Failed to execute /usr/local/bin/runagent: No such file or directory
Aug 19 10:30:49 debianns8test (runagent)[2348]: promtail.service: Failed at step EXEC spawning /usr/local/bin/runagent: No such file or directory
Aug 19 10:30:49 debianns8test systemd[1]: promtail.service: Control process exited, code=exited, status=203/EXEC
Aug 19 10:30:49 debianns8test systemd[1]: promtail.service: Failed with result 'exit-code'.
Aug 19 10:30:49 debianns8test systemd[1]: Failed to start promtail.service - Alloy (previously Promtail) logs collector for Loki.
Aug 19 10:33:50 debianns8test (runagent)[2522]: dhgen.service: Changing to the requested working directory failed: No such file or directory
Aug 19 10:33:50 debianns8test (runagent)[2522]: dhgen.service: Failed at step CHDIR spawning runagent: No such file or directory
Aug 19 10:33:50 debianns8test systemd[1283]: dhgen.service: Main process exited, code=exited, status=200/CHDIR
Aug 19 10:33:50 debianns8test systemd[1283]: dhgen.service: Failed with result 'exit-code'.
Aug 19 10:33:50 debianns8test systemd[1283]: Failed to start dhgen.service - Diffie-Hellman group generator.
3 Likes
5

When you have more info, I think we can open an issue inside the tracker to support the new Debian version.

3 Likes
6

There are also issues when Installing NS8 on Trixie:

Python was upgraded from 3.11 to 3.13 and there are errors. I think we need an updated python requirement file instead of /etc/nethserver/pyreq3_11.txt

Collecting jnius==1.1.0 (from -r /etc/nethserver/pyreq3_11.txt (line 10))
  Using cached jnius-1.1.0.tar.gz (28 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... error
  error: subprocess-exited-with-error
  
  × Getting requirements to build wheel did not run successfully.
  │ exit code: 1
  ╰─> [28 lines of output]
      
      
      You need Cython to compile Pyjnius.
3 Likes
7

python3.13 is available in epel for rocky9, I recal we try to stick on the same version for both debian and rockylinux

1 Like
8

Opened an issue.

2 Likes
9

Hey @stephdl i already updatet to Rev 9. After i check the installation i got INFO: Check for LVM autoactivation settings on LVM and LVM-thin storages

NOTICE: storage ‘local-lvm’ has guest volumes with autoactivation enabled
NOTICE: Starting with PVE 9, autoactivation will be disabled for new LVM/LVM-thin guest volumes. This system has some volumes that still have autoactivation enabled. All volumes with autoactivations reside on local storage, where this normally does not cause any issues.
You can run the following command to disable autoactivation for existing LVM/LVM-thin guest volumes: /usr/share/pve-manager/migrations/pve-lvm-disable-autoactivation

Do you know what it is the meaning of it?

10

Here’s some info about it from the Proxmox wiki: Upgrade from 8 to 9 - Proxmox VE

1 Like