Koji regen-repo error

[Mike Bonnet]

On 12/5/13 9:36 AM, Bojtos Péter wrote:
> The problem appeared today again, although I set up in kojira to keep repos for 1 week. The root log's end is this:
>
> DEBUG util.py:314:  Executing command: /usr/bin/repoquery -c /var/lib/mock/dist-slxrv3-build-7179-1529/root//etc/yum.conf -a --qf '%{nevra} %{buildtime} %{size} %{pkgid} %{repoid}' > /var/lib/mock/dist-slxrv3-build-7179-1529/result/available_pkgs with env {'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin'}
> DEBUG util.py:264:  Traceback (most recent call last):
> DEBUG util.py:264:    File "/usr/bin/repoquery", line 1510, in <module>
> DEBUG util.py:264:      main(sys.argv)
> DEBUG util.py:264:    File "/usr/bin/repoquery", line 1504, in main
> DEBUG util.py:264:      repoq.runQuery(regexs)
> DEBUG util.py:264:    File "/usr/bin/repoquery", line 982, in runQuery
> DEBUG util.py:264:      pkgs = self.matchPkgs(items, plain_pkgs=plain_pkgs)
> DEBUG util.py:264:    File "/usr/bin/repoquery", line 903, in matchPkgs
> DEBUG util.py:264:      pkgs = self.returnPkgList(patterns=items)
> DEBUG util.py:264:    File "/usr/bin/repoquery", line 856, in returnPkgList
> DEBUG util.py:264:      pkgs = self.pkgSack.returnNewestByNameArch(**kwargs)
> DEBUG util.py:264:    File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1013, in <lambda>
> DEBUG util.py:264:      pkgSack = property(fget=lambda self: self._getSacks(),
> DEBUG util.py:264:    File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 779, in _getSacks
> DEBUG util.py:264:      self.repos.populateSack(which=repos)
> DEBUG util.py:264:    File "/usr/lib/python2.7/site-packages/yum/repos.py", line 309, in populateSack
> DEBUG util.py:264:      self.doSetup()
> DEBUG util.py:264:    File "/usr/lib/python2.7/site-packages/yum/repos.py", line 134, in doSetup
> DEBUG util.py:264:      self.retrieveAllMD()
> DEBUG util.py:264:    File "/usr/lib/python2.7/site-packages/yum/repos.py", line 92, in retrieveAllMD
> DEBUG util.py:264:      downloading = repo._commonRetrieveDataMD_list(mdtypes)
> DEBUG util.py:264:    File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1540, in _commonRetrieveDataMD_list
> DEBUG util.py:264:      os.rename(local, local + '.old.tmp')
> DEBUG util.py:264:  OSError: [Errno 2] No such file or directory
> DEBUG util.py:354:  Child return code was: 1
> DEBUG util.py:314:  Executing command: ['/bin/umount', '-n', '-l', '/var/lib/mock/dist-slxrv3-build-7179-1529/root/dev/pts'] with env {'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin'}
>
>
> The server is:
> koji-hub-1.8.0-1.el6.noarch
>
> The builder version is:
> koji-builder-1.8.0-1.fc17.noarch

This looks like a problem with mock or repoquery.  What version of those 
do you have installed on your builder?

> Any suggestion, where to start to debug?
>
> Thank you,
> Peter
>
>
> ----- Eredeti üzenet -----
>> Feladó: "Didier Fabert" <didier.fabert at gmail.com>
>> Címzett: "Discussion of Fedora build system" <buildsys at lists.fedoraproject.org>
>> Elküldött üzenetek: Kedd, 2013. November 19. 10:28:19
>> Tárgy: Re: Koji regen-repo error
>>
>> On Friday 15 November 2013 09:04:11 Mike Bonnet wrote:
>>> On 11/15/13 5:48 AM, Didier Fabert wrote:
>>>> Hi all,
>>>>
>>>> I have strange error since last week on my koji. All regen-repo tasks are
>>>> failed with error LockError: [Errno 37] No locks available
>>>>
>>>> Koji works perfectly since January month. Directory /mnt/koji is a nfs
>>>> mount but i can touch a new file on it. Database is ok too.
>>>>
>>>> I have two builders, and error appear on both.
>>>>
>>>> Any idea ?
>>>>
>>>
>>> koji.LockError is only raised in two places, both around fnctl.lockf():
>>>
>>> http://docs.python.org/release/2.6.8/library/fcntl.html#fcntl.lockf
>>>
>>> The fcntl manpage says:
>>>
>>> ENOLCK Too many segment locks open, lock table is full, or a remote
>>> locking protocol failed (e.g., locking over NFS).
>>>
>>> Are you mounting /mnt/koji over nfs?  Maybe the nfslock service died?
>>> Is something else holding a lot of locks?
>>
>> Yes, you're right, nfslock was dead on NFS server (el5)
>> After restarting nfslock service on my NFS server, all is OK.
>>
>> Thanks a lot Mike to pointing me to the right direction.
>>
>> --
>> Didier
>> --
>> buildsys mailing list
>> buildsys at lists.fedoraproject.org
>> https://admin.fedoraproject.org/mailman/listinfo/buildsys
> --
> buildsys mailing list
> buildsys at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/buildsys
>