Connecting as root using "Linux PAM standard authentication", and I am getting:
Login failed. Please try again
journalctl confirms the passowrd is correct but the login still fails.
I can connect via ssh, though it is slow, but cannot connect via GUI.
This usually happens under moderate or high system load.
Currently top says:
iotop shows
free shows some swap usage:
I did
I changed it to 1.
If I turn swap back on, it is getting filled again, the IO load spikes and I cannot login via GUI:
(with swappiness 1)
(Note: I have a zpool ans the arc is limited to 4G)
Why can't I login via web gui under such moderate load if the SWAP is being used?
How come 1.4G of swap is used despite having 2.5G RAM available right after re-enabling swap.
Login failed. Please try again
journalctl confirms the passowrd is correct but the login still fails.
Code:
journalctl -f
Dec 23 10:46:17 proxmox sshd[1462869]: Accepted password for root from 192.168.5.100 port 54428 ssh2
Dec 23 10:46:17 proxmox sshd[1462869]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0)
Dec 23 10:46:22 proxmox systemd-logind[692]: New session 14026 of user root.q
Dec 23 10:46:22 proxmox systemd[1]: Started session-14026.scope - Session 14026 of User root.
Dec 23 10:46:24 proxmox sshd[1462869]: pam_env(sshd:session): deprecated reading of user environment enabled
Dec 23 10:46:40 proxmox pvestatd[1092]: status update time (11.530 seconds)
Dec 23 10:46:44 proxmox pve-firewall[1090]: firewall update time (5.780 seconds)
Dec 23 10:47:17 proxmox pvedaemon[1361469]: <root@pam> successful auth for user 'root@pam'
Dec 23 10:47:20 proxmox pveproxy[1280597]: proxy detected vanished client connectionI can connect via ssh, though it is slow, but cannot connect via GUI.
This usually happens under moderate or high system load.
Currently top says:
Code:
top - 10:54:03 up 106 days, 21:49, 2 users, load average: 2.49, 2.65, 1.86
Tasks: 313 total, 1 running, 312 sleeping, 0 stopped, 0 zombie
%Cpu(s): 3.6 us, 3.2 sy, 0.0 ni, 33.5 id, 59.2 wa, 0.0 hi, 0.5 si, 0.0 st
MiB Mem : 7857.1 total, 2318.1 free, 5588.0 used, 206.3 buff/cache
MiB Swap: 7632.0 total, 6341.3 free, 1290.7 used. 2269.1 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
372571 transmi+ 20 0 175668 142728 2560 S 4.7 1.8 81,12 transmission-da
1090 root 20 0 193884 9996 4864 S 2.0 0.1 12,00 pve-firewall
1437265 root rt 0 562236 169436 52960 S 1.3 2.1 12,58 corosync
557 root 1 -19 0 0 0 S 0.7 0.0 110:11.84 z_wr_issiotop shows
Code:
Total DISK READ: 2.54 M/s | Total DISK WRITE: 27.08 K/s
Current DISK READ: 2.87 M/s | Current DISK WRITE: 10.15 K/s
TID PRIO USER DISK READ DISK WRITE SWAPIN IO> COMMAND 1459871 be/4 root 13.54 K/s 0.00 B/s 0.00 % 15.05 % [kworker/u4:5+dm-thin]
1462949 be/4 root 10.15 K/s 0.00 B/s 0.00 % 13.46 % [kworker/u4:4+flush-252:9]
1465440 be/4 root 3.38 K/s 0.00 B/s 0.00 % 1.93 % python3 /usr/sbin/iotop
1090 be/4 root 104.93 K/s 0.00 B/s 0.00 % 0.00 % pve-firewall
1092 be/4 root 253.87 K/s 0.00 B/s 0.00 % 0.00 % pvestatd
133498 be/4 100000 121.86 K/s 0.00 B/s 0.00 % 0.00 % initfree shows some swap usage:
Code:
# free -h
total used free shared buff/cache available
Mem: 7.7Gi 5.2Gi 2.5Gi 21Mi 204Mi 2.5Gi
Swap: 7.5Gi 1.3Gi 6.2GiI did
swapoff -a and I could login instantly via Web gui. (my swappiness is 10)I changed it to 1.
If I turn swap back on, it is getting filled again, the IO load spikes and I cannot login via GUI:
Code:
free -h
total used free shared buff/cache available
Mem: 7.7Gi 5.3Gi 2.4Gi 21Mi 189Mi 2.3Gi
Swap: 7.5Gi 1.2Gi 6.2Gi(Note: I have a zpool ans the arc is limited to 4G)
Why can't I login via web gui under such moderate load if the SWAP is being used?
How come 1.4G of swap is used despite having 2.5G RAM available right after re-enabling swap.
Last edited: