Hello,
We have a openldap 2.3.27 database with 42 GB of total data size . The server is running with 32 bit processor and it crashes once in 2-3 days.. As a work around for now , we are restarting the slapd process using cron job. But the restart takes 45 min to 1 hour time and sometimes more than that. Is there any way to bring up the server fast ? It is taking time to cache data before it start ?
Thanks, Sumith.
On Monday 10 September 2007 23:36:30 Sumith Narayanan wrote:
Hello,
We have a openldap 2.3.27 database with 42 GB of total data size . The server is running with 32 bit processor
Bad idea. How much ram does it have?
and it crashes once in 2-3 days..
Maybe you should try and find out why, rather than using sticky tape ...
As a work around for now , we are restarting the slapd process using cron job. But the restart takes 45 min to 1 hour time and sometimes more than that. Is there any way to bring up the server fast ?
Depends on your configuration, of which you have not supplied *any* details.
It is taking time to cache data before it start ?
No, most likely, you haven't configured a checkpoint on the database, and so database recovery is taking a long time.
For more assistance, provide all the configuration options that relate to the database backend you are using, and any tuning you have done for the library (DB_CONFIG file, or dbconfig directives in slapd.conf).
Regards, Buchan
<quote who="Buchan Milne">
On Monday 10 September 2007 23:36:30 Sumith Narayanan wrote:
Hello,
We have a openldap 2.3.27 database with 42 GB of total data size . The server is running with 32 bit processor
Bad idea. How much ram does it have?
Once fixed, a move to a 64-bit machine would be a good idea for keeping a decent cache.
Gavin.
Sumith Narayanan wrote:
We have a openldap 2.3.27 database with 42 GB of total data size . The server is running with 32 bit processor and it crashes once in 2-3 days.. As a work around for now , we are restarting the slapd process using cron job.
I'd rather search for the cause of the crashes. It definitely helps people on the list to help you if you elaborate on the system/software environment you're running it with.
Maybe an upgrade to latest stable version (2.3.38 as of now) would help either.
Ciao, Michael.
"Sumith Narayanan" sumith.narayanan@gmail.com writes:
Hello,
We have a openldap 2.3.27 database with 42 GB of total data size . The server is running with 32 bit processor and it crashes once in 2-3 days.. As a work around for now , we are restarting the slapd process using cron job. But the restart takes 45 min to 1 hour time and sometimes more than that. Is there any way to bring up the server fast ? It is taking time to cache data before it start ?
what is your memory size? is your configuration appropriate? DB_CONFIG, slapd.conf?
-Dieter
It's almost certain that this configuration is inappropriate. You're unlikely to get a decently tuned cache for a database that size in 32-bit process space.
As for your "crashes," you're likely OOM running into the DN cache issues previously discussed
http://www.openldap.org/lists/openldap-software/200708/msg00106.html
and you may find help with a 64-bit platform, OpenLDAP 2.4, or some combination thereof.
On Tue, 11 Sep 2007, Dieter Kluenter wrote:
"Sumith Narayanan" sumith.narayanan@gmail.com writes:
Hello,
We have a openldap 2.3.27 database with 42 GB of total data size . The server is running with 32 bit processor and it crashes once in 2-3 days.. As a work around for now , we are restarting the slapd process using cron job. But the restart takes 45 min to 1 hour time and sometimes more than that. Is there any way to bring up the server fast ? It is taking time to cache data before it start ?
what is your memory size? is your configuration appropriate? DB_CONFIG, slapd.conf?
-Dieter
-- Dieter Klünter | Systemberatung http://www.dkluenter.de GPG Key ID:8EF7B6C6
--On Tuesday, September 11, 2007 8:59 AM -0400 Aaron Richton richton@nbcs.rutgers.edu wrote:
It's almost certain that this configuration is inappropriate. You're unlikely to get a decently tuned cache for a database that size in 32-bit process space.
As for your "crashes," you're likely OOM running into the DN cache issues previously discussed
http://www.openldap.org/lists/openldap-software/200708/msg00106.html
and you may find help with a 64-bit platform, OpenLDAP 2.4, or some combination thereof.
I think it is a little premature for OpenLDAP 2.4, but definitely go 64-bit, do some tuning, and actually provide useful details. You don't note the OS either, but if it is Linux, you probably want to use something like tcmalloc instead of glibc for memory management as well.
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
openldap-software@openldap.org
-
Aaron Richton -
Buchan Milne -
Dieter Kluenter -
Gavin Henry -
Michael Ströder -
Quanah Gibson-Mount -
Sumith Narayanan