error.log in Nginx being written as error.log.1

Posted February 7, 2016 7.1k views

Hi, what should I do to avoid error.log being written as error.log.1 ? I tried changing the owner/group to www-data and changing the permissions to 774 but today I noticed that the problem hasn’t been fixed.

Today the access.log.1 and error.log.1 are both -rw-r—– and the owner is www-data and the group is adm

while access.log and error.log are both -rw-r–r– and the owner is www-data and the group is also www-data.

Using LEMP on ubuntu 14.04. I appreciate any help.

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Submit an Answer
1 answer

Hey there,

The access.log and error.log files are the live/active files. The files with a .1, .2, etc after it are the older log entries being rolled off. This tutorial touches on the logrotate configuration.

Hope this helps!

Happy coding,

Jon Schwenn
Platform Support Specialist

by Justin Ellingwood
Understanding the logging mechanisms of your server will help you diagnose problems and avoid larger problems down the road. In this article, we will explore Nginx's logging capabilities. We will discuss the configuration options and the tools that can be used to maintain your logs.