summaryrefslogtreecommitdiffstats
path: root/watchfrr/watchfrr.c
diff options
context:
space:
mode:
authorDonald Sharp <sharpd@cumulusnetworks.com>2019-09-16 20:25:55 +0200
committerDonald Sharp <sharpd@cumulusnetworks.com>2019-09-16 20:25:55 +0200
commit3f391becca8d50345bbe779ee75349a64f0c6e63 (patch)
tree0df054022112c5cf206ab8d2933df947ddebc05e /watchfrr/watchfrr.c
parentdoc: Add watchfrr documentation (diff)
downloadfrr-3f391becca8d50345bbe779ee75349a64f0c6e63.tar.xz
frr-3f391becca8d50345bbe779ee75349a64f0c6e63.zip
watchfrr: Convert `wtf` to a more meaningful message
There is a fairly common state we are seeing where watchfrr has decided that something is not right and is printing out a `wtf` message. At this point I am not sure what is going on or how we are getting here, but let's add a bit more data dump to the message so that we can figure out what is going on. This is mainly being done because at this point in time I have no clue the what/how of how we got here and I cannot reproduce. Maybe by adding more useful information here I can figure out what is going on. Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com.
Diffstat (limited to '')
-rw-r--r--watchfrr/watchfrr.c4
1 files changed, 3 insertions, 1 deletions
diff --git a/watchfrr/watchfrr.c b/watchfrr/watchfrr.c
index 7586718cd..a6a910a1d 100644
--- a/watchfrr/watchfrr.c
+++ b/watchfrr/watchfrr.c
@@ -561,7 +561,9 @@ static int wakeup_init(struct thread *t_wakeup)
static void restart_done(struct daemon *dmn)
{
if (dmn->state != DAEMON_DOWN) {
- zlog_warn("wtf?");
+ zlog_warn(
+ "Daemon: %s: is in %s state but expected it to be in DAEMON_DOWN state",
+ dmn->name, state_str[dmn->state]);
return;
}
if (dmn->t_wakeup)