Hi Mike,
After troubleshooting the issue for a bit, we were able to get the Koji setup working, and
can now generate the build root repositories and build packages. The main issue was that
the builders needed to use /tmp/koji as the ‘workdir’ which then removed any of the
strange permissions errors that would occur when the builder would attempt to process the
task. I had originally had this set to the shared volume for the Kojira/Koji-hub server on
/mnt/koji, which was not working as expected.
Thanks for your assistance in tracing it down,
Kirk Harr
Systems and Network Engineer
End Point Corporation
On Mar 27, 2015, at 2:33 PM, Mike McLean <mikem(a)redhat.com>
wrote:
On 02/26/2015 05:49 PM, Kirk Harr wrote:
> Hi Mike,
>
> I added those logging lines to the kojid python and then when attempting a repository
refresh the output that is caught in the log is:
> <snip>
> 2015-02-26 17:44:14,886 [WARNING] koji.TaskManager: TRACEBACK: Traceback (most recent
call last):
> File "/usr/lib/python2.6/site-packages/koji/daemon.py", line 1161, in
runTask
> response = (handler.run(),)
> File "/usr/lib/python2.6/site-packages/koji/tasks.py", line 157, in run
> return koji.util.call_with_argcheck(self.handler, self.params, self.opts)
> File "/usr/lib/python2.6/site-packages/koji/util.py", line 139, in
call_with_argcheck
> return func(*args, **kwargs)
> File "/usr/sbin/kojid", line 3408, in handler
> self.logger.warn("Stat says: %r", os.lstat(path))
> OSError: [Errno 61] No data available: '/mnt/koji/repos/dist-centos6-build/1127’
> </snip>
> Its appears the lstat test on the path is returning this error, but I am not familiar
with OSError 61. I was able to run ls on the directory referenced, so it definitely exists
but I am starting to believe there is something else preventing the file read from that
location. Any idea what could cause an error of this type?
selinux maybe?
Did you trying inserting a long sleep after the repoInit call?
I think you said that the directory was there (presumably on the builder's mount)
when you looked for it after the fact. So either
1) there is some race issue where the builder does not see the fs update in time
2) somehow the kojid process does not have access to read it (even if your root shell
does)
Maybe try running 'watch ls -l /mnt/koji/repos/dist-centos6-build/' in a root
shell on the builder while you replicate the problem (to see if you can observe a lag.
> Thanks again for your help in tracing down the cause of this problem.
>
> Kirk Harr
> Systems and Network Engineer
> End Point Corporation
>
>
>> On Feb 19, 2015, at 4:19 PM, Mike McLean <mikem(a)redhat.com> wrote:
>>
>> self.logger.warn("Got repo: %r", path)
>> self.logger.warn("Stat says: %r", os.lstat(path))
>
> --
> buildsys mailing list
> buildsys(a)lists.fedoraproject.org
>
https://admin.fedoraproject.org/mailman/listinfo/buildsys
>
--
buildsys mailing list
buildsys(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys