new koji-web error
by Michael Cronenworth
I have a koji instance running on Fedora 14 that has been running great.
Last week I ran about 150 updates and now when I click on any new log
file to view it I get this message:
An error has occurred while processing your request.
Fault: <Fault 1: "<type 'exceptions.OverflowError'>: int exceeds XML-RPC
limits">
Traceback (most recent call last):
File "/usr/share/koji-web/lib/kojiweb/publisher.py", line 16, in publish_object
return old_publish_object(req, object)
File "/usr/lib64/python2.7/site-packages/mod_python/publisher.py", line 425, in publish_object
return publish_object(req,util.apply_fs_data(object, req.form, req=req))
File "/usr/lib64/python2.7/site-packages/mod_python/util.py", line 554, in apply_fs_data
return object(**args)
File "/usr/share/koji-web/scripts/index.py", line 668, in getfile
output = server.listTaskOutput(taskID, stat=True)
File "/usr/lib/python2.7/site-packages/koji/__init__.py", line 1510, in __call__
return self.__func(self.__name,args,opts)
File "/usr/lib/python2.7/site-packages/koji/__init__.py", line 1760, in _callMethod
raise err
Fault:<Fault 1: "<type 'exceptions.OverflowError'>: int exceeds XML-RPC limits">
Please note: Old tasks (prior to the 150 pkg update) are not affected. I can view their logs without this error.
koji was not updated. mock was, but downgrading it and running another task did not fix this.
Any ideas?
12 years, 5 months
This action requires admin privileges
by Vijay N. Majagaonkar
I am not able to perform any admin actions on koji server.
I started setting up local koji server using
http://fedoraproject.org/wiki/Koji/ServerHowTo this as help page and
following is my current environment.
fedora 12 x86_64 bit
koji pkgs -
koji-hub-1.4.0-2.fc12.noarch
koji-1.4.0-2.fc12.noarch
I have configured system till hub setup where we can perform command line
actions, and here I am able to connect to server but failed to add user or
new tag to koji server.
[kojiadmin@kojiblr ~]$ koji -d list-pkgs
successfully connected to hub
(no matching packages)
[kojiadmin@kojiblr ~]$ koji -d list-tags
successfully connected to hub
*[**kojiadmin**@kojiblr ~]$ koji -d add-tag dist-panthor*
*successfully connected to hub*
*This action requires admin privileges*
*[kojiadmin@kojiblr ~]$ koji -d add-user kojira*
*successfully connected to hub*
*This action requires admin privileges*
I have added kojiadmin into DB as admin user,
koji=> select * from users;
id | name | password | status | usertype | krb_principal
----+-------------------+----------+--------+----------+---------------
2 | kojiadmin | | 0 | 0 |
koji=> select * from user_perms;
user_id | perm_id | create_event | revoke_event | creator_id | revoker_id |
active
---------+---------+--------------+--------------+------------+------------+--------
2 | 1 | 5 | | 2 | |
t
Can someone point me where missed any configuration that causing me to run
an admin commands on koji.
Thanks for the help
;)
12 years, 5 months
cannot build packages after update
by Michael Cronenworth
It seems koji-web is the least of my worries.
I cannot get Fedora 15 or RHEL5 packages to build in my, once working,
koji instance. I can queue the package build and yum downloads the
build-deps, but when the build starts I get messages such as:
Fedora 15 builds:
collect2: cannot find 'ld'
RHEL5 builds:
gcc: error trying to exec 'cc1': execvp: Permission denied
Note: The Koji builder has SELinux in permissive mode at the moment.
I am fixing to revert the package update I applied, but before I do I am
going to attach the list of updates I applied in hope someone sees a
possible update I can downgrade.
Thanks,
Michael
12 years, 5 months
Problem with koji build system
by Robin YB(yang)
Hello everyone, I am a new koji user. These days I was setting up koji environment on redhat6, using koji 1.6.0 and mock 1.1.12. After that, I tried to run koji build system on my own server. Then I encountered a problem about mock. when I run the build command, the build system did not work correctly, and exited with the following information:
BuildrootError: could not init mock buildroot, mock exited with status 20.
After that, I checked the build log, and find it failed after sending this command to yum:
“/usr/bin/yum �installroot /home/fedora/mock/build0.1-build-43-28/root/ groupinstall build ”
The error information is:
Warning: Group build does not have any packages.
The yum.conf directory was :
/home/fedora/mock/build0.1-build-42-28/root/etc/yum/yum.conf
And the repodata directory was:
/home/fedora/koji/repos/build0.1-build/28/x86_64/repodata
I checked the comps.xml and the repomd.xml in repodata,and could not find any problem.
When I use yum to run this command :
/usr/bin/yum �installroot /home/fedora/mock/build0.1-build-43-28/root/ groupinstall build
It was the same error.
But when I use other directories as the installroot, this error didn’t happen. Did someone know why did this happen?
Root.log:
3093 DEBUG util.py:60: creating dir: /home/fedora/mock/build0.1-build-43-28/root/dev/shm
3095 DEBUG backend.py:739: ['/usr/bin/yum', '--installroot', '/home/fedora/mock/build0.1-build-43-28/root/', 'groupinstall', 'build']
3096 DEBUG util.py:284: Executing command: ['/usr/bin/yum', '--installroot', '/home/fedora/mock/build0.1-build-43-28/root/', 'groupinstall', 'build']
3097 DEBUG util.py:250: Ignored option -c (probably due to merging -yc != -y -c)
3098 DEBUG util.py:250: Warning: Group build does not have any packages.
Regards
Robin
12 years, 6 months
[BUG] Koji and Lustre
by Thomas Guthmann
Hey guys,
We found a bug(?) in listTaskOutput (/usr/share/koji-hub/kojihub.py)
when used with a Lustre filesystem. This function parses all attributes
of every file of a build and is used when you want to display
build.log/root.log through the web interface. Everything returned by
listTaskOutput is returned through XML-RPC and as a result we had this :
An error has occurred while processing your request.
Fault: <Fault 1: 'exceptions.OverflowError: long int exceeds XML-RPC
limits'>
Traceback (most recent call last):
File "/usr/share/koji-web/lib/kojiweb/publisher.py", line 16, in
publish_object
return old_publish_object(req, object)
File "/usr/lib64/python2.4/site-packages/mod_python/publisher.py",
line 412, in publish_object
return publish_object(req,util.apply_fs_data(object, req.form,
req=req))
File "/usr/lib64/python2.4/site-packages/mod_python/util.py", line
439, in apply_fs_data
return object(**args)
File "/usr/share/koji-web/scripts/index.py", line 649, in getfile
output = server.listTaskOutput(taskID, stat=True)
File "/usr/lib/python2.4/site-packages/koji/__init__.py", line 1468,
in __call__
return self.__func(self.__name,args,opts)
File "/usr/lib/python2.4/site-packages/koji/__init__.py", line 1718,
in _callMethod
raise err
Fault: <Fault 1: 'exceptions.OverflowError: long int exceeds XML-RPC
limits'>
The issue comes from the st_dev value gathered by getStat (stat). In
Lustre this value can be very high and that's why it complains. To fix
that, we used the same condition than st_size, we cast the value as a
string. See attached patch.
Example (see 'Device:' the value after the '/'):
# stat build.log
File: `build.log'
Size: 106021 Blocks: 208 IO Block: 2097152 regular file
Device: e04ae70eh/3763005198d Inode: 721664 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 48/ apache) Gid: ( 48/ apache)
Access: 2010-07-13 10:44:40.000000000 +1000
Modify: 2010-07-12 12:54:15.000000000 +1000
Change: 2010-07-12 12:54:52.000000000 +1000
# That's what is read by listTaskOutput
relfilename=build.log ATTR=st_atime GETATTR=1278981616
relfilename=build.log ATTR=st_blksize GETATTR=2097152
relfilename=build.log ATTR=st_blocks GETATTR=208
relfilename=build.log ATTR=st_ctime GETATTR=1278903292
relfilename=build.log ATTR=st_dev GETATTR=3763005198 <----- /!\
relfilename=build.log ATTR=st_gid GETATTR=48
relfilename=build.log ATTR=st_ino GETATTR=721664
relfilename=build.log ATTR=st_mode GETATTR=33188
relfilename=build.log ATTR=st_mtime GETATTR=1278903255
relfilename=build.log ATTR=st_nlink GETATTR=1
relfilename=build.log ATTR=st_rdev GETATTR=0
relfilename=build.log ATTR=st_size GETATTR=106021
relfilename=build.log ATTR=st_uid GETATTR=48
Hope it helps, lost a good amount of time on that one :)
Cheers,
Thomas
12 years, 6 months
How can I add another arch when project is going
by Yanchuan Nian
Hi there,
There are one or more arches in each build tag.These arches are decided before a project opening.I what to know how to add another arch when the project is going.for instance,tag1 contains two arches(i386 and x86_64) at the beginning, and dist-tag1 is a target using tag1 as its build tag.I can build zlib successfully with this command
koji build dist-tag1 /path/to/zlib-1.2.3-4.src.rpm
Then I add mips as the third arch of tag1, and rebuild zlib
koji build dist-tag1 /path/to/zlib-1.2.3-4.src.rpm
A error occurs "Build already exists". zlib-1.2.3-4.mips.rpm can not generate for the information of zlib-1.2.3-4 has been stored in the database.Is there a solution for this problem?If I have to modify the source code of koji, how?
Thanks in advance.
Yanchuan Nian
--
buildsys mailing list
buildsys(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
12 years, 6 months
Re: buildsys Digest, Vol 78, Issue 12
by Jinze Xue
Thanks!!
2011-09-01
xuejinze
发件人: buildsys-request
发送时间: 2011-08-31 20:00:19
收件人: buildsys
抄送:
主题: buildsys Digest, Vol 78, Issue 12
Send buildsys mailing list submissions to
buildsys(a)lists.fedoraproject.org
To subscribe or unsubscribe via the World Wide Web, visit
https://admin.fedoraproject.org/mailman/listinfo/buildsys
or, via email, send a message with subject or body 'help' to
buildsys-request(a)lists.fedoraproject.org
You can reach the person managing the list at
buildsys-owner(a)lists.fedoraproject.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of buildsys digest..."
Today's Topics:
1. Re: about sparc koji (Dennis Gilmore)
----------------------------------------------------------------------
Message: 1
Date: Tue, 30 Aug 2011 10:23:48 -0500
From: Dennis Gilmore <dennis(a)ausil.us>
Subject: Re: about sparc koji
To: buildsys(a)lists.fedoraproject.org
Message-ID: <201108301023.54598.dennis(a)ausil.us>
Content-Type: text/plain; charset="utf-8"
On Tuesday, August 30, 2011 01:37:08 AM xuejinze wrote:
> hello,
>
>
> We find the sparc koji web can't open in these days, what's happened?
> the pages provide us many useful infomations about packages and build logs,
> when will it work normally?
> expecting
> thanks very much!!
the hardware is down due to a hardware faiilure. it will be down until the
replacement hardware arrives.
Dennis
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
Url : http://lists.fedoraproject.org/pipermail/buildsys/attachments/20110830/ac...
------------------------------
--
buildsys mailing list
buildsys(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
End of buildsys Digest, Vol 78, Issue 12
****************************************
12 years, 6 months