Home / server / Questions / 842499
In Process
Sankalp Sharma
Asked: 2017-04-05 06:00:22 +0800 CST

nginx cache stuck in "UPDATING" state

  • 772

On a decently loaded nginx/1.4.6 instance running on Ubuntu 16.04 LTS, sometimes the resources served are not getting expired. I always get "UPDATING" response instead of a "HIT" or a "MISS", which I would normally expect. This response with "UPDATING" header serves stale content, and is stuck there.

This had been fine for a long time; the only change that was recently implemented was that I recently configured letsencrypt-based encryption on my nginx instance.

Update: I'm also seeing logs that read like:

ignore long locked inactive cache entry 9b4d24d307449cfe263aab0ee53676c8

ubuntu

1 Answers

  1. Update on this: from what it appears, it was due to nginx process crashing and re-spawning. The crashing happened because I recently moved to HTTPS, and were using a rather lengthy cipher for encryption, which caused the server to get more loaded (using Letsencrypt, BTW).

    Fix applied : I reduced the cipher text length, observed for over a week, and it went all fine after that.

    • 0