cache manager process exited with fatal code 2 and cannot be respawned

[Maxim Konovalov]

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?
>>>
>> http://nginx.org/en/docs/ngx_core_module.html#worker_connections
>>
>> It's a default number of worker_connections.
> Yes, but if I specify a differen number, like
> http://www.ruby-forum.com/topic/4407591#1083581
> this should be different. Now this could lead to the conclusion,
> that nginx is not reading that file, but nginx -t clearly says so.
> Also,
> if I introduce syntactic errors in that file, nginx complains.
> 
> As Igor Sysoev suggested earlier
> http://www.ruby-forum.com/topic/4407591#1083572
> 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
> guess?)
> 
> Any thoughts on this are welcome.
> 
> Isaac
> 
Just for the record -- the issue should be fixed by r4918:

http://trac.nginx.org/nginx/changeset/4918/nginx

-- 
Maxim Konovalov
+7 (910) 4293178
http://nginx.com/support.html