-
-
Notifications
You must be signed in to change notification settings - Fork 414
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
[🐛 BUG]: Fail to upload files #1314
Comments
Hey @egonbraun 👋🏻 server:
command: "php /app/vendor/bin/rr-worker start"
relay: pipes
user: www-data <--- THIS
group: www-data <--- THIS I suspect, that there are not enough permissions to open the file. |
Hey @rustatian ! Surprisingly that fixed it. But now I have even more questions! hahahaha I checked /tmp and it is properly set in my system:
And this is how the
So, are you suggesting this is a permissions issue or is Roadrunner doing something wrong? Thanks for the fix! |
Hey @egonbraun 👋🏻 |
Correct. |
So, when the RR process creates a file in the |
Hey @egonbraun 👋🏻 |
Done! Thanks! |
But one thing I still don't get. Roadrunner was indeed set to start as The main Roadrunner process was root but the workers were So, how can I do what you are proposing? Thanks again! |
It would be best if you did not generally start RR from the
Not all daemons require a |
Maybe I am just being dumb, so apologies for that. :) Do you mean that the binary of roadrunner should be started as a user different than root? I mean, we user supervisor, so I can ask supervisor to start the roadrunner bootstrap script as a different user. Yeah, if that's the case, then this is something I was definitely not doing. But it's totally doable. |
No no, you're asking good questions. I'm thinking about the permissions... I mean, should we create |
But, PHP should not touch these files. The original problem I guess is the |
Since we're not actively supporting this package (you know, we're busy with the |
@egonbraun Hey 👋🏻 |
Got it! For now I will keep running Thanks @rustatian :) |
My pleasure 👍🏻 |
Hey @egonbraun 👋🏻 |
No duplicates 🥲.
What happened?
When we tried to upload an image to our backend service the worker failed and the client received an HTTP 500 error message, the logs just stated that the file did not exist.
Our stack is running:
We noticed that the error happens before our code is even triggered, indicating that the issue happens while Laravel is building the request to send to out controller class. The error itself is triggered in the following file as part of the
nyholm/psr7
library (I believe is a core dependency of Laravel or Synfony).It's worth noting our applicating runs inside a Docker container.
Our roadrunner configuration:
I have checked the information provided in the caveats wiki section (which mentions a similar issue regarding the upload of files) and also the information in this issue.
I have also tried changing the
isValid()
function of theUploadedFile.php
Synfony class and it also did not workThanks!
Version (rr --version)
2.11.3
Relevant log output
The text was updated successfully, but these errors were encountered: