Proxmox VE 3.0 unable to login to web interface

[asaguru]

Hi,

I am using proxmox VE 3.0 i am able to login to server with same password but i am not able to login to server web interface. i am already using same server web interface more the 5month suddenly it stop working while trying to login it is saying "Login failed, please try again"

i restarted the server, tried to restart the pveproxy

pveversion -v
pve-manager: 3.0-20 (pve-manager/3.0/0428106c)
running kernel: 2.6.32-20-pve
proxmox-ve-2.6.32: 3.0-100
pve-kernel-2.6.32-20-pve: 2.6.32-100
lvm2: 2.02.95-pve3
clvm: 2.02.95-pve3
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-1
pve-cluster: 3.0-4
qemu-server: 3.0-15
pve-firmware: 1.0-22
libpve-common-perl: 3.0-4
libpve-access-control: 3.0-4
libpve-storage-perl: 3.0-6
vncterm: 1.1-3
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-12
ksm-control-daemon: 1.1-1

syslog

Mar 16 19:18:11 proxmox2 kernel: Neighbour table overflow.
Mar 16 19:18:11 proxmox2 kernel: Neighbour table overflow.
Mar 16 19:18:11 proxmox2 kernel: Neighbour table overflow.
Mar 16 19:18:11 proxmox2 kernel: Neighbour table overflow.
Mar 16 19:18:11 proxmox2 kernel: Neighbour table overflow.
Mar 16 19:18:16 proxmox2 kernel: __ratelimit: 2141 callbacks suppressed
Mar 16 19:18:16 proxmox2 kernel: Neighbour table overflow.
Mar 16 19:18:16 proxmox2 kernel: Neighbour table overflow.
Mar 16 19:18:16 proxmox2 kernel: Neighbour table overflow.
Mar 16 19:18:16 proxmox2 kernel: Neighbour table overflow.
Mar 16 19:18:16 proxmox2 kernel: Neighbour table overflow.
Mar 16 19:18:16 proxmox2 kernel: Neighbour table overflow.
Mar 16 19:18:16 proxmox2 kernel: Neighbour table overflow.
Mar 16 19:18:16 proxmox2 kernel: Neighbour table overflow.
Mar 16 19:18:16 proxmox2 kernel: Neighbour table overflow.
Mar 16 19:18:16 proxmox2 kernel: Neighbour table overflow.

Regards,
Asaguru

 

[vgstech]

You need to increment the ARP limits of your server.


First step:

The solution to the problem is to increase the threshold level for the network devices

To check the present threshold level 1

cat /proc/sys/net/ipv4/neigh/default/gc_thresh1

It will give some value as 128 or 256 or 512.

This can be increased to the next level. Like if the value is 128 then make the thresh1 value as 256 and thresh2 as 512 and thresh3 as 1024.

echo 256 > /proc/sys/net/ipv4/neigh/default/gc_thresh1
echo 512 > /proc/sys/net/ipv4/neigh/default/gc_thresh2
echo 1024 > /proc/sys/net/ipv4/neigh/default/gc_thresh3

This will stop the Error messages that were recieved in the log file.

Second step:

Doing changes permanent, add these values to /etc/sysctl.conf file like that:


# Force gc to clean-up quickly
net.ipv4.neigh.default.gc_interval = 3600


# Set ARP cache entry timeout
net.ipv4.neigh.default.gc_stale_time = 3600


# We increase the thresholds for ARP tables
net.ipv4.neigh.default.gc_thresh1 = 256
net.ipv4.neigh.default.gc_thresh2 = 512
net.ipv4.neigh.default.gc_thresh3 = 1024


This resolve the same problem for me.


Regards