Dear Monit team,
this is a common issue (cloning VMs is an everyday task or maybe you just have a VM template with an installed monit) and I thought about how on could solve this annoying problem.
Maybe one could implement a possibility to renew the id file from M/Monit. And/or one could think about adding an command line option to monit which does the same:
monit renew-id
Maybe this would be a feature to add in the next release?
From: address@hidden [mailto:address@hidden On Behalf Of Martin Pala
Sent: Wednesday, December 04, 2013 12:49 PM
To: This is the general mailing list for monit
Subject: Re: Getting Issue with Cloned machines and "host_monitid_unique" key
the Monit ID is stored in the file (by default ~/.monit.id, you can customize the location using "set idfile" statement)
1.) stop monit on the host with ID duplicate
2.) remove the ID file: rm -f ~/.monit.id
3.) start monit (it will automatically generate new ID and store it to the file)
Hi All,
I am trying to get multiple instances of same machine started up in the VMWare VCenter client (Cloned machines from the template of one using VMWare.
I am able to successfully add server1 and it shows up correctly in the mmonit screen.
I am getting following error messages in mmonit logs when I try to add server2
2013-12-04 05:24:40 SQLException: ERROR: duplicate key value violates unique constraint "host_monitid_unique"
raised in PostgresqlPreparedStatement_execute at src/db/postgresql/PostgresqlPreparedStatement.c:184 when processing URL /collector
It seems that monit is using something from the system which are not different in the cloned machines and so I am getting above errors and the sever2 is not getting added correctly.
My Question is: What does monit use as unique Id ?
Can we manually provide unique ID for monit ? if yes how ?
--
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general
smime.p7s