Gossamer Forum
Home : Gossamer Threads Inc. : Custom Modification Jobs :

Full Links SQL and its globals and plug ins debugging

Quote Reply
Full Links SQL and its globals and plug ins debugging
Hi

Our site has been crashing almost daily due to overload..

WE have limited the problem to Links SQl and its applications..

Can anyone do a full debugging or Links SQL, Globals and plug ins and tell us what is the problem..

We only have FTP and SSH access to the server right now.
Regards
KaTaBd

Users plug In - Multi Search And Remote Search plug in - WebRing plug in - Muslims Directory
Quote Reply
Re: [katabd] Full Links SQL and its globals and plug ins debugging In reply to
Hi KaTaBd,

May be your site being attacked outside, not problem with internal scripts?

Just let me know if I could give a hand.

Cheers,

Cheers,

Dat

Programming and creating plugins and templates
Blog
Quote Reply
Re: [tandat] Full Links SQL and its globals and plug ins debugging In reply to
Hi

Thanks any help will be great, I still have FTP and SSH access..
If it is external at least we will know.

The host saying it is internal, BUT if it is can you find out what it is?
Regards
KaTaBd

Users plug In - Multi Search And Remote Search plug in - WebRing plug in - Muslims Directory
Quote Reply
Re: [katabd] Full Links SQL and its globals and plug ins debugging In reply to
Please send me that so that I can take a look

Regards,

Cheers,

Dat

Programming and creating plugins and templates
Blog
Quote Reply
Re: [katabd] Full Links SQL and its globals and plug ins debugging In reply to
A few ideas:

Check your error and access logs.

Also, if you can, run "top" to see what is chewing up the most resources/cpu

ps -ef or ps -aux can also help find processes that are long-running and/or chewing up resources.

If you are *not* running under Unix.... That's the problem ;)

internally, jump.cgi and/or search.cgi are the usual culprits. *sometimes* a corrupt database table will slow things down, so having your ISP run repair on the database might help.

If you are generating graphics, on the fly, *that* can be the issue, as imagemagic can chew up a lot of resources doing almost nothing.

netpbm and GD.pm can also chew up resources, but usually on a smaller level, though with multiple processes, it can add up.

If it's just volume, eg: your hits are way up and traffic is way up, switching to mod_perl (or a faster server with more RAM) may be the only/best solution.


PUGDOG� Enterprises, Inc.

The best way to contact me is to NOT use Email.
Please leave a PM here.