The db.log files are not dated, the entries could have been from a long time ago, such as the fork caused by pre-0.8 clients choking on a big block. Delete.
The log file is for Berkeley databases, which is only the wallet and peers database files now. Humongous wallet?
You can add a config option to increase some of the database parameters (https://bitcointalksearch.org/topic/m.1615346), but it is better for all for you to clear the logs and see if this ever occurs again, and if devs can reproduce or fix it with information about your client or files.
Topic: db.log full of Lock table is out of available lock entries (Read 1106 times)
Running on 32bit debian, 0.8.5 reports a db.log full of "Lock table is out of available lock entries". Doesn't seem to be affecting bitcoind nor block processing.
Anything to poke at?
Anything to poke at?
Jump to: