We keep running out of resources!

[Jim Oaks]

You guys keep seeing database errors or the site down. The sites going up and down. For some reason we're running out of resources. I'm working on it now.

 

[JFA_Spyderman]

Thanks for staying on top of it Jim!

 

[ArcticRaiders]

If you would like any help with any of it I have quite a bit of experience in that area and could help you if needed just send me a message

 

[almostclueless]

Dammit, Jim.......I'm a website owner, not a miracle worker!!!

 

[Jim Oaks]

The problem is kmemsize

The size of unswappable kernel memory allocated for the internal kernel structures for the processes of a particular VPS. We keep going in to the black zone.

Somewhere I thought I read that this memory isn't swappable, you should be using it up unless something was misconfigured. I don't know if trying to upgrade services to more memory will resolve this.

I can look at my Virtuozzo QoS Alerts and see us going Green, Yellow and Black Zones. I should be able to put 10 sites on this VPS and I'm running out of resources with 1. Doesn't make sense.

 

[Jim Oaks]

The system apparently shuts down resources (Apache) when we get close and then comes back up making the forum go up and down.

 

[Jim Oaks]

This is what I read:

kmemsize Kernel memory footprint, rated in bytes, is used to hold data about your processes, network connections. This memory is unswappable so its a hot commodity for RapidVPS to keep in check. Each process in a linux system uses 10-50kb of kernel memory. Like numproc, you won't surpass this unless one of your applications is misbehaving, in which case RapidVPS is saving its server from getting swamped.

 

[Jim Oaks]

kmemsize

held -------4625273
maxheld----4648725
barrier------16384000
limit--------18022400
failcnt-----25316546

 

[camma83]

Sounds like a memory leak issue, Where its not freeing up what was used, or replacing with new data, but just adding too it and eventually eats it all up. A system reboot will be a temp fix but not resolve it.

 

[Jim Oaks]

Ya, I can't figure out how to fix it.

It started out with an error in the PM's. We were getting a database error with error 17. vBulletin told me:

This error means:

System error: 17 = File exists

You or your host will need to clear out the contents of the server's /tmp directory and try again.

The file is in the /tmp folder. I tried deleting the file but couldn't.

 

[predator]

i am glad you guys know what you are doing.....its greek to me

 

[ArcticRaiders]

so this is hosted on a vps, where from if you don't mind me asking?

 

[Jim Oaks]

Sounds like a memory leak issue, Where its not freeing up what was used, or replacing with new data, but just adding too it and eventually eats it all up. A system reboot will be a temp fix but not resolve it.

I have to figure out how to find the memory leak.

I had to reboot tonight because I couldn't get to the PM's. Got the same Error 17 trying to write to the file in the /tmp folder.

 

[predator]

so is the problem fixed or is is band-aided?

 

[Jim Oaks]