Ingo Schmidt
October 01, 2013 10:38AM
Hi!

I have seen this question has been asked before in the list, but
unfortunately there haven't been any answers, so let's see if I have
more luck :)

In can successfully upgrade the nginx binary on the fly as documented here:
http://wiki.nginx.org/CommandLine#Upgrading_To_a_New_Binary_On_The_Fly

However, if nginx was started via Upstart and then upgraded like this,
Upstart ends up in a confused state:
"status nginx" will show that nginx is running, but no PID is shown.
"stop nginx" states that the upstart job is stopped (but nginx is still
running)
"start nginx" states that it works, but Upstart shows no PID as it
normally does.
"reload nginx" says "unknown instance"

The only way to fix this is to actually manually stop and start nginx,
but then there is some downtime. Is it possible to work around this
problem? Should I avoid using Upstart? If yes, what are my options to
run nginx with the on-the-fly upgrade possibility?

Cheers, Ingo =;->

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

nginx and upstart

Ingo Schmidt October 01, 2013 10:38AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 96
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 500 on July 15, 2024
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready