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
Archiving doesn't work anymore on 1.1.x with the cron script #1974
Comments
What do you get when you execute these from the shell? php -v
|
I got this : (Debian Squeeze)
|
Maybe related, see forum post: http://forum.piwik.org/read.php?2,70783 Error Message
|
MANY users have this issue: http://forum.piwik.org/read.php?2,70638 |
(In [3649]) refs #1974 - Notice: Undefined index: SCRIPT_NAME (occurs when using php-cgi) |
Fixed, sorry, It was a problem of permissions, with the -x option of sh, I saw the script said "Coudn't write on ....' I changed the permissions and now it works. Sorry for the inconveniance. |
(In [3652]) fixes #1974 - force the execute bit (if needed) |
No, the problem of permissions wasn't here, it was because some directories of my piwik installation weren't writable by the user with who I started the script. It's because I had to change the user of my "/home/piwik/public_html" to www-data (user used by Apache on Debian) to do the update via the website because I didn't install suPHP or other tools to make the script be executed by its owner (piwik in my case). I forgot after that to restore the original permissions that made fail the archive script. It would be useful that the archive.sh verify that it can write in the diretories it needs, the administrator would see immediatly where is the problem. :) |
Hello,
I'm using piwik with the option (in french) "Autoriser l'archivage de Piwik se dclencher lorsque les rapports sont visionns depuis le navigateur" set to "no", I'm using so a cron to execute the "archive.sh" every hours, but since my update to 1.1.1 this morning my piwik doesn't show any new data today.
So I tried to execute the script manually :
As you can see it doesn't do anything.
I setted back the option to "Yes" and the new data are shown, so I suppose that the script doesn't work anymore.
Ask if you want more details :)
Keywords: archive cron
The text was updated successfully, but these errors were encountered: