Oops, I spoke too quickly. The problem isn't with the close, it's with
the door_info() syscall. Perhaps file descriptor 8 isn't a door ...
[billy]
--
/-=[ BILLY S HALSEY ]=--\
| Member of Technical Staff, Sun Microsystems, Inc. ESP Solaris SW |
|
Sorry bout that;
http://www.stetson.edu/~paland/phptruss.txt
On Fri, Jun 21, 2002 at 06:44:28PM -0700, Billy S Halsey wrote:
> You need to paste a little more of the output. Looks like it's got a
> problem trying to close file descriptor 8. If you scroll up a bit more,
> you'll see a call to
You need to paste a little more of the output. Looks like it's got a
problem trying to close file descriptor 8. If you scroll up a bit more,
you'll see a call to open() with a return value of 8. That will show the
file it is trying to open and then close. For some reason it appears
that it is
Thanks.
I was running it without the -f and not getting much.
Running a truss -f httpd I get the normal first process that forks and
then on the second process I get:
29958: fcntl(8, F_SETFD, 0x0001) = 0
29958: door_info(8, 0xFF23A460)Err#9 EBADF
Patrick,
Try running it thus:
truss -f apachectl start
That should tell you where it's dying.
[billy]
--
/-=[ BILLY S HALSEY ]=--\
| Member of Technical Staff, Sun Microsystems, Inc. ESP Solaris SW |
| "All opinions and technical advice offered
Not really, no. You can run httpd directly from within gdb and see what it
says. Otherwise I would suggest recompiling both Apache and PHP from
scratch.
The combination of Apache 1.3.26 and PHP 4.2.1 works fine.
-Rasmus
On Fri, 21 Jun 2002, Patrick Aland wrote:
> Thats the thing. There is no
Thats the thing. There is no error message. apachectl start says that
apache started. However when you look there are not httpd processes
running. I comment out the load module and it works.
Theres nothing in the apache error logs either. Is there some way to
increase the debugging?
On Fri, Ju
Without the actual error message, there is nothing we can do.
On Fri, 21 Jun 2002, Patrick Aland wrote:
> Hey all,
> I just upgraded to 4.2.1 on apache 1.3.26 and now apache won't start.
> If I comment out the LoadModule in the httpd.conf apache starts fine,
> otherwise it just starts and exit
Hey all,
I just upgraded to 4.2.1 on apache 1.3.26 and now apache won't start.
If I comment out the LoadModule in the httpd.conf apache starts fine,
otherwise it just starts and exits almost like it can't fork. I don't
get any error messages.
Running on Solaris 7 with gcc 3.1
I use postgres but
9 matches
Mail list logo
