EPG123 Log Parser

An evolving, supported alternative to Rovi
Forum rules
★ Download the latest EPG123 here: http://epg123.garyan2.net <> Setup guide here: http://epg123.garyan2.net/downloads/epg123_Guide.pdf
duncane

Posts: 119
Joined: Mon Jun 06, 2011 5:02 pm
Location: Scotland

HTPC Specs: Show details

Re: EPG123 Log Parser

#21

Post by duncane » Sun Dec 24, 2017 6:20 pm

Hi, I'm receiving this error on startup. More Error Info dialog below it.
Cheers
Attachments
Capture.JPG

User avatar
StinkyImp

Posts: 211
Joined: Thu May 11, 2017 7:53 pm
Location:

HTPC Specs: Show details

#22

Post by StinkyImp » Sun Dec 24, 2017 6:33 pm

Thanks for the feedback!

Would you send me your log files? I'll be better able to see where it's failing.

If you have more than one trace.log I'd like to use all of them.

duncane

Posts: 119
Joined: Mon Jun 06, 2011 5:02 pm
Location: Scotland

HTPC Specs: Show details

#23

Post by duncane » Sun Dec 24, 2017 6:45 pm

Hi, PM'd the trace log. The last run of EPG123 actually failed tonight which you'll see at the very bottom. This is on a test system so I wasn't too bothered and thought I'd wait to see what happens tomorrow night.
Cheers

User avatar
StinkyImp

Posts: 211
Joined: Thu May 11, 2017 7:53 pm
Location:

HTPC Specs: Show details

#24

Post by StinkyImp » Sun Dec 24, 2017 6:55 pm

Just looking at the error you posted above, it appears that your system tracks dates in the YYYYDDMM format and mine looks at the format as YYYYMMDD. I'll have to do some digging to see how I can overcome that.

In addition, this log parser doesn't care if EPG123 has a failure, it parses what's given to it, errors and all.

Thanks for your feedback and have a great holiday!

duncane

Posts: 119
Joined: Mon Jun 06, 2011 5:02 pm
Location: Scotland

HTPC Specs: Show details

#25

Post by duncane » Sun Dec 24, 2017 7:02 pm

No problem, have a good one!
Cheers

User avatar
StinkyImp

Posts: 211
Joined: Thu May 11, 2017 7:53 pm
Location:

HTPC Specs: Show details

#26

Post by StinkyImp » Fri Dec 29, 2017 1:58 pm

Happy New Year (almost)!

With duncane's gracious offer to become my test subject I was able to rewrite the code to handle trace.log dates in the DD/MM/YYY format. He reports back that everything appears to be working correctly!

There is one caveat... While I was happily working in the US and thinking, "Dates? Haven't they been around since ummm... forever?" and found out that even though they'd been around forever, nobody has ever standardized them!

At this point US configured (MM/DD/YYY) and most European, South America, and Australian (DD/MM/YYYY) machines should work famously. I point this out because unfortunately, all countries adhere to their own date formats, including separators. It's highly conceivable that someone could have trace.log dates in the format of YYYY-MM-DD. Currently this will not work for those situations.

So... I'll be working on that problem.

Canadians - Based on my research it appears that this will not work with your log files. If you would be willing to assist me with this I would certainly appreciate it. I couldn't have made the current changes without duncane's feedback.

In the meantime this release includes the following changes:
  • 1. An "Operating Guide.pdf" that will extract to the same directory as this utility and is available from within the interface.
  • 2. Code cleanup.
  • 3. Will now analyze DD/MM/YYYY formatted logs.
To reiterate...
  • This utility will not affect EPG123 or it's logs. It works off copies.
  • This utility is completely portable and will only write information in the folder it's placed in.
Instructions - Create a temporary (or permanent) folder in a place of your choosing and drop the "EPG123 Log Parser.zip" file in it. Change zip to exe and you're off.

User avatar
StinkyImp

Posts: 211
Joined: Thu May 11, 2017 7:53 pm
Location:

HTPC Specs: Show details

#27

Post by StinkyImp » Thu Jan 04, 2018 11:23 pm

This may as well be a new utility. I kept the user interface and (to me) the date range selector is a must, especially when I currently have almost a year's worth of logs. It's nice to see trends in execution times, the number of days I ran certain versions, etc. I've also included additional error checking and other safeguards to assure that the actual live EPG123 log files are never harmed.

