I noticed a couple of problems with nsmon today when routing to one of
our nameservers went down. I have a config file that looks like this.
DOMAINNAME istar.ca
#
mail 154.11.136.66 AUTH
news 154.11.136.66 AUTH
home 154.11.136.66 AUTH
auth 154.11.136.66 AUTH
and the netconsole and log output ends up looking like this.
Site Address Time +-Variable-+ +-Value-+ Condition
istar.ca 154.11.136.66 15:40 named-status 0 Warning
istar.ca 154.11.136.66 15:40 named-status 0 Warning
istar.ca 154.11.136.66 15:40 named-status 0 Warning
istar.ca 154.11.136.66 15:40 named-status 0 Warning
istar.ca 154.11.136.66 15:40 named-status 0 Warning
Thu Aug 27 13:23:00 1998 [nsmon]: SITE istar.ca 154.11.136.66 VAR named-status 0 0 SOA LEVEL Critical LOGLEVEL Critical NOCOP down
Thu Aug 27 13:23:00 1998 [nsmon]: SITE istar.ca 154.11.136.66 VAR named-status 0 0 SOA LEVEL Critical LOGLEVEL Critical NOCOP down
Thu Aug 27 13:23:00 1998 [nsmon]: SITE istar.ca 154.11.136.66 VAR named-status 0 0 SOA LEVEL Critical LOGLEVEL Critical NOCOP down
Thu Aug 27 13:23:00 1998 [nsmon]: SITE istar.ca 154.11.136.66 VAR named-status 0 0 SOA LEVEL Critical LOGLEVEL Critical NOCOP down
Wouldn't it be more useful if the site was listed as mail.istar.ca,
news.istar.ca, etc?
Also when the site was reachable I don't seem to have got up messages in
the data or log files so the sites stayed flagged in netconsole until I
restarted nsmon.
--
Artificial Intelligence stands no chance against Natural Stupidity.
GAT d- -p+(--) c++++ l++ u++ t- m--- W--- !v
b+++ e* s-/+ n-(?) h++ f+g+ w+++ y*
|