Re: [Savannah-users] SVN commit problems
Andreas Schwab wrote: > Perhaps the reboot happend just when the lock was held, and left some > inconsistent state on the nfs server? Maybe. I can't say that isn't it. But I have seen this problem appear (elsewhere on other systems) even when neither system had been rebooted recently. Bob
Re: [Savannah-users] SVN commit problems
Thanks, Bob! On Thu, Nov 30, 2017 at 4:40 AM, Bob Proulx wrote: > Hi Steve, > >> This time the commit worked. > > Then I am sure this is a problem with the nfs lockd. Rotating the > file out of the way causes the problem to follow the original file and > the new file works fine. I have chased this problem before elsewhere > and am sure that if we were to double blind this by rotating the saved > off file back that the lock problem would return again. This is a bug > that has been around for a while. > > Interestingly enough the system was rebooted very recently for the > lastest security kernel upgrade. Which I just mention because it > isn't a case of the system having been up for ages. It was rebooted > just two days ago. > >> Shall I still experiment with the test project? > > Not necessary now. Since it is working for your project. But if it > had failed there then the test-project would have been a good > comparison. > > I think things will be fine from here forward. But if you encounter > the problem again please let us know and we will work the problem > again. > > Bob
Re: [Savannah-users] SVN commit problems
On Nov 29 2017, Bob Proulx wrote: > Interestingly enough the system was rebooted very recently for the > lastest security kernel upgrade. Which I just mention because it > isn't a case of the system having been up for ages. It was rebooted > just two days ago. Perhaps the reboot happend just when the lock was held, and left some inconsistent state on the nfs server? Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."
Re: [Savannah-users] SVN commit problems
Hi Steve, > This time the commit worked. Then I am sure this is a problem with the nfs lockd. Rotating the file out of the way causes the problem to follow the original file and the new file works fine. I have chased this problem before elsewhere and am sure that if we were to double blind this by rotating the saved off file back that the lock problem would return again. This is a bug that has been around for a while. Interestingly enough the system was rebooted very recently for the lastest security kernel upgrade. Which I just mention because it isn't a case of the system having been up for ages. It was rebooted just two days ago. > Shall I still experiment with the test project? Not necessary now. Since it is working for your project. But if it had failed there then the test-project would have been a good comparison. I think things will be fine from here forward. But if you encounter the problem again please let us know and we will work the problem again. Bob
Re: [Savannah-users] SVN commit problems
Hi, This time the commit worked. Shall I still experiment with the test project? On Thu, Nov 30, 2017 at 1:10 AM, Bob Proulx wrote: > Hi Steve, > > Steve White wrote: >> OK I tried it again. Still not working -- it has hung: >> >> $ svn commit >> Sending... >> Transmitting file data ...done >> Committing transaction... > > And that also shows a process stuck on it on the server side. > > root@vcs0:~# lsof | grep txn-current-lock > svnserve 20468 Stevan_White4u REG 0,24 > 07003445 /net/vcs/srv/svn/freefont/db/txn-current-lock (vcs:/) > >> 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. > > Sometimes the root cause is not immediately clear. I tested to our > test-project and I could commit okay. I have a suspicion and tried > something. Please try it again now. > > (I hate to say before I know but I have seen the nfs lockd get into an > odd state on individual files before. This is tied to the inode and > so tracks the physical file and not the name. Therefore I rotated > that file out of the way and a copy into place. This doesn't > eliminate the problem but side-steps it. If it is one of those times > again then the problem will follow the file and all will appear okay > now. And if not then it is something completely different. Just a > diagnose step.) > >> I'll leave it like this for a while so you can look at it. > > I killed that process on the server side. > >> What else can I look at? > > I added you to the test-project. Please check that out and make some > random change to test-file1.txt or create a new file or whatever and > then commit that back in. Did that work? Do that twice or three > times. Does that work? It's a test project to test svn functionality > on Savannah so please keep it clean but the changes aren't important > otherwise. Any diddle and commit should test the flow. > > svn co svn+ssh://stevan_wh...@svn.savannah.nongnu.org/test-project > > Bob
Re: [Savannah-users] SVN commit problems
Hi Steve, Steve White wrote: > OK I tried it again. Still not working -- it has hung: > > $ svn commit > Sending... > Transmitting file data ...done > Committing transaction... And that also shows a process stuck on it on the server side. root@vcs0:~# lsof | grep txn-current-lock svnserve 20468 Stevan_White4u REG 0,24 0 7003445 /net/vcs/srv/svn/freefont/db/txn-current-lock (vcs:/) > 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. Sometimes the root cause is not immediately clear. I tested to our test-project and I could commit okay. I have a suspicion and tried something. Please try it again now. (I hate to say before I know but I have seen the nfs lockd get into an odd state on individual files before. This is tied to the inode and so tracks the physical file and not the name. Therefore I rotated that file out of the way and a copy into place. This doesn't eliminate the problem but side-steps it. If it is one of those times again then the problem will follow the file and all will appear okay now. And if not then it is something completely different. Just a diagnose step.) > I'll leave it like this for a while so you can look at it. I killed that process on the server side. > What else can I look at? I added you to the test-project. Please check that out and make some random change to test-file1.txt or create a new file or whatever and then commit that back in. Did that work? Do that twice or three times. Does that work? It's a test project to test svn functionality on Savannah so please keep it clean but the changes aren't important otherwise. Any diddle and commit should test the flow. svn co svn+ssh://stevan_wh...@svn.savannah.nongnu.org/test-project Bob
Re: [Savannah-users] SVN commit problems
Hi Bob, OK I tried it again. Still not working -- it has hung: $ svn commit Sending... 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/000:00:01 svn commit swhite 19363 19355 0 00:13 pts/000: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 wrote: > Hello Steve, > > Steve White wrote: >> Hi, since yesterday I've been getting errors on svn commit: >> >> Sending ... >> Transmitting file data ...done >> Committing transaction... >> svn: E37: Commit failed (details follow): >> svn: E37: 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
Re: [Savannah-users] SVN commit problems
Hello Steve, Steve White wrote: > Hi, since yesterday I've been getting errors on svn commit: > > Sending ... > Transmitting file data ...done > Committing transaction... > svn: E37: Commit failed (details follow): > svn: E37: 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
[Savannah-users] SVN commit problems
Hi, since yesterday I've been getting errors on svn commit: Sending ... Transmitting file data ...done Committing transaction... svn: E37: Commit failed (details follow): svn: E37: Can't get exclusive lock on file '/srv/svn/freefont/db/txn-current-lock': No locks available ... It doesn't happen every time, but for some hours now I've been unable to commit anything. This appears to be a server issue. Please have a look at it. Thanks!
