php 7.0.7 and mysql 5.7.13

csf

I don't know which it was, but after updating my local dev to the latest stable releases of php and mysql, my front-end became a big table of errors:

( ! ) Warning: file_put_contents(/Users/me/Sites/discussion/assets/rev-manifest.json): failed to open stream: Permission denied in /Users/me/Sites/discussion/vendor/flarum/core/src/Asset/RevisionCompiler.php on line 179
Call Stack
#	Time	Memory	Function	Location
1	0.0466	362472	{main}( )	.../index.php:0
2	0.6507	973944	Flarum\Http\AbstractServer->listen( )	.../index.php:16
3	5.8261	6635928	Zend\Diactoros\Server->listen( )	.../AbstractServer.php:38
...
etc

What do do? (Downgrading local dev isn't an option.)

I do know that with another system I have in local dev (CMS), it was some kind of change in mysql 5.7.x that caused problems, something with DATE/TIME. Similar issues were reported in new versions of Percona DB too, apparently. I suspect web hosts will be updating DB servers soon enough, so you might want to look into it.

csf

Which folders would we be talking about? And why would they have changed?

csf

I don't have have a www.conf file. I was using Apple's native php for El Capitan, which for me was located at /usr/local/php5, and within that there is no pool.d either.

Since I can't wait for Apple's new Sierra OS in order to get Apple's version of php7 binaries, I used L//P's well-supported package following this, which installed php7 alongside Apple's own php5 at /user/local/php5-7.0.7-20160526-160257 (yes, goofy name). With a couple of file mods the new version is read in through Apache's httpd.conf file and as an extension of the native php.ini file.

In any case, there are no files that you inquire about in the php7 directory either.

JoshyPHP

The shotgun solution would be to just chmod 0777 -R flarum. That'll fix that particular issue.

The correct way to fix it would be to find out what user php-fpm and nginx run as and either make it match the old user or chown your files to the new user.

csf

JoshyPHP The correct way to fix it would be to find out what user php-fpm and nginx run as and either make it match the old user or chown your files to the new user.

Ok, thanks. I'll explore it.

csf

I think I found the files...

/user/local/php7/etc/php-fpm.d/www.conf.default

I don't know why they have .d and .default extensions, but I'm guessing they're not active like that.

Do you suggest I drop the extensions?
Then what I am I looking for, exactly?

csf

Changed this:

user = nobody
group = nobody
...
;listen.owner = nobody
;listen.group = nobody

To:

user = www-data
group = www-data
...
listen.owner = www-data
listen.group = www-data

But it didn't change anything. Still have all the errors.

So then I decided to try the shotgun method just as a test to make sure this is even the problem. I'm assuming, @JoshyPHP, that you mean this flarum directory: .../vendor/flarum?

When I try to run it, it returns:

chmod: -R: No such file or directory.

But I can run chmod 0777 flarum, but it doesn't make the original front-page errors go away.

JoshyPHP

@csf I assume you need to restart the server for the changes to take effect.

As for chmod, I don't know about Apple's version but the -R means recursive. That error message doesn't make sense to me.

About the dir, I was talking about the root dir, the one that contains the vendor dir.

csf

Btw, if I drop the extensions from php-fpm.d and www.conf.default, that doesn't make a different either in terms of the "right" way.

And...

$ cd /users/me/Sites
$ chmod 0777 -R discussion
chmod: -R: No such file or directory

I suspect this might have something to do with -R on Mac, but it doesn't really suggest to me what to do. I tried using sudo before the command and that didn't work either.

datitisev

csf ~~I'm guessing~~ I know chmod 0777 -R discussion won't work because the directory needs to be right after the code (i.e. 0777). You should also set it as 0775 instead of 0777.

Try running the following. It doesn't error me.

$ chmod -R 0775 discussion

Interesting Find: Why is this forum not using one of the latest dev-master versions? I hate the old inline code style ?

csf

datitisev chmod -R 0775 discussion

That was part of the problem (thanks!), but not all of it. Instead of a table of errors like originally seen, I now get Flarum's familiar "Whoops" handler page. At the top of that in the black area is:

Less_Exception_Parser
Less.php cache directory isn't writable: /Users/me/Sites/discussion/storage/less/

The problem seems to be on the /discussion/storage/less directory, I guess. So then I ran this on the install directory:

chmod -R 0775 discussion

And using the ls -l command @Bek suggested I see permissions are set for 775:

drwxrwxr-x 27 me staff 918 Jun 9 10:07 discussion

I then look at the permissions for the /discussion/storage directory, and those are set as rwxr-xr-x (I'm leaving the "d" off here intentionally), so I run a separate permissions command on that directory:

chmod -R 0775 discussion/storage

which puts it right:

drwxrwxr-x 8 me staff 272 Apr 21 16:22 storage

Why the "-R" option didn't work when running the command on the /discussion, I don't know (I thought it was supposed to change all subdirectories too), but it changed the permissions when I ran the command again directly on the /storage directory.

But this doesn't fix Whoops error; the problem still persists on the /less directory, so I run it there too:

chmod -R 0775 discussion/storage/less

And this changes the permissions there:

drwxrwxr-x 138 me staff 4692 Jun 17 14:34 less

This time the Whoops error changes...

Less_Exception_Parser
Less.php cache directory isn't writable: /Users/me/Sites/discussion/storage/less/

Running ls -l on the /less directory, I find a long list like this:

-rwxr-xr-x  1 _www    staff    17063 Jun 12 11:46 lessphp_14kjn4fqnjb48w8w0c0wo0cc0cos40g.lesscache
-rwxr-xr-x  1 _www    staff    26636 Jun 12 11:46 lessphp_18x2bkuuqin4kkgso88sw480wog88c4.lesscache
-rwxr-xr-x  1 _www    staff    75692 Jun 10 17:56 lessphp_1bef9xp6mh6sccc8844kgo0sggkgkg0.lesscache
-rwxr-xr-x  1 _www    staff    16777 Jun 12 11:46 lessphp_1sot8ushvptwc0ww444s8wg88c8wwc0.lesscache
etc

What I notice here, finally, is that my username (me) is replaced by _www. I suspect that has something to do with it, but I don't know what to correct at this point.

Btw, there is also one instance of _www in the install directory, on config.php:

-rw-r--r-- 1 _www staff 428 Mar 30 19:49 config.php

If I try and change permission on that file, it seems I'm not allowed:

chmod 0775 config.php
chmod: Unable to change file mode on config.php: Operation not permitted

I don't know if that's normal or not.

csf

I've managed to change all the files in the /less directory to 775 and me as owner (instead of _www). For example...

-rwxrwxr-x  1 me  staff    17063 Jun 12 11:46 lessphp_14kjn4fqnjb48w8w0c0wo0cc0cos40g.lesscache
-rwxrwxr-x  1 me  staff    26636 Jun 12 11:46 lessphp_18x2bkuuqin4kkgso88sw480wog88c4.lesscache
...

But I still get this Whoops error and no working boards...

Less_Exception_Parser
Less.php cache directory isn't writable: /Users/me/Sites/discussion/storage/less/

The /less directory itself is also drwxrwxr-x.

I don't know what to do here, but I'm dead in the water. ?

webeindustry

csf

How are you expecting PHP-FPM to write when neither the group or user is www-data, yet that's what you set in the pool.d/www.conf file?

Try to chgrp to www-data -R on the less directory, and then run:

flarum cache:clear

csf

I'm not an expert on this. I'm just looking for some help. I'll try what you're suggesting.

webeindustry

Apologies I wasn't trying to come of harsh, just genuinely curious.

Let us know if any of our suggestions are working out or not

Also if you create a gitter acct and look me up, I can help you out real-time (slow day for me!)

csf

Okay, so as I explained earlier in this thread, I upgraded to php 7.0.7 using the L//P package, which sits beside the old (Apple OS) version but overrides it in a couple of places to make the new version work. So I have both versions in this folder...

/usr/local/php5
/usr/local/php5-7.0.7-20160526-160257 (i.e. 7.0.7)

Each has its own www.conf.default file at...

/user/local/{php version}/etc/php-fpm.d/www.conf.default

Oh... I've just realize that if I open the php5 version of the www.conf.default file, then that file opens (as expected). But if I open the php7 version (e.g. mate php5-7.0.7-20160526-160257), it actually opens the php5 version. So that must be part of the L//P package design, to reuse same file in Apple's install, I'm guessing. In any case, any change I make to either www.conf.default file location (whether change contents or rename file), it only makes the change on the php5 version, so that's where I'll keep focusing.

I've edited the www.conf.default to for this:

user = www-data
group = www-data
...
listen.owner = www-data
listen.group = www-data

After restarting the server, the "Whoops" error on the /less directory changes back to the error originally reported at top of this thread:

( ! ) Warning: file_put_contents(/Users/me/Sites/discussion/assets/rev-manifest.json): failed to open stream: Permission denied in /Users/me/Sites/discussion/vendor/flarum/core/src/Asset/RevisionCompiler.php on line 179

If I change the file name to www.conf (i.e. drop the ".default"), the same error results. So I'm guessing either the file name doesn't matter (illogical) or the file isn't being used/read at all. I've left the name changed as www.conf.

Running ls -l on my .../storage/less directory give me records like this...

-rwxr-xr-x  1 _www    staff    17063 Jun 12 11:46 lessphp_14kjn4fqnjb48w8w0c0wo0cc0cos40g.lesscache

I don't know why the user is "_www" instead of "me", but I seem to be able to change the user easy enough if I want to. In any case, I'm not sure that's relevant at the moment considering the current error status has changed again back to what it was originally, pointing to somewhere in .../vendor/flarum...

Moving on, I tried running what @webeindustry said on the /less directory just for kicks, and it gives me an illegal group name...

chgrp to www-data -R less
chgrp: to: illegal group name

If I try to use sudo chgrp to www-data -R less, I get the same result.

That's where I'm at. Not far.

Just so you know, I'm comfortable using the command-line, but I've never played with any php files before outside of uncommenting the occasional line in an php.ini file. This www.conf and user/group designations and permissions stuff is new territory. It seems strange to me that a simple update of the php would cause so much trouble, but what do I know...

webeindustry

That wasn't meant to be verbatim. Sorry. chgrp www-data less -R.

I'm wondering why you would want to keep the php5 on your server. Do you have a reason to run it? I would remove all traces of PHP5, & PHP7, then install PHP7 again. Try to clean things up a bit and start fresh.

Something to consider.

Ah I read up to where you're using this local dev with apple osx? Yea, that's going to be out of my territory. I'm not sure how that setup is working, but really dislike anything vagrant not sure if that's similar at all. You probably don't want to go through all of this efforts, but if I were having issues with developing within a mac, I'd be looking to dual-boot into a linux environment, so that I could run a standard install.

csf

webeindustry That wasn't meant to be verbatim. Sorry. chgrp www-data less -R

Ha... I didn't even notice that. I should have.

But even trying...

chgrp -R www-data less

chgrp www-data less -R

or using sudo with either one still results with:

chgrp: www-data: illegal group name

I just changed the user value to "me" again (instead of the original _www user value) and that brought back the more familiar Whoops error page saying it couldn't write to the less directory.

Then I looked at the permissions set on the less files on production (with WebFaction), and they have my username as both user and group, for example:

-rwxr-xr-x  1 username    username    17063 Jun 12 11:46 lessphp_14kjn4fqnjb48w8w0c0wo0cc0cos40g.lesscache

So I tried that on local, changing "staff" to "me", but it turns out the same:

sudo chgrp -R me less
chgrp: me: illegal group name

Since we seem to be trying to change the group name permissions, "staff", on the less files to "www-data", but can't — what if I changed the "www-data" in the www.conf file to "staff" instead? ?

webeindustry I'm wondering why you would want to keep the php5 on your server.

No particular reason other than I'm just following the lead of the L//P package, which I think is meant to sit unobtrusively out of the way of Apple's native binaries. That way when OS Sierra comes along with it's own version of php7 (El Capitan is only 5), it updates the native stuff with a newer stable version of php7, and then it's L//P's override version that I would remove.

webeindustry

If you have your www.conf file using www-data as a group, and yet that's not even a group on the webserver then you will likely have a problem. Figure out what user and group your webserver is running with, and then set that to match your www.conf file for php-fpm.

In linux, with nginx you could try something like this:

ps -eo pid,comm,euser,supgrp | grep nginx

I don't know how this would work on a mac.

So start with the webserver user/group, set that to match with php-fpm, then with permissions for your Flarum install. We're trying to find something that works, not harden your local dev. Keep it simple and if this doesn't work, then the problem must lie with something else.

csf

Just to follow up here... I've had to shotgun the whole install directory with 777 to get it to work.

Php's www.conf file has nothing to do with anything in my case, that's why it was named www.conf.default.

It was actually in Apache's httpd-conf file where user and group were defined and influencing things, both as _www.

But that was independent of Mac's own users/groups. So I've been learning about Mac permissions a bit more and the dscl command-line utility. Long story short... I think in order to make the thing more secure than 777, I need to add my Mac user to the _www group, and perhaps to the staff group too (a Mac-relative group) so that when Mac and Apache both need whatever rights on a directory/file, there won't be a complaint, as there was with the /less directory.

I haven't experimented with it yet, but I will eventually.

Thanks for trying to help. It was all part of my education. ?