@anonymous-matomo-user opened this Issue on June 6th 2012

I couldnt find a way to start the purging process via the command line. In case this already exists maybe it should be better documented.

Otherwise, it would be great to have this option (just like with the auto archiving script) so you dont have to deal with limits PHP might have and to get more debugging possibilities in case something goes wrong (Im currently trying to get purging to work with my 10 gb database).

@mattab commented on June 17th 2012 Member

You should be able to start the purge using the command line, by reproducing the same link as the "Purge now" link.

@mattab commented on June 17th 2012 Member

(In [6482]) Refs #3199

@anonymous-matomo-user commented on June 17th 2012

Do you mean calling the script via wget? That way, the script would still be influenced by the PHP limitations. I thought more of a shell script solution.

@mattab commented on June 19th 2012 Member

No I mean running it on the command line eg.

/usr/bin/php piwik/index.php -- "module=X&action=Y&etc."

I haven't tried but if you replace the module=X... by the URL it should run in CLI ?

@anonymous-matomo-user commented on June 20th 2012

The URL from "purge DB now" looks like this:

The only difference to the URL already opened is the "#" at the end, so I guess this will call some AJAX stuff which I cannot start from the CLI. Please correct me if I am wrong.

In case this works, would it show information about what is being done? That is the main problem why Im asking, as the purge run over night took ~10 hours to complete (purging from 5 to 4.2 gb) and I could only have a look at the SQL statements being run by using "MySQL Administrator" but didnt get any feedback/status from Piwik (or I couldnt find it).

Therefore, a user might assume that the process is stalled and kill the process.

@mattab commented on July 19th 2012 Member

UNfortunately it won't show the information being done, for that using the mysql admin tool is the best.

This Issue was closed on July 19th 2012
Powered by GitHub Issue Mirror