rml704

Thanks, the old box might have had issues due to the processor I am guessing then since it was somewhere around 600 mhz with a gig of ram and it was killing mysql. The only other thing I can think of is it was the processor speed on the old box causing the problems?

and yes these sites are getting very little traffic atm – it is time I start pounding them and take advantage of what I am paying for here… ??

Ahh O.K. No I didn’t catch the linked article error – That helps explain alot… Can you tell me though … I can’t use free – m on my box so all I can get my readins off of is top, this is the most recent reading

Mem: 1467M Active, 202M Inact, 191M Wired, 76M Cache, 112M Buf, 3732K Free
Swap: 3901M Total, 16K Used, 3901M Free

I get now that the 1467M are active meaning they are being used to put pages in the cache essentially (what isn’t actually being used anyways) and I have another 202 megs that are inactive at this point I could still pull from.

How, if I can’t use the free -m command can I tell how much memory the box is actually using that isn’t in swap mode? Does the active memory ever reset itself ? Thanks for answeering a linux newbie’s questions and being patient! I actually was dropping my mysql db on the old server which is why I was so frieked about this when I saw it … especially after paying to upgrade it ??

Clark, not pulling anythign from Adsense deluxe in this situation.. as far as statcounter all it does is embed the counter in the footer… stupid plugin … regardless it makes things more organized but should only embed it into the code once and that’s it.. If it runs every time I woudl be suprised…

Error, I have to disagree WordPress is hogging the memory.. Let me explain. First of all I didn’t realize inactive memory was memory that would be freed up when needed so that helps the way the last one was shown. Here is another one after I clicked around in the wordpress backend about 20 times to different sections.. It gobbled up another 600 megs of memory as I had it down to roughly 700 megs active, just from clicking around..

Here was the readout after doing that

ast pid: 12553; load averages: 0.18, 0.13, 0.05 up 1+04:15:59 16:28:49
208 processes: 1 running, 203 sleeping, 4 zombie
CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle
Mem: 1316M Active, 355M Inact, 190M Wired, 74M Cache, 112M Buf, 4344K Free
Swap: 3901M Total, 16K Used, 3901M Free

Here is the readout after waiting a few minutes so the ram it is tying up should of been freed back up … but it isn’t

last pid: 12576; load averages: 0.01, 0.07, 0.04 up 1+04:18:20 16:31:10
203 processes: 1 running, 198 sleeping, 4 zombie
CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle
Mem: 1315M Active, 355M Inact, 190M Wired, 74M Cache, 112M Buf, 5572K Free
Swap: 3901M Total, 16K Used, 3901M Free

Basically every time I click anything in the wordpress backend I use about 20 megs of memory and it isn’t ever releasing it. So right now if I click 20 more times in the backend it will raise to using 1900M and I’ll be flat out of memory.

Best way to put my problem, is it’s as if whatever I do in the backend doesn’t ever quit using the ram until I manually kill the PIDs off .. if that makes sense?

Getting an error here too … anyone ?

There was another thread about this but I wanted to close this one for anyone else who has the same problem. I realized I had ‘force lowercase’ in my ftp options – so the files were all uploaded in lower case. Once I capitalized the proper letters in the file name it worked fine ??

Woot Woot – Found our problems … and I feel liek an ASS!!

You have your ftp set to make all files lower case upon uploading them… You need to change the case of that file and you will be good to go ??

Does this mean WP Is auto pinging after a post? If so where do I go to seee where? Sorry, beginner here…

Bump – same problem here … class-IXR.php

If I revert to 1.5 how to I ‘downgrade’ ?

It is apparently adding my entry but I think it has a problem with auto pinging for some reason.. This is the section of code where it is hitting a snag …

First line is 841

function weblog_ping($server = ”, $path = ”) {
global $wp_version;
include_once (ABSPATH . WPINC . ‘/class-IXR.php’);

// using a timeout of 3 seconds should be enough to cover slow servers
$client = new IXR_Client($server, ((!strlen(trim($path)) || (‘/’ == $path)) ? false : $path));
$client->timeout = 3;
$client->useragent .= ‘ — WordPress/’.$wp_version;

// when set to true, this outputs debug messages by itself
$client->debug = false;
$home = trailingslashit( get_option(‘home’) );
if ( !$client->query(‘weblogUpdates.extendedPing’, get_settings(‘blogname’), $home, get_bloginfo(‘rss2_url’) ) ) // then try a normal ping
$client->query(‘weblogUpdates.ping’, get_settings(‘blogname’), $home);
}