Hi Bob, OK I tried it again. Still not working -- it has hung:
$ svn commit Sending ...<correct list of files> Transmitting file data ...done Committing transaction... And nothing for several minuts. Previously I killed the process and tried again later -- this is when I saw the issue with the lock on the server. I have been committing the same way pretty regularly recently and this thing just started happening yesterday. And I saw it happen on a different system, when I committed something from there. I'll leave it like this for a while so you can look at it. What else can I look at? There's only one SVN process running: $ ps -aef |grep svn swhite 19355 3728 0 00:13 pts/0 00:00:01 svn commit swhite 19363 19355 0 00:13 pts/0 00:00:00 ssh -q -o ControlMaster=no -- stevan_wh...@svn.savannah.gnu.org svnserve -t Thanks! On Wed, Nov 29, 2017 at 10:46 PM, Bob Proulx <b...@proulx.com> wrote: > Hello Steve, > > Steve White wrote: >> Hi, since yesterday I've been getting errors on svn commit: >> >> Sending ... <sends all files> >> Transmitting file data ...done >> Committing transaction... >> svn: E000037: Commit failed (details follow): >> svn: E000037: Can't get exclusive lock on file >> '/srv/svn/freefont/db/txn-current-lock': No locks available >> ... > > There appears to be a process of yours still running attached to that file. > >> It doesn't happen every time, but for some hours now I've been unable >> to commit anything. > > It seems that there are two processes hanging around attached to that > file. I can only guess that some networking glitches between your > client and the server has left some processes unclosed. They should > timeout eventually but the timeout is long to accomodate people > working on slow connections. > >> This appears to be a server issue. Please have a look at it. > > I have killed off the two processes I saw of yours that were attached > to that file. That should release the locks for it and you should be > able to get a new semaphore lock now. But there is nothing that would > prevent this from happening again. If it happened once then it could > happen again. Please let us know if it does and we can deal with it > again then. > > Bob