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

Jump to bottom

After Update to matomo 3.6 problems with PHP FPM versions #13389

Open
kanow opened this issue Sep 5, 2018 · 2 comments
Open

After Update to matomo 3.6 problems with PHP FPM versions #13389

kanow opened this issue Sep 5, 2018 · 2 comments
Labels
Can't reproduce (yet) For issues that are reported by several people, but can't be reproduced reliably and need more data
Milestone
For Prioritization

Comments

@kanow
Copy link

kanow commented Sep 5, 2018

Hi,
after updating matomo to 3.6 we can't use matomo on php FPM versions. We must switch to CGI versions to get matomo working. Those problems are in different version, from 5.5 till 7.1.
The last upgrade step, the database update, failed with 500 error. But on reloading the page I can login into the matomo user interface and everything seems working correctly.
Error Log says:

[Wed Sep 05 18:11:35.038238 2018] [fcgid:warn] [pid 18398:tid 139911537600256] (104)Connection reset by peer: [client xx.xx.xx.xx:55632] mod_fcgid: error reading data from FastCGI server, referer: https://piwik.customerdomain.de/index.php?module=CoreUpdater&action=
[Wed Sep 05 18:11:35.038283 2018] [core:error] [pid 18398:tid 139911537600256] [client xx.xx.xx.xx:55632] End of script output before headers: index.php, referer: https://piwik.customerdomain.de/index.php?module=CoreUpdater&action=

PHP 7.1 is running.
@fdellwing
Copy link
Contributor

fdellwing commented Sep 5, 2018 •
edited

Please check if the FPM server has the rights to access and execute the files.

@mattab
Copy link
Member

mattab commented Sep 5, 2018

I also experienced this problem once but I couldn't also see any information in the log and ended up ignoring it as everything was working after this error

@Findus23 Findus23 added the Can't reproduce (yet) For issues that are reported by several people, but can't be reproduced reliably and need more data label May 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Can't reproduce (yet) For issues that are reported by several people, but can't be reproduced reliably and need more data
Projects
None yet
Milestone
For Prioritization
Development

No branches or pull requests
5 participants
@mattab @Findus23 @kanow @fdellwing @innocraft-automation