-
Notifications
You must be signed in to change notification settings - Fork 131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better Error Reporting of Errors in User/Common Code #43
Comments
On Tue, Jan 22, 2013 at 11:38:04AM -0800, krkeegan wrote:
Sure thing: 20/01/2013 22:51:39 ---------- Restart ---------- 20/01/2013 22:51:45 : 20/01/2013 22:51:45 : Omnistat[2]->send_cmd did not get expected first byte (0x82) in ack reply to command 02 20 48 01 6b (got 0x06 in 0x06 0x22 0x48 0x01 0xed ) at ../lib/Omnistat.pm line 498. 20/01/2013 23:10:53 ---------- Restart ---------- 10/01/2013 05:02:38 ---------- Restart ---------- 10/01/2013 09:27:00 : Could not get TempOutdoorCrawlspace temp at (eval 850) line 7190. 10/01/2013 09:33:14 ---------- Restart ---------- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. |
Marc, It looks like you have Stdout and possible Stderr set to output to the mhl 2>&1 >> data/logs/error.log I otherwise can't find how this would be written. On Tue, Jan 22, 2013 at 12:48 PM, Marc MERLIN [email protected]:
|
On Tue, Jan 22, 2013 at 01:01:25PM -0800, krkeegan wrote:
I run No special trickery, it just works for me. Marc"A mouse is a device used to point at the xterm you want to type in" - A.S.R. |
Currently, if a user uses the "reload user code" command and there is an error in one of the user code files the user is only notified of the error in the console output. There is no option to enable logging of the error.
All of this is buried deep within the main mh perl file. Notably, the eval_user_code_load handles a lot of the error reporting to the console with a series of simple print commands.
Optionally sending these errors to a log seems like a good idea. This should probably be in addition to sending the errors to console.
As a side note, is anything other than a "Restart" ever sent to the error_log?
The text was updated successfully, but these errors were encountered: