This is similar to the way email alerts are sent when servers are marked as DOWN.
Like the log messages corresponding to these state changes the messages have log level notice. Thus they are suppressed by the default email-alert level of 'alert'. To allow these messages the email-alert level should be set to 'notice', 'info' or 'debug'. e.g: email-alert level notice "email-alert mailers" and "email-alert to" settings are also required in order for any email alerts to be sent. A follow-up patch will document the above. Signed-off-by: Simon Horman <ho...@verge.net.au> --- src/server.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/server.c b/src/server.c index a50f9e123741..ee6b8508dac0 100644 --- a/src/server.c +++ b/src/server.c @@ -332,6 +332,7 @@ void srv_set_running(struct server *s, const char *reason) srv_append_status(&trash, s, reason, xferred, 0); Warning("%s.\n", trash.str); send_log(s->proxy, LOG_NOTICE, "%s.\n", trash.str); + send_email_alert(s, LOG_NOTICE, "%s", trash.str); for (srv = s->trackers; srv; srv = srv->tracknext) srv_set_running(srv, NULL); @@ -484,6 +485,7 @@ void srv_set_admin_flag(struct server *s, enum srv_admin mode) Warning("%s.\n", trash.str); send_log(s->proxy, LOG_NOTICE, "%s.\n", trash.str); + send_email_alert(s, LOG_NOTICE, "%s", trash.str); if (prev_srv_count && s->proxy->srv_bck == 0 && s->proxy->srv_act == 0) set_backend_down(s->proxy); -- 2.1.4