Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...

Database Forum / Ingres Topics / May 2005

Tip: Looking for answers? Try searching our database.

PHP times out waiting for an ingres connection

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
jferrell1@hotmail.com - 28 Apr 2005 21:57 GMT
This is an intermittent problem I've been running into with PHP and
Ingres.  We're running PHP with Apache on HPUX connecting to an Ingres
2.6
database using the r3 client tools (this happened with the 2.6 tools as
well.)  This isn't due to a corrupted install of something as this
happens on both the primary webserver and the backup webserver (backup
is just a B2000 workstation and has no more that 10-12 users on it at
any one time, the primary has around 100 users on average)

I get a timeout error (maximum execution time of 30 seconds...)
intermittently that is reporting that the line where the page timed out
was where we do an ingres_connect() statement.  We've tried restarting
apache every night, switching to using ingres_pconnect(), bumping up
the number of allowable inbound connections to gcc, bumping up the
number of gcc's running, setting apache httpd processes to die after
handling 10 requests, verifying the the database server's gcc processes
can handle the number of connections, and other steps that I can't
think of off the top of my head.

The problem is intermittent but driving me crazy, I can't find any
information on this anywhere.
Artur Fajok - 29 Apr 2005 06:25 GMT
> This is an intermittent problem I've been running into with PHP and
> Ingres.  We're running PHP with Apache on HPUX connecting to an Ingres
[quoted text clipped - 17 lines]
> The problem is intermittent but driving me crazy, I can't find any
> information on this anywhere.

Check DNS settings - I have strong feelings, that this is DNS related.
Are both machines using same DNS server? Are they known to it? RevDNS is
set up?

Regards,
Artur Fajok
jferrell - 06 May 2005 01:18 GMT
> Check DNS settings - I have strong feelings, that this is DNS related.
> Are both machines using same DNS server? Are they known to it? RevDNS is
> set up?
>
> Regards,
> Artur Fajok

I checked and DNS is working correctly.  I think this is specific to
Apache 1.3.28 on HPUX utilizing PHP & Ingres (not a large demographic).
We didn't have this problem before upgrading to 1.3.28.  I set up a
linux server running Apache 1.3.33 and moved the site over there, no
problems so far, also downgrading the old server (the HP I was
originally writing about) away from Apache 1.3.28 seems to have fixed
the problem.
faxio@email.it - 06 May 2005 12:09 GMT
Hi,
I have the same problem with a configuration IIS + Ingres + Php.
Any ideas?
grant - 09 May 2005 15:50 GMT
hi,

Are all connections hanging or just occasional connections? Which
interface are you using to connect to Ingres; ODBC or native Ingres?
What versions of Ingres, PHP and IIS/Windows are you using?

ta

grant
faxio@email.it - 10 May 2005 14:15 GMT
All connections dies due timeout.
I use an ODBC connection, native ingres functions does not work.
Ingres version: 2.6
PHP: 4.3.11
IIS: 5
Windows XP
grant - 10 May 2005 15:08 GMT
That combination of software should work ok. The only thing I can think
of is that the process owner of the web server (normally
IUSR_machinename) is not a valid Ingres user.

g
grant - 09 May 2005 15:44 GMT
out of interest,

was php rebuilt with the newer apache?
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.