The problem really seems to be duplicate of the "allow localhost".
I'm not able to reproduce the issue on any of our lab machines and testing configurations. There most probably is redundancy in your "allow" options - when monit adds the hostname to the ACL, it resolves it to the IP address. It seems the your "localhost" hostname may resolve to the same IP address which corresponds to "xx.xx.xx.xx" in your configuration. Please check localhost entry in /etc/hosts and try to resolve it using "host localhost". If the localhost IP address is different from "xx.xx.xx.xx", please check if your configuration file has only one "set httpd" statement ... the duplicate can be caused by second "set httpd" with "allow localhost". If possible, please send your monit configuration file to [email protected] Best regards, Martin > On 02 Jun 2016, at 17:26, me mine <[email protected]> wrote: > > Hello, and thank you for your response. > > The error is as follows: > > @backup jim]# monit status > Skipping redundant host 'localhost' > > > > This is my config for that item: > > set httpd port 2812 and > allow localhost # allow localhost to connect to the server and > allow xx.xx.xx.xx > allow admin:password # require user 'admin' with password 'monit' > > This did work in 5.16, and allow access from both localhost and the m/monit > host. > > > > Jim > > ----- Original Message ----- > From: "Martin Pala" <[email protected]> > To: "This is the general mailing list for monit" <[email protected]> > Sent: Thursday, June 2, 2016 5:51:05 AM > Subject: Re: monit 5.16-5.18 changes > > Hello Jim, > > Monit 5.17 or later expands the $HOST variable into the system hostname only. > The FQDN is used only in sender address for alert delivery. > > The warning about duplicate localhost warning - please can you post the full > error as reported by monit? If the warning is related to the "set httpd" > statement, it should show up only if you have a duplicate "allow" option with > the same host and the template is: > > Skipping redundant host '<hostname>' > > To remove the warning it should be sufficient to just remove the duplicate > allow option - only one will remain and the CLI access will still work. > > Best regards, > Martin > > > >> On 01 Jun 2016, at 22:40, me mine <[email protected]> wrote: >> >> Hello >> >> I updated to 5.18 from 5.16, with no other changes. I noticed that all >> systems with 5.16 were displaying the system name as the FQDN of the >> machine, but after the update to 5.18, only the host portion. >> >> I also started to receive the error on monit load or reload, and status, >> about "duplicate localhost" being ignored. >> >> I have not resolved the FQDN item, but can eliminate the duplicate localhost >> message by removing the allow localhost from my global config section of >> monitrc. However, this then prevents my access fro the CLI. >> >> The only thing I read in the change log for 5.17 and 5.18 was an item change >> related to duplicate "allows" preventing loading(or something to that >> effect), but I was never experiencing that problem. >> >> I was curious if I had missed an item or needed change. >> >> Also, as a m/monit user, I now have to specify a persistent hostname on the >> host config page. >> >> Thank you!! >> >> -jim >> >> >> -- >> To unsubscribe: >> https://lists.nongnu.org/mailman/listinfo/monit-general > > > -- > To unsubscribe: > https://lists.nongnu.org/mailman/listinfo/monit-general > > > > -- > To unsubscribe: > https://lists.nongnu.org/mailman/listinfo/monit-general -- To unsubscribe: https://lists.nongnu.org/mailman/listinfo/monit-general
