Date: Fri, 8 Feb 2002 09:13:22 -0600 From: "Jaime Bozza" <jbozza@thinkburst.com> To: "'Olivier - Triple X Networks'" <olivier@triplexnetworks.com> Cc: <freebsd-stable@freebsd.org> Subject: RE: Re[2]: Apache/PHP/Mysql problems with stable Message-ID: <007c01c1b0b3$263ed0d0$6401010a@bozza> In-Reply-To: <2778619969.20020208160152@triplexnetworks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
<G> If you noticed, that was a message to me. I've had some long conversations dealing with this problem. Needless to say, it's not a FreeBSD problem at all, but a PHP problem. The only reason it didn't show up in versions previous to PHP 4.1.0/4.1.1 was due to the fact that they changed the internal structures in 4.1.0/1, which caused the segfaults. Basically, your session_read function is probably returning "false" when there is no data. It needs to return a blank string (return '';) instead. This will make the segfaults disappear. (Apparantly, Yasuo fixed this problem in the latest CVS, so it may come out for 4.2.0, but the above fix works perfectly. PHP was treating the return value as a string *always*. When you return "false", it caused the internal pointers to get all messed up, causing PHP to crash at trying to save the session data.) The PHP-Dev list is where most of the conversation actually happened. Jaime -----Original Message----- From: Olivier - Triple X Networks [mailto:olivier@triplexnetworks.com] Sent: Friday, February 08, 2002 9:02 AM To: Jaime Bozza Cc: freebsd-stable@freebsd.org Subject: Re[2]: Apache/PHP/Mysql problems with stable Hello Jaime, Yes - I am. When looking for user-defined session handler problems on google, I found this interesting similar problem: http://www.phpbuilder.com/mail/php-general/2001121/1234.php There is no solution given on that thread - if you know one, I would be more than interested to hear :) Olivier. Friday, February 08, 2002, 3:40:52 PM, you wrote: JB> By any chance, are you using a "user-defined" session handler in JB> PHP? JB> Jaime Bozza JB> -----Original Message----- JB> From: owner-freebsd-stable@FreeBSD.ORG JB> [mailto:owner-freebsd-stable@FreeBSD.ORG] On Behalf Of Olivier - JB> Triple X Networks JB> Sent: Friday, February 08, 2002 8:21 AM JB> To: freebsd-stable@freebsd.org JB> Subject: Apache/PHP/Mysql problems with stable JB> Hi, JB> Since I upgraded to 4.5-STABLE from 4.4-RELEASE, I keep getting JB> these JB> errors: JB> Feb 7 17:39:42 core /kernel: pid 6594 (httpd), uid 80: exited on JB> signal 11 Feb 7 18:02:31 core /kernel: pid 6074 (httpd), uid 80: JB> exited on signal 11 JB> Feb 7 18:13:27 core /kernel: pid 2864 (httpd), uid 80: exited on signal JB> 11 JB> Feb 7 18:19:20 core /kernel: pid 4872 (httpd), uid 80: exited on signal JB> 11 JB> Feb 7 18:21:56 core /kernel: pid 2868 (httpd), uid 80: exited on signal JB> 11 JB> Feb 7 18:29:14 core /kernel: pid 6029 (httpd), uid 80: exited on signal JB> 11 JB> Feb 7 18:30:26 core /kernel: pid 7608 (httpd), uid 80: exited on signal JB> 10 JB> Feb 7 18:32:44 core /kernel: pid 4546 (httpd), uid 80: exited on signal JB> 11 JB> Feb 7 18:42:48 core /kernel: pid 3496 (httpd), uid 80: exited on signal JB> 11 JB> (notice the signal 10 - this occurs occasionally) JB> I'm running apache 1.3.23, PHP 4.1.1 & MySQL 3.23.47 JB> I have only seen the problem occuring on a PHP webpage which is JB> linked to a MySQL database - but it's possible that it also JB> interrupts non-php webpages - no guarantee. JB> Anyone know how I can track the source of this problem? Or what I JB> should do? JB> I already stress-tested my new kernel by doing a make buildworld, JB> which went perfectly fine without any problems at all. JB> Additional note: I have upgraded my ports collection - before this I JB> was running apache 1.3.22 and an older PHP/Mysql version. I have JB> never had problems. JB> To Unsubscribe: send mail to majordomo@FreeBSD.org JB> with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?007c01c1b0b3$263ed0d0$6401010a>