Server overload

New Member Joined: Mar 27, 2005 Posts: 18

Thanks Raven.
The change in the mail add. worked.
I am using 6.9 version of PHP-Nuke atm (with ChatServ's patches and your Sentinel program). A few weeks back, my web host reported that I am using about 60% of server resources thereby setting my website under suspension.
I hardly get about 20-30 visitors (at one time) on my website. So how could I be using that many resources ? I am on a shared host btw.
I am in the process of changing my web host anyway. But can you give me any leads ?
Again, since a few days back, no members (including myself as the God admin) cannot log in to the site. It gives a "warning; header information already sent" and it mentions the path to my config.php and auth.php and sends me back to the login page (I forgot the exact error message. But I can get it only when they re-enable my website).
Any ideas on this ?

Regards.

Posted: Sun Mar 27, 2005 8:21 am

I would ask them to provide a slow query log for the site if they would. Obviously we can't view your site right now to look for the obvious offenders. But there are several threads throughout the site dealing with perfomance in general.

Older tracking modules, who is where, who is online, surveys would all be suspect. Look at the blocks in particular many generate as many queries as you would expect to find on a full page. Using Cache-Lite (Raven has a very nice admin CP for it very reasonably) to cache some of these blocks can provide a lot of relief.

If your not using the Nuke Sentinel harvestor blocker it would be a good idea to enable it or consider blocking those in htaccess otherwise.

Your host can provide you with the best information if they are willing to work with you. But otherwise you are kind of on your own to find and resolve the issues and might find you logs the best place to start.

The headers already sent error is well documented and there are several simple solutions outlined here: http://www.ravenphpscripts.com/faq-2-Nuke+.html-+Troubleshooting#17

Site Admin/Owner Joined: Aug 27, 2002 Posts: 17088

FreeSpirit,

Glad that worked! Feel free to contact me about a hostingquote - you won't be sorry!

Posted: Sun Mar 27, 2005 11:38 pm

Thanks sixonetonoffun,
I don't use who is where, who's online or surveys at the moment. But hmm... yeah.. using CacheLite would be a good idea. I had used it before actually, but I had disabled it. That was a long time back.
I am using the NukeSentinel program. For the harvesters (Sentinel blocked a lot of them) I just used to redirect them to http:// . Maybe I should have added the 127.0.0.1 like some others do.... har...har....
My host doesn't provide me with any leads - that's the problem. I believe the "slow query log" you mentioned would be Greek to them.
Thanks for the link to rectify most Nuke problems. Those are very helpful for any Nuker. But the error message I mentioned was not listed there. I believe it could be solved. But I really can't when I cannot even log in to my cpanel now. I'll try to look into it as soon as my site's re-enabled.

Raven,
I'll get in touch with you soon enough. Smile

. Thanks.

Posted: Sun Mar 27, 2005 11:47 pm

As Six said, http://www.ravenphpscripts.com/faq-2-Nuke+.html-+Troubleshooting#17 - that is the link that should resolve the header's error.

Posted: Mon Mar 28, 2005 9:53 pm

In your honest opinion, is the 6.9 version of PHP-Nuke secure ? I had it running pretty well until lately. I hadn't made any changes but I got the "warning; ....." error message suddenly.

Posted: Mon Mar 28, 2005 9:58 pm

I run it here Smile

. The warning message has nothing at all to do with security. It has to do with how and when data is fed to the browser.

Posted: Mon Mar 28, 2005 10:20 pm

Yeah Raven... I had a feeling you run 6.9 as well. Smile

I remember browsing through your forums a few months back and you mentioned that you're sticking on 6.9 when others were already onto 7.x. That was the reason why I upgraded my the then 6.7 to 6.9 Razz

and stuck with it.
Let my *%$#@$# web host re-enable my site and then let me try to have a look at the problem again.