[389-users] read_state: failed to get generator's state

[Jim Tyrrell]

Hi,

I have a setup with 3 389 Directory servers in a master-master setup 
which has been working fine until now.  One of the servers died this 
morning due to a memory issue and now will not restart:


[18/May/2011:12:34:32 +0100] memory allocator - malloc of 1538 bytes 
failed; OS error 12 (Cannot allocate memory)
The server has probably allocated all available virtual memory. To solve
this problem, make more virtual memory available to your server, or reduce
one or more of the following server configuration settings:
   nsslapd-cachesize        (Database Settings - Maximum entries in cache)
   nsslapd-cachememsize     (Database Settings - Memory available for cache)
   nsslapd-dbcachesize      (LDBM Plug-in Settings - Maximum cache size)
   nsslapd-import-cachesize (LDBM Plug-in Settings - Import cache size).
Can't recover; calling exit(1).


I'm not unable to restart the server, the error log reports the following:

[18/May/2011:12:58:38 +0100] - 389-Directory/1.2.2 B2009.237.206 starting up
[18/May/2011:12:58:38 +0100] uuid - read_state: failed to get 
generator's state
[18/May/2011:12:58:38 +0100] uuid - uuid_init: failed to get generator's 
state
[18/May/2011:12:58:38 +0100] uniqueid generator - uniqueIDGenInit: 
generator initialization failed
[18/May/2011:12:58:38 +0100] - Fatal Error---Failed to initialize 
uniqueid generator; error = 13. Exiting now.
         389-Directory/1.2.2 B2009.237.206


Any ideas what the issue is and how to fix?  Where is it trying to get 
the generators state from?

Thanks.

Jim.