|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #13630 GDBM writes frequently fail during heavy traffic.
Submitted: 2001-10-10 15:56 UTC Modified: 2002-05-25 09:03 UTC
Avg. Score:3.5 ± 0.5
Reproduced:2 of 2 (100.0%)
Same Version:1 (50.0%)
Same OS:0 (0.0%)
From: cabel at panic dot com Assigned:
Status: Not a bug Package: DBM/DBA related
PHP Version: 4.0.6 OS: RedHat 7.1
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
Solve the problem:
42 - 40 = ?
Subscribe to this entry?

 [2001-10-10 15:56 UTC] cabel at panic dot com
We're using GDBM version 1.8.0, as of May 19, 1999. We have 
a fairly active web site whichs pulls content from a GDBM 

Usually this access is read-only. Occasionally -- to update 
a counter or information -- we need to open these databases 
with write access.

A sample line to do this:

  $dbm = dbmopen("facedb", "w");

Usually, this is never a problem. However, during heavy 
load -- when more people than usual are updating data or 
counters and thus needing to write to this database -- the 
dbmopen() call fails with the following error:

"Warning: dbmopen_gdbm(itemsdb): 10 [Can't be writer], 11 
[Resource temporarily unavailable] in db.php on line 5"

The PHP documentation page for dbmopen() states: "Note that 
PHP does its own file locking in addition to any file 
locking that may be done by the DBM library itself."

Is this true? If so, why would we be encountering this bug?

I guess the first question, which I might not be qualified 
to answer: is this a GDBM problem, or a PHP problem?

Would switching to another database style help? Can we trap 
this error and try again?

Enough question. That's my bug report.



Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2002-04-03 08:22 UTC] ege at my-lan dot de
OS: Tru64 4.0F
apache 1.3.19
gdbm 1.8.0

i can't use gdbm, because the read only access
failed, if more the one process read from the
same database
 [2002-05-25 09:03 UTC]
Thank you for taking the time to report a problem with PHP.
Unfortunately your version of PHP is too old -- the problem
might already be fixed. Please download a new PHP
version from

If you are able to reproduce the bug with one of the latest
versions of PHP, please change the PHP version on this bug report
to the version you tested and change the status back to "Open".
Again, thank you for your continued support of PHP.

Also try upgrading GDBM...
PHP Copyright © 2001-2023 The PHP Group
All rights reserved.
Last updated: Mon Dec 04 10:01:26 2023 UTC