Quote
Mako77
Output is as follows:
2013-03-07 21:35:02,334: [DEBUG] Resolver: static
0 lines parsed, 0 lines recorded, 0 records/sec (avg), 0 records/sec (current)
2013-03-07 21:35:02,552: [DEBUG] Launched recorder
Parsing log log-Feb-2009...
2013-03-07 21:35:02,568: [DEBUG] Detecting the log format
2013-03-07 21:35:02,584: [DEBUG] Format ncsa_extended matches
3221 lines parsed, 0 lines recorded, 0 records/sec (avg), 0 records/sec (current
)
2013-03-07 21:35:03,865: [DEBUG] Error when connecting to Piwik: <urlopen error
None>
5071 lines parsed, 0 lines recorded, 0 records/sec (avg), 0 records/sec (current
)
5071 lines parsed, 0 lines recorded, 0 records/sec (avg), 0 records/sec (current
)
5071 lines parsed, 0 lines recorded, 0 records/sec (avg), 0 records/sec (current
)
2013-03-07 21:35:06,818: [DEBUG] Error when connecting to Piwik: <urlopen error
None>
5071 lines parsed, 0 lines recorded, 0 records/sec (avg), 0 records/sec (current
)
5071 lines parsed, 0 lines recorded, 0 records/sec (avg), 0 records/sec (current
)
5071 lines parsed, 0 lines recorded, 0 records/sec (avg), 0 records/sec (current
)
2013-03-07 21:35:10,395: [DEBUG] Error when connecting to Piwik: <urlopen error
None>
Fatal error: None
You can restart the import of "log-Feb-2009" from the point it fail
ed by specifying --skip=79 on the command line.
If I use the parameter --disable-bulk-tracking then it seems to say more about lines recorded but still has the urlopen error problem.
Would love to see this working :S
To get this particular import to resume use --skip=5071. Mind you, I don't know by doing this if valid log lines are being passed over. Have to wait for an actual bug fix. i.e. don't use what's actually reported by skip, instead go by lines parsed.