package upload/import speed
Hello all, When importing or building RPM's from source is there an option that is throttling the upload speed of the package? We are seeing speeds of 10kbps which makes importing/building large packages very slow. Thanks. -- Naveen Gavini Student Systems Programmer OSS/CSS - OIT Rutgers [EMAIL PROTECTED] -- Fedora-buildsys-list mailing list Fedora-buildsys-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
Problems using import --link
] Permission denied\n\n
tb_type = extended\n data = ?xml
version=\'1.0\'?\nmethodCall\nmethodNameimportRPM/methodName\nparams\nparam\nvaluestringcli-import/1216842099.8955669.PLyYLFZS/string/value\n/param\nparam\nvaluestringalsa-lib-1.0.14-1.rc4.el5.src.rpm/string/value\n/param\n/params\n/methodCall\n\n
method = importRPM\nFrame _dispatch in /usr/share/koji-hub/kojixmlrpc.py
at line 156\n self =
_mp_df1c13776110deb1e020020636703560.ModXMLRPCRequestHandler object at
0x2b349c6f0d10\n start = 1216842100.38\n params = ERROR WHILE PRINTING
VALUE\n func = bound method RootExports.importRPM of
_mp_4e76479ee7b716cdbf29397025ee2356.RootExports object at
0x2b349c6f08d0\n method = importRPM\n opts = {}\nFrame importRPM in
/usr/share/koji-hub/kojihub.py at line 4110\n uploadpath =
/mnt/koji/work\n basename = alsa-lib-1.0.14-1.rc4.el5.src.rpm\n rpminfo
= {\'build_id\': 20L, \'brootid\': None, \'sourcepackage\': 1, \'name\':
\'alsa-lib\', \'buildtime\': 1194704966, \'id\': 28L, \'epoch\': None,
\'version\': \'1.0.14\', \'build\': {\'sourcepackage\': 1, \'name\':
\'alsa-lib\', \'buildtime\': 1194704966, \'epoch\': None, \'version\':
\'1.0.14\', \'release\': \'1.rc4.el5\', \'sourcerpm\': [], \'arch\':
\'src\', \'id\': 20L}, \'release\': \'1.rc4.el5\', \'sourcerpm\': [],
\'arch\': \'src\', \'payloadhash\':
\'8fa4adb63144d52fc1ceb29f6022b7cb\', \'size\': 796510}\n path =
cli-import/1216842099.8955669.PLyYLFZS\n self =
_mp_4e76479ee7b716cdbf29397025ee2356.RootExports object at
0x2b349c6f08d0\n fn =
/mnt/koji/work/cli-import/1216842099.8955669.PLyYLFZS/alsa-lib-1.0.14-1.rc4.el5.src.rpm\nFrame
import_rpm_file in /usr/share/koji-hub/kojihub.py at line 2991\n
final_path =
/mnt/koji/packages/alsa-lib/1.0.14/1.rc4.el5/src/alsa-lib-1.0.14-1.rc4.el5.src.rpm\n
rpminfo = {\'build_id\': 20L, \'brootid\': None, \'sourcepackage\': 1,
\'name\': \'alsa-lib\', \'buildtime\': 1194704966, \'id\': 28L,
\'epoch\': None, \'version\': \'1.0.14\', \'build\': {\'sourcepackage\':
1, \'name\': \'alsa-lib\', \'buildtime\': 1194704966, \'epoch\': None,
\'version\': \'1.0.14\', \'release\': \'1.rc4.el5\', \'sourcerpm\': [],
\'arch\': \'src\', \'id\': 20L}, \'release\': \'1.rc4.el5\',
\'sourcerpm\': [], \'arch\': \'src\', \'payloadhash\':
\'8fa4adb63144d52fc1ceb29f6022b7cb\', \'size\': 796510}\n buildinfo =
{\'sourcepackage\': 1, \'name\': \'alsa-lib\', \'buildtime\':
1194704966, \'epoch\': None, \'version\': \'1.0.14\', \'release\':
\'1.rc4.el5\', \'sourcerpm\': [], \'arch\': \'src\', \'id\': 20L}\n fn =
/mnt/koji/work/cli-import/1216842099.8955669.PLyYLFZS/alsa-lib-1.0.14-1.rc4.el5.src.rpm\n'
Any ideas?
Thanks.
--
Naveen Gavini
Student Systems Programmer
OSS/CSS - OIT Rutgers
[EMAIL PROTECTED]
--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
GenericError Repo directory missing
Hello all,
We have installed the Koji build system and are able to import RPMS. We
are having issues building from SRPMS as it's prompting us that it is
unable to find the file once it is uploaded. The other issue is we have
seen about 500 tasks fail for newRepo (noarch) with the message:
GenericError: Repo directory missing:
/mnt/koji/repos/rutgers-centos5-build/538.
We have set the permissions to daemon on /mnt/koji (same user as apache).
It seems when we try to manually look at the directory it exists, this
is also the same for when the srpm is uploaded and it fails prompting us
file not found, even though we can find it by looking at that directory
on the server.
Below is the kojira.log
2008-07-22 19:46:31,358 [DEBUG] koji.repo.manager: Reading current repo data
2008-07-22 19:46:36,855 [DEBUG] koji.repo.manager: Repo data:
[{'create_event': 552, 'state': 0, 'tag_id': 2, 'tag_name':
'rutgers-centos5-build', 'create_ts': 1216754980.8750801, 'id': 534},
{'create_event': 553, 'state': 0, 'tag_id': 2, 'tag_name':
'rutgers-centos5-build', 'create_ts': 1216755215.82616, 'id': 535}]
2008-07-22 19:46:42,399 [DEBUG] koji.repo.manager: Needed tags: [2]
2008-07-22 19:46:42,400 [DEBUG] koji.repo.manager: Current tags: [2]
2008-07-22 19:46:42,400 [DEBUG] koji.repo: Checking for changes: [1, 2]
2008-07-22 19:46:47,902 [DEBUG] koji.repo: No tag changes since event 552
2008-07-22 19:46:47,902 [DEBUG] koji.repo: Checking for changes: [1, 2]
2008-07-22 19:46:53,429 [DEBUG] koji.repo: No tag changes since event 553
2008-07-22 19:46:53,430 [DEBUG] koji.repo.manager: order: []
2008-07-22 19:46:53,430 [DEBUG] koji.repo.manager: repo 534: tag=2,
state=INIT
2008-07-22 19:46:53,430 [DEBUG] koji.repo.manager: repo 535: tag=2,
state=INIT
2008-07-22 19:46:53,430 [DEBUG] koji.repo.manager: task 548 for tag 2
2008-07-22 19:46:53,430 [DEBUG] koji.repo.manager: Scanning filesystem
for repos
2008-07-22 19:47:09,590 [INFO] koji.repo.manager: Problem: newRepo task
548 for tag 2 is FAILED
2008-07-22 19:47:09,591 [DEBUG] koji.repo.manager: Current tasks: {}
2008-07-22 19:47:09,591 [DEBUG] koji.repo.manager: Updating repos
2008-07-22 19:47:09,591 [DEBUG] koji.repo.manager: Reading current repo data
2008-07-22 19:47:15,273 [DEBUG] koji.repo.manager: Repo data:
[{'create_event': 552, 'state': 0, 'tag_id': 2, 'tag_name':
'rutgers-centos5-build', 'create_ts': 1216754980.8750801, 'id': 534},
{'create_event': 553, 'state': 0, 'tag_id': 2, 'tag_name':
'rutgers-centos5-build', 'create_ts': 1216755215.82616, 'id': 535},
{'create_event': 554, 'state': 0, 'tag_id': 2, 'tag_name':
'rutgers-centos5-build', 'create_ts': 1216756145.8847401, 'id': 536}]
2008-07-22 19:47:15,273 [INFO] koji.repo.manager: Found repo 536, state=INIT
2008-07-22 19:47:26,421 [DEBUG] koji.repo.manager: Needed tags: [2]
2008-07-22 19:47:26,421 [DEBUG] koji.repo.manager: Current tags: [2]
2008-07-22 19:47:26,421 [DEBUG] koji.repo: Checking for changes: [1, 2]
2008-07-22 19:47:31,905 [DEBUG] koji.repo: No tag changes since event 554
2008-07-22 19:47:31,905 [DEBUG] koji.repo: Checking for changes: [1, 2]
Any idea?
Thanks.
--
Naveen Gavini
Student Systems Programmer
OSS/CSS - OIT Rutgers
[EMAIL PROTECTED]
--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
Re: GenericError Repo directory missing
Mike Bonnet wrote:
On Tue, 2008-07-22 at 16:02 -0400, Naveen Gavini wrote:
Hello all,
We have installed the Koji build system and are able to import RPMS. We
are having issues building from SRPMS as it's prompting us that it is
unable to find the file once it is uploaded. The other issue is we have
seen about 500 tasks fail for newRepo (noarch) with the message:
GenericError: Repo directory missing:
/mnt/koji/repos/rutgers-centos5-build/538.
Does the /mnt/koji/repos directory exist? Is it owned by the same user
httpd runs as?
Also, have you tried to change topdir to something other than /mnt/koji?
There are known problem with this, it needs to be fixed.
We were able to fix this. The problem seemed to be that we did not have
this directory (/mnt/koji) mounted on the builder, it was only mounted
on the hub which runs kojira. We thought since kojira was creating the
repos directories that would suffice. It also needs to be accessible by
the builder.
Thanks.
We have set the permissions to daemon on /mnt/koji (same user as apache).
It seems when we try to manually look at the directory it exists, this
is also the same for when the srpm is uploaded and it fails prompting us
file not found, even though we can find it by looking at that directory
on the server.
Below is the kojira.log
2008-07-22 19:46:31,358 [DEBUG] koji.repo.manager: Reading current repo data
2008-07-22 19:46:36,855 [DEBUG] koji.repo.manager: Repo data:
[{'create_event': 552, 'state': 0, 'tag_id': 2, 'tag_name':
'rutgers-centos5-build', 'create_ts': 1216754980.8750801, 'id': 534},
{'create_event': 553, 'state': 0, 'tag_id': 2, 'tag_name':
'rutgers-centos5-build', 'create_ts': 1216755215.82616, 'id': 535}]
2008-07-22 19:46:42,399 [DEBUG] koji.repo.manager: Needed tags: [2]
2008-07-22 19:46:42,400 [DEBUG] koji.repo.manager: Current tags: [2]
2008-07-22 19:46:42,400 [DEBUG] koji.repo: Checking for changes: [1, 2]
2008-07-22 19:46:47,902 [DEBUG] koji.repo: No tag changes since event 552
2008-07-22 19:46:47,902 [DEBUG] koji.repo: Checking for changes: [1, 2]
2008-07-22 19:46:53,429 [DEBUG] koji.repo: No tag changes since event 553
2008-07-22 19:46:53,430 [DEBUG] koji.repo.manager: order: []
2008-07-22 19:46:53,430 [DEBUG] koji.repo.manager: repo 534: tag=2,
state=INIT
2008-07-22 19:46:53,430 [DEBUG] koji.repo.manager: repo 535: tag=2,
state=INIT
2008-07-22 19:46:53,430 [DEBUG] koji.repo.manager: task 548 for tag 2
2008-07-22 19:46:53,430 [DEBUG] koji.repo.manager: Scanning filesystem
for repos
2008-07-22 19:47:09,590 [INFO] koji.repo.manager: Problem: newRepo task
548 for tag 2 is FAILED
2008-07-22 19:47:09,591 [DEBUG] koji.repo.manager: Current tasks: {}
2008-07-22 19:47:09,591 [DEBUG] koji.repo.manager: Updating repos
2008-07-22 19:47:09,591 [DEBUG] koji.repo.manager: Reading current repo data
2008-07-22 19:47:15,273 [DEBUG] koji.repo.manager: Repo data:
[{'create_event': 552, 'state': 0, 'tag_id': 2, 'tag_name':
'rutgers-centos5-build', 'create_ts': 1216754980.8750801, 'id': 534},
{'create_event': 553, 'state': 0, 'tag_id': 2, 'tag_name':
'rutgers-centos5-build', 'create_ts': 1216755215.82616, 'id': 535},
{'create_event': 554, 'state': 0, 'tag_id': 2, 'tag_name':
'rutgers-centos5-build', 'create_ts': 1216756145.8847401, 'id': 536}]
2008-07-22 19:47:15,273 [INFO] koji.repo.manager: Found repo 536, state=INIT
2008-07-22 19:47:26,421 [DEBUG] koji.repo.manager: Needed tags: [2]
2008-07-22 19:47:26,421 [DEBUG] koji.repo.manager: Current tags: [2]
2008-07-22 19:47:26,421 [DEBUG] koji.repo: Checking for changes: [1, 2]
2008-07-22 19:47:31,905 [DEBUG] koji.repo: No tag changes since event 554
2008-07-22 19:47:31,905 [DEBUG] koji.repo: Checking for changes: [1, 2]
Any idea?
Thanks.
--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
--
Naveen Gavini
Student Systems Programmer
OSS/CSS - OIT Rutgers
[EMAIL PROTECTED]
--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
Re: How init mock in Koji?
Mike McLean wrote: Linul wrote: I have already set my koji server and every component is work OK. But not have any document mention howto init the buildroot?(or use mock environment) We are having a similar issue with problems on how to init the buildroot. We generated a config using 'koji mock-config' and copied this to site-defaults.cfg and default.cfg but we get the following error: When manually running mock it seems to init properly (we did not test with a package). This is the error with building from an SRPM via koji build: 2008-07-22 21:14:42,845 [WARNING] koji.build.TaskManager: could not init mock buildroot, mock exited with status 30 Is there any further documentation on how to do this step? Thanks for your help. It's not entirely clear what you're asking, but here goes... mock is used by koji-builder to create buildroots. In normal operation, you submit a build to the system, the builders pick it up and use mock to create a buildroot and run the build. If, on the other hand, you want to run mock manually against the repos that koji maintains (not normal operation, but useful nonetheless), then you should just be able to generate a mock config with the 'koji mock-config' command. You can use that config with a manual run of mock. Sometimes the config may need a little tweaking. If this doesn't answer your question, then perhaps you could provide a bit more context. -- Naveen Gavini Student Systems Programmer OSS/CSS - OIT Rutgers [EMAIL PROTECTED] -- Fedora-buildsys-list mailing list Fedora-buildsys-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
mod_python error installing Koji
Hello all,
We are trying to setup the Koji build system for our Centos and Fedora
repositories. We are getting the errors below after following the setup
guide.
We have tried numerous different things to attempt to correct the errors
and nothing has worked. We initially thought it was an issue of what
user it was
being run as and we changed users around this did not work. We changed
various settings in our apache configuration and still no dice.
Here is the errors we are seeing on http://192.168.226.61/koji/:
MOD_PYTHON ERROR
ProcessId: 9453
Interpreter:'127.0.0.1'
ServerName: '127.0.0.1'
DocumentRoot: '/var/www/html'
URI:'/koji/'
Location: None
Directory: '/usr/share/koji-web/scripts/'
Filename: '/usr/share/koji-web/scripts/index.py'
PathInfo: ''
Phase: 'PythonHandler'
Handler:'mod_python.publisher'
Traceback (most recent call last):
File /usr/lib64/python2.4/site-packages/mod_python/importer.py, line 1537,
in HandlerDispatch
default=default_handler, arg=req, silent=hlist.silent)
File /usr/lib64/python2.4/site-packages/mod_python/importer.py, line 1229,
in _process_target
result = _execute_target(config, req, object, arg)
File /usr/lib64/python2.4/site-packages/mod_python/importer.py, line 1128,
in _execute_target
result = object(arg)
File /usr/lib64/python2.4/site-packages/mod_python/publisher.py, line 213,
in handler
published = publish_object(req, object)
File /usr/lib64/python2.4/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.4/site-packages/mod_python/util.py, line 554, in
apply_fs_data
return object(**args)
File /usr/share/koji-web/scripts/index.py, line 175, in index
start=buildStart, dataName='builds', prefix='build', order=buildOrder,
pageSize=10)
File /usr/share/koji-web/lib/kojiweb/util.py, line 109, in paginateMethod
totalRows = getattr(server, methodName)(*args, **kw)
File /usr/lib/python2.4/site-packages/koji/__init__.py, line 1077, in
__call__
return self.__func(self.__name,args,opts)
File /usr/lib/python2.4/site-packages/koji/__init__.py, line 1302, in
_callMethod
return proxy.__getattr__(name)(*args)
File /usr/lib64/python2.4/xmlrpclib.py, line 1096, in __call__
return self.__send(self.__name, args)
File /usr/lib64/python2.4/xmlrpclib.py, line 1383, in __request
verbose=self.__verbose
File /usr/lib64/python2.4/xmlrpclib.py, line 1137, in request
headers
ProtocolError: ProtocolError for 192.168.226.61/kojihub: 500 Internal Server
Error
MODULE CACHE DETAILS
Accessed: Wed Jul 16 16:47:56 2008
Generation: 1
_mp_0dec3ca8c086f5baed01b0d5504fa2b0 {
FileName: '/usr/share/koji-web/scripts/index.py'
Instance: 1
Generation: 1
Modified: Fri Dec 14 21:12:36 2007
Imported: Wed Jul 16 16:36:02 2008
}
Here is the error we are seeing on http://192.168.226.61/koji/index.chtml:
Forbidden
You don't have permission to access /koji/index.chtml on this server.
Here is the error we are seeing on http://192.168.226.61/kojihub:
Internal Server Error
blah blah blah
http://192.168.226.61/koji-static/
Displays a directory listing of a few files and directories so I am
assuming it is working correctly.
Anyone have any ideas?
Thanks.
--
Naveen Gavini
Student Systems Programmer
OSS/CSS - OIT Rutgers
[EMAIL PROTECTED]
--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
