Hi Sean, It is probably safer not to put the intermediate files in [dspace]/log/ and called dspace.log.* as the 'traditional' DSpace statistics reports still look in that directory for dspace.log* files, and DSpace will still be writing its dspace.log* log files there. Best keep them somewhere separate if possible.
I've tried importing the dspace.log file you sent, and it seemed to work fine: gendiglt02:~ stuartlewis$ /dspace/bin/dspace stats-log-importer -i dspace.log Processing file: dspace.log Processed 309 log lines - 4 entries added to solr: 1.294% - 144 errors: 46.602% - 161 search engine activity skipped: 52.104% About to commit data to solr... done! (it lists 144errors, but that is because you have handles that don't exist in my development copy of DSpace - otherwise no errors were thrown) The error you mentioned in your first email 'Error seeking country while seeking 3251471352' is thrown when the code tries to find out what country and city the request was made from. It looks this up from an IP address. Could you re-run the script, and when it throws one of these errors, look at the file it is importing, find the line that has that value on, and copy that line into an email? It is strange that there is a 10 digit number instead of an IP address, so we need to work out where it is getting that from. Thanks, Stuart ________________________________________ From: Sean Carte [[email protected]] Sent: Saturday, 6 March 2010 1:32 a.m. To: Stuart Lewis Cc: dspace-tech Subject: Re: [Dspace-tech] DSpace 1.6 Upgrade & Statistics On 4 March 2010 23:29, Stuart Lewis <[email protected]> wrote: > >The log files are only getting converted into an intermediate file format >ready for > import into solr. [dspace]/log/dspace.log* files still get created in the > same format, so > it might be worth saving the converted files somewhere else, and as a > different file > name, so as not to get confused between the log4j 'dspace.log' files, and > these > intermediate files that contain less information ready to be imported into > solr. I did something like that: I copied all the original dspace.log* files to another directory, then converted them with the intermediate files ending up in my /dspace/log/ directory, which I then tried to import: dsp...@esal-lr:~$ /dspace/bin/dspace stats-log-converter -i /dspace/log/old/dspace.log -o /dspace/log/dspace.log -m dsp...@esal-lr:~$ /dspace/bin/dspace stats-log-importer -i /dspace/log/dspace.log -m > Could you send me a copy of one of your original dspace.log files, and the > corresponding version which stats-log-converter creates? I can then look at > them, and try importing them on my machine to see what might be going wrong. > Attached. Sean -- Sean Carte esAL Library Systems Manager +27 72 898 8775 +27 31 373 2490 fax: 0866741254 http://esal.dut.ac.za/ ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
