-
Notifications
You must be signed in to change notification settings - Fork 149
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
multiple users on same system encounter permissions errors #429
Comments
Hey! So we looked into this and weren't able to reproduce the first behavior, but we were able to reproduce the second (PermissionError: [Errno 13] Permission denied: '/000000_locals'). The reason this is happening is because we need to access each existing SharedMemory file to check for potential collisions between local directory names for different StreamingDatasets here -- without this, multiple StreamingDatasets could point to the same local directories, messing up the samples. For this case, we would recommend making sure each user creating StreamingDatasets has the same permissions, or updating user permissions to make sure that |
Thanks for looking into it! I'm confused how the first issue didn't replicate - my understanding of the issue was that this os.makedirs call made it so that For my system (an academic cluster), it's not easy to ensure that |
I just doublechecked again and the |
closing the issue due to inactivity. Please feel free to re-open if you think this is still an issue. |
@karan6181 Reopening this issue because I ran into the same issue on my university cluster. There is also an easy solution. Instead of hardcoding |
#570 is merged. |
@knighton is it already in release? I still have this problem (PermissionError: [Errno 13] Permission denied: '/000000_locals') |
@Oktai15 are you still seeing this with the latest version of streaming? |
Environment
To reproduce
Steps to reproduce the behavior:
tmp/streaming
A similar issue related to shared memory that only happens if your process crashes:
/tmp/streaming
to prevent the first issue.You can verify this with the following script:
Expected behavior
No errors.
Additional context
StreamingDataset initialization will create a directory
tmp/streaming
if it does not exist yet, and so the first user will own that directory.Subsequent users on the same system are now locked out unless the first user manually chmods the directory or system cleans up
tmp/streaming
.A similar issue can happen with the SharedMemory objects in
dev/shm
.Using the
clean_stale_shared_memory
function doesn't fix this because it encounters the same permissions error.The text was updated successfully, but these errors were encountered: