-
Notifications
You must be signed in to change notification settings - Fork 426
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
Container won't start: Error when reading /var/lib/rabbitmq/.erlang.cookie: eacces #318
Comments
We've only had one other issue with your specific error #114 |
What is very weird here is that cookie file read operations fail for several seconds, so it's not a cookie generation/read race condition that a basic retry would work around. |
Just seen it happen with the rabbitmq:3.7.10-management-alpine that was updated 19 days ago, so it's probably not a problem from the last builds... although it started happening only a couple days ago. Will try reproduce and bump the docker version maybe... |
Hi, i managed to get the erlang crash dump from a failure, it's at https://gist.github.com/lindycoder/e16fd1a23ceaf292311978fc3d2620e5 was reproduced with
|
@lindycoder the dump doesn't add much to what you already posted. The node terminates very early because it fails to load the cookie file. There are no RabbitMQ modules loaded on the node, which is a good hint at how early it happens. I'm not a Docker expert by any stretch but it sounds like a volume initialization race condition with RabbitMQ node startup. |
Not a bad suggestion, since the dockerfile declares a |
I'm also retrying with that directory mounted, so that it's a bound volume, will see if it gets better, if it does it might be the volume driver... #shotinthedark |
Honestly, I've never seen a delay in Docker's volume/bind mounting -- it does all that before it ever launches the user process, so there shouldn't ever be a timing issue there. 😕 |
Random idea: AppArmor is now "helpfully" getting in the way? |
Well seems it magically solved itself for no apparent reason, it might be a problem with the hypervisor of the vm running the docker i was running this with, i don't know. It might be a just a weird behavior, if it comes back i might just put a restart: unless-stopped in the compose file cause simply restarting the container does fix the issue. Thanks for the help! |
This comment has been minimized.
This comment has been minimized.
The same issue #114. It's not always reproduced. Adding |
Hi we've been having issues starting this container for the last 2 to 6 days, it happens about 80% of the time:
Error when reading /var/lib/rabbitmq/.erlang.cookie: eacces
We run this image (latest
rabbitmq:management-alpine
) alone (not part of a cluster) on aLinux web1 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
withDocker version 18.03.1-ce, build 9ee9f40
.This is part of a continuous integration test so it breaks our pipeline for no reason.
I saw that the image latest was updated 6 days ago, so i'll try to pin it down 1 version an see if it still breaks.
Here's how we launch the image:
Here's a log from the container that won't start
Thank you!
The text was updated successfully, but these errors were encountered: