*sigh* someone who is familiar with bugs

[fandelem]

(from previous versions of mysql)

my webserver has:

mysql Ver 11.6 Distrib 3.23.28-gamma, for pc-linux-gnu (i686)

which is not the latest version.

but here is my problem: I have narrowed it down to only when php accesses mysql does it return "Unrecognized Response" errors and "Document Contains No Data" errors. If it is just a PHP script, it works flawlessly.

So, that leads me to believe it is something either with PHP configured wrong interfacing with Mysql, or Mysql not at the current version.

So.. have their been any bad reports with this version? Actually, I have never heard of the 'gamma' version -- what exactly is it? (in regards to alpha, beta, etc..?)

Anyways, another eerie thing (as my webserver is reluctant to assume it is their fault so I have done almost everything in my power to assure myself and them that it is not my script) -- you can go here: http://www.fandelem.com/lyrics/test.php to see my entire server stats, but here is the part that concerns me:

Under the Apache heading:

Hostname : Port fandelem.com : 0

shouldn't this be fandelem.com : 80 ???

i'm curious, what exactly results when this is 0? I would think it my entire website wouldn't be working, but everything aside from mysql/php interaction works flawlessly. perhaps this is used when mysql returns to the script and then there in lies the error? hmmm

have i been clear enough? i hope so, if not, basically, go to http://www.fandelem.com/lyrics/ and click around for like one minute and you will get errors eventually (it is all php/mysql interaction)

thanks so much to anyone who replies,

~kyle

[kparker]

That 'port 0' is definitely wierd, and it can't be literally the case: I most certainly am getting it on port 80 when I try it.

One thing to be sure, before going further, is that you are checking the return values from all your mysql functions and displaying mysql_error() when they fail: that might tell you something more.

[fandelem]

hehe laugh, i guess it would not exclude many people, you got me there.

and yes, with every query i have something like: $sql_result = mysql_query($sql) or die ("Couldn't execute query. (showlinks()) ".mysql_error());

but you see, it doesn't actually spit back any sort of error when this occurs. in IE, it says, "Cannot find Server (as the title) and gives you the generic 'The Page Cannot Be Displayed' error" -- and Netscape gives the infamous "Document contains no data" -- and in lynx it gives: "Alert!: Unexpected network read error; connection aborted. Unable to access document"

the unfortunate wrench, is that this happens sporadically. what could be the cause of sometimes it works, and sometimes it will not?

hot damn! okay i was sitting on the webserver running top and trying to get a page error that usually happens, and i did.. and check this:

0 nobody 1 0 11624 11M 10804 S 0 0.3 9.0 0:00 httpd
24294 nobody 1 0 0 0 0 Z 0 0.1 0.0 0:00 httpd <defun
24586 nobody 1 0 11028 10M 10660 S 0 0.1 8.6 0:00 httpd
24641 nobody 0 0 11264 10M 10724 S 0 0.1 8.7 0:00 httpd
24642 nobody 1 0 11024 10M 10652 S 0 0.1 8.6 0:00 httpd

what does that defunct mean?

sigh, i wish i had access to the logfiles. i have access to my personal error_log and access_log however they do not show anything when this occurs.

so, it seems like it is something specifically wrong with apache, and not really mysql or php; is that safe to assume?

thanks for responding.. i wish i could get this fixed 🙁

[kparker]

defun[ct], plus the Z in the status column, make it sound like a zombie process: i.e. one that has no owner. Something somewhere is crashing; can you find nothing interesting in apache's error log? Clearly, it's a problem with httpd, but remember that if you're running mod_php then php is compiled into the httpd executable, so it may still be something wrong with php rather than the base apache.

[fandelem]

okay, well answer me this: for every zombie process / defun[ct] process, would it be in the logs? (even though i don't have access to them, i can still make them look at them and maybe they will know what is up)

hmm..

Loaded Modules
mod_php4, mod_jds, mod_setenvif, mod_so, mod_headers, mod_expires, mod_digest, mod_auth_dbm, mod_auth_anon, mod_auth, mod_access, mod_alias, mod_userdir, mod_actions, mod_asis, mod_cgi, mod_dir, mod_autoindex, mod_include, mod_info, mod_status, mod_negotiation, mod_mime, mod_mime_magic, mod_log_config, mod_env, http_core

i take it that it is compiled as a module. well they have the latest version of php..

oh, i forgot to mention earlier, but last night i installed mysql/php/apache on my home server and it works flawlessly -- no crashes or anything what i experience on my actual webserver (sigh, i wish i had faster than 56k -- i'd host it my self). so i guess it narrows it down to the problem being on their heads, not on mine, right (ie. it probably isn't my script making them run out of memory or something.. seeing how my home server is a p133)?

where should i go from here? just tell them that i found a zombie/defunct process when the crashing occurs, and that it seems like it is an apache/php problem? (exclude mysql from the equation??)

thanks,

kyle

[kparker]

mod_php4 ... compiled as a module

Exactly. All I can suggest is to whine at them until they discover/fix the problem. :-)

[fandelem]

heh heh check it out:

actually, i found the problem. and it seems to be
much bigger than what i am experiencing. i believe
they are out of memory,
hardcore 😉

sifting through error files, i found this in apache's (keep in mind this is only the last few lines)

FATAL: erealloc(): Unable to allocate 61440 bytes
FATAL: erealloc(): Unable to allocate 61440 bytes
FATAL: erealloc(): Unable to allocate 61440 bytes
FATAL: erealloc(): Unable to allocate 61440 bytes
FATAL: erealloc(): Unable to allocate 61440 bytes
FATAL: erealloc(): Unable to allocate 61440 bytes
[Tue May 1 05:20:50 2001] [notice] child pid 13437 exit signal Segmentation fau
lt (11)
FATAL: erealloc(): Unable to allocate 61440 bytes
FATAL: erealloc(): Unable to allocate 61440 bytes
FATAL: erealloc(): Unable to allocate 61440 bytes
Out of memory (Needed 8164 bytes)

and what makes me positive this is the problem...
when I try my error, these exact lines replicate in the
error file. 😉

my guess is that it isn't just happening to my website,
seeing how i am 'tail'ing this file and not accessing my
website and more out of memory errors are appearing..

(well, at least i feel better knowing it isn't me being paranoid)

do you think they just need to put in more memory and they will be fine? (i feel so relieved if that is the only problem, even though i wish i knew how to fix the fandelem:0 problem..)

thanks,

kyle

[fandelem]

not to mention the error file was 24 megs. yawns after five painful hours