- clo-devel - mailman3.common-lisp.net

Re: [clo-devel] Commit fail on USOCKET SVN
by Hans Hübner 11 May '11

11 May '11

problem fixed. On Wednesday, May 11, 2011, Chun Tian (binghe) <binghe.lisp(a)gmail.com> wrote: > Hi, Hans > > Still cannot commit. But I tried my other project's SVN on cl.net, i.e. cl-net-snmp, svn commit is OK. So I guess this maybe a usocket specific issue. Now I've done a full dump of usocket svn data, and try to rebuild it into a new repository directory. > > But I need some root help, the first is following command: > > chmod g+w /project/usocket > > This let me (ctian, member of usocket group) could modify project root directory to create any new top-level directory. > > Regards, > > Chun Tian (binghe) > > 在 2011-5-11，13:47， Hans Hübner 写道： > >> Drew fixed the box and I manually mounted the nfs file systems. >> Please try again! >> >> -Hans >> >> 2011/5/11 Hans Hübner <hans.huebner(a)gmail.com>: >>> Oh well, I rebooted the box, but it fails to come up again. Drew will >>> have to take care of this. Sorry. >>> >>> -Hans >>> >>> 2011/5/11 Chun Tian (binghe) <binghe.lisp(a)gmail.com>: >>>> Hi, Hans >>>> >>>> Thanks for taking care this, but I'm afraid that the problem is still there. Below is what I did in past minutes: >>>> >>>> """ >>>> binghe@binghe-i7:~/Lisp/usocket/branches/0.5.x/test$ LANG=C svn ci -m "[test] Issue elliott-slaughter.2 (WAIT-FOR-INPUT/win32 on TCP socket)" >>>> Sending test/wait-for-input.lisp >>>> Transmitting file data .svn: Commit failed (details follow): >>>> svn: Can't get exclusive lock on file '/project/usocket/svn/db/write-lock': No locks available >>>> """ >>>> >>>> As a Linux administrator, I think the theory behind your NFS fix is good, but to make the configuration change actually applied to current system, you have to completely unmount the NFS volumes on common-lisp.net, and do a full restart of NFS related services and then mount them again. Or, A simply reboot of common-lisp.net (I'm not sure if it's virtual machine) could achieve the goal easily. But any of the two choices would cause services temporary shutdown. >>>> >>>> Regards, >>>> >>>> Chun Tian (binghe) >>>> >>>> 在 2011-5-11，12:38， Hans Hübner 写道： >>>> >>>>> Hi Binghe, >>>>> >>>>> thank you for reporting the problem. I have made a change in the NFS >>>>> configuration (http://gibbonsr.net/2009/02/nfs-and-subversion-it-can-work/) >>>>> so that Subversion should now work. Can you please give it a try and >>>>> let me know if it is okay? >>>>> >>>>> common-lisp.net is currently being migrated to a new "box", which is >>>>> why there may be some issues in the coming days and week. Please >>>>> don't hesitate to report them. >>>>> >>>>> Thanks, >>>>> Hans >>>>> >>>>> 2011/5/11 Chun Tian <binghe.lisp(a)gmail.com>: >>>>>> Hi, Hans >>>>>> >>>>>> Are you still an administrator of common-lisp.net? Recently I cannot commit to USOCKET SVN any more, my SVN client said: >>>>>> >>>>>>> "Commit failed: Can't get exclusive lock on file '/project/usocket/svn/db/write-lock': No locks available" >>>>>> >>>>>> I think this may be caused by NFS on common-lisp.net, please help me confirm if any other developer met the same issue. >>>>>> >>>>>> Thanks, >>>>>> >>>>>> Chun Tian (binghe) >>>>>> >>>>>> 下面是被转发的邮件： >>>>>> >>>>>>> 发件人: "Chun Tian (binghe)" <binghe.lisp(a)gmail.com> >>>>>>> 日期: 2011年5月10日 23时52分42秒+0800 >>>>>>> 收件人: Erik Huelsmann <ehuels(a)gmail.com> >>>>>>> 主题: Commit fail on USOCKET SVN >>>>>>> >>>>>>> Hi, Erik >>>>>>> >>>>>>> I think USOCKET SVN have something wrong, because I cannot commit new code to it, the error message is: >>>>>>> >>>>>>> "Commit failed: Can't get exclusive lock on file '/project/usocket/svn/db/write-lock': No locks available" >>>>>>> >>>>>>> I

1 0

Re: [clo-devel] Commit fail on USOCKET SVN
by Hans Hübner 11 May '11

11 May '11

Drew fixed the box and I manually mounted the nfs file systems. Please try again! -Hans 2011/5/11 Hans Hübner <hans.huebner(a)gmail.com>: > Oh well, I rebooted the box, but it fails to come up again. Drew will > have to take care of this. Sorry. > > -Hans > > 2011/5/11 Chun Tian (binghe) <binghe.lisp(a)gmail.com>: >> Hi, Hans >> >> Thanks for taking care this, but I'm afraid that the problem is still there. Below is what I did in past minutes: >> >> """ >> binghe@binghe-i7:~/Lisp/usocket/branches/0.5.x/test$ LANG=C svn ci -m "[test] Issue elliott-slaughter.2 (WAIT-FOR-INPUT/win32 on TCP socket)" >> Sending test/wait-for-input.lisp >> Transmitting file data .svn: Commit failed (details follow): >> svn: Can't get exclusive lock on file '/project/usocket/svn/db/write-lock': No locks available >> """ >> >> As a Linux administrator, I think the theory behind your NFS fix is good, but to make the configuration change actually applied to current system, you have to completely unmount the NFS volumes on common-lisp.net, and do a full restart of NFS related services and then mount them again. Or, A simply reboot of common-lisp.net (I'm not sure if it's virtual machine) could achieve the goal easily. But any of the two choices would cause services temporary shutdown. >> >> Regards, >> >> Chun Tian (binghe) >> >> 在 2011-5-11，12:38， Hans Hübner 写道： >> >>> Hi Binghe, >>> >>> thank you for reporting the problem. I have made a change in the NFS >>> configuration (http://gibbonsr.net/2009/02/nfs-and-subversion-it-can-work/) >>> so that Subversion should now work. Can you please give it a try and >>> let me know if it is okay? >>> >>> common-lisp.net is currently being migrated to a new "box", which is >>> why there may be some issues in the coming days and week. Please >>> don't hesitate to report them. >>> >>> Thanks, >>> Hans >>> >>> 2011/5/11 Chun Tian <binghe.lisp(a)gmail.com>: >>>> Hi, Hans >>>> >>>> Are you still an administrator of common-lisp.net? Recently I cannot commit to USOCKET SVN any more, my SVN client said: >>>> >>>>> "Commit failed: Can't get exclusive lock on file '/project/usocket/svn/db/write-lock': No locks available" >>>> >>>> I think this may be caused by NFS on common-lisp.net, please help me confirm if any other developer met the same issue. >>>> >>>> Thanks, >>>> >>>> Chun Tian (binghe) >>>> >>>> 下面是被转发的邮件： >>>> >>>>> 发件人: "Chun Tian (binghe)" <binghe.lisp(a)gmail.com> >>>>> 日期: 2011年5月10日 23时52分42秒+0800 >>>>> 收件人: Erik Huelsmann <ehuels(a)gmail.com> >>>>> 主题: Commit fail on USOCKET SVN >>>>> >>>>> Hi, Erik >>>>> >>>>> I think USOCKET SVN have something wrong, because I cannot commit new code to it, the error message is: >>>>> >>>>> "Commit failed: Can't get exclusive lock on file '/project/usocket/svn/db/write-lock': No locks available" >>>>> >>>>> I searched on Internet [1], but all possible reasons (file system permission, disk full, svnadmin recover) have been checked, nothing found and I still cannot commit. It's a shame to me because I'm a SVN administrator in my working company ... >>>>> >>>>> Please confirm if you can commit anything to USOCKET SVN, or just help me solve this. >>>>> >>>>> Regards, >>>>> >>>>> Chun Tian (binghe) >>>>> >>>>> [1] http://www.opensubscriber.com/message/users@subversion.tigris.org/7277559.h… >>>>> >>>>> >>>> >>>> >> >> >

1 0

Re: [clo-devel] Commit fail on USOCKET SVN
by Hans Hübner 11 May '11

11 May '11

Hi Binghe, thank you for reporting the problem. I have made a change in the NFS configuration (http://gibbonsr.net/2009/02/nfs-and-subversion-it-can-work/) so that Subversion should now work. Can you please give it a try and let me know if it is okay? common-lisp.net is currently being migrated to a new "box", which is why there may be some issues in the coming days and week. Please don't hesitate to report them. Thanks, Hans 2011/5/11 Chun Tian <binghe.lisp(a)gmail.com>: > Hi, Hans > > Are you still an administrator of common-lisp.net? Recently I cannot commit to USOCKET SVN any more, my SVN client said: > >> "Commit failed: Can't get exclusive lock on file '/project/usocket/svn/db/write-lock': No locks available" > > I think this may be caused by NFS on common-lisp.net, please help me confirm if any other developer met the same issue. > > Thanks, > > Chun Tian (binghe) > > 下面是被转发的邮件： > >> 发件人: "Chun Tian (binghe)" <binghe.lisp(a)gmail.com> >> 日期: 2011年5月10日 23时52分42秒+0800 >> 收件人: Erik Huelsmann <ehuels(a)gmail.com> >> 主题: Commit fail on USOCKET SVN >> >> Hi, Erik >> >> I think USOCKET SVN have something wrong, because I cannot commit new code to it, the error message is: >> >> "Commit failed: Can't get exclusive lock on file '/project/usocket/svn/db/write-lock': No locks available" >> >> I searched on Internet [1], but all possible reasons (file system permission, disk full, svnadmin recover) have been checked, nothing found and I still cannot commit. It's a shame to me because I'm a SVN administrator in my working company ... >> >> Please confirm if you can commit anything to USOCKET SVN, or just help me solve this. >> >> Regards, >> >> Chun Tian (binghe) >> >> [1] http://www.opensubscriber.com/message/users@subversion.tigris.org/7277559.h… >> >> > >

1 0

[clo-devel] Managing (version controlling) the common-lisp.net main website
by Erik Huelsmann 08 May '11

08 May '11

The clo project contains a copy of the c-l.net website in its repository. This repository is checked out in the public_html directory of the clo project and synced hourly from there to the main web pages in /var/www. However, if I look at the /var/www directory, it contains much more than what's in the clo directory and repository. To resolve this situation, I'd like to copy all files in /var/www to the clo project and add them to the repository. There were ideas from others - I believe Raymond and Stelian - to use a different solution to maintain the website; maybe using a CMS or wiki-based system which allows WYSIWYG editing on the web. For now, I'm going with my "copy back" solution. However, it looks to me like we do need *some* kind of enhanced control. (Maybe even just a description of location of different kinds of files for maintainers to consult?) Bye, Erik.

1 0

[clo-devel] cvsroot syncing regularly takes too long
by Erik Huelsmann 08 May '11

08 May '11

Hi, On new-cl-net, the "sync cvsroot" script is regularly exceeding its runtime window (which is 20 minutes). One solution could be to change the nice parameter (-20). I'm hoping that others have better ideas, like changing the script from polling to event-based, which would eliminate the need to check all files individually. Does anybody have some cycles to look into the options? Bye, Erik.

2 2

[clo-devel] Security update required for exim4
by Hans Hübner 07 May '11

07 May '11

Drew, it seems that the Debian distribution that is installed on tiger does not supply a very current version of exim4, and today a security hole was reported in the version that we are running. Is it possible to add a package source with up to date security fixes so that we can update exim4? Thanks, Hans

1 0

Re: [clo-devel] link to OTRS docs for mail processing
by Hans Hübner 07 May '11

07 May '11

Hi Erik, I have installed the otrs gateway at otrs(a)tiger.common-lisp.net - As otrs runs under a specific user ID and I did not feel like inventing a suid wrapper, I have implemented the gateway by an explicit exim configuration directive (see /etc/exim4/configure if you are interested). I sent a few test mails to that address, but otrs did not reply to them, and I don't have an account in otrs yet. Can you add that for me, please? Thanks! Hans On Sat, May 7, 2011 at 2:33 PM, Erik Huelsmann <ehuels(a)gmail.com> wrote: > Hi Hans, > > This link discusses it: http://doc.otrs.org/3.0/en/html/x2048.html > > Basically, you need to pipe the mail into 'bin/PostMaster.pl' (which > is in /usr/share/otrs :-l ) > > The docs are for OTRS 3.0 while we still run 2.4, but there are few > changes in this area. > > Bye, > > Erik. >

1 0

[clo-devel] Testing exim4+mailman+sa+greylistd setup on tiger.common-lisp.net
by Hans Hübner 07 May '11

07 May '11

When you're reading this, things should be in working order. -Hans

1 0

[clo-devel] testing mailman+exim
by root 07 May '11

07 May '11

nothing else

1 0

[clo-devel] Migration status 2011-04-26
by Erik Huelsmann 27 Apr '11

27 Apr '11

Although last week's attempt to run cl-net off a network FS failed, this weekend a renewed attempt succeeded. This means we'll have completely current data on both old and new cl.net. This provides a solid basis to start migrating different services to the new machine. One of the things currently being moved is the ssh authenticated access. Other services to migrate soon are: * trac.common-lisp.net * paste.lisp.org / the bots * www.common-lisp.net / the webserver setup (with proxies and all) * the cron jobs * MTA/mailing lists * others Stelian and I are working through the steps and issues slowly on #tech.coop; if you want to discuss with us or want to know about progress or help out, come to the channel, hang around and join our efforts. Bye, Erik.

3 2