What's wrong with my new vps on Jabba?

[esonline]

Hi

I have three vpses with Jaguarpc currently. Apparently, one of them -- on Jabba -- has been giving problems in these first weeks of my getting it.

Three days ago, I receive email messages such as those below just before the server went down:

FATAL: emalloc(): Unable to allocate 752 bytes
/bin/bash: line 1: 17783 Terminated ./iworx.pex --fively

/bin/bash: line 1: 25655 Segmentation fault ./iworx.pex --fively

JaguarPC staff said: "We have checked and found your VPS was hitting memory paramter 'privvmpages'.We have restarted your VPS to fix the error of your interworx panel and it is loading fine now.If the problem persists then you may need to upgrade ram on your VPS so that you may not face this issue any further."

I said: "WHat I don't understand is that I should need to upgrade RAM when this vps is a spare vps that has only one active website running on it. I am merely keeping this vps for future expansion needs so I don't mind it hosting just one website."

Early this morning (wee hours of the morning where I live halfway around the world), the server spewed warning email messages such as:

bin/bash: line 1: 30444 Terminated ./iworx.pex --fively

/bin/bash: line 1: 32257 Terminated ./iworx.pex --fively

/bin/bash: line 1: 22040 Terminated ./iworx.pex --fively

I reopened the support ticket and went back to bed.

Then the server went down.

JaguarPC staff said: "When I checked your VPS was in mounted state. I have started it. Nodeworx is loading fine and I am able to login without any error/problem."

The thing is that there is only ONE (1) active website running on this vps. AND this website is mostly serving visitors when USA is asleep and my part of the world is awake.

Early this morning, when the vps went down, my part of the world was asleep and there wasn't much activity on the vps.

So, I think it is not the single website that is causing problems.

If that is the case, then what is wrong with this vps?

Here are the specs: Discovery Plan 192MB RAM Interworx Control Panel
Here are the website's stats: 30 July 2007 9400 hits 3000 pageviews 500 visits
31 July 2007 8800 hits 3600 pageviews 290 visits

Three days ago, JaguarPC staff also said: "I have tried to figure out the problem related to memory usage at the moment but as currently the server is running fine so could not find the reason as why the VPS goes under resource shortage. If this happens again, we will need to check for this first without having the server to be restarted."

So when I reopened the ticket early this morning after the vps spewed out warning messages, I thought the chaps would "check for this first without having the server to be restarted" but I only got a "When I checked your VPS was in mounted state. I have started it. Nodeworx is loading fine and I am able to login without any error/problem." answer this morning.

I have left the ticket open.

I believe the vps was down for a good five hours.

What should I do?

Should I do away with this 3rd vps (with only 1 active website) and transfer the website to another Freedom vps that I have with JaguarPC?

OR

Should I continue having this 3rd vps and bear these little stomachaches that it gets every so many days?
In the ticket, three days ago, I had remarked "(Of course I can simply move this website to another FREEDOM vps that I have with you that has only two websites on it, and the problem will be solved but that's not my intention as I wish to keep this 3rd vps. I don't mind paying for it though it's underused)"

HELP!

[Rob]

You could always completely re-install the vps from Virtuozzo and see if that solves the memory problem.

Looking on the interworx website for system requirements its stating that it will run on 128MB but they recommend you have at least 256MB of memory for it to run properly.

So if you do decide to re-install the VPS and it still presented you with issues you could try a memory upgrade or switch control panels to say plesk if your only hosting 1 domain you wont need 256MB ram for plesk to run.

Or failing that just switch the site to one of your other servers and scrap the broken one

[thisisit3]

Could this be related to a known problem with the virtuozzo kernel? might be worth a look.

[Gwaihir]

It's probably not the one website that's short on memory, but the control panel. Frankly, I thought they'd altogether stopped putting control panels on VPSes with less than 256MB.