Gossamer Forum
Home : Products : Gossamer Links : Discussions :

Urgent: Memory leak

Quote Reply
Urgent: Memory leak
Hi,
I have the latest version of LinkSQL upto 3 weeks ago. suddenly my hosting account was suspended due to bringing server down. I was told search.cgi consume over 1GB memory. My database was only 3-4k links.
Site was hosted on mid-size shared server dual CPU P4 Dell server. Can someone from Gossamer team help me trace why links consume so much memory.

Regards
Quote Reply
Re: [jasy007] Urgent: Memory leak In reply to
I'm guessing like most people, you do not search for any information on your Problem!

http://www.gossamer-threads.com/...p;sb=score&mh=25

Last edited by:

rascal: Jan 14, 2007, 3:17 PM
Quote Reply
Re: [rascal] Urgent: Memory leak In reply to
In Reply To:
I'm guessing like most people, you do not search for any information on your Problem!

http://www.gossamer-threads.com/...p;sb=score&mh=25

I had already looked at the threads, none of them applies. Moreover this is 3.x ver. A small database of 2k-3k took over 1GB ram, that is something wrong somewhere.
Quote Reply
Re: [jasy007] Urgent: Memory leak In reply to
It's hard to say what the problem was without some way of reproducing the problem. We haven't had any reports with problems with the search so it may be an isolated incident. If you can find out what exactly caused it (eg. search terms, type of search, etc), we might be able to look into it, but with the current information, there's not much we can do.

Adrian
Quote Reply
Re: [brewt] Urgent: Memory leak In reply to
As I was told, it was caused during searching of term "Xdvid", the process brought down the server as it consumed all available physical memory.

Also, after logging into cpanel, I notice it was perl 5.8.4 & I asked them to update to latest released now at 5.8.8 (although they updated to 5.8.7)
perl on the website mentioned some kind of leak not sure if it was linked to this issue.
http://search.cpan.org/...pod/perl586delta.pod

also http://search.cpan.org/...pod/perl588delta.pod



ORIGINAL EMAIL:-
Your account on the Thames server was suspended this evening after an outage was caused by a portion of your site:

22-18 22094 0/5758/72622 _ 293.70 75 1150 0.0 53.19 1132.55
84.124.150.XXX xxxxxxx.xxxxxxxxxxxxx.com GET
/?query=Xdvid&/Xdvid.html HTTP/1.1


This particular request consumed over 1GB of memory on the server and escalated everything out of control.

This type of behavior cannot be tolerated in our shared environment, you will either need to locate a new provider, or consider an isolated environment where your actions won't affect other users.

Thank you,

Thomas XXXXXX
XXXXXXXX, LLC

Last edited by:

jasy007: Jan 16, 2007, 10:45 AM
Quote Reply
Re: [jasy007] Urgent: Memory leak In reply to
Are you sure that query went to glinks? The log entry only says that it's going to /, so unless you have a rewrite rule changing that to search.cgi it probably isn't glinks. It also doesn't look like a search query that glinks would create by default.

Your ISP suspended your account due to a single problem with your site (has anything like this happened before)? That seems a little extreme.

Adrian
Quote Reply
Re: [brewt] Urgent: Memory leak In reply to
yes it does seems extreme, may be they were looking for scapegoat when their server went down, anyway the script may have consumed that much memory, but as far as where lies the problem not sure... it could be issue with perl or mysql or apache etc... also. But if that is true, the script may have triggered that weekness or it could be just script issue also.

as far as URL...

it's
search.xxxxxxx.com\?query=XXXX
in fact it is same as...

www.xxxxxxx.com/search/search.cgi

as you know I created sub domain by the dir name...
so www.xxxxxxx.com/search became search.xxxxxxx.com/
I did another smart thing...
created index.html file in search dir
and placed...
<!--#include virtual="/search/search.cgi"-->
inside it.