Hi,
I am running openldap servers 2.4.40 with bdb on CentOS 6, it creates 10 MB log file in every 2 - 3 minutes, no surprisingly, it fills up the disk quickly.
To fix the issue, I added following statement to DB_CONFIG, restarted splapd, but it does not seem work, the log files are still glowing and creating. Could anyone help please why the DB_LOG_AUTOREMOVE is unable to stop log files? Sorry for posting it to different lists as we are not be able to run the ldap server when it fills up the disk so quickly.
set_flags DB_LOG_AUTOREMOVE
Thanks for your helps.
Kind regards,
--On Friday, March 04, 2016 11:49 AM +1100 jupiter jupiter.hce@gmail.com wrote:
Hi,
I am running openldap servers 2.4.40 with bdb on CentOS 6
1) Do not use the broken build from RHEL. See the LTB project or the Symas builds, as noted on this list numerous times for current OpenLDAP builds.
2) Switch to back-mdb instead of back-bdb or back-hdb
As to your issue, did you set a checkpoint?
--Quanah
--
Quanah Gibson-Mount Platform Architect Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration A division of Synacor, Inc
Hi,
I am running openldap servers 2.4.40 with bdb on CentOS 6
- Do not use the broken build from RHEL. See the LTB project or the
Symas builds, as noted on this list numerous times for current OpenLDAP builds.
I'm running openldap-2.4.40-6.el6_7.x86_64 on Scientific Linux 6.7. Autoremove works as expected. As Quanah asked: did you define a checkpoint?
Regards, Dirk
Thanks Dirk and Quanah for the response, sorry did not know it needs to define a checkpoint, could you please elaborate it how to define it?
Thank you very much and appreciate it.
Kind regards,
- j
On Fri, Mar 4, 2016 at 6:42 PM, Dirk Kastens <dirk.kastens@uni-osnabrueck.de
wrote:
Hi,
I am running openldap servers 2.4.40 with bdb on CentOS 6
- Do not use the broken build from RHEL. See the LTB project or the
Symas builds, as noted on this list numerous times for current OpenLDAP builds.
I'm running openldap-2.4.40-6.el6_7.x86_64 on Scientific Linux 6.7. Autoremove works as expected. As Quanah asked: did you define a checkpoint?
Regards, Dirk
Hi Dirk,
I am running the same package version openldap-2.4.40-6.el6_7.x86_64 as you do. I've double checked the /etc/openldap/slapd.d//olcDatabase={2}bdb.ldif, the olcDbCheckpoint: 1024 15 has already been defined in that file, and I did restarted slapd, but the log files are still glowing. What else I could still be missing?
Thanks.
- j
On Sun, Mar 6, 2016 at 7:15 PM, jupiter jupiter.hce@gmail.com wrote:
Thanks Dirk and Quanah for the response, sorry did not know it needs to define a checkpoint, could you please elaborate it how to define it?
Thank you very much and appreciate it.
Kind regards,
- j
On Fri, Mar 4, 2016 at 6:42 PM, Dirk Kastens < dirk.kastens@uni-osnabrueck.de> wrote:
Hi,
I am running openldap servers 2.4.40 with bdb on CentOS 6
- Do not use the broken build from RHEL. See the LTB project or the
Symas builds, as noted on this list numerous times for current OpenLDAP builds.
I'm running openldap-2.4.40-6.el6_7.x86_64 on Scientific Linux 6.7. Autoremove works as expected. As Quanah asked: did you define a checkpoint?
Regards, Dirk
Hi,
I am running the same package version openldap-2.4.40-6.el6_7.x86_64 as you do. I've double checked the /etc/openldap/slapd.d//olcDatabase={2}bdb.ldif, the olcDbCheckpoint: 1024 15 has already been defined in that file, and I did restarted slapd, but the log files are still glowing. What else I could still be missing?
How big is your db? I've set the logsize to 100 MB and only the last two files are kept. Install the db4-utils and run the command db_archive. This will show you the logfiles that are no longer used. "db_archive -d" will delete the unused logfiles. But this should be done by slapd automatically.
Dirk
Hi Dirk,
On Mon, Mar 7, 2016 at 6:44 PM, Dirk Kastens <dirk.kastens@uni-osnabrueck.de
wrote:
Hi,
I am running the same package version openldap-2.4.40-6.el6_7.x86_64 as
you do. I've double checked the /etc/openldap/slapd.d//olcDatabase={2}bdb.ldif, the olcDbCheckpoint: 1024 15 has already been defined in that file, and I did restarted slapd, but the log files are still glowing. What else I could still be missing?
How big is your db? I've set the logsize to 100 MB and only the last two files are kept. Install the db4-utils and run the command db_archive. This will show you the logfiles that are no longer used. "db_archive -d" will delete the unused logfiles. But this should be done by slapd automatically.
The logsize is set to 10 MB, it creates a 10 MB log file every 2 - 3 minutes (it grows so fast, like the movie "Evolution" :-)), I ran the db_archive -d 10 hours ago when the disk was full, and I have run the db_archive -d now as the disk is full again despite the server is not too busy. Why doesn't the slapd do it automatically? Apart that issue, the ldap is running very well. I really want to figure out what is going on, but if I cannot find a solution, I have no choice but run a cron job to call db_archive -d every 8 hours. I guess that should not cause ldap any side effect, right?
Thank you very much.
Dirk
--On Monday, March 07, 2016 9:35 PM +1100 jupiter jupiter.hce@gmail.com wrote:
The logsize is set to 10 MB, it creates a 10 MB log file every 2 - 3 minutes (it grows so fast, like the movie "Evolution" :-)), I ran the db_archive -d 10 hours ago when the disk was full, and I have run the db_archive -d now as the disk is full again despite the server is not too busy. Why doesn't the slapd do it automatically? Apart that issue, the ldap is running very well. I really want to figure out what is going on, but if I cannot find a solution, I have no choice but run a cron job to call db_archive -d every 8 hours. I guess that should not cause ldap any side effect, right?
The real solution, again, is to dump the broken RH build and switch to MDB. Then there will no longer be any pointless log files created, and your system will be both more secure and faster (and take a smaller footprint).
--Quanah
--
Quanah Gibson-Mount Platform Architect Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration A division of Synacor, Inc
openldap-technical@openldap.org
-
Dirk Kastens -
jupiter -
Quanah Gibson-Mount