cache manager process exited with fatal code 2 and cannot be respawned
maxim at nginx.com
Wed Nov 21 07:25:10 UTC 2012
On 11/9/12 10:33 PM, Isaac Hailperin wrote:
> On 11/09/2012 05:27 PM, Maxim Konovalov wrote:
>> On 11/9/12 5:15 PM, Isaac Hailperin wrote:
>>> I also wonder where the 512 worker_connections from the error
>>> message come from. There is no such number in my config. Is it
>>> hardcoded somewhere?
>> It's a default number of worker_connections.
> Yes, but if I specify a differen number, like
> this should be different. Now this could lead to the conclusion,
> that nginx is not reading that file, but nginx -t clearly says so.
> if I introduce syntactic errors in that file, nginx complains.
> As Igor Sysoev suggested earlier
> the worker_connection parameter might not be related, since also
> cache manager and loader use connections.
> If these are hard coded to a max of 512, this might be the cause:
> there are exactly 1002 vhosts which each listen on a different port.
> Now its not 1024, which would be 512*2, but may be there is some
> overhead which makes me come to this limit?
> If my thinking is correct (?), is there a way to overcome this
> limit? (other then using just one port for ssl ... it would mean
> using different ip addresses, which would have the same effect, I
> Any thoughts on this are welcome.
Just for the record -- the issue should be fixed by r4918:
+7 (910) 4293178
More information about the nginx