This is an entire core rewrite that actually calculates the user's date structure. The only thing is... I don't have hundreds of computers to test it on so I wrote in a user date verification dialog. If my independently calculated human readable date agrees to the extracted date from the copy of the trace.log file, then we're good to go. The user simply needs to verify it.
Date Verification.png
If there's a date mismatch, then the user can create a diagnostic report and PM it to me so I can try to replicate and then fix the error.

These are the only requirements that I've coded for:
  1. The target system uses a 4 digit year.
  2. Uses any combination, in any order, of Year, Month, and Day.
  3. Uses one of the following to separate their dates, (/) forward slash, (.) period, (-) dash, or a single blank space.
The new version also includes an "Operating Guide" that goes into more detail about the actual operation of the utility and can be opened from within the user interface. Please pay attention to the "persistent files" section. Keeping the ini and predefined terms are beneficial to subsequent executions.

The current version is 1.6.0A. In the future I'm going to post all versions and updates here.

User avatar
StinkyImp

Posts: 211
Joined: Thu May 11, 2017 7:53 pm
Location:

HTPC Specs: Show details

#28

Post by StinkyImp » Sat Jan 06, 2018 3:26 pm

At this point my HTPC is running like a top and I intend to clone my primary once a month as disaster prevention so... I'm set for the foreseeable future and my visits here will likely diminish unless I have a problem.

I built this utility for me (just for fun) so I'll probably tinker with it as I continue to use it and see things that I'd like to change. One thing that's been nagging at me is the requirement to use 4 digit years. I'm not sure anyone uses 2 digit years anymore, but hey, someone might! Other than that the version numbers at the link above will increment based on changes. Sometimes (like the most recent) are simply cosmetic changes...

Quick note about "Everything" - I was debugging and thought, "What if I wanted to see everything that happened last Saturday or some other date in the past?" so I added "Everything" to the Predefined list that would generate a report for everything that happened for a date (or range) of the user's choosing. Right now I have 11 months of log files and that's a LOT of data.

In the meantime I'm keeping this an "ALPHA" release simply because I don't have enough feedback to make a determination otherwise. ;) Since I won't be visiting much, the best way to submit bug reports would be via the email link in my profile.

Many thanks :clap: to garyan2, duncane, and Scallica for all their patience and assistance with this silly project!

User avatar
StinkyImp

Posts: 211
Joined: Thu May 11, 2017 7:53 pm
Location:

HTPC Specs: Show details

#29

Post by StinkyImp » Thu Mar 21, 2019 11:36 pm

Would anyone be interested in helping test the newest version of this?

As far as the log files, it makes a copy of the live logs and works from the copies only. It's also completely self-contained and portable.

I haven't been keeping track of all the changes I've made over the past year or so, but they're enhancements that I've found useful.

It now includes (if available) some general information that Gary might find useful when providing support.

NOTE: Windows 10 WMC installations will most likely fail the "ehshell version" check because of the funky way it needs to be installed.

I've created a 64 bit version that saves some time when chugging through really large log files. Mine is 775 days old (a little over two years) and it took 33 seconds to go through 59,583 log lines. My "trace.log" is only 36 days and 3,100 lines. It takes 2 - 3 seconds to process.

Log Parser 32 vs 64.png
Left is 32 bit version <----- -----> Right is 64 bit version
Versions for testing: Thanks in advance for any feedback!

EDIT:
Installation - Create a directory and unzip the executable into it. Double-click to start it.
Removal (uninstall) - Delete the directory you created.

User avatar
d00zah

Posts: 118
Joined: Fri Nov 07, 2014 7:20 pm
Location:

HTPC Specs: Show details

#30

Post by d00zah » Fri Mar 22, 2019 12:33 am

Cursory examination... no issues jump out except last detected 'client version' string, as defined:

[9/7/2018 3:43:42 AM] [ INFO] epg123 client version: 1.2.4.0

where the report ends. After that, string has changed to:

[3/21/2019 3:37:55 AM] Beginning epg123 client execution. version 1.2.11.0

Defined new string 'client execution. version'. Just need to remember difference when evaluating logs.

User avatar
StinkyImp

Posts: 211
Joined: Thu May 11, 2017 7:53 pm
Location:

