VPN Probleme nach Update pve6to7

shrdlicka said:
ich hätte erwähnen sollen, dass es der Log der Node und nicht von der VM sein sollte. ;)
Click to expand...
So was muss man mir in der Tat sagen ;)
Das Ergebnis ist riesig...
Ich hab mal etwas den Container betreffend (Shutdown/Start) rausgesucht:

Code: 
Sep 26 17:23:18 pve pvedaemon[1630]: <root@pam> starting task UPID:pve:002F0390:01987FB1:6331C3E6:vzshutdown:101:root@pam:
Sep 26 17:23:18 pve pvedaemon[3081104]: shutdown CT 101: UPID:pve:002F0390:01987FB1:6331C3E6:vzshutdown:101:root@pam:
Sep 26 17:23:19 pve kernel: fwbr101i0: port 2(veth101i0) entered disabled state
Sep 26 17:23:19 pve kernel: device veth101i0 left promiscuous mode
Sep 26 17:23:19 pve kernel: fwbr101i0: port 2(veth101i0) entered disabled state
Sep 26 17:23:19 pve audit[3081180]: AVC apparmor="STATUS" operation="profile_remove" profile="/usr/bin/lxc-start" name="lxc-101_</var/lib/lxc>" pid=3081180 comm="apparmor_parser"
Sep 26 17:23:19 pve kernel: audit: type=1400 audit(1664205799.586:81): apparmor="STATUS" operation="profile_remove" profile="/usr/bin/lxc-start" name="lxc-101_</var/lib/lxc>" pid=3081180 comm="apparmor_parser"
Sep 26 17:23:20 pve kernel: fwbr101i0: port 1(fwln101i0) entered disabled state
Sep 26 17:23:20 pve kernel: vmbr0: port 3(fwpr101p0) entered disabled state
Sep 26 17:23:20 pve kernel: device fwln101i0 left promiscuous mode
Sep 26 17:23:20 pve kernel: fwbr101i0: port 1(fwln101i0) entered disabled state
Sep 26 17:23:20 pve kernel: device fwpr101p0 left promiscuous mode
Sep 26 17:23:20 pve kernel: vmbr0: port 3(fwpr101p0) entered disabled state
Sep 26 17:23:20 pve pvedaemon[1629]: unable to get PID for CT 101 (not running?)
Sep 26 17:23:20 pve pvedaemon[1630]: <root@pam> end task UPID:pve:002F0390:01987FB1:6331C3E6:vzshutdown:101:root@pam: OK
Sep 26 17:23:20 pve systemd[1]: pve-container@101.service: Succeeded.
Sep 26 17:23:22 pve pvedaemon[1631]: <root@pam> starting task UPID:pve:002F0437:01988145:6331C3EA:vzstart:101:root@pam:
Sep 26 17:23:22 pve pvedaemon[3081271]: starting CT 101: UPID:pve:002F0437:01988145:6331C3EA:vzstart:101:root@pam:
Sep 26 17:23:22 pve systemd[1]: Started PVE LXC Container: 101.
Sep 26 17:23:23 pve audit[3081285]: AVC apparmor="STATUS" operation="profile_load" profile="/usr/bin/lxc-start" name="lxc-101_</var/lib/lxc>" pid=3081285 comm="apparmor_parser"
Sep 26 17:23:23 pve kernel: audit: type=1400 audit(1664205803.542:82): apparmor="STATUS" operation="profile_load" profile="/usr/bin/lxc-start" name="lxc-101_</var/lib/lxc>" pid=3081285 comm="apparmor_parser"
Sep 26 17:23:23 pve systemd-udevd[3081289]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Sep 26 17:23:23 pve systemd-udevd[3081289]: Using default interface naming scheme 'v247'.
Sep 26 17:23:23 pve systemd-udevd[3081296]: Using default interface naming scheme 'v247'.
Sep 26 17:23:23 pve systemd-udevd[3081296]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Sep 26 17:23:24 pve systemd-udevd[3081296]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Sep 26 17:23:24 pve systemd-udevd[3081297]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Sep 26 17:23:24 pve systemd-udevd[3081297]: Using default interface naming scheme 'v247'.
Sep 26 17:23:24 pve kernel: vmbr0: port 3(fwpr101p0) entered blocking state
Sep 26 17:23:24 pve kernel: vmbr0: port 3(fwpr101p0) entered disabled state
Sep 26 17:23:24 pve kernel: device fwpr101p0 entered promiscuous mode
Sep 26 17:23:24 pve kernel: vmbr0: port 3(fwpr101p0) entered blocking state
Sep 26 17:23:24 pve kernel: vmbr0: port 3(fwpr101p0) entered forwarding state
Sep 26 17:23:24 pve kernel: fwbr101i0: port 1(fwln101i0) entered blocking state
Sep 26 17:23:24 pve kernel: fwbr101i0: port 1(fwln101i0) entered disabled state
Sep 26 17:23:24 pve kernel: device fwln101i0 entered promiscuous mode
Sep 26 17:23:24 pve kernel: fwbr101i0: port 1(fwln101i0) entered blocking state
Sep 26 17:23:24 pve kernel: fwbr101i0: port 1(fwln101i0) entered forwarding state
Sep 26 17:23:24 pve kernel: fwbr101i0: port 2(veth101i0) entered blocking state
Sep 26 17:23:24 pve kernel: fwbr101i0: port 2(veth101i0) entered disabled state
Sep 26 17:23:24 pve kernel: device veth101i0 entered promiscuous mode
Sep 26 17:23:24 pve kernel: eth0: renamed from vethOxRUKo
Sep 26 17:23:24 pve pvedaemon[1631]: <root@pam> end task UPID:pve:002F0437:01988145:6331C3EA:vzstart:101:root@pam: OK
Sep 26 17:23:24 pve kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sep 26 17:23:24 pve kernel: fwbr101i0: port 2(veth101i0) entered blocking state
Sep 26 17:23:24 pve kernel: fwbr101i0: port 2(veth101i0) entered forwarding state

Gibt das irgendwelche Aufschlüsse?
 
Am interessantesten wäre der der Zeitabschnitt vom starten des containers bis er nicht mehr funktioniert:

Hier ein Beispiel für einen Logauszug von 9 bis 10 Uhr am 29. Sept. 2022:
Code: 
journalctl --since "2022-09-29 09:00" --until "2022-09-29 10:00"
 
shrdlicka said:
Am interessantesten wäre der der Zeitabschnitt vom starten des containers bis er nicht mehr funktioniert:

Hier ein Beispiel für einen Logauszug von 9 bis 10 Uhr am 29. Sept. 2022:
Code: 
journalctl --since "2022-09-29 09:00" --until "2022-09-29 10:00"
Click to expand...
Besten Dank für den Befehl :)
Ich habe den Container neu gestartet und abgewartet: nach dem Neustart taucht er als aktives Geät in der Fritzbox auf, nach ca. 10 Minuten nicht mehr - in der Zeit ist im Log aber nichts mehr passiert...

Code: 
root@pve:~# journalctl --since "2022-09-29 10:55"
-- Journal begins at Wed 2022-09-21 12:46:00 CEST, ends at Thu 2022-09-29 11:06:11 CEST. --
Sep 29 10:55:01 pve pvestatd[1577]: storage 'NAS' is not online
Sep 29 10:55:09 pve systemd-logind[1058]: Session 2258 logged out. Waiting for processes to exit.
Sep 29 10:55:09 pve systemd[1]: session-2258.scope: Succeeded.
Sep 29 10:55:09 pve systemd-logind[1058]: Removed session 2258.
Sep 29 10:55:09 pve pvedaemon[1579221]: <root@pam> end task UPID:pve:00181A8D:030050C9:63355D08:vncshell::root@pam: OK
Sep 29 10:55:11 pve pvestatd[1577]: storage 'NAS' is not online
Sep 29 10:55:14 pve pvedaemon[1579221]: <root@pam> starting task UPID:pve:00181D81:03007A2D:63355D72:vzstart:101:root@pam:
Sep 29 10:55:14 pve pvedaemon[1580417]: starting CT 101: UPID:pve:00181D81:03007A2D:63355D72:vzstart:101:root@pam:
Sep 29 10:55:14 pve systemd[1]: Started PVE LXC Container: 101.
Sep 29 10:55:14 pve audit[1580431]: AVC apparmor="STATUS" operation="profile_load" profile="/usr/bin/lxc-start" name="lxc-101_</var/lib/lxc>" pid=1580431 comm="apparmor_parser"
Sep 29 10:55:14 pve kernel: audit: type=1400 audit(1664441714.958:586): apparmor="STATUS" operation="profile_load" profile="/usr/bin/lxc-start" name="lxc-101_</var/lib/lxc>" pid=1580431 comm="apparmor_parser"
Sep 29 10:55:14 pve systemd-udevd[1580435]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Sep 29 10:55:14 pve systemd-udevd[1580435]: Using default interface naming scheme 'v247'.
Sep 29 10:55:15 pve systemd-udevd[1580443]: Using default interface naming scheme 'v247'.
Sep 29 10:55:15 pve systemd-udevd[1580443]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Sep 29 10:55:15 pve systemd-udevd[1580443]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Sep 29 10:55:15 pve systemd-udevd[1580446]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Sep 29 10:55:15 pve systemd-udevd[1580446]: Using default interface naming scheme 'v247'.
Sep 29 10:55:15 pve kernel: vmbr0: port 3(fwpr101p0) entered blocking state
Sep 29 10:55:15 pve kernel: vmbr0: port 3(fwpr101p0) entered disabled state
Sep 29 10:55:15 pve kernel: device fwpr101p0 entered promiscuous mode
Sep 29 10:55:15 pve kernel: vmbr0: port 3(fwpr101p0) entered blocking state
Sep 29 10:55:15 pve kernel: vmbr0: port 3(fwpr101p0) entered forwarding state
Sep 29 10:55:15 pve kernel: fwbr101i0: port 1(fwln101i0) entered blocking state
Sep 29 10:55:15 pve kernel: fwbr101i0: port 1(fwln101i0) entered disabled state
Sep 29 10:55:15 pve kernel: device fwln101i0 entered promiscuous mode
Sep 29 10:55:15 pve kernel: fwbr101i0: port 1(fwln101i0) entered blocking state
Sep 29 10:55:15 pve kernel: fwbr101i0: port 1(fwln101i0) entered forwarding state
Sep 29 10:55:15 pve kernel: fwbr101i0: port 2(veth101i0) entered blocking state
Sep 29 10:55:15 pve kernel: fwbr101i0: port 2(veth101i0) entered disabled state
Sep 29 10:55:15 pve kernel: device veth101i0 entered promiscuous mode
Sep 29 10:55:15 pve kernel: eth0: renamed from veth33VkmR
Sep 29 10:55:15 pve pvedaemon[1579221]: <root@pam> end task UPID:pve:00181D81:03007A2D:63355D72:vzstart:101:root@pam: OK
Sep 29 10:55:16 pve kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sep 29 10:55:16 pve kernel: fwbr101i0: port 2(veth101i0) entered blocking state
Sep 29 10:55:16 pve kernel: fwbr101i0: port 2(veth101i0) entered forwarding state
Sep 29 10:55:19 pve systemd[1]: Stopping User Manager for UID 0...
Sep 29 10:55:19 pve systemd[1579672]: Stopped target Main User Target.
Sep 29 10:55:19 pve systemd[1579672]: Stopped target Basic System.
Sep 29 10:55:19 pve systemd[1579672]: Stopped target Paths.
Sep 29 10:55:19 pve systemd[1579672]: Stopped target Sockets.
Sep 29 10:55:19 pve systemd[1579672]: Stopped target Timers.
Sep 29 10:55:19 pve systemd[1579672]: dirmngr.socket: Succeeded.
Sep 29 10:55:19 pve systemd[1579672]: Closed GnuPG network certificate management daemon.
Sep 29 10:55:19 pve systemd[1579672]: gpg-agent-browser.socket: Succeeded.
Sep 29 10:55:19 pve systemd[1579672]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Sep 29 10:55:19 pve systemd[1579672]: gpg-agent-extra.socket: Succeeded.
Sep 29 10:55:19 pve systemd[1579672]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Sep 29 10:55:19 pve systemd[1579672]: gpg-agent-ssh.socket: Succeeded.
Sep 29 10:55:19 pve systemd[1579672]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Sep 29 10:55:19 pve systemd[1579672]: gpg-agent.socket: Succeeded.
Sep 29 10:55:19 pve systemd[1579672]: Closed GnuPG cryptographic agent and passphrase cache.
Sep 29 10:55:19 pve systemd[1579672]: Removed slice User Application Slice.
Sep 29 10:55:19 pve systemd[1579672]: Reached target Shutdown.
Sep 29 10:55:19 pve systemd[1579672]: systemd-exit.service: Succeeded.
Sep 29 10:55:19 pve systemd[1579672]: Finished Exit the Session.
Sep 29 10:55:19 pve systemd[1579672]: Reached target Exit the Session.
Sep 29 10:55:19 pve systemd[1]: user@0.service: Succeeded.
Sep 29 10:55:19 pve systemd[1]: Stopped User Manager for UID 0.
Sep 29 10:55:19 pve systemd[1]: Stopping User Runtime Directory /run/user/0...
Sep 29 10:55:19 pve systemd[1]: run-user-0.mount: Succeeded.
Sep 29 10:55:19 pve systemd[1]: user-runtime-dir@0.service: Succeeded.
Sep 29 10:55:19 pve systemd[1]: Stopped User Runtime Directory /run/user/0.
Sep 29 10:55:19 pve systemd[1]: Removed slice User Slice of UID 0.
Sep 29 10:55:22 pve pvestatd[1577]: storage 'NAS' is not online
Sep 29 10:55:31 pve pvestatd[1577]: storage 'NAS' is not online
Sep 29 10:55:41 pve pvestatd[1577]: storage 'NAS' is not online
Sep 29 10:55:52 pve pvestatd[1577]: storage 'NAS' is not online
Sep 29 10:56:01 pve pvestatd[1577]: storage 'NAS' is not online
Sep 29 10:56:11 pve pvestatd[1577]: storage 'NAS' is not online
Sep 29 10:56:19 pve pvedaemon[3922684]: <root@pam> starting task UPID:pve:0018230C:030093AF:63355DB3:vncshell::root@pam:
Sep 29 10:56:19 pve pvedaemon[1581836]: starting termproxy UPID:pve:0018230C:030093AF:63355DB3:vncshell::root@pam:
Sep 29 10:56:19 pve pvedaemon[1579221]: <root@pam> successful auth for user 'root@pam'
Sep 29 10:56:19 pve login[1581841]: pam_unix(login:session): session opened for user root(uid=0) by root(uid=0)
Sep 29 10:56:19 pve systemd[1]: Created slice User Slice of UID 0.
Sep 29 10:56:19 pve systemd[1]: Starting User Runtime Directory /run/user/0...
Sep 29 10:56:19 pve systemd-logind[1058]: New session 2260 of user root.
Sep 29 10:56:19 pve systemd[1]: Finished User Runtime Directory /run/user/0.
Sep 29 10:56:19 pve systemd[1]: Starting User Manager for UID 0...
Sep 29 10:56:19 pve systemd[1581847]: pam_unix(systemd-user:session): session opened for user root(uid=0) by (uid=0)
Sep 29 10:56:19 pve systemd[1581847]: Queued start job for default target Main User Target.
Sep 29 10:56:19 pve systemd[1581847]: Created slice User Application Slice.
Sep 29 10:56:19 pve systemd[1581847]: Reached target Paths.
Sep 29 10:56:19 pve systemd[1581847]: Reached target Timers.
Sep 29 10:56:19 pve systemd[1581847]: Listening on GnuPG network certificate management daemon.
Sep 29 10:56:19 pve systemd[1581847]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Sep 29 10:56:19 pve systemd[1581847]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Sep 29 10:56:19 pve systemd[1581847]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Sep 29 10:56:19 pve systemd[1581847]: Listening on GnuPG cryptographic agent and passphrase cache.
Sep 29 10:56:19 pve systemd[1581847]: Reached target Sockets.
Sep 29 10:56:19 pve systemd[1581847]: Reached target Basic System.
Sep 29 10:56:19 pve systemd[1581847]: Reached target Main User Target.
Sep 29 10:56:19 pve systemd[1581847]: Startup finished in 85ms.
Sep 29 10:56:19 pve systemd[1]: Started User Manager for UID 0.
Sep 29 10:56:19 pve systemd[1]: Started Session 2260 of user root.
Sep 29 10:56:19 pve login[1581861]: ROOT LOGIN  on '/dev/pts/0'
Sep 29 10:56:22 pve pvestatd[1577]: storage 'NAS' is not online
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom