2012/9/12 Roberto De Ioris <[email protected]>: >> Machine I'm using to collect carbon stats is a VM with slow I/O, it's >> possible that I'm hitting connection timeout since with current code >> carbon plugin will not print any error message and probably set >> last_update=now() so at next cycle stats won't be resend. >> I'll try to fix that later today. >> >> > > This is probably the reason, as uwsgi_connect() do no print error messages, > but simply fails with -1
Let's make a deal: I will refactor carbon plugin a little bit, so that it logs timeout errors and in case of timeout it will retry at next cycle. You will add plugin hook that will be executed at master exit (right now I can only call plugin at any worker exit) so that I can also finish #148. How about that? -- Łukasz Mierzwa _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
