Apache 1.2.3: fopen: Error 0: could not open error log file

Apache 1.2.3: fopen: Error 0: could not open error log file

Post by Patrick Pinche » Sat, 23 Aug 1997 04:00:00

I just downloaded and installed Apache 1.2.3 on Solaris 2.4.  I was
running 1.0.3, but now with 1.2.3 when I start the httpd daemon, I get

    fopen: Error 00
    httpd: could not open error log file /usr/local/www/httpd/xxxxxxx

Error 0 is a system error I believe (i.e.this is not a problem with
permissions or invalid directory, etc.) so I was thinking it may be
I've hit the file descriptor limit on number of open files. But this
can't be becasue it works fine with 1.0.3.

Does anyone have any ideas on this error? Post here or e-mail. (I've
checked the FAQ, DejaNews, Apache Week, no luck).



1. Apache 1.2.6--error opening logs

We have encountered a problem with our log files.  Here is the background:

We have 132 VirtualHost entries, each with a specific TransferLog and
ErrorLog directive.  Therefore, each domain has two logs, if that wasn't
obvious already :)  

bash-2.00# kill -1 10440
bash-2.00# fopen: Interrupted system call
httpd: could not open error log file /usr/local/etc/httpd/logs/3.2.error.

Yikes!  This seems to be a problem with number of open log files.  If I
comment out any log file, transfer or otherwise, things still work.

Any ideas?



2. Help with core file and stack size needed

3. Strange error messages in Apache error log

4. Unix Admin

5. strange sh errors in Apache error log

6. large uids

7. Aargs error in Apache error log

8. Help! lpr printing problems!

9. Ytree Error opening terminal: xterm.Error opening terminal: xterm.

10. Many errors in error log: Doc not UTF-8

11. cannot open /: I/O error (error on a file)

12. Error - Error Text: Too many open files

13. Help! Apache fopen: Error 0