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.CriticalIndicates the severity of an issue is very critical and the issue has a very high priority.duplicateFor issues that already existed in our issue tracker and were reported previously.
Our company is considering using Piwik as our primary web analytics software, but must be able to import old web logs (python software). The problem is similar to that of other posts, which reports Fatal Error: None while printing:
1369 lines parsed, 0 lines recorded, 0 records/sec (avg), 0 records/sec (current)
We are running MySQL Server 5.5 and PHP 5.4 in IIS. The log files are from urchin and are .gz format. Every now and then, a log will successfully import but when we try again, it produces the same error. Any thoughts would be greatly appreciated and allow us to use Piwik as our primary software. Thanks.
Keywords: logs, importing, error
The text was updated successfully, but these errors were encountered:
BugFor errors / faults / flaws / inconsistencies etc.CriticalIndicates the severity of an issue is very critical and the issue has a very high priority.duplicateFor issues that already existed in our issue tracker and were reported previously.
Our company is considering using Piwik as our primary web analytics software, but must be able to import old web logs (python software). The problem is similar to that of other posts, which reports Fatal Error: None while printing:
1369 lines parsed, 0 lines recorded, 0 records/sec (avg), 0 records/sec (current)
We are running MySQL Server 5.5 and PHP 5.4 in IIS. The log files are from urchin and are .gz format. Every now and then, a log will successfully import but when we try again, it produces the same error. Any thoughts would be greatly appreciated and allow us to use Piwik as our primary software. Thanks.
Keywords: logs, importing, error
The text was updated successfully, but these errors were encountered: