Skip to Main Content

Berkeley DB Family

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Mutex leak in db_verify

jstanekOct 23 2015 — edited Nov 12 2015

== Description of problem:

Accoding to db_stat command, it seems that mutex leak occurs when db_verify command is executed.

# db_stat -h . -x

1174 Mutex free count <---

# db_verify -h . `ls *.bdb`

# db_stat -h . -x

1138 Mutex free count <---

In our customer, slapcat command failed after executing db_verify command many times with the following message because of this issue.

---

bdb(dc=ldap,dc=xxxxx,dc=or,dc=jp): unable to allocate memory for mutex; resize mutex region

---

== Version-Release number of selected component (if applicable):

Red Hat Enterprise Linux Version Number: RHEL6

Release Number: 6.5

Architecture: x86_64

Kernel Version: 2.6.32-431.el6

Related Package Version: db4-4.7.25-18.el6_4

Related Middleware / Application: none.

== How reproducible:

Always

== Steps to Reproduce:

1. Stop slapd service.

# service slapd stop

2. Execute db_stat command.

# db_stat -h . -x

Confirm "Mutex free count".

3. Execute db_verify command.

# db_verify -h . `ls *.bdb`

4. Execute db_stat command.

# db_stat -h . -x

Confirm "Mutex free count".

== Actual results:

mutex leak occurs.

== Expected results:

mutex leak does not occur.

== Additional info:

Hardware configuration:

Model/Hypervisor: VMware ESXi 5.5 update 2

CPU Info: Intel(R) Xeon(R) CPU E5-2695 v2 @ 2.40GHz

Memory Info: 16336016 kB

Original bug report

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Dec 10 2015
Added on Oct 23 2015
18 comments
4,012 views