-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
System Check: Tracker status: 500 #8417
Comments
Just ran into the same problem, thanks @mattab that was driving me crazy. |
I have the same issue but cat piwik.old > piwik.php did not help :-/ |
@Geobert I have to admit a couple of times it didn't work for me either. However the files are being compared it seems unstable. Unfortunately I can't help you anymore than to say that I kept trying with it and eventually it would relent. A better approach is probably to delve into how the file comparison is happening in the first place. |
@benjackson84 thanks for your answer, but keep trying what? Just refreshing the page? Or doing cat piwik.old > piwik.php and refresh over and over again? using 2.14.3 BTW |
@Geobert sorry "kept trying" was a bit vague. I ran piwik, then deleted the file then ran piwik again, then restored the file and ran piwik again, then added a new line to the file then ran piwik again, then deleted the new line and ran piwik again. It was a trial and error process (which I hate), I got the impression I was battling with a cache. Eventually it accepted the file. |
Same error here, but I don't have an old piwik.php file. After using the latest beta release no problems anymore. |
Fresh Piwik install on fresh Debian Jessie. Having a "Warning" during Piwik installation for this. Hope it won't bite later. |
Please try with latest beta as hopefully the problem is fixed: http://piwik.org/faq/how-to-update/faq_159/ |
Could you please point me to verify this is a problem at all? How would it manifest? |
In my case (Piwik 2.14.3, new installation) I can see in Apache's error log:
And IMHO there was no instruction to create such a config file before going through the installation steps. Actually the installation process will create it. After it is created, there's no HTTP 500 error any more. So, just ignoring the warning seems to be ok. I have installed via |
I've just run into this issue, running nginx + php-fpm on port 443, Centos 7 + Ajenti V. Initially saw the 500 error on install, tried disabling the mod_ssl which is running on port 9000 for subversion but no change. Having looked on my server (which I wget then unzip the file on) the piwik.php is showing as zero bytes. Moved the file to piwik.old and then pasted into vi a copy of the source piwik.php, saved it and tested with a 200 result. |
+1 Well done! thanks @mattab |
@dcht00 it's not something you can always seen in an editor.^M |
works for me too. I created an empty piwik.php file, then copy and paste the content to this file. voila....the page loads with no errors. Thanks, |
-- New Installation...
500 GET request to piwik.php failed. Try whitelisting this URL from HTTP Authentication and disable mod_security (you may have to ask your webhost). After making this change, restart your web server.
So wrong! The resolution to this issue was REMOVE non-linux artifacts left in the file.
222.229.x.x - - [23/Jul/2015:23:31:46 +0900] "GET /piwik.php HTTP/1.1" 500 - "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:39.0) Gecko/20100101 Firefox/39.0"
[user@webserver piwik]# mv piwik.php piwik.old; echo "" > piwik.php
222.229.x.x - - [23/Jul/2015:23:33:12 +0900] "GET /piwik.php HTTP/1.1" 200 3 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:39.0) Gecko/20100101 Firefox/39.0"
-- The file loads, there is nothing wrong with the web server.
-- Continue installation
File size mismatch: /var/www/html/piwik/piwik.php (expected length: 2534, found: 21)
-- Nice to see it was checked.
THE SOLUTION:
[user@webserver piwik]# cat piwik.old > piwik.php
-- Indicating there is a non-linux artifact somewhere in the file causing the issue. diff WILL NOT show the two files are different.
The text was updated successfully, but these errors were encountered: