proxmox web panel output problem (logout)

D

djsami

Renowned Member
Aug 24, 2009
193
5
83
Hello

proxmox constantly throws web panels we couldn't find a solution

proxmox-ve: 6.1-2 (running kernel: 5.3.18-2-pve) pve-manager: 6.1-7 (running version: 6.1-7/13e58d5e) pve-kernel-helper: 6.1-7 pve-kernel-5.3: 6.1-5 pve-kernel-5.3.18-2-pve: 5.3.18-2 pve-kernel-5.3.10-1-pve: 5.3.10-1 ceph-fuse: 12.2.11+dfsg1-2.1+b1 corosync: 3.0.3-pve1 criu: 3.11-3 glusterfs-client: 5.5-3 ifupdown: 0.8.35+pve1 ksm-control-daemon: 1.3-1 libjs-extjs: 6.0.1-10 libknet1: 1.15-pve1 libpve-access-control: 6.0-6 libpve-apiclient-perl: 3.0-3 libpve-common-perl: 6.0-13 libpve-guest-common-perl: 3.0-3 libpve-http-server-perl: 3.0-4 libpve-storage-perl: 6.1-5 libqb0: 1.0.5-1 libspice-server1: 0.14.2-4~pve6+1 lvm2: 2.03.02-pve4 lxc-pve: 3.2.1-1 lxcfs: 3.0.3-pve60 novnc-pve: 1.1.0-1 proxmox-mini-journalreader: 1.1-1 proxmox-widget-toolkit: 2.1-3 pve-cluster: 6.1-4 pve-container: 3.0-21 pve-docs: 6.1-6 pve-edk2-firmware: 2.20200229-1 pve-firewall: 4.0-10 pve-firmware: 3.0-6 pve-ha-manager: 3.0-8 pve-i18n: 2.0-4 pve-qemu-kvm: 4.1.1-3 pve-xtermjs: 4.3.0-1 qemu-server: 6.1-6 smartmontools: 7.1-pve2 spiceterm: 3.1-1 vncterm: 1.6-1 zfsutils-linux: 0.8.3-pve1
 
Hi,

you mean you are suddenly logout and get the login window again?

Does this happen immediately after login, X minutes afterwards or if you click on something specific?

I think this is due to somehow the backend replying with a access denied error code or exception, can you open your Browsers Web Developer console, go to the network tab and reload the Webinterface, then checkout for request with HTTP code >= 400

They may even have some error info encoded in the header or response.
 
  • Like
Reactions: djsami
t.lamprecht said:
Hi,

you mean you are suddenly logout and get the login window again?

Does this happen immediately after login, X minutes afterwards or if you click on something specific?

I think this is due to somehow the backend replying with a access denied error code or exception, can you open your Browsers Web Developer console, go to the network tab and reload the Webinterface, then checkout for request with HTTP code >= 400

They may even have some error info encoded in the header or response.
Click to expand...


exactly 5 minutes later the system throws me
400 error Gives a fault
 
t.lamprecht said:
What fault? We need more information here, else we cannot help you - please try to add as much as possible.

Also, any errors in the syslog/journal during that time?
Click to expand...

this problem existed yesterday, today there is no, i don't understand why

it looks okay right now

If it happens again, I will update the subject
 
same problem started again unfortunately

Code: 
eb 08 20:56:25 akin pveproxy[60617]: worker exit
Feb 08 20:56:25 akin pveproxy[1199]: worker 60617 finished
Feb 08 20:56:25 akin pveproxy[1199]: starting 1 worker(s)
Feb 08 20:56:25 akin pveproxy[1199]: worker 63676 started
Feb 08 20:56:36 akin pvedaemon[54551]: <root@pam> starting task UPID:akin:0000F943:0022A0F2:6202AED4:srvstop:chrony:root@pam:
Feb 08 20:56:36 akin pvedaemon[63811]: stopping service chrony: UPID:akin:0000F943:0022A0F2:6202AED4:srvstop:chrony:root@pam:
Feb 08 20:56:36 akin chronyd[969]: chronyd exiting
Feb 08 20:56:36 akin systemd[1]: Stopping chrony, an NTP client/server...
Feb 08 20:56:36 akin systemd[1]: chrony.service: Succeeded.
Feb 08 20:56:36 akin systemd[1]: Stopped chrony, an NTP client/server.
Feb 08 20:56:36 akin pvedaemon[54551]: <root@pam> end task UPID:akin:0000F943:0022A0F2:6202AED4:srvstop:chrony:root@pam: OK
Feb 08 20:56:48 akin pveproxy[1199]: worker 58140 finished
Feb 08 20:56:48 akin pveproxy[1199]: starting 1 worker(s)
Feb 08 20:56:48 akin pveproxy[1199]: worker 63970 started
Feb 08 20:56:48 akin pvedaemon[54551]: <root@pam> successful auth for user 'root@pam'
Feb 08 20:56:52 akin pveproxy[63969]: got inotify poll request in wrong process - disabling inotify
Feb 08 20:56:57 akin pvedaemon[63980]: starting vnc proxy UPID:akin:0000F9EC:0022A936:6202AEE9:vncproxy:100:root@pam:
Feb 08 20:56:57 akin pvedaemon[35922]: <root@pam> starting task UPID:akin:0000F9EC:0022A936:6202AEE9:vncproxy:100:root@pam:
Feb 08 20:57:42 akin pvedaemon[35922]: worker exit
Feb 08 20:57:42 akin pvedaemon[1190]: worker 35922 finished
Feb 08 20:57:42 akin pvedaemon[1190]: starting 1 worker(s)
Feb 08 20:57:42 akin pvedaemon[1190]: worker 64092 started
Feb 08 20:59:07 akin pvedaemon[54551]: <root@pam> end task UPID:akin:0000F3F8:0021E962:6202ACFE:vncproxy:110:root@pam: OK
Feb 08 20:59:39 akin pvedaemon[64649]: starting vnc proxy UPID:akin:0000FC89:0022E870:6202AF8B:vncproxy:101:root@pam:
Feb 08 20:59:39 akin pvedaemon[64092]: <root@pam> starting task UPID:akin:0000FC89:0022E870:6202AF8B:vncproxy:101:root@pam:
Feb 08 21:00:38 akin pvedaemon[54551]: <root@pam> successful auth for user 'root@pam'
Feb 08 21:00:43 akin pvedaemon[64092]: <root@pam> end task UPID:akin:0000FC89:0022E870:6202AF8B:vncproxy:101:root@pam: OK
Feb 08 21:00:47 akin pvedaemon[65508]: starting vnc proxy UPID:akin:0000FFE4:00230333:6202AFCF:vncproxy:102:root@pam:
Feb 08 21:00:47 akin pvedaemon[61974]: <root@pam> starting task UPID:akin:0000FFE4:00230333:6202AFCF:vncproxy:102:root@pam:
Feb 08 21:01:22 akin pvedaemon[61974]: <root@pam> successful auth for user 'root@pam'
Feb 08 21:01:50 akin pvedaemon[61974]: <root@pam> end task UPID:akin:0000FFE4:00230333:6202AFCF:vncproxy:102:root@pam: OK
Feb 08 21:02:41 akin pvedaemon[66079]: starting vnc proxy UPID:akin:0001021F:00232FD5:6202B041:vncproxy:103:root@pam:
Feb 08 21:02:41 akin pvedaemon[64092]: <root@pam> starting task UPID:akin:0001021F:00232FD5:6202B041:vncproxy:103:root@pam:
Feb 08 21:03:09 akin pveproxy[66218]: got inotify poll request in wrong process - disabling inotify
Feb 08 21:03:09 akin pveproxy[1199]: worker 60876 finished
Feb 08 21:03:09 akin pveproxy[1199]: starting 1 worker(s)
Feb 08 21:03:09 akin pveproxy[1199]: worker 66219 started
Feb 08 21:03:46 akin pvedaemon[64092]: <root@pam> end task UPID:akin:0001021F:00232FD5:6202B041:vncproxy:103:root@pam: OK
Feb 08 21:03:50 akin pvedaemon[66382]: starting vnc proxy UPID:akin:0001034E:00234AC0:6202B086:vncproxy:104:root@pam:
Feb 08 21:03:50 akin pvedaemon[54551]: <root@pam> starting task UPID:akin:0001034E:00234AC0:6202B086:vncproxy:104:root@pam:
Feb 08 21:04:50 akin pvedaemon[54551]: <root@pam> end task UPID:akin:0001034E:00234AC0:6202B086:vncproxy:104:root@pam: OK
Feb 08 21:04:54 akin pvedaemon[64092]: <root@pam> starting task UPID:akin:00010557:002363A0:6202B0C6:vncproxy:105:root@pam:
Feb 08 21:04:54 akin pvedaemon[66903]: starting vnc proxy UPID:akin:00010557:002363A0:6202B0C6:vncproxy:105:root@pam:
Sunucu Görünümü
Kayıtlar

Code: 
proxmox-ve: 7.1-1 (running kernel: 5.13.19-4-pve)
pve-manager: 7.1-10 (running version: 7.1-10/6ddebafe)
pve-kernel-helper: 7.1-10
pve-kernel-5.13: 7.1-7
pve-kernel-5.13.19-4-pve: 5.13.19-9
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 15.2.15-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-6
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-2
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.1-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.3.0-1
proxmox-backup-client: 2.1.5-1
proxmox-backup-file-restore: 2.1.5-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-5
pve-cluster: 7.1-3
pve-container: 4.1-3
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-5
pve-ha-manager: 3.3-3
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.1-1
pve-xtermjs: 4.16.0-1
qemu-server: 7.1-4
smartmontools: 7.2-1
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.2-pve1
 
You must log in or register to reply here.
Top Bottom