As we discussed in Discord, webproxy is repeatedly throwing errors into the container logs once per minute. Webproxy still works fine. The error is:
awk: fatal: cannot open file `/var/log/nginx/access.log' for reading: No such file or directory
Within the container, examining /var/log/nginx shows:
a bunch of logs with size = 0, and notably, no access.log or error.log.
Looking at /etc/nginx/nginx.conf, the final lines say
# This entry is to enable iptables blocking. The ### will be removed if enabled upon start of the container:
access_log /dev/stdout ;
}
You had some suspicion that the issue lies with VERBOSELOG but honestly I kind of lost the train of though while trying different things on my own. After setting VERBOSELOG=OFF, restarting the container, then VERBOSELOG=ON again, and restarting again, whether right or wrong, does seem to have stopped the behavior. No more awk errors, /var/log/nginx/access.log exists and is being written to.
Anyway, now there's an issue to track this behavior.
As we discussed in Discord, webproxy is repeatedly throwing errors into the container logs once per minute. Webproxy still works fine. The error is:
Within the container, examining /var/log/nginx shows:
a bunch of logs with size = 0, and notably, no
access.logorerror.log.Looking at /etc/nginx/nginx.conf, the final lines say
You had some suspicion that the issue lies with
VERBOSELOGbut honestly I kind of lost the train of though while trying different things on my own. After settingVERBOSELOG=OFF, restarting the container, thenVERBOSELOG=ONagain, and restarting again, whether right or wrong, does seem to have stopped the behavior. No more awk errors,/var/log/nginx/access.logexists and is being written to.Anyway, now there's an issue to track this behavior.