MySQL Bugs: #106481: Work bench error log file incorrectly on windows MYSQL server

Bug #106481	Work bench error log file incorrectly on windows MYSQL server
Submitted:	17 Feb 2022 0:27	Modified:	1 Mar 2022 2:15
Reporter:	Mx Dog	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S3 (Non-critical)
Version:	8.0.28	OS:	Windows (Microsoft Windows 10 Pro)
Assigned to:		CPU Architecture:	Any
Tags:	format, log, WBBugReporter

Description:
All data from the log is in the details field the Time Stamp and Type Fields are empty. 

this seems to only be windows MySQL server because my Linux servers display correctly. /n/r difference ?

 

How to repeat:
open windows mysql8 server error log file in workbench 

Suggested fix:
determine what is different between Linux and windows server logs and fix the regex ( whatever you are using) that splits the fields?

The Workbench log

Attachment: wb.log (application/octet-stream, text), 46.57 KiB.

8.0.28 A linux error log from another local server

Attachment: MySql-Linux-error.log (application/octet-stream, text), 40.60 KiB.

Picture of the error

Attachment: WbLogError.PNG (image/png, text), 370.69 KiB.

Hello,

Thank you for the bug report.
I tried to reproduce your issue on Windows 10 with MySQL workbench 8.0.28 but I am not seeing any issues at my end.

Regards,
Ashwini Patil

Please find the screenshot below

Attachment: 106481_test_results.PNG (image/png, text), 75.40 KiB.

I deleted the logs rebooted computer and by extension the Mysql instance and it seemed to self correct ....maybe had a bad character(s) in the log file ? 

sorry, false alarm it seems. will update if it returns.

as an aside the parsing algorithm might need tweaked to ignore crud formatting and or chars with a corrupted log file.