Welcome! Log In Create A New Profile

Advanced

Re: emergency msg after changing cache path

Maxim Dounin
September 07, 2016 11:00AM
Hello!

On Wed, Sep 07, 2016 at 10:30:18AM -0400, shiz wrote:

> Got this message after changing the cache path? Could not find a solution
> after googling it. Any help?
>
> [emerg] 15154#15154: cache "my_zone" uses the "/dev/shm/nginx" cache path
> while previously it used the "/tmp/nginx" cache path

You are trying to reload a configuration to an incompatible one,
with a shared memory zone used for different cache. It's not
something nginx is prepared to handle, so it refuses to reload the
configuration. Available options are:

- change the configuration to a compatible one (e.g., rename the
cache zone so nginx will create a new one);

- do a binary upgrade to start a new instance of nginx with only
listening sockets inherited (see http://nginx.org/en/docs/control.html#upgrade,
usually can be simplified to "service nginx upgrade");

- just restart nginx.

--
Maxim Dounin
http://nginx.org/

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

emergency msg after changing cache path

shiz September 07, 2016 10:30AM

Re: emergency msg after changing cache path

Maxim Dounin September 07, 2016 11:00AM

Re: emergency msg after changing cache path

shiz September 07, 2016 04:52PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 94
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready