search

asim / pingy

lightweight read-only mmonit in ruby
0 stars 0 forks source link

Question #6

Closed michaelminter closed 10 years ago

michaelminter commented 10 years ago

Do you know why monit would keep sending requests without the delay?

I have two Sinatra apps that seemingly respond with the same headers. There is one server running Monit. When I change the set mmonit from one server to the other all the data is parsed but Monit will not wait the designated 60 second poll time like the other.

Any ideas?

michaelminter commented 10 years ago

I've narrowed this down to:

(errors) [CDT Oct 3 22:33:42] error : M/Monit: error receiving data from http://:12345/542b53c169702d22da000000 -- Resource temporarily unavailable [CDT Oct 3 22:33:42] error : M/Monit: communication failed (status message)

(pov) https://github.com/arnaudsj/monit/blob/aa491f6ca2d2dd79abebf1e97b6f3a14fd4453e8/collector.c#L182 https://github.com/arnaudsj/monit/blob/aa491f6ca2d2dd79abebf1e97b6f3a14fd4453e8/collector.c#L115

I don't know C very well.

I'm guessing it's a server thing at this point. The good one is hosted on Heroku and the one that's giving me grief is self-managed. Both AWS :/

michaelminter commented 10 years ago

Looks like this problem is in Monit 5.1 and gone by 5.8.1 (as far as I can see)

asim commented 10 years ago

Is there any relation to the data store you're using for mmonit? SQLite is single threaded and could potentially be causing some issues if your sending updates via many monit agents.

michaelminter commented 10 years ago

Both are Sinatra apps, one using Redis, and the other MongoDB.

I'm pretty sure it's something to do with the server response.

Though they're both AWS I'm guessing the web server might be the culprit. The one "not working" with Monit is Nginx/Passenger...

asim commented 10 years ago

Sorry for not getting back on this sooner. Were you able to resolve the issue?

michaelminter commented 10 years ago

I have no idea why two servers hosted by the same company get different responses from Monit.

I did find that the difference between Monit version 5.1 and 5.2 the issue is resolved. But that just means that you can't use the default yum repositories :/

Pretty much have moved on to other projects. Oh well