i have an upstream clause with two servers. one is the primary and the other is the backup. upstream Service { server 127.0.0.1:8106; server 127.0.0.1:8100 backup; } periodically, the primary server marks itself "down", reloads nginx, restarts, removes the "down" status, reloads nginx, and continues. i observe that sometimes traffic continues to go to the baby james.anderson - Other discussion
we found it to be impractical to move from ubuntu's released nginx version in order to avoid that the perl module crashed on _every_ reload. i was unaware, that the presence of the nchan module could cause an issue if one did not use it, but will disable it an see if that helps.by james.anderson - Nginx Mailing List - English
we observe that after several days in service, where the server is reloaded several hundred times a day, it eventually stops responding. a reload completes, but still all connections time out. a restart corrects the issue. is there a limit to the number of times a server permits a reload before it is necessary to restart it. when the problem starts, entries like the following appear in theby james.anderson - Nginx Mailing List - English
![]() |
![]() |
![]() |
![]() |
|