--On Monday, June 23, 2008 11:04:36 AM -0700 Howard Chu hyc@symas.com wrote:
Bill MacAllister wrote:
Howard,
We just upgraded to 2.3.42 and are seeing the problem again in our production environment. I have attached a backtrace and db_stat output. This output if from the busy server. I will disconnect the network next and see what happens.
The db_stat output seems to indicate that entries that are being fetched for read access are not getting unlocked. This behavior is new since 2.3.4x for you? What's the last release version where this does not occur?
The last version that we ran in production that did not exhibit this behavior was 2.3.25. We have tried both 2.3.41 and 2.3.42 and seen the problem. We backed out of 2.3.41 when we hit the problem.
Bill
+-------------------------------------------------------- | Bill MacAllister whm@stanford.edu | Systems Software Programmer, ITS Unix Systems, Stanford University