PVEProxy constantly needs a restart?

[runonthebuns]

Hello,

I've been experiencing some weird problems recently where the web interface won't load!
It's not just me, but everyone else as well who tries to access the web interface in it's unusual down time.
The only way that I know fixes this temp is to do "service pveproxy restart"


Here are the results for ioping /dev/sdb



and these are the results for doing free -g




I don't know how to pinpoint this problem or to fix it, any help will be great!

Thank you in advance,

 

[runonthebuns]

Pinging XXX.XXX.XX.XXX with 32 bytes of data:
Reply from XXX.XXX.XX.XXX: bytes=32 time=269ms TTL=45
Request timed out.
Reply from XXX.XXX.XX.XXX: bytes=32 time=271ms TTL=45
Reply from XXX.XXX.XX.XXX: bytes=32 time=285ms TTL=45


Ping statistics for XXX.XXX.XX.XXX:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 269ms, Maximum = 285ms, Average = 275ms

I get about 0%-50% loss most of the time. I can't load the login page.
The problem still persists. Anyone know how to fix it? I did a dist-upgrade hoping that it will fix it, but it didn't.

 

[Martin Cleaver]

Is your ip address changing?

 

[runonthebuns]

Is your ip address changing?

My IP address or the servers? The servers IP address is the same, and I believe my IP address is also the same.

 

[Martin Cleaver]

Ok I'd meant server.

Try some of these: http://www.linuxhomenetworking.com/...:_Simple_Network_Troubleshooting#.VIGHs2t5mSM

 

[runonthebuns]

Ok I'd meant server.

Try some of these: http://www.linuxhomenetworking.com/...:_Simple_Network_Troubleshooting#.VIGHs2t5mSM

That's a lot to read. Is there something that can help me pin down what the real problem is?

 

[Martin Cleaver]

Traceroute and hardware, I guess. Good luck.