|Applies To||Web Agent Apache V4.9 Agent|
Working system with a large number of vhosts. In some cases 70 to 160. Customer added two more virtual hosts.
|Issue||AxM - Adding more virtual Hosts in Apache caused working site to fail |
It "appears" that we might have hit a limitation of the number or size of virtual hosts in Apache as it fails to load with the following error. Below is the output of the apache service log in solaris:
Note: There is no webagent.xml file. This is an unsupported feature and that part of the error message should be avoided.
ulimit number of open files limit exceeded. Especially on older Soalris systems the limit was 256. On newer systems the lmit is 64K.
apachectl - This is a shell script that the Customer calls to start and stop apache.
This sets the maximum open files for the apache process to 65536. So there are obviously plenty of file descriptors available and thus not the problem, so the customer thought. After further analysis, it was determined that customer was running the 32 bit version of Apache on Solaris and apparently hitting a 256 file descriptor limit even though apache sets the file descriptor at 65536. Historically, 32-bit applications have been limited to using the first 256 numerical file descriptors for use with standard I/O streams.
extended FILE facility
The extended FILE facility allows 32-bit processes to use any valid file descriptor with the standard I/O C-library functions. The extended FILE facility is enabled from the shell level before an application is launched. So, in this case, by adding the following command to the apachctl shell, it can extend the 32-bit file descriptor process limit for apache and thus start apache with the newly a vhosts.
|Legacy Article ID||a57528|