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

Permission denied error on Lock.php line 100 #4

Closed
giacomomasseron opened this issue Nov 20, 2017 · 4 comments
Closed

Permission denied error on Lock.php line 100 #4

giacomomasseron opened this issue Nov 20, 2017 · 4 comments

Comments

@giacomomasseron
Copy link

Hi,
After many days of use of this package, today I get this error on my project:

exception 'ErrorException' with message 'fopen(/tmp/sessionlocks/819861d192fb45da5e87f7d0218065360cef03bb): failed to open stream: Permission denied' in /.../public_html/vendor/rairlie/laravel-locking-session/src/Rairlie/LockingSession/Lock.php:100

I am sure the user does have permission to write "/tmp" file, indeed this package worked for many days.

What can be?

Thanks

@rairlie
Copy link
Owner

rairlie commented Nov 21, 2017

Hi there.

It's difficult to say without knowing more about your config and environment. The fact that it failed on that line suggests the lock dir (/tmp/sessionlocks) existed on disk, but it was unable to write to it. Is it possible another process changed the ownership or permissions on the lock dir after it was created - e.g. a cron job?

@giacomomasseron
Copy link
Author

You were right, is it possible to change the directory? My problem is that 2 projects use same directory, so there are conflicts.

@rairlie
Copy link
Owner

rairlie commented Nov 23, 2017

Ah ok, that makes sense. Currently the lock dir is a constant, but I will look at making it configurable.

@rairlie
Copy link
Owner

rairlie commented Nov 28, 2017

Hi - this is now configurable - see the note in README.md

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

No branches or pull requests

2 participants