Re: Connect fails but only from this one file WHY
Hello.
Please provide complete PHP error message.
> that the bad new file is doing something bad that boggles subsequent
> connections? If so what?
Maybe. To find out what your file is doing with the server use the
following things:
http://dev.mysql.com/doc/refman/5.0/en/show-processlist.html
http://dev.mysql.com/doc/refman/5.0/en/Query_log.html
Gerald Taylor wrote:
> i am developing a php app. in the beginning of every file there is
> a require_once("./setup.php"); that does the housekeeping, fetches the
> connection credentials and connects to the database. All that worked
> fine until this morning I made a new file.
>
> Now I get a connection failure when I try to connect but ONLY from this
> one php file. I can connect to the server fine manually, the server is
> not unduly loaded, all the other apps that use this db server are fine
> and even the other files in THIS app using THIS particular db seem to be
> connecting fine. Well actually I should say that one of the other files
> *did* get this error once but on a subsequent call it corrected itself.
> I should also say that the "bad" file did connect fine the first time I
> ran it but I haven't been able to make it do it since. Is it possible
> that the bad new file is doing something bad that boggles subsequent
> connections? If so what?
>
> It is using exactly the same include file that works in all the other
> files.I'm stumped Thank you...
>
>
--
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
__ ___ ___ __
/ |/ /_ __/ __/ __ \/ /Gleb Paharenko
/ /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED]
/_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET
<___/ www.mysql.com
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Connect fails but only from this one file WHY
Gerald Taylor wrote:
i am developing a php app. in the beginning of every file there is
a require_once("./setup.php"); that does the housekeeping, fetches the
connection credentials and connects to the database. All that worked
fine until this morning I made a new file.
Now I get a connection failure when I try to connect but ONLY from this
one php file. I can connect to the server fine manually, the server is
not unduly loaded, all the other apps that use this db server are fine
and even the other files in THIS app using THIS particular db seem to be
connecting fine. Well actually I should say that one of the other files
*did* get this error once but on a subsequent call it corrected itself.
I should also say that the "bad" file did connect fine the first time I
ran it but I haven't been able to make it do it since. Is it possible
that the bad new file is doing something bad that boggles subsequent
connections? If so what?
It is using exactly the same include file that works in all the other
files.I'm stumped Thank you...
Without seeing the code or the error message(s), it is impossible to say. Show
us your connection code from the include file (hide the password, of course).
Show us the error you get from mysql. With that info, I'm sure someone can
diagnose the problem.
Michael
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Connect fails but only from this one file WHY
i am developing a php app. in the beginning of every file there is
a require_once("./setup.php"); that does the housekeeping, fetches the
connection credentials and connects to the database. All that worked
fine until this morning I made a new file.
Now I get a connection failure when I try to connect but ONLY from this
one php file. I can connect to the server fine manually, the server is
not unduly loaded, all the other apps that use this db server are fine
and even the other files in THIS app using THIS particular db seem to be
connecting fine. Well actually I should say that one of the other files
*did* get this error once but on a subsequent call it corrected itself.
I should also say that the "bad" file did connect fine the first time
I ran it but I haven't been able to make it do it since. Is it possible
that the bad new file is doing something bad that boggles subsequent
connections? If so what?
It is using exactly the same include file that works in all the other
files.I'm stumped Thank you...
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
