Re: Getting Issue with Cloned machines and "host_monitid_unique" key

[Mital Vora]

Hello Martin,

Thank you for the detailed instructions .. I am able to see the new machines in mmonit correctly.

Also instructions by  address@hidden also looks promising.

Run the following before you clone the vm.
service monit stop
rm -f /var/lib/monit/id
rm -f /var/lib/monit/state

I will give it a try .. thanks guys.

Regards,

Mital Vora.

On Wed, Dec 4, 2013 at 5:19 PM, Martin Pala <address@hidden> wrote:

Hi,

the Monit ID is stored in the file (by default ~/.monit.id, you can customize the location using "set idfile" statement)

To generate new ID:

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)

Regards,

Martin

On 04 Dec 2013, at 12:44, Mital Vora <address@hidden> wrote:

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 ?

Regards,

Mital Vora.

--
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general

--
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general