Hi @derSascha

thanks for suggestion.

I'm curious to learn more because it's the first report about this issue.

This results in permission problems writing to tmp/* files.

Could you post the error messages?

HI @mattab

error message: Piwik couldn't write to some directories...

ls -l piwik-current/tmp
drwxr-x---  2 www-piwik     www-piwik 4096 Mar 26 21:23 assets
drwxr-x---  3 www-piwik     www-piwik 4096 Mar 26 21:21 cache
drwxr-x---  2 www-piwik-adm www-piwik 4096 Mar 26 21:23 logs
drwxr-x---  2 www-piwik-adm www-piwik 4096 Mar 26 21:23 tcpdf
drwxr-x--- 38 www-piwik-adm www-piwik 4096 Mar 26 21:23 templates_c

My setup runs the tracking code as piwik user (more threads, less memory per thread) and the admin ui as piwik-adm user (threads ondemand with more memory). This ends up with permission trouble and i have to run chmod -R g+w tmp/* to fix the permission (both users are in the same piwik group).

Shouldn't it fallback anyway in case 750 is not enough? See https://github.com/piwik/piwik/blob/2.13.0-b1/core/Filesystem.php#L90-L96

Maybe this doesn't work correctly? I reckon it would be better here to be a bit paranoid and try 750 by default and if it doesn't work 770. Maybe we should try there 770 as well?

👍
My Nginx uses the www-data user, so when I try to run the console utility as myself I get

  [InvalidArgumentException]
  The directory "/var/www/sites/piwiki-2.14.3/tmp/cache/tracker/" is not writable.

I really don't want to do sudo -H -u www-data bash -c './console', so I applied the patch from @derSascha , but I would love to see this merged.

Thank you for this proposed pull request.

Because it was last updated more than one month ago, it is our policy to close pull requests opened for a long time without updates. If you would like to continue work on the pull request, please simply ping us to have it re-opened (after you have pushed a new commit).

We hope you understand this and we look forward to seeing an update from you on this pull request or another one!

Thanks.