-
Notifications
You must be signed in to change notification settings - Fork 24
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
Receiver crashes if DNs file is being written to and read from at the same time. #79
Comments
It happened again. |
I did the tiniest amount of investigation to try and come up with a repeatable test for this and it seems (at least under Python 3) having the dns file open for writing while trying to read from it isn't sufficient to cause this. Maybe the cause is trying to read the exact moment the write is actually flushed to disk... |
Sounds like a simple retry would be sufficient after ~30 seconds, with a limit of, say, 3 attempts before barfing. |
So it's ending up here: Line 377 in 83e33c7
So it's getting a |
resolve apel#79 . i was unsure which part to loop so i just repeated the whole chunk within the try statement.
resolve apel#79 . i was unsure which part to loop so i just repeated the whole chunk within the try statement.
resolve apel#79 . i was unsure which part to loop so i just repeated the whole chunk within the try statement.
resolve apel#79 . i have just looped everything in the try statement although i am not sure if it is whats needed.
resolve apel#79 . i have just looped everything in the try statement although i am not sure if it is whats needed.
resolve apel#79 . i have just looped everything in the try statement although i am not sure if it is whats needed.
resolve apel#79 . i have just looped everything in the try statement although i am not sure if it is whats needed.
As per this ELOG,
bin/receiver.py
seems to crashes ifget_dns
is called while the DNs file is being written to by the auth component of APEL.It would be good to be able to reproduce this bug to determine the exact cause.
The text was updated successfully, but these errors were encountered: