nginx,

Nginx and 'using inherited sockets' notice

Apr 24, 2022 · 1 min read · Post a comment
Nginx and 'using inherited sockets' notice

If you have been debugging and digging into the nginx logs, you might have stubled upon the following notice log message:

2022/03/10 06:04:32 [notice] 31447#31447: using inherited sockets from "6;7;8;9;

I’ll try to explain it briefly.

Prerequisites

  • Nginx

Explanation

First of all, notice is a severity= parameter value, meaning it defines the severity level of syslog messages. Notice presents the casual log messages. Overall, there are seven values in order of increasing severity: debug, info, notice, warn, error (being the default one), crit, alert and emerg.

Now, using inherited sockets from message means that the current Nginx binary is being replaced by a new one on the fly, therefore gaining control over the listening sockets. This message usually appears when there is a Nginx upgrade to a newer version, or adding / removing server modules. So, you have nothing to worry about.

Read more about Upgrading To a New Binary On The Fly.

Conclusion

Feel free to leave a comment below and if you find this tutorial useful, follow our official channel on Telegram.