Comment 7 for bug 1899164

> You may be able to fix this by setting `error_log` yourself in your http configuration section.

Check the config I provided, error_log is defined there. Yet the warning is printed, because nginx tries to access error_log before reading config file. I can start nginx (with a warning) after overriding path of settings I don't even want to use, but do you really believe that's how it supposed to work?