headers
Hoffman, Brian [USA] | 21 Jun 2012 15:36
Gravatar

nginx 1.2.1 won't start with large CRL


I have a CRL loaded into ssl_crl variable in the config file that's about 256MB in size and nginx won't start. I get the following error:

nginx: [emerg] fork() failed (12: Cannot allocate memory)

I believe this is due to nginx trying to load the file into memory and it's bombing. It maxes out my server's RAM and then just crashes.


- Brian
_______________________________________________
nginx mailing list
nginx@...
http://mailman.nginx.org/mailman/listinfo/nginx
Permalink | Reply |
headers
Maxim Dounin | 21 Jun 2012 16:18
Picon

Re: nginx 1.2.1 won't start with large CRL

Hello!

On Thu, Jun 21, 2012 at 01:36:27PM +0000, Hoffman, Brian [USA] wrote:

> 
> I have a CRL loaded into ssl_crl variable in the config file that's about 256MB in size and nginx won't
start. I get the following error:
> 
> nginx: [emerg] fork() failed (12: Cannot allocate memory)
> 
> I believe this is due to nginx trying to load the file into memory and it's bombing. It maxes out my server's
RAM and then just crashes.

I would rather rewrite the subject as "nginx won't start if there 
isn't enough memory".  It won't.  Try adding more memory and/or 
find a way to keep your CRL small.

Maxim Dounin
Permalink | Reply |
headers
hoffmabc | 30 Apr 2013 18:10
Picon

Re: nginx 1.2.1 won't start with large CRL

The CRL cannot get any smaller as it's a DoD CRL. Also adding more memory
does not solve the problem. It seems to have an issue with starting the
server period with a large CRL.

[alert] 19759#0: fork() failed while spawning "worker process" (12: Cannot
allocate memory)

Posted at Nginx Forum: http://forum.nginx.org/read.php?2,227763,238749#msg-238749
Permalink | Reply |

Gmane