Comment 61 for bug 1786910

Hi shaochieh.chiang,

Thanks for getting back to me.

I still need more information, how many services, processes and so on are you monitoring?
Can you share your monitrc configuration?

Your log also contain errors from nginx ... have you tried to solve them?

I'm still not convinced that your problem is related to the "restart all" problem reported here.

The "cannot parse response" error message comes from util.c:2072 (Util_parseMonitHttpResponse) and it comes up when the HTTP response is larger than 300 ... so a 404 (not found) or any other error response code could end up generating the "cannot parse response".

So I believe that there's some problem between your monit and nginx.

Since you are the only person reporting this problem so far, I also would like you to send the information directly to my email (you can get from my launchpad profile), as I am considering your problem as a different problem, not related to the main topic here.
And I don't want people to get confused by our discussion.

As soon as we get more information, we can open a new bug ticket here in launchpad to track your issue, or update this one if there's any relation.

Thanks