cosign-discuss at umich.edu
general discussion of cosign development and deployment
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: FW: Apache, Cosign, PHP, Oracle client and PostgreSQL (fwd)
Can someone on this list aid us in working through this issue? We are
trying to use apache 2.0.52, php 5.0.2 to access an oracle database. We
are using the apache2 filter from cosign-1.6.2 for authentication. The
base operating system is Redhat Enterprise with the apache and php rpm's
removed and the packages above compiled from source.
The webserver tends to be unstable and will start to throw 'service
unavailable' errors after operating some time. Has anyone else had any
similiar issues, or can anyone shed any light on this issue? Apache seems
to run fine without the cosign activated. Thanks.
School of Dentistry Programming Services
---------- Forwarded message ----------
Date: Wed, 15 Dec 2004 14:47:37 -0500 (EST)
From: LANE WILLIAM HOY <lanewhoy@xxxxxxxxx>
To: Rick Getchell <rgetchel@xxxxxxxxx>
Subject: Re: FW: Apache, Cosign, PHP, Oracle client and PostgreSQL
We are using Apache 2.0.52, php 5.0.2, and cosign 1.6.2 (with the apache2
filter), and Oracle 10g for the client libraries. Everything except the Oracle
software was compiled from source, and php was compiled with the --with-oci8
flag (among others).
The cosign will work for a while after apache is started, but will eventually
start giving 'server not available' errors after a while. Http requests are
forcibly redirected to the TLS/cosign-enabled virtual site via mod_rewrite.
On Wed, 15 Dec 2004, Rick Getchell wrote:
From: Willie Northway [mailto:willn@xxxxxxxxx]
Sent: Wednesday, December 15, 2004 1:24 PM
To: Rick Getchell
Subject: Re: Apache, Cosign, PHP, Oracle client and PostgreSQL
On Dec 15, 2004, at 11:38 AM, Rick Getchell wrote:
Anybody gotten Apache, Cosign, PHP, Oracle client and PostgreSQL to
play together nicely on Redhat? If not Redhat, a different
The SPG site:
was run on apache / php / oracle client talking to an oracle server on
Solaris protected by cosign for about 2 years. A few months ago, we
transferred it to UMCE Linux. How are they not playing nicely together?
What's happening, or what error messages are you seeing?
Have you found that some packages will play together well, but when you
add something else into the mix, that it breaks? This shouldn't
necessarily be an issue with redhat.
If you feel it's specifically a cosign issue, you can send email to
Willie Northway University of Michigan Webmaster Team