VPS Kloxo/LXA Question
Question: How much ram should an install of Kloxo/LXAdmin use on a fresh install to a vps? I've just got a new vps and it shows 200mb ram used with nothing else on it, no domains or nameservers or anything set up yet and it seems a bit (a lot) excessive to me. As a comparison my current (old) vps is using 82mb ram with over 20 domains, including active web proxies, which is what I'd call normal. Cpanel then yeah, loadsa ram used for nothing but Kloxo?
For the techies and folks that know about these things - specs:
Old vps: 30GB hd, 768mb ram, 600GB b/w
OS: centos-5-i386-hostinabox576 + Kloxo Single Server 6.0.2083 Stable
New vps: 20GB hd, 512mb/1GB burst ram, 1TB b/w
OS: centos-5.5-x86 + Kloxo Single Server 6.0.2085 Stable (& Kloxo installed by support 'cause no hostinabox iso)
Is there something wrong with the new setup or is there some kind of phantom ram eating monster lurking in the machine hogging resources? Or was it installed wrongly? Support say I'm imagining problems and they do it the same to all their boxes. I know nothing of unix/linux etc. I'm more of a hardware kinda chap.
You can check output of top -c command, that would help you to see what is consuming more ram on your server.
I might if I knew how. My apologies but I have no idea what to type where and no idea where to begin. I'm afraid I need idiot proof instructions, sorry.
Originally Posted by BreezeHost
Do I need ssh for that? I've downloaded something called putty but haven't worked out what to do with it. Or can I do it in console on the solus vm thing? Or in Kloxo? (console is blank on that). I liked it better when it's got hostinabox, just rebuild and job done.
Kloxo itself has a bit where is shows resources - Admin Home > Servers > Processes - and according to that it's the mysql part using 135.92mb ram (/usr/libexec/mysqld --basedir=/usr --datadir=/var/lib/mysql --user=mysql --pid-file=/var/run/mysqld/) for whatever reason. My other vps uses 14.38mb for the same process so unless it's a version difference I can't explain it, it seems a bit excessive though. I even re-installed it myself and it was just the same, 200mb ram doing nothing :sigh:
I did try to terminate the mysql process, thinking I don't use the database for glype, and I won't be using zelune proxies. Oops! That was a bad idea, lol. That stopped kloxo working altogether "Unable to connect to MySQL Database", oh dear. A reboot sorted it but don't try this at home.
So it looks like I'm going to have to live with it for now, I'll see how it performs with a proxy or two on it next week, I've got other problems to sort now, my main comp had a h/d failure today, 1 drive on a raid 0 (main c drive) damnit! Looks unrecoverable too so it's on the backup now, that's 3 weeks old so I've lost 3 weeks data, grrr. Still, it's something else to worry about for now.