HTPC Specs: Show details

#31

Post by StinkyImp » Fri Mar 22, 2019 3:12 pm

Are you saying that the lower part of the report under the heading "GENERAL INFORMATION" reported the wrong EPG123 version? It should be retrieving the last instance in the log that follows "client execution. version"

Code: Select all

===== GENERAL INFORMATION ======================================
Total lines processed:	3095
EPG123 version:		1.2.7.0
Log Path:		C:\epg123\
ehshell version:	6.1.7601.23434
Operating System:	Windows 7 Professional (64 bit)
Processor:		Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz
Total RAM:		8.00 GB
Logfile timespan:	2/14/2019 thru 3/21/2019 (36 days)
Was any other information in that section incorrect?

I know over the course of time, this utility has saved me from asking some really stupid questions. I'm hoping that if anyone else uses it and posts results for Gary, it will include some basic information in the "General Information" section to help him troubleshoot.

Thank you for your feedback! :D

User avatar
d00zah

Posts: 118
Joined: Fri Nov 07, 2014 7:20 pm
Location:

HTPC Specs: Show details

#32

Post by d00zah » Fri Mar 22, 2019 3:38 pm

All the 'GENERAL INFORMATION' summary detail was correct. Just noticed the list of log entries containing 'client version' stopped on 9/7/2018, when the logging changed. Had forgotten (early onset 'sometimers') that search strings are user defined. When I realized that, I just added the new/updated string.

User avatar
StinkyImp

Posts: 211
Joined: Thu May 11, 2017 7:53 pm
Location:

HTPC Specs: Show details

#33

Post by StinkyImp » Wed Apr 03, 2019 7:54 pm

Minor update (version 1.7.0):
  • Fixed an issue where the progress meter displayed improperly on huge (merged) logs.
  • Disabled "ehshell" version checking on Windows 10 systems.
  • Included an updated Operating Guide.
  • ... minor code cleanup.
Portable "zip" versions (create a folder and extract the executable into that folder)
  • 32 bit -> EPG123 Log Parser v170-32.zip
  • 64 bit -> EPG123 Log Parser v170-64.zip
Installer Version (with complete uninstaller)
  • 32 bit -> EPG123 LogParser32 Setup.exe
  • 64 bit -> EPG123 LogParser64 Setup.exe
I was going to link each file directly but the forum limited the number of URL's to three. The utility files can be downloaded from here.

Security Check:

User avatar
StinkyImp

Posts: 211
Joined: Thu May 11, 2017 7:53 pm
Location:

HTPC Specs: Show details

#34

Post by StinkyImp » Sat Apr 13, 2019 5:54 pm

I use this utility almost every day, primarily to check for errors and warnings. Over the course of time I see minor things I'd like to change or enhance but I don't see them being worth the effort to implement at the time... So they go into the back of my mind.

This recent flood of changes are because of the buildup of all the little enhancements that have accumulated over time. The most recent changes were initiated by the progress meter displaying improperly on huge merged files. At that point it had been over a year since the last update.

Minor update (version 1.7.1):
  • Expanded reporting to include some generic system information that "may" be helpful in troubleshooting. (See Below)
  • Replaced the generic log file name with the actual log file names used for the current query.
  • "Prettied up" the installer graphic.
  • ... more minor code cleanup.
Portable "zip" versions (create a folder and extract the executable into that folder)
  • 32 bit -> EPG123 Log Parser v171-32.zip
  • 64 bit -> EPG123 Log Parser v171-64.zip
Installer Version (with complete uninstaller)
  • 32 bit -> EPG123 LogParser32 Setup.exe
  • 64 bit -> EPG123 LogParser64 Setup.exe
Security Check: New "System Information" section in the report summary:

Code: Select all

===== SYSTEM INFORMATION =======================================
Operating System:	Windows 7 Professional (64 bit)
Processor:		Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz
Total RAM:		8.00 GB
ehshell version:	6.1.7601.23434
EPG123 version:		1.2.7.0
Last boot time:		March 31, 2019 - 4:51 PM
System Uptime:		12 Days 12 Hours 44 Minutes
I check the forum regularly but since I won't be updating this thread very often, the utility files will be placed here as they're updated.

I'm currently satisfied with the operation and reporting of this utility so it may be another year (or more) before any further updates!

Post Reply