Re: DB::connect sometimes die
| From: | Stefan Neufeind | Date: | Thu, 03 Jun 2004 16:18:12 +0000 |
| Subject: | Re: DB::connect sometimes die | ||
| References: | 1 | Groups: | php.pear.general |
| Request: | Send a blank email to pear-general+get-12875@lists.php.net to get a copy of this message | ||
On 3 Jun 2004 at 18:11, Sönke Ruempler wrote:
> today i noticed that DB:connect sometimes yust lets the php script exit
> without any message.
>
> Versions are:
>
> Apache 1.3.29
> PHP 4.3.6
> DB 1.6.4
> MySQL 4.0.18
>
> That happens only on one server, other servers with the same configuration
> don't do :(
>
> With normal mysql_connect function, that never happens. In the mysql access
> log there are no entries, too :-(
>
> I tried with DB debug mode = 10, no results.
>
> How can i debug that???
Stresstesting possibly? Hmm, it's strange that you say that direct
mysql-access works like a charme without any problems. My first
thought was that on one server mysql receives too many connections
and doesn't allow any more, while on the other servers there are
still connections available.
Do you use persistens connections with DB which you don't when
connecting directly?
Do you run the same versions on the other servers?
Could you run a test-script multiple times automatically on the
problematic server but access mysql from a known-working-server? This
way you could track down if possibly mysql is the problem or
Apache/PHP.
Try to write a test-script that simply connects to a db, grabs a
given text from the DB and compares it locally. Insert debug-output
on every stage (e.g. connect, then check if connected etc.) and see
where the problem occurs. Also you might want to try to set
error_reporting(E_ALL) in your test-script to be aware as soon as any
illegal type-casts occur or something that might be a hidden cause
for problems.
Good luck,
Stefan