For about the last week I've been suffering with "memory allocation" errors bringing my vps to a grinding halt.
Processes go zombie and then numothersock and numfile gets blown shortly afterwards. When I try to check VZ it's not there (i.e. no response in any browser). The only way I can fix the problem is to reboot the vps (from SSH) but VZPP remains inaccessible until I raise a support ticket (#12555335) and they restart the main vps service.
This has happened 3 times in the last 4 days! :-(
This has only been a problem in the last few days and nothing significant has changed on my vps (although incoming emails - bounces to me generated by spammers spoofing a non-existent address in my domain - may have gone up recently).
I pressed support to explain why VZ is apparently crashing and I was told
"This can happen because of mis configurations in Service VPS. If this continues then we may have to reinstall Service VPS to get it fixed."
Coincidentally, Jag auto-rebooted my server (cerberus) a few days ago because
"The Node was inaccessible because of high load. It has already been rebooted and now the VPSs are coming up one by one. Once all VPSs will be up, we will keep the Node under monitoring to figure out that what caused the high load."
Is it possible that VZ crashing is causing the problems with my memory allocation errors? Could Jag have altered something to fix the "high load" that is crashing VZ? (or indeed is the "high load" - from some other vps- crashing vz?)
Geoff.


LinkBack URL
About LinkBacks
- crashing vz?)



Reply With Quote

Bookmarks