Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Apache /docker.stdout busy or permission errors #156

Open
mblaschke opened this issue Jan 9, 2017 · 4 comments
Open

Apache /docker.stdout busy or permission errors #156

mblaschke opened this issue Jan 9, 2017 · 4 comments

Comments

@mblaschke
Copy link
Member

There are at least 2 reports from problems with /docker.stdout due to permission errors:

app_1         | [Mon Jan 09 09:02:18.518789 2017] [log_config:error] [pid 1984:tid 140401578567552] (13)Permission denied: AH00649: could not open transfer log file /docker.stdout.
app_1         | AH00015: Unable to open logs

also see laradock/laradock#505

@mblaschke
Copy link
Member Author

✅ Ubuntu 16.04 with btrfs
✅ Dinghy with aufs

@mblaschke
Copy link
Member Author

Switched from file to pipe in syslog, maybe the problem is fixed now. We still can't reproduce the isssue

@julrich
Copy link

julrich commented Jan 23, 2017

That might help with a warning we're seeing on some instances, a lot, too:
[SYSLOG] syslog-ng[20]: WARNING: you are using the file driver, underlying file is a FIFO, it should be used by pipe(); filename='/docker.stdout'

@julrich
Copy link

julrich commented Jan 23, 2017

I see, that's exactly what's in the Changelog, too :)
c86b5d5#diff-4ac32a78649ca5bdd8e0ba38b7006a1eR8

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants