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
PHP Fatal error: Either cli core:archive or web index.php, but not both #6189
Comments
can you try to re-upload all files from 2.6.1 ? when the interface doesn't work is there an error message, could you display it with the full backtrace? |
I set up 2.6.1 from scratch, went through the installation and connected to my existing database. Problem is here again. I don't have more backtrace then the following: On CLI and Apaches error_log I get:
In the Browser I see the same:
|
Downgraded to 2.5.0: same Fatal error! So I guess the Bug got introduced in 2.5.0. So we are back to 2.4.1, where cli and web work at the same time. |
@andreli what php version do you use? |
@mattab: 5.3.3 |
can you try upgrade to most recent, maybe this would fix this issue? |
Most recent Piwik or PHP? Piwik runs on enterprise infrastructure, so upgrading PHP is no option. |
@mattab: We can live with Piwik version 2.4.1 and will see further once we have a higher version of PHP available, which might be happening beginning next year. But shouldn't you then update the documentation, that currently still states on http://piwik.org/docs/requirements/: PHP version 5.3.2 or greater? |
FYI: We are experiencing with Piwik 2.7.0 still the same problem. |
I have the exact same problem with PHP 5.4.4 on Debian. Either the auto archiver cron works or the web interface but not both. It does't seem to be permissions related. |
Thanks for the report, unfortunately we cannot reproduce the issue yet. |
another thing I noticed is that I can call |
Ok I found it. The piwik installation is in a directory that is accessible under two paths – one being a symlinked version. The vhost was configured to use one path while the cron job tried to call the script with the other path. Probably composer/twig doesn't use |
Thanks for follow up! hopefully @andreli you have the same issue? |
@qwesda : Thanks for your findings. We are as well running piwik symlinked into different servers: So, how have I to set up my infrastructure so that composer/twig does not trip? |
I am not sure myself why this problem appears, in my case I just have two installations of Piwik in two different directories (no symlinks) - everything is seperate (database user, tables, etc.), so nothing should collide, yet in my Nginx error log these errors appear:
I have two paths, "testing" and "latest", and the error message only occurs when I am trying to access the web interface in "testing", yet the error mentions a class which is already declared in "latest". |
Thanks for the report, but we cannot reproduce. if you know how to reproduce, please create a new issue with steps to reproduce, we will definitely investigate & fix it. thanks |
I updated from 2.4.1 to 2.6.1.
Everything seamed to work fine with the exception of
After deleting the contents of /tmp, the cron job worked fine, but then the web interface ceased to work. After again deleting /tmp, the web was back, as was the problem with my cron job.
Error:
Did I miss a configuration or did I run in a known bug?
The text was updated successfully, but these errors were encountered: