Error in exception handler: Permission Monolog/Handler/StreamHandler.php #655
Comments
|
You need to make the app/storage folder and the things under it writable for the web server. |
|
Do the services required to write to app/storage not operate under the Apache user? Perms were recursive so Apache has read write and execute in that directory. I even tried 777 to be sure. |
|
It would be if you were running php with mod_php; but I don't see that mod so I assume its probably php-fpm. check |
|
It's Apache. -rwxrwxrwx. 1 apache apache 5.1K Mar 10 03:24 StreamHandler.php |
|
Wait, you changed the permissions on the StreamHandler? Also today is the 10th so that log file isn't the one its going to try to write to ... Change the permissions of the whole storage folder and subfolders to 777 and see if that resolves the problem. If it does, pull it back to 775. if pulling it back to 775 breaks it again then somewhere you're configs are not acting as the user you expect. |
|
Setting it all to 777 again... Same error. |
|
what do you see when running |
|
Some googling many folks point to clearing the cache after/before changing the permissions. I'm not sure I follow this but its worth trying: |
|
@skwerlman @Indemnity83 Yields: |
|
There absolutely must be something wrong with your permissions; Can you make a file in the public folder, something like |
|
Apache :/ |
|
I'm at a loss... |
|
For the record, this is the repo I got php 5.6 from for Centos 7 if it matters. https://webtatic.com/packages/php56/ I couldn't follow the guide exactly due to it installing php 5.4 and other extensions under that version by default. That, running composer.phar outside of TechnicSolder/ and setting the perms up based on httpd's user were the only commands I did differently vs the guide's commands. Could it be an issue with the repo? What distro are you all using in the guide? I am running a VM on Google Could so I could just try following it do the dot again. It's certainly apache and httpd that is running. Spamming refresh on the page makes this service spike. Don't know what else it could be if it's not something being handled incorrectly here.
|
|
For anyone here referencing URLs, I am shutting down the VM. So, they will not work at this time. |
IF the VM is just handling solder you should of followed the solder docs when first setting up - in particular https://www.digitalocean.com/community/tutorials/how-to-install-linux-nginx-mysql-php-lemp-stack-on-centos-7 before starting the actual process of obtaining the needed packages via yum Mid way through that digital ocean guide before installing php I'd first follow https://rpms.remirepo.net/wizard/ to ensure you have the correct repo added for php 5.6+ |
|
@spannerman79 Cool so now I get a bad gateway. Solder Config |
|
Sidenote, this is issue 655 |
|
Ok, I am able to get a server up. I followed this guide for Debian 8 (skipping mysql since I have a cloud SQL instance) https://www.digitalocean.com/community/tutorials/how-to-install-linux-nginx-mysql-php-lemp-stack-on-debian-8. Able to login and get it going. But now when I try to make a Modpack or edit the modpack I get the same error.
This is, again, involving me changing the ownership of /var/www/ to nginx and me per this answer So why it is able to write to this log file on login but not on modpack creation or adjustments? Why even certain sectors in the folder? This also happens when I try to add a new modpack now as opposed to after hitting "add modpack". Also, that fodler specified in the screenshot doesn't exist. |
|
Seriously is this not proof of a code issue? If the entire folder is chmod 777 yet I get these issues? How could it even be a perms issue in the first place is I have had 777 |
|
I know this is going to sound pompous, I don't intend it to, but I don't think its proof of a code issue because there are hundreds if not thousands of deployments of solder without this issue. I can't figure out what is different about yours, but something must be. |
|
Reached out to Google to be safe as they provide support for handling lemp stack setups. So after a thread with them in the background (with them monitoring this one), this is what I got. So if no one here has any ideas as to why such an odd thing would happen, even after we initially confirmed 15 some odd posts ago that I was using 777 on my folder, I think I'll just use the CDN they gave me to keep distributing the .zip for now... |
|
Do you think this may be a SELinux issue? |
|
If you're using SELinux it might be.
…On Sat, Aug 10, 2019, 19:50 Johnathan Dunker ***@***.***> wrote:
Do you think this may be a SELinux issue?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#655?email_source=notifications&email_token=AAEBDUM2WIPQ6LDZFPPKOCDQD4EXHA5CNFSM4EUUX3EKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4ATAZI#issuecomment-520171621>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAEBDULWNWNIKPVEPHWDBHTQD4EXHANCNFSM4EUUX3EA>
.
|
|
In this scenario, I was not using SELinux. |
|
Maybe this hint will solve your problem: |
|
1 year later and some experience at a hosting company, ill try to take a wack at this again as well as containerizing it. Kubernetes is a thing now so I'd be happy to make a chart for it too if it all works to simplify everyone's experience. |
|
This is a permissions issue. The storage folder needs to be writable by the PHP daemon (which may or may not be the same user as your web server). I'm closing this now. |
Thank you @Indemnity83, it works for me after changing this to the same user and group as php-fpm |
The stream or file "/var/www/html/TechnicSolder/app/storage/logs/solderlog-2018-03-10.txt" could not be opened: failed to open stream: Permission denied in /var/www/html/TechnicSolder/vendor/monolog/monolog/src/Monolog/Handler/StreamHandler.php:107
First setup. Followed the guide. Perms are recusive....
The text was updated successfully, but these errors were encountered: