web session timeout

S

sirmosi

New Member
Jan 5, 2020
14
0
1
38
hi
i'm using proxmox with 4 node Clustered together, the problem is when i log in to the web session after some minutes it loges out automaticly , does it have a way to solve this ?
here is my pveversion -v

proxmox-ve: 5.4-1 (running kernel: 4.15.18-12-pve)
pve-manager: 5.4-3 (running version: 5.4-3/0a6eaa62)
pve-kernel-4.15: 5.3-3
pve-kernel-4.15.18-12-pve: 4.15.18-35
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-8
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-50
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-13
libpve-storage-perl: 5.0-41
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-3
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-25
pve-cluster: 5.0-36
pve-container: 2.0-37
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-19
pve-firmware: 2.0-6
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 2.12.1-3
pve-xtermjs: 3.12.0-1
qemu-server: 5.0-50
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2
 
Is there any error in journalctl -f ?

Also check the time in your server if correct timedatectl
 
i've got error and says it's not running with
Code: 
  systemctl status systemd-timesyncd.service
but i try to start service and it is running now.

does it solve the problem ?
 
Last edited:
Hi,

Could you look in /var/log/pveproxy/access.log what error code the client get when they time out?
 
Moayad said:
Hi,

Could you look in /var/log/pveproxy/access.log what error code the client get when they time out?
Click to expand...

here is the result :


Code: 
192.168.70.9 - root@pam [04/06/2020:14:33:13 +0430] "GET /api2/json/cluster/resources HTTP/1.1" 200 4301
192.168.70.9 - - [04/06/2020:14:33:15 +0430] "GET /api2/json/cluster/tasks HTTP/1.1" 401 -
192.168.70.9 - - [04/06/2020:14:33:16 +0430] "GET /api2/json/nodes/prox2/qemu/120/status/current HTTP/1.1" 401 -
192.168.70.9 - - [04/06/2020:14:33:17 +0430] "GET /api2/extjs/nodes/prox2/qemu/129/config?_dc=1591264995698 HTTP/1.1" 401 -
192.168.70.9 - - [04/06/2020:14:33:17 +0430] "GET /api2/json/nodes/prox2/qemu/129/rrddata?timeframe=hour&cf=AVERAGE HTTP/1.1" 401 -
192.168.70.9 - - [04/06/2020:14:33:18 +0430] "GET /api2/json/nodes/prox2/qemu/129/status/current HTTP/1.1" 401 -
192.168.70.9 - - [04/06/2020:14:33:20 +0430] "GET /api2/json/cluster/resources HTTP/1.1" 401 -
192.168.70.9 - - [04/06/2020:14:33:20 +0430] "GET /api2/json/access/domains HTTP/1.1" 200 214

after the last line nothing happens, till i login again
 
Hi,

Did you checked systemctl status systemd-timesyncd.service after logout if running?

Any browser addons installed which could interfere with connections or cookies?
 
I have the exact same issue on a single, freshly installed Proxmox 6.2-4 setup. Login times out after an extremely short period of time (sometimes seconds, sometimes minutes).

Below is the output from both "hwclock" and also "date" as well as showing systemd-timesyncd.service is running.

root@pve:~# hwclock
2020-07-12 17:02:00.218156+10:00
root@pve:~# date
Sun 12 Jul 2020 05:02:01 PM AEST

root@pve:~# systemctl status systemd-timesyncd.service
● systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled)
Drop-In: /usr/lib/systemd/system/systemd-timesyncd.service.d
└─disable-with-time-daemon.conf
Active: active (running) since Mon 2020-07-13 00:06:42 AEST; 7h left


"journalctl -f" shows a lot of repetition of the following:

Jul 12 17:08:09 pve pmxcfs[1072]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-storage/pve/local-lvm: -1
Jul 12 17:08:09 pve pmxcfs[1072]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-storage/pve/local-lvm: /var/lib/rrdcached/db/pve2-storage/pve/local-lvm: illegal attempt to update using time 1594537689 when last update time is 1594562827 (minimum one second step)

Also, when the session times out, I see the following error on the page:
"permission denied - invalid PVR ticket (401)"
 
Last edited:
  • Like
Reactions: HiltonT and Moayad
HiltonT said:
I have the exact same issue on a single, freshly installed Proxmox 6.2-4 setup. Login times out after an extremely short period of time (sometimes seconds, sometimes minutes).

Below is the output from both "hwclock" and also "date" as well as showing systemd-timesyncd.service is running.

root@pve:~# hwclock
2020-07-12 17:02:00.218156+10:00
root@pve:~# date
Sun 12 Jul 2020 05:02:01 PM AEST

root@pve:~# systemctl status systemd-timesyncd.service
● systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled)
Drop-In: /usr/lib/systemd/system/systemd-timesyncd.service.d
└─disable-with-time-daemon.conf
Active: active (running) since Mon 2020-07-13 00:06:42 AEST; 7h left


"journalctl -f" shows a lot of repetition of the following:

Jul 12 17:08:09 pve pmxcfs[1072]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-storage/pve/local-lvm: -1
Jul 12 17:08:09 pve pmxcfs[1072]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-storage/pve/local-lvm: /var/lib/rrdcached/db/pve2-storage/pve/local-lvm: illegal attempt to update using time 1594537689 when last update time is 1594562827 (minimum one second step)

Also, when the session times out, I see the following error on the page:
"permission denied - invalid PVR ticket (401)"
Click to expand...

Just letting you know that 6.2-9 doesn't seem to have this issue any more...
 
  • Like
Reactions: smargerison
possibly your current system time just finally caught up to the one you had during installation/first boot - then the problem fixes itself already without the bug fix.
 
  • Like
Reactions: HiltonT
I know I didn't have any system time issues on this machine. This issue persisted even through multiple reboots. It is completely non-existent in 6.2-9. This system was running well for quite a number of years (Dell R510) with Server 2019, before that 2016, before that 2008 R2 and had Hyper-V guests on it all the way through.

And that there may well point to the possible problem - the system clock would have originally been in Windows Standard Time (ie, AEST, east coast of 'Srayamate) because Windows can't handle UTC+TZoffset. When the Proxmox ISO was deployed, it would have assumed that the system clock was in real time (UTC), so the issue would have "magically" self-corrected 10 hours after the initial install of Proxmox 6.2-4 even if I didn't do the update. Innnnnteresting - and maybe worth a mention in the docs somewhere if this can be reproduced (though, you said that it has now been addressed in github).
 
yes, it could be reproduced, and as usual, once a bug is reproducible finding the cause and fixing it was easy/straightforward. it will no longer be possible to trigger it starting with the next PVE ISO (6.3), and until then we know what to tell users who are affected since the workaround is quite easy :)
 
  • Like
Reactions: HiltonT
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
Back