[Date Prev][Date Next]
Re: slapcat unable to make ldif file with size > 2GB
- To: mukim pathan <email@example.com>, openldap-technical <firstname.lastname@example.org>
- Subject: Re: slapcat unable to make ldif file with size > 2GB
- From: "Brett @Google" <email@example.com>
- Date: Sun, 7 Jun 2009 11:51:59 +1000
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=KS+pRneyuQrz6cAqckqoNtHeFRPvEoaB9GpajEQdkGQ=; b=Bs9p2bIOpSCnElcLkma4II4i4R+XwEaCQbuxCgowmzGrsJYEVvIMLMyIdQwVhKnA4b KcGTKb/QcS2Dj2Pafd7fJ3p3vJQOcxhUxu6LZAxgIEZ2jDuX5EgthvpXFzeauJZ21Yky TF2jj2tmLBI58jItbWZjQoaADVXquDfN+hfeo=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=DlsH+tlwjVFpSMKRx5uTqbPFLgerCaSAb5qpz8nMr4Q4rJHM04gfRYnkr+wH5GUO/D 95bLrzDPJbkwrw9qLxZQXizyz6mHF0jf/ds7C908biVfF1nqElmxuzv2EvhQZnmYh32C uauWkrxJpA1KLC8VhTde6wiYonTu56KarX6uU=
- In-reply-to: <firstname.lastname@example.org>
- References: <email@example.com>
This might happen on a 32 bit kernel, or perhaps you are using 32 bit BDB libraries..
If this is the case, you will need to upgrade your OS or recompile openldap against 64 bit libraries. i'd setup a test system, and validate which of the above is true.
i think on Linux it would be a kernel/policy issue, on solaris it would be a linking issue, as by default both the openldap and BDB configure only picks up 32 bit libraries, solaris ships both 32 and 64 bit libraries, but he 64 bit libraries are in /usr/lib/sparcv9 (not the default location).
there is some chance that it's a policy restriction also, check "ulimit -a" for max file size.
On Fri, Jun 5, 2009 at 11:46 PM, mukim pathan <firstname.lastname@example.org>
I am trying to create backup of database using slapcat. But as soon as .ldif file reaches size of 2GB, it is giving me an error of File Size Limit Exceeded and quitting the process.
I am using bdb 2.3.43. Is there anything I can do about it?