Same error with version 5.4.1:
C:\Support\Remedy Utilities\Python Log Analyzer\pyARLogAnalyzer5.4.1>pyarloganalyzer.py --logdir
pyARLogAnalyzer version 5.4.1 by Vincent RIEDWEG (Etat de Genève)
Reading and sorting C:\Support\Remedy Utilities\Python Log Analyzer\pyARLogAnalyzer5.4.1\logs\DS_S37_ESC.001.log
Writing sorted and filtered file...
File C:\Support\Remedy Utilities\Python Log Analyzer\pyARLogAnalyzer5.4.1\logs\DS_S37_ESC.001.log sorted and filtered
Calculating statistics for C:\Support\Remedy Utilities\Python Log Analyzer\pyARLogAnalyzer5.4.1\logs\DS_S37_ESC.001.log
Traceback (most recent call last):
File "C:\Support\Remedy Utilities\Python Log Analyzer\pyARLogAnalyzer5.4.1\pyARLogAnalyzer.py", line 812, in <module> currentline=splitline(line, i)
File "C:\Support\Remedy Utilities\Python Log Analyzer\pyARLogAnalyzer5.4.1\pyARLogAnalyzer.py", line 261, in splitline linesplit['poolint']=int(linesplit['user'][19:-1].strip())
ValueError: invalid literal for int() with base 10: ''
one problem with creating a record in an 'audit' form is that if the first update errors out, that audit entry would be rolled back....so, not surprising that there would only be 1....which is why I suggested doing a run-process to an external log file instead of a push to a form...because Remedy wouldn't be able to roll back the writing of the log file.
Could you send me the log please? I'll have a look.
Thanks for the log file...
It's now fixed...
It was due to duplicates lines in escalation log file on queue Admin (390600) instead of Escalation (390603). Theses lines are now ignored.
You can find the fixed 5.4.2 pre-release here.
Works a charm, thanks!