You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BugFor errors / faults / flaws / inconsistencies etc.wontfixIf you can reproduce this issue, please reopen the issue or create a new one describing it.
This page has generated 15000 records with unique name field in the piwik_log_action table.
When we run the archive script it segfaults on the first processing step, the rest is fine. The error is following:
/var/www/piwik/misc/cron/archive.sh: line 73: 18891 Segmentation fault $CMD
All suggestions in the FAQ are tried but none seem to work.
One solution found was to remove the token from the name field in every record. But this would not be a long term solution as it would require constant updating the database or filtering at tracker level.
Keywords: segfault cron
The text was updated successfully, but these errors were encountered:
BugFor errors / faults / flaws / inconsistencies etc.wontfixIf you can reproduce this issue, please reopen the issue or create a new one describing it.
We have piwik running in a medium to high traffic website.
Of of the url's being tracked is following: http://www.example.com/unique_token=123489DSFAAF23DSAF34321FDASDF
This page has generated 15000 records with unique
name
field in the piwik_log_action table.When we run the archive script it segfaults on the first processing step, the rest is fine. The error is following:
/var/www/piwik/misc/cron/archive.sh: line 73: 18891 Segmentation fault $CMD
All suggestions in the FAQ are tried but none seem to work.
One solution found was to remove the token from the name field in every record. But this would not be a long term solution as it would require constant updating the database or filtering at tracker level.
Keywords: segfault cron
The text was updated successfully, but these errors were encountered: