Open thepry opened 6 years ago
Do you still need this workaround after updating to v1.0.6 ? It fixes some issue with log rotation that may be the cause of this
@ztrange ran in to this issue on 1.0.9. Adding the RUN rm -f /var/log/nginx/error.log
to Dockerfile fixed it for us. We do have a 2 stage build (a Dockerfile.base which inherits FROM phusion/passenger-ruby26:1.0.9
and a Dockerfile which inherits from that, but we've had that set up for a while and the logs have worked in the past. We did make some Dockerfile changes and just changed from Rancher1 (Cattle based) to Rancher2 (K8S based) for our deployment. Somewhere between those 2 sets of things, this issue cropped up.
Confirming that adding RUN rm -f /var/log/nginx/error.log
to Dockerfile
solved the issue.
I pre-delete /var/log/nginx/error.log
in the new image, does that help?
UPDATE: Adding
RUN rm -f /var/log/nginx/error.log
to my Docker file helped with this issue. I'm not sure why, maybe it's some weird bug with nginx-log-forwarder service and error.log file.....
Hi. I'm using
phusion/passenger-ruby25:0.9.34
with Rails. Rails are using STDOUT as log destination, but the log doesn't appear in thedocker logs
, even though it is present in/var/log/nginx/error.log
If I run
docker exec backend sv restart nginx-log-forwarder
it appears.Do you have any idea how to fix this problem?
Nginx + passenger + rails 5.1.4
ubuntu EC2 (couldn't reproduce on my mac)
nothing :)
New Logs appear in the STDOUT
Only initial log: