AnsweredAssumed Answered

Rebooting node with CLDB master on M3 on Ubuntu gives 1 hour delay

Question asked by cleonn on Mar 22, 2013
Latest reply on Mar 27, 2013 by cleonn
Is there a delay of 1 hour on rebooting an Ubuntu CLDB master?

Ran apt-get upgrade on the machine. No hardware changes on the machine, just a regular reboot.

Just to be sure, after 1 hour had passed and I had access to CLDB again, I shut down warden on the CDLB master and rebooted the machine. No changes made to the system at all. And lo and behold, the "unique id" had changed again and I have to wait 1 hour before CLDB can start.

I don't mind this delay, we can live with it. But I haven't been able to find anywhere where it states that a regular reboot of the CLDB master on an M3 installation triggers the 1 hour delay. So I'm curious to if this is by design or a bug.

/opt/mapr/logs/cldb.log.2:2013-03-20 15:01:05,764 INFO LicenseManager [RPC-thread-1]: 0x23: unique id: 00259024700c-49434D53-0200-9024-2500-249025000C70-0001310721-0021495809-0002883585
/opt/mapr/logs/cldb.log:2013-03-22 15:33:43,417 INFO LicenseManager [RPC-thread-9]: 0x23: unique id: 001b21bff0a0-49434D53-0200-9024-2500-249025000C70-0001310721-0021495809-0002883585
/opt/mapr/logs/cldb.log:2013-03-22 16:13:49,565 INFO LicenseManager [RPC-thread-10]: 0x23: unique id: 001b21bff0a1-49434D53-0200-9024-2500-249025000C70-0001310721-0021495809-0002883585


Distributor ID: Ubuntu
Description:    Ubuntu 12.04.2 LTS
Release:        12.04
Codename:       precise

Linux mapr005 3.2.0-39-generic #62-Ubuntu SMP Thu Feb 28 00:28:53 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux