Something tells me this was an EQ related change per the last patch that has reared it's head when we rolled into May, hence GINA will need to patched to fix it. Atleast we have a work around in the meantime
Changing the date fixes gina but breaks something about firefox. Many pages are coming up with the error An error occurred during a connection to www.reuters.com. The OCSP response contains out-of-date information. Error code: SEC_ERROR_OCSP_OLD_RESPONSE
Changing the date on your machine can break a lot of software that calls home for licensing checks as well. So beware doing that. Hopefully the Gina dev can fix this quickly.
I have been in contact with someone who knows the dev and he has relayed the problem to him. Fingers crossed.
PM'd the dev for GINA here on the forums. If someone has an active account on eqresource and can post in the bugs thread for gambosoft, that will help as well.
For anyone that knows how to run Python here's an example script that works as the workaround I mentioned. That is, if you're desperate and raiding today. Just change the file names up top and run it from your logs dir. Code: import re import win32file eqLogFile = 'eqlog_Kazint_firiona.txt' fixedLogFile = 'eqlog_Kazint_firiona_ginafixed.txt' logRe = re.compile('^(\[\w{3}\s\w{3}\s)(\s)(.*)') logfile = open(eqLogFile, 'r') newfile = win32file.CreateFile( fixedLogFile, win32file.GENERIC_WRITE, win32file.FILE_SHARE_DELETE | win32file.FILE_SHARE_READ | win32file.FILE_SHARE_WRITE, None, win32file.OPEN_ALWAYS, win32file.FILE_FLAG_WRITE_THROUGH, None) logfile.readlines() win32file.SetEndOfFile(newfile) while True: line = logfile.readline() result = logRe.search(line) if result is not None: newline = result.group(1) + '0' + result.group(3) + '\n' win32file.WriteFile(newfile, newline.encode()) else: win32file.WriteFile(newfile, line.encode()) win32file.FlushFileBuffers(newfile)
my log file that it auto monitors seems fine still, also tried loading the same log file, works fine too.
Anyone tried using a regex for the new time stamp format in any of their triggers to see if that helps?
Did a quick test today and Gina is working for me but the matched text now includes the date and time stamp
Gina gives me an error on loading but then stays up. But first time it gets a trigger it closes with no apparent warning.
Perhaps somebody at DBG needs to take a look at this as well? Changing the log format without any notice is not nice. Change it back?
Something else to pass along is it seems to be affecting the ability to search in logs also in log files containing the new timestamps.