Greetings, On recently upgrading to 2.2.8, I was rather surprised to find that my new binary would not start on the production server. The error message is: [Wed Apr 02 19:25:18 2008] [error] Init: Unable to read server certificate from file /path-to-certificates/cert99.crt [Wed Apr 02 19:25:18 2008] [error] SSL Library Error: 33558552 error:02001018:system library:fopen:Too many open files [Wed Apr 02 19:25:18 2008] [error] SSL Library Error: 537317378 error:2006D002:BIO routines:BIO_new_file:system lib After trying all the usual suspects to do with increasing system resources, I discovered that this was documented in an old bugzilla: https://issues.apache.org/bugzilla/show_bug.cgi?id=14219 I commented out a few VHs and found that the problem only kicked in when the number of VHs (hence log files) and SSL certs reached a certain size. So it seems that the problem is indeed due to a file descriptor exceeding 255, as the report describes. The funny thing is, apache 2.2.6 starts perfectly when loaded with the *exact* same config file (hence same number of files to handle)... So my question is, does anybody know what has changed between 2.2.6 and 2.2.8 that could resurrect this rather limiting behaviour? Rgds, Owen Boyle Disclaimer: Any disclaimer attached to this message may be ignored. This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please notify the sender urgently and then immediately delete the message and any copies of it from your system. Please also immediately destroy any hardcopies of the message. The sender's company reserves the right to monitor all e-mail communications through their networks. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|