Invalid non-UTF8 bank names break the mhttpd status page

Got into a strange corner case. As far as I understand, the following is what happened:

1) Frontend program went bad and created a bank with a non-UTF8 bank name.

2) Error message was printed into the midas log. The error message included the utf-8 incompatible string, in a message like

"Invalid name XXXX passed to YYYY: UTF-8 incompatible string"

3) After this message got into the midas log, the mhttpd status page started continuously popping up an error message, complaining about the non-UTF8 string preventing the JSON conversion. The problem is that the mhttpd JS makes a call to JS method cm_msg_retrieve which retrieves the last 100 messages, which then causes the error.

I fixed the error by removing the offending line from midas.log. You can also just wait till 100 extra messages get put into the midas.log

But hopefully it is possible to modify the status.html code so that it doesn't pop up continuous errors when this happens.

Comments (2)