Verbindung zu shell bei Upgrade zu 9 verloren, was jetzt?

R

Rockhound53

Member
May 24, 2024
38
1
8
Hallo zusammen,

Ich habe ein einziges Setup, 1 Rechner und nichts Besonderes installiert.

Das Check Script lief so durch. Danach habe ich die Repos aktualisiert und das apt-disuprgrade ausgeführt, nach der Frage, ob Dienste neu gestartet werden sollen, habe ich diea mit ja geantwortet, danach hatte sich die Shell im Browser nicht mehr aktualisiert.

Ich habe dann im Browser auf neu geladen geklickt und dann war die Shell leer.

Jetzt weiß ich nicht, ob er im Hintergrund noch was macht. Ab und zu komme ich mal wieder in die GuI, mal geht nicht.

Als ich drin war und noch einmal apt-update gemacht habe, kam, dass irgendwas gelockt ist.

Jmand eine Idee was ich machen kann?

Danke und Grüße
 
Dann geht leider immer noch nicht weiter:

1754839927871.png

Wenn ich versuche über die GUI im Browser mich zu verbinden kommt:

Can't call method "process" on an undefined value at /usr/share/perl5/PVE/Service/pveproxy.pm line 284.

Ob ich den process "apt" mal "killen" soll? oder gibt es noch eine andere Möglichkeit?

komisch ist, dass ja anscheinetn schon auf 9.0.3 upgedatet ist, der Kernel aber noch nicht.
 
Das wirft mir pve8to9 aus:

Bash: 
root@pve-SkYNeT:~# pve8to9
= CHECKING VERSION INFORMATION FOR PVE PACKAGES =

Checking for package updates..
PASS: all packages up-to-date

Checking proxmox-ve package version..
PASS: already upgraded to Proxmox VE 9

Checking running kernel version..
WARN: unexpected running and installed kernel '6.8.12-13-pve'.

= CHECKING CLUSTER HEALTH/SETTINGS =

SKIP: standalone node.

= CHECKING HYPER-CONVERGED CEPH STATUS =

SKIP: no hyper-converged ceph setup detected!

= CHECKING CONFIGURED STORAGES =

PASS: storage 'SkYNeT-offsite' enabled and active.
PASS: storage 'local' enabled and active.
PASS: storage 'local-zfs' enabled and active.
INFO: Checking storage content type configuration..
PASS: no storage content problems found
PASS: no storage re-uses a directory for multiple content types.
INFO: Check for usage of native GlusterFS storage plugin...
PASS: No GlusterFS storage found.
INFO: Checking whether all external RBD storages have the 'keyring' option configured
SKIP: No RBD storage configured.

= VIRTUAL GUEST CHECKS =

INFO: Checking for running guests..
PASS: no running guest detected.
INFO: Checking if LXCFS is running with FUSE3 library, if already upgraded..
PASS: systems seems to be upgraded and LXCFS is running with FUSE 3 library
INFO: Checking for VirtIO devices that would change their MTU...
PASS: All guest config descriptions fit in the new limit of 8 KiB
INFO: Checking container configs for deprecated lxc.cgroup entries
PASS: No legacy 'lxc.cgroup' keys found.
INFO: Checking VM configurations for outdated machine versions
PASS: All VM machine versions are recent enough

= MISCELLANEOUS CHECKS =

INFO: Checking common daemon services..
Failed to connect to system scope bus via local transport: Connection refused
WARN: systemd unit 'pveproxy.service' is in state 'unknown'
Failed to connect to system scope bus via local transport: Connection refused
WARN: systemd unit 'pvedaemon.service' is in state 'unknown'
Failed to connect to system scope bus via local transport: Connection refused
WARN: systemd unit 'pvescheduler.service' is in state 'unknown'
Failed to connect to system scope bus via local transport: Connection refused
WARN: systemd unit 'pvestatd.service' is in state 'unknown'
INFO: Checking for supported & active NTP service..
WARN: No (active) time synchronisation daemon (NTP) detected, but synchronized systems are important, especially for cluster and/or ceph!
INFO: Checking if the local node's hostname 'pve-SkYNeT' is resolvable..
INFO: Checking if resolved IP is configured on local node..
PASS: Resolved node IP '10.0.40.40' configured and active on single interface.
INFO: Check node certificate's RSA key size
PASS: Certificate 'pve-root-ca.pem' passed Debian Busters (and newer) security level for TLS connections (4096 >= 2048)
PASS: Certificate 'pve-ssl.pem' passed Debian Busters (and newer) security level for TLS connections (2048 >= 2048)
INFO: Checking backup retention settings..
PASS: no backup retention problems found.
INFO: checking CIFS credential location..
PASS: no CIFS credentials at outdated location found.
INFO: Checking permission system changes..
INFO: Checking custom role IDs
PASS: none of the 1 custom roles need handling
INFO: Checking node and guest description/note length..
PASS: All node config descriptions fit in the new limit of 64 KiB
INFO: Checking if the suite for the Debian security repository is correct..
PASS: found no suite mismatch
INFO: Checking for existence of NVIDIA vGPU Manager..
PASS: No NVIDIA vGPU Service found.
INFO: Checking bootloader configuration...
WARN: systemd-boot meta-package installed this will cause issues on upgrades of boot-related packages. Install 'systemd-boot-efi' and 'systemd-boot-tools' explicitly and remove 'systemd-boot'
INFO: Check for dkms modules...
SKIP: could not get dkms status
INFO: Check for legacy 'filter' or 'group' sections in /etc/pve/notifications.cfg...
INFO: Check for legacy 'notification-policy' or 'notification-target' options in /etc/pve/jobs.cfg...
PASS: No legacy 'notification-policy' or 'notification-target' options found!
INFO: Check for LVM autoactivation settings on LVM and LVM-thin storages...
PASS: No volumes were found that could potentially have issues due to the disabling of LVM autoactivation.
INFO: Check space requirements for RRD migration...
PASS: Enough free disk space for increased RRD metric granularity requirements, which is roughly 17.68 MiB.
INFO: Checking for IPAM DB files that have not yet been migrated.
PASS: No legacy IPAM DB found.
PASS: No legacy MAC DB found.
INFO: Checking if the legacy sysctl file '/etc/sysctl.conf' needs to be migrated to new '/etc/sysctl.d/' path.
PASS: Legacy file '/etc/sysctl.conf' is not present.
INFO: Checking if matching CPU microcode package is installed.
PASS: Found matching CPU microcode package 'intel-microcode' installed.
SKIP: NOTE: Expensive checks, like CT cgroupv2 compat, not performed without '--full' parameter

= SUMMARY =

TOTAL:    41
PASSED:   29
SKIPPED:  5
WARNINGS: 7
FAILURES: 0

ATTENTION: Please check the output for detailed information!
 
So, habe Apt beendet und danch "apt -f Install" ausgeführt.

Es kam dann die Info, dass ich "dpkg --configure -a" ausführen soll, was ich auch gemacht habe. Dann kamen die ganzen fragen ob die Dateien beibehalten werden sollen, wo ich immer mit enter bestätigt habe.

Jetzt gibt es bei "apt update folgende Meldung:

Code: 
root@pve-SkYNeT:~# apt update
Hit:1 http://deb.debian.org/debian trixie InRelease
Hit:2 http://security.debian.org/debian-security trixie-security InRelease
Hit:3 http://download.proxmox.com/debian/pve trixie InRelease
Hit:4 http://deb.debian.org/debian trixie-updates InRelease
Err:5 https://enterprise.proxmox.com/debian/pve trixie InRelease
  401  Unauthorized [IP: 45.84.67.184 443]
Error: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/trixie/InRelease  401  Unauthorized [IP: 45.84.67.184 443]
Error: The repository 'https://enterprise.proxmox.com/debian/pve trixie InRelease' is not signed.
Notice: Updating from such a repository can't be done securely, and is therefore disabled by default.
Notice: See apt-secure(8) manpage for repository creation and user configuration details.
root@pve-SkYNeT:~# apt dist-upgrade
Summary:
  Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
root@pve-SkYNeT:~# pveversion
pve-manager/9.0.3/025864202ebb6109 (running kernel: 6.8.12-13-pve)

und "pve8to9" spuckt folgendes aus:

Code: 
root@pve-SkYNeT:~# pve8to9
= CHECKING VERSION INFORMATION FOR PVE PACKAGES =

Checking for package updates..
PASS: all packages up-to-date

Checking proxmox-ve package version..
PASS: already upgraded to Proxmox VE 9

Checking running kernel version..
WARN: a suitable kernel (proxmox-kernel-6.14) is installed, but an unsuitable (6.8.12-13-pve) is booted, missing reboot?!

= CHECKING CLUSTER HEALTH/SETTINGS =

SKIP: standalone node.

= CHECKING HYPER-CONVERGED CEPH STATUS =

SKIP: no hyper-converged ceph setup detected!

= CHECKING CONFIGURED STORAGES =

PASS: storage 'SkYNeT-offsite' enabled and active.
PASS: storage 'local' enabled and active.
PASS: storage 'local-zfs' enabled and active.
INFO: Checking storage content type configuration..
PASS: no storage content problems found
PASS: no storage re-uses a directory for multiple content types.
INFO: Check for usage of native GlusterFS storage plugin...
PASS: No GlusterFS storage found.
INFO: Checking whether all external RBD storages have the 'keyring' option configured
SKIP: No RBD storage configured.

= VIRTUAL GUEST CHECKS =

INFO: Checking for running guests..
PASS: no running guest detected.
INFO: Checking if LXCFS is running with FUSE3 library, if already upgraded..
PASS: systems seems to be upgraded and LXCFS is running with FUSE 3 library
INFO: Checking for VirtIO devices that would change their MTU...
PASS: All guest config descriptions fit in the new limit of 8 KiB
INFO: Checking container configs for deprecated lxc.cgroup entries
PASS: No legacy 'lxc.cgroup' keys found.
INFO: Checking VM configurations for outdated machine versions
PASS: All VM machine versions are recent enough

= MISCELLANEOUS CHECKS =

INFO: Checking common daemon services..
Failed to connect to system scope bus via local transport: Connection refused
WARN: systemd unit 'pveproxy.service' is in state 'unknown'
Failed to connect to system scope bus via local transport: Connection refused
WARN: systemd unit 'pvedaemon.service' is in state 'unknown'
Failed to connect to system scope bus via local transport: Connection refused
WARN: systemd unit 'pvescheduler.service' is in state 'unknown'
Failed to connect to system scope bus via local transport: Connection refused
WARN: systemd unit 'pvestatd.service' is in state 'unknown'
INFO: Checking for supported & active NTP service..
WARN: No (active) time synchronisation daemon (NTP) detected, but synchronized systems are important, especially for cluster and/or ceph!
INFO: Checking if the local node's hostname 'pve-SkYNeT' is resolvable..
INFO: Checking if resolved IP is configured on local node..
PASS: Resolved node IP '10.0.40.40' configured and active on single interface.
INFO: Check node certificate's RSA key size
PASS: Certificate 'pve-root-ca.pem' passed Debian Busters (and newer) security level for TLS connections (4096 >= 2048)
PASS: Certificate 'pve-ssl.pem' passed Debian Busters (and newer) security level for TLS connections (2048 >= 2048)
INFO: Checking backup retention settings..
PASS: no backup retention problems found.
INFO: checking CIFS credential location..
PASS: no CIFS credentials at outdated location found.
INFO: Checking permission system changes..
INFO: Checking custom role IDs
PASS: none of the 1 custom roles need handling
INFO: Checking node and guest description/note length..
PASS: All node config descriptions fit in the new limit of 64 KiB
INFO: Checking if the suite for the Debian security repository is correct..
PASS: found no suite mismatch
INFO: Checking for existence of NVIDIA vGPU Manager..
PASS: No NVIDIA vGPU Service found.
INFO: Checking bootloader configuration...
WARN: systemd-boot meta-package installed this will cause issues on upgrades of boot-related packages. Install 'systemd-boot-efi' and 'systemd-boot-tools' explicitly and remove 'systemd-boot'
INFO: Check for dkms modules...
SKIP: could not get dkms status
INFO: Check for legacy 'filter' or 'group' sections in /etc/pve/notifications.cfg...
INFO: Check for legacy 'notification-policy' or 'notification-target' options in /etc/pve/jobs.cfg...
PASS: No legacy 'notification-policy' or 'notification-target' options found!
INFO: Check for LVM autoactivation settings on LVM and LVM-thin storages...
PASS: No volumes were found that could potentially have issues due to the disabling of LVM autoactivation.
INFO: Check post RRD metrics data format migration situation...
WARN: Found '15' RRD files that have not yet been migrated to the new schema.
pve2-vm/200
         pve2-vm/207
         pve2-vm/100
         pve2-vm/203
         pve2-vm/204
         pve2-vm/206
         pve2-vm/201
         pve2-vm/102
         pve2-vm/205
         pve2-vm/101
         pve2-vm/202
         pve2-node/pve-SkYNeT
         pve2-storage/pve-SkYNeT/SkYNeT-offsite
         pve2-storage/pve-SkYNeT/local-zfs
         pve2-storage/pve-SkYNeT/local
        Please run the following command manually:
        /usr/libexec/proxmox/proxmox-rrd-migration-tool --migrate

INFO: Checking for IPAM DB files that have not yet been migrated.
PASS: No legacy IPAM DB found.
PASS: No legacy MAC DB found.
INFO: Checking if the legacy sysctl file '/etc/sysctl.conf' needs to be migrated to new '/etc/sysctl.d/' path.
PASS: Legacy file '/etc/sysctl.conf' is not present.
INFO: Checking if matching CPU microcode package is installed.
PASS: Found matching CPU microcode package 'intel-microcode' installed.
SKIP: NOTE: Expensive checks, like CT cgroupv2 compat, not performed without '--full' parameter

= SUMMARY =

TOTAL:    41
PASSED:   28
SKIPPED:  5
WARNINGS: 8
FAILURES: 0

ATTENTION: Please check the output for detailed information!

Soll ich jetzt neu starten oder muss ich vorher noch etwas machen?
 
Hallo UdoB,

Danke, das ist auch nicht meine Sorge gewesen, die Frage war ob sonst alles soweit ist, dass ich neustarten kann? Da sind ja noch ein paar andere Warnungen in dem pve8to9...

Danke für deine Hilfe...
 
Rockhound53 said:
Da sind ja noch ein paar andere Warnungen in dem pve8to9...
Click to expand...
Warnungen sind nur Warnungen.

Ich kann die "Connection refused" nicht einordnen, sorry. Ich würde rebooten. Aber wenn dann dein Rechner explodiert, will ich nicht schuld sein ;-)
 
Das nächste Problem, der Neustart geht nicht:

PXL_20250810_165243034.jpg
Und dabei wollte ich doch nur mal kurz am Sonntag das Upgrade machen...:verwirrt:

Wie kann ich den Rechner jetzt am besten neu starten? Die Frage: echo b > /prox/sysrq-trigger?

Aber das ist ja dann sicherlich wie Stecker ziehen?
 
Also habe ich dann den Stecker gezogen und nach einigen Neustarts läuft jetzt erstmal wieder alles.

Jellyfin und Immich wollten erst nicht starten, das /dev/dri/card0 wurde nicht gefunden. Anscheinend wurde das in /dev/dri/card1 umbenannt und nachdem ich das geändert hatte, liefen auch die LCXs normal.

Jetzt habe ich noch einen Punkt beim Checktool:

Code: 
INFO: Bootloader-Konfiguration wird überprüft …
WARNUNG: Das installierte Metapaket systemd-boot führt zu Problemen bei Upgrades von bootbezogenen Paketen. Installieren Sie „systemd-boot-efi“ und „systemd-boot-tools“ explizit und entfernen Sie „systemd-boot“.

Die Frage ist, soll ich das genau so machen, wie es dort steht, also die beiden Pakete installieren und systemd-boot entfernen?

Dann hatte ich auch Glances eingerichtet, aber es scheint nach dem Update nicht mehr vorhanden zu sein. Wir das automatisch deinstalliert?

Danke und Grüße
 
Last edited:
Rockhound53 said:
Also habe ich dann den Stecker gezogen und nach einigen Neustarts läuft jetzt erstmal wieder alles.
Click to expand...
Mut zur Lücke wird doch manchmal belohnt,
  • ich würde zuerst die repos kontrollieren und ggfs. bereinigen. Entweder per WebGUI oder shell
  • am besten die non-subsciption aktivieren.
  • danach apt update && apt upgrade
  • dann pve8to9 ausführen.
  • alle Vorschläge des scripts ausführen
  • reboot
  • Daumen drücken.
Bzgl. glances kann ich nichts sagen, außer das xxd (etwas was ich im Leben noch nie wahr genommen habe) plötzlich fehlte und manuell nachinstalliert werden musste.
 
Last edited:
Hallo zusammen,

heute Nacht sich sich mein Proxmox aufgehangen, neustart hat nicht funktioniert und ich konnte wieder einmal nur den Stecker ziehen.

Folgendes stand im Protokoll:

Code: 
Aug 15 02:01:54 pve-SkYNeT pveproxy[3707535]: proxy detected vanished client connection
Aug 15 02:01:54 pve-SkYNeT pveproxy[3706942]: proxy detected vanished client connection
Aug 15 02:02:47 pve-SkYNeT kernel: INFO: task iou-wrk-1602:3719860 blocked for more than 122 seconds.
Aug 15 02:02:47 pve-SkYNeT kernel:       Tainted: P     U     O       6.14.8-2-pve #1
Aug 15 02:02:47 pve-SkYNeT kernel:       Blocked by coredump.
Aug 15 02:02:47 pve-SkYNeT kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Aug 15 02:02:47 pve-SkYNeT kernel: task:iou-wrk-1602    state:D stack:0     pid:3719860 tgid:1602  ppid:1      task_flags:0x84040dc flags:0x00004000
Aug 15 02:02:47 pve-SkYNeT kernel: Call Trace:
Aug 15 02:02:47 pve-SkYNeT kernel:  <TASK>
Aug 15 02:02:47 pve-SkYNeT kernel:  __schedule+0x466/0x13f0
Aug 15 02:02:47 pve-SkYNeT kernel:  schedule+0x29/0x130
Aug 15 02:02:47 pve-SkYNeT kernel:  schedule_preempt_disabled+0x15/0x30
Aug 15 02:02:47 pve-SkYNeT kernel:  rwsem_down_read_slowpath+0x230/0x460
Aug 15 02:02:47 pve-SkYNeT kernel:  ? native_load_gs_index+0x3b/0x60
Aug 15 02:02:47 pve-SkYNeT kernel:  down_read+0x48/0xc0
Aug 15 02:02:47 pve-SkYNeT kernel:  do_exit+0x259/0xa90
Aug 15 02:02:47 pve-SkYNeT kernel:  ? kvfree_call_rcu+0xe3/0x330
Aug 15 02:02:47 pve-SkYNeT kernel:  io_wq_worker+0x321/0x3e0
Aug 15 02:02:47 pve-SkYNeT kernel:  ? finish_task_switch.isra.0+0x9c/0x340
Aug 15 02:02:47 pve-SkYNeT kernel:  ? __pfx_io_wq_worker+0x10/0x10
Aug 15 02:02:47 pve-SkYNeT kernel:  ret_from_fork+0x44/0x70
Aug 15 02:02:47 pve-SkYNeT kernel:  ? __pfx_io_wq_worker+0x10/0x10
Aug 15 02:02:47 pve-SkYNeT kernel:  ret_from_fork_asm+0x1a/0x30
Aug 15 02:02:47 pve-SkYNeT kernel: RIP: 0033:0x0
Aug 15 02:02:47 pve-SkYNeT kernel: RSP: 002b:0000000000000000 EFLAGS: 00000246 ORIG_RAX: 000000000000010f
Aug 15 02:02:47 pve-SkYNeT kernel: RAX: 0000000000000000 RBX: 00007bdfe4019840 RCX: 00007bdfe726d9ee
Aug 15 02:02:47 pve-SkYNeT kernel: RDX: 00007ffc70bd54e0 RSI: 0000000000000061 RDI: 0000628b0711cf80
Aug 15 02:02:47 pve-SkYNeT kernel: RBP: 00007ffc70bd554c R08: 0000000000000008 R09: 0000000000000000
Aug 15 02:02:47 pve-SkYNeT kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000000030f26c20
Aug 15 02:02:47 pve-SkYNeT kernel: R13: 0000628b05d151e0 R14: 0000628af3f75d70 R15: 00007ffc70bd5550
Aug 15 02:02:47 pve-SkYNeT kernel:  </TASK>
Aug 15 02:02:47 pve-SkYNeT kernel: INFO: task libuv-worker:6035 blocked for more than 122 seconds.
Aug 15 02:02:47 pve-SkYNeT kernel:       Tainted: P     U     O       6.14.8-2-pve #1
Aug 15 02:02:47 pve-SkYNeT kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Aug 15 02:02:47 pve-SkYNeT kernel: task:libuv-worker    state:D stack:0     pid:6035  tgid:5433  ppid:5132   task_flags:0x400040 flags:0x00000002
Aug 15 02:02:47 pve-SkYNeT kernel: Call Trace:
Aug 15 02:02:47 pve-SkYNeT kernel:  <TASK>
Aug 15 02:02:47 pve-SkYNeT kernel:  __schedule+0x466/0x13f0
Aug 15 02:02:47 pve-SkYNeT kernel:  ? wb_update_bandwidth+0x4f/0x80
Aug 15 02:02:47 pve-SkYNeT kernel:  schedule+0x29/0x130
Aug 15 02:02:47 pve-SkYNeT kernel:  io_schedule+0x4c/0x80
Aug 15 02:02:47 pve-SkYNeT kernel:  folio_wait_bit_common+0x122/0x2e0
Aug 15 02:02:47 pve-SkYNeT kernel:  ? __pfx_wake_page_function+0x10/0x10
Aug 15 02:02:47 pve-SkYNeT kernel:  folio_wait_bit+0x18/0x30
Aug 15 02:02:47 pve-SkYNeT kernel:  folio_wait_writeback+0x2b/0xa0
Aug 15 02:02:47 pve-SkYNeT kernel:  __filemap_fdatawait_range+0x88/0xf0
Aug 15 02:02:47 pve-SkYNeT kernel:  filemap_write_and_wait_range+0x94/0xc0
Aug 15 02:02:47 pve-SkYNeT kernel:  nfs_wb_all+0x27/0x120 [nfs]
Aug 15 02:02:47 pve-SkYNeT kernel:  nfs_file_flush+0x5a/0x80 [nfs]
Aug 15 02:02:47 pve-SkYNeT kernel:  filp_flush+0x38/0xb0
Aug 15 02:02:47 pve-SkYNeT kernel:  __x64_sys_close+0x33/0x90
Aug 15 02:02:47 pve-SkYNeT kernel:  x64_sys_call+0x1786/0x2310
Aug 15 02:02:47 pve-SkYNeT kernel:  do_syscall_64+0x7e/0x170
Aug 15 02:02:47 pve-SkYNeT kernel:  ? nfs_end_io_write+0x15/0x20 [nfs]
Aug 15 02:02:47 pve-SkYNeT kernel:  ? nfs_file_write+0x12b/0x280 [nfs]
Aug 15 02:02:47 pve-SkYNeT kernel:  ? vfs_write+0x299/0x460
Aug 15 02:02:47 pve-SkYNeT kernel:  ? ksys_write+0x9b/0xf0
Aug 15 02:02:47 pve-SkYNeT kernel:  ? arch_exit_to_user_mode_prepare.isra.0+0x22/0xd0
Aug 15 02:02:47 pve-SkYNeT kernel:  ? syscall_exit_to_user_mode+0x38/0x1d0
Aug 15 02:02:47 pve-SkYNeT kernel:  ? do_syscall_64+0x8a/0x170
Aug 15 02:02:47 pve-SkYNeT kernel:  ? do_futex+0x18e/0x260
Aug 15 02:02:47 pve-SkYNeT kernel:  ? __x64_sys_futex+0x128/0x200
Aug 15 02:02:47 pve-SkYNeT kernel:  ? arch_exit_to_user_mode_prepare.isra.0+0x22/0xd0
Aug 15 02:02:47 pve-SkYNeT kernel:  ? syscall_exit_to_user_mode+0x38/0x1d0
Aug 15 02:02:47 pve-SkYNeT kernel:  ? do_syscall_64+0x8a/0x170
Aug 15 02:02:47 pve-SkYNeT kernel:  ? do_syscall_64+0x8a/0x170
Aug 15 02:02:47 pve-SkYNeT kernel:  ? do_syscall_64+0x8a/0x170
Aug 15 02:02:47 pve-SkYNeT kernel:  ? syscall_exit_to_user_mode+0x38/0x1d0
Aug 15 02:02:47 pve-SkYNeT kernel:  ? do_syscall_64+0x8a/0x170
Aug 15 02:02:47 pve-SkYNeT kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
Aug 15 02:02:47 pve-SkYNeT kernel: RIP: 0033:0x7a3537a64779
Aug 15 02:02:47 pve-SkYNeT kernel: RSP: 002b:00007a34fb23ac48 EFLAGS: 00000246 ORIG_RAX: 0000000000000003
Aug 15 02:02:47 pve-SkYNeT kernel: RAX: ffffffffffffffda RBX: 00007a34fb23b4f8 RCX: 00007a3537a64779
Aug 15 02:02:47 pve-SkYNeT kernel: RDX: 00007a35379e5f13 RSI: 0000000000000001 RDI: 0000000000000050
Aug 15 02:02:47 pve-SkYNeT kernel: RBP: 00007a34fb23ac50 R08: 000000000689e3e4 R09: 00007a34fb23ad70
Aug 15 02:02:47 pve-SkYNeT kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
Aug 15 02:02:47 pve-SkYNeT kernel: R13: 0000000000000073 R14: 00007a34f42f2800 R15: 00007a34f42f2800
Aug 15 02:02:47 pve-SkYNeT kernel:  </TASK>
Aug 15 02:03:21 pve-SkYNeT pveproxy[3707535]: proxy detected vanished client connection
Aug 15 02:03:21 pve-SkYNeT pveproxy[3707535]: proxy detected vanished client connection
Aug 15 02:03:21 pve-SkYNeT pveproxy[3707535]: proxy detected vanished client connection
Aug 15 02:03:23 pve-SkYNeT pveproxy[3711162]: proxy detected vanished client connection
Aug 15 02:03:51 pve-SkYNeT pveproxy[3707535]: proxy detected vanished client connection
Aug 15 02:03:51 pve-SkYNeT pveproxy[3707535]: proxy detected vanished client connection
Aug 15 02:04:05 pve-SkYNeT kernel: nfs: server 10.0.40.10 not responding, still trying
Aug 15 02:04:05 pve-SkYNeT kernel: nfs: server 10.0.40.10 not responding, still trying
Aug 15 02:04:08 pve-SkYNeT kernel: nfs: server 10.0.40.10 not responding, still trying
Aug 15 02:04:08 pve-SkYNeT kernel: nfs: server 10.0.40.10 not responding, still trying
Aug 15 02:04:11 pve-SkYNeT kernel: nfs: server 10.0.40.10 not responding, still trying
Aug 15 02:04:50 pve-SkYNeT kernel: INFO: task iou-wrk-1602:3719860 blocked for more than 245 seconds.
Aug 15 02:04:50 pve-SkYNeT kernel:       Tainted: P     U     O       6.14.8-2-pve #1
Aug 15 02:04:50 pve-SkYNeT kernel:       Blocked by coredump.
Aug 15 02:04:50 pve-SkYNeT kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Aug 15 02:04:50 pve-SkYNeT kernel: task:iou-wrk-1602    state:D stack:0     pid:3719860 tgid:1602  ppid:1      task_flags:0x84040dc flags:0x00004000
Aug 15 02:04:50 pve-SkYNeT kernel: Call Trace:
Aug 15 02:04:50 pve-SkYNeT kernel:  <TASK>
Aug 15 02:04:50 pve-SkYNeT kernel:  __schedule+0x466/0x13f0
Aug 15 02:04:50 pve-SkYNeT kernel:  schedule+0x29/0x130
Aug 15 02:04:50 pve-SkYNeT kernel:  schedule_preempt_disabled+0x15/0x30
Aug 15 02:04:50 pve-SkYNeT kernel:  rwsem_down_read_slowpath+0x230/0x460
Aug 15 02:04:50 pve-SkYNeT kernel:  ? native_load_gs_index+0x3b/0x60
Aug 15 02:04:50 pve-SkYNeT kernel:  down_read+0x48/0xc0
Aug 15 02:04:50 pve-SkYNeT kernel:  do_exit+0x259/0xa90
Aug 15 02:04:50 pve-SkYNeT kernel:  ? kvfree_call_rcu+0xe3/0x330
Aug 15 02:04:50 pve-SkYNeT kernel:  io_wq_worker+0x321/0x3e0
Aug 15 02:04:50 pve-SkYNeT kernel:  ? finish_task_switch.isra.0+0x9c/0x340
Aug 15 02:04:50 pve-SkYNeT kernel:  ? __pfx_io_wq_worker+0x10/0x10
Aug 15 02:04:50 pve-SkYNeT kernel:  ret_from_fork+0x44/0x70
Aug 15 02:04:50 pve-SkYNeT kernel:  ? __pfx_io_wq_worker+0x10/0x10
Aug 15 02:04:50 pve-SkYNeT kernel:  ret_from_fork_asm+0x1a/0x30
Aug 15 02:04:50 pve-SkYNeT kernel: RIP: 0033:0x0

Dies ist nur ein Auszug, den ganzen Log habe ich einmal beigefügt. 

Kann da jemand was mit anfangen? die Fehlermeldungen mit dem "nfs: server 10.0.40.10 not responding, still trying" liegt evtl. an dem bind mount zum OMV server. jetzt aktuell läuft erstmal wieder alles, würde aber gerne wissen was da passiert ist?

Danke und Grüße
 

Attachments

You must log in or register to reply here.
Top Bottom