From wacker at octothorp.org Tue May 6 16:07:54 2008 From: wacker at octothorp.org (William F. Acker WB2FLW +1-303-722-7209) Date: Tue, 6 May 2008 10:07:54 -0600 (MDT) Subject: Unresolvable deps when building Rawhide. Message-ID: Hi all, When I do a Pungi run on an x86_64, I get the following. Pungi.Gather:WARNING: Unresolvable dependency jakarta-commons-beanutils-javadoc in checkstyle.noarch Pungi.Gather:INFO: Added jakarta-commons-beanutils.x86_64 for checkstyle.noarch Pungi.Gather:WARNING: Unresolvable dependency antlr-javadoc in checkstyle.noarch Pungi.Gather:INFO: Added jdom.x86_64 for checkstyle.noarch Pungi.Gather:WARNING: Unresolvable dependency xml-commons-apis-javadoc in checkstyle.noarch Pungi.Gather:WARNING: Unresolvable dependency ant-javadoc in checkstyle.noarch I believe this is related to the last batch of package exclusions to save space that appeared in the fedora-9 ks file with the latest version of Pungi. Is this condition OK? Might it be possible for someone to select the wrong package combination and have a failed installation, or would this be caught when dependencies are checked Thanks. -- Bill in Denver From jkeating at j2solutions.net Tue May 6 18:03:49 2008 From: jkeating at j2solutions.net (Jesse Keating) Date: Tue, 06 May 2008 14:03:49 -0400 Subject: Unresolvable deps when building Rawhide. In-Reply-To: References: Message-ID: <1210097029.17842.16.camel@localhost.localdomain> On Tue, 2008-05-06 at 10:07 -0600, William F. Acker WB2FLW +1-303-722-7209 wrote: > > When I do a Pungi run on an x86_64, I get the following. > Pungi.Gather:WARNING: Unresolvable dependency > jakarta-commons-beanutils-javadoc in checkstyle.noarch > Pungi.Gather:INFO: Added jakarta-commons-beanutils.x86_64 for > checkstyle.noarch > Pungi.Gather:WARNING: Unresolvable dependency antlr-javadoc in > checkstyle.noarch > Pungi.Gather:INFO: Added jdom.x86_64 for checkstyle.noarch > Pungi.Gather:WARNING: Unresolvable dependency xml-commons-apis-javadoc > in checkstyle.noarch > Pungi.Gather:WARNING: Unresolvable dependency ant-javadoc in > checkstyle.noarch > > I believe this is related to the last batch of package > exclusions to > save space that appeared in the fedora-9 ks file with the latest > version > of Pungi. Is this condition OK? Might it be possible for someone to > select the wrong package combination and have a failed installation, > or > would this be caught when dependencies are checked > Hrm, that's odd. I could have sworn the code would allow for the deps to be dragged in if they're asked for. You may have uncovered a bug in pungi code... Can you file this in bugzilla or the pungi trac space? -- Jesse Keating RHCE (jkeating.livejournal.com) Fedora Project (fedoraproject.org/wiki/JesseKeating) GPG Public Key (geek.j2solutions.net/jkeating.j2solutions.pub) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From paul.schroeder at bluecoat.com Wed May 7 16:24:55 2008 From: paul.schroeder at bluecoat.com (Paul B Schroeder) Date: Wed, 07 May 2008 11:24:55 -0500 Subject: koji.build: Session expired Message-ID: <1210177495.15042.15.camel@localhost.localdomain> Hello.. I'm running F8 with the latest koji-* packages: [root at koji koji]# rpm -qa 'koji*' koji-hub-1.2.2-2.fc8 koji-1.2.2-2.fc8 koji-utils-1.2.2-2.fc8 koji-web-1.2.2-2.fc8 koji-builder-1.2.2-2.fc8 I've been following the Koji Server HOWTO here: http://fedoraproject.org/wiki/Koji/ServerHowTo I've gotten all of the way through it, but I'm having issues when starting kojira. It doesn't stay running and it seems to somehow be causing kojid to shutdown as well. I've turned on debug for kojid and kojira. I see this in kojid.log: 2008-05-07 06:10:37,895 [ERROR] koji.build: Session expired 2008-05-07 06:10:37,896 [WARNING] koji.build: Shutting down, please wait... Below is a full output of what I see in those logs. Am I missing something simple? Anybody have any clue what's going wrong? Thanks in advance...Paul... /var/log/kojid.log (before I attempt to start kojira): 2008-05-07 06:10:04,662 [INFO] koji.build: Starting up 2008-05-07 06:10:05,125 [DEBUG] koji.build.TaskManager: Local buildroots: 0 2008-05-07 06:10:05,125 [DEBUG] koji.build.TaskManager: Active buildroots: 0 2008-05-07 06:10:05,126 [DEBUG] koji.build.TaskManager: Expired/stray buildroots: 0 2008-05-07 06:10:05,438 [DEBUG] koji.build.TaskManager: Task Load: 0.0 2008-05-07 06:10:05,438 [DEBUG] koji.build.TaskManager: Current tasks: {} 2008-05-07 06:10:05,743 [DEBUG] koji.build.TaskManager: hostdata: {'capacity': 2.0, 'name': 'koji.bcstx.cacheflow.com', 'enabled': True, 'arches': 'i386 x86_64', 'task_load': 0.0, 'ready': True, 'user_id': 3, 'id': 1} 2008-05-07 06:10:05,750 [DEBUG] koji.build.TaskManager: disk space available in '/var/lib/mock': 43829 MB 2008-05-07 06:10:06,186 [DEBUG] koji.build.TaskManager: Load Data: 2008-05-07 06:10:06,186 [DEBUG] koji.build.TaskManager: hosts: [{'capacity': 2.0, 'name': 'koji.bcstx.cacheflow.com', 'channels': [1, 2], 'arches': 'i386 x86_64', 'task_load': 0.0, 'id': 1}] 2008-05-07 06:10:06,187 [DEBUG] koji.build.TaskManager: tasks: [] 2008-05-07 06:10:06,187 [DEBUG] koji.build.TaskManager: bins: {'1:noarch': 1, '2:noarch': 1, '1:x86_64': 1, '1:i386': 1, '2:x86_64': 1, '2:i386': 1} /var/log/kojid.log (after I start kojira): 2008-05-07 06:10:21,504 [DEBUG] koji.build.TaskManager: Local buildroots: 0 2008-05-07 06:10:21,505 [DEBUG] koji.build.TaskManager: Active buildroots: 0 2008-05-07 06:10:21,505 [DEBUG] koji.build.TaskManager: Expired/stray buildroots: 0 2008-05-07 06:10:21,818 [DEBUG] koji.build.TaskManager: Task Load: 0.0 2008-05-07 06:10:21,818 [DEBUG] koji.build.TaskManager: Current tasks: {} 2008-05-07 06:10:22,138 [DEBUG] koji.build.TaskManager: hostdata: {'capacity': 2.0, 'name': 'koji.bcstx.cacheflow.com', 'enabled': True, 'arches': 'i386 x86_64', 'task_load': 0.0, 'ready': True, 'user_id': 3, 'id': 1} 2008-05-07 06:10:22,145 [DEBUG] koji.build.TaskManager: disk space available in '/var/lib/mock': 43829 MB 2008-05-07 06:10:22,586 [DEBUG] koji.build.TaskManager: Load Data: 2008-05-07 06:10:22,586 [DEBUG] koji.build.TaskManager: hosts: [{'capacity': 2.0, 'name': 'koji.bcstx.cacheflow.com', 'channels': [1, 2], 'arches': 'i386 x86_64', 'task_load': 0.0, 'id': 1}] 2008-05-07 06:10:22,587 [DEBUG] koji.build.TaskManager: tasks: [] 2008-05-07 06:10:22,587 [DEBUG] koji.build.TaskManager: bins: {'1:noarch': 1, '2:noarch': 1, '1:x86_64': 1, '1:i386': 1, '2:x86_64': 1, '2:i386': 1} 2008-05-07 06:10:37,895 [ERROR] koji.build: Session expired 2008-05-07 06:10:37,896 [WARNING] koji.build: Shutting down, please wait... /var/log/kojira.log: 2008-05-07 06:10:25,519 [DEBUG] koji.repo.manager: Reading current repo data 2008-05-07 06:10:25,654 [DEBUG] koji.repo.manager: Repo data: [] 2008-05-07 06:10:25,654 [DEBUG] koji.repo.manager: Scanning filesystem for repos From paul.schroeder at bluecoat.com Wed May 7 16:27:46 2008 From: paul.schroeder at bluecoat.com (Paul B Schroeder) Date: Wed, 07 May 2008 11:27:46 -0500 Subject: koji.build: Session expired In-Reply-To: <1210177495.15042.15.camel@localhost.localdomain> References: <1210177495.15042.15.camel@localhost.localdomain> Message-ID: <1210177666.15042.18.camel@localhost.localdomain> Oh yea.. It should also be noted that I set this up using SSL authentication, not kerberos.. Thanks again...Paul.. On Wed, 2008-05-07 at 11:24 -0500, Paul B Schroeder wrote: > Hello.. > > I'm running F8 with the latest koji-* packages: > [root at koji koji]# rpm -qa 'koji*' > koji-hub-1.2.2-2.fc8 > koji-1.2.2-2.fc8 > koji-utils-1.2.2-2.fc8 > koji-web-1.2.2-2.fc8 > koji-builder-1.2.2-2.fc8 > > I've been following the Koji Server HOWTO here: > http://fedoraproject.org/wiki/Koji/ServerHowTo > > I've gotten all of the way through it, but I'm having issues when > starting kojira. It doesn't stay running and it seems to somehow be > causing kojid to shutdown as well. I've turned on debug for kojid and > kojira. I see this in kojid.log: > > 2008-05-07 06:10:37,895 [ERROR] koji.build: Session expired > 2008-05-07 06:10:37,896 [WARNING] koji.build: Shutting down, please > wait... > > Below is a full output of what I see in those logs. Am I missing > something simple? Anybody have any clue what's going wrong? > > Thanks in advance...Paul... > > > /var/log/kojid.log (before I attempt to start kojira): > 2008-05-07 06:10:04,662 [INFO] koji.build: Starting up > 2008-05-07 06:10:05,125 [DEBUG] koji.build.TaskManager: Local > buildroots: 0 > 2008-05-07 06:10:05,125 [DEBUG] koji.build.TaskManager: Active > buildroots: 0 > 2008-05-07 06:10:05,126 [DEBUG] koji.build.TaskManager: Expired/stray > buildroots: 0 > 2008-05-07 06:10:05,438 [DEBUG] koji.build.TaskManager: Task Load: 0.0 > 2008-05-07 06:10:05,438 [DEBUG] koji.build.TaskManager: Current tasks: > {} > 2008-05-07 06:10:05,743 [DEBUG] koji.build.TaskManager: hostdata: > {'capacity': 2.0, 'name': 'koji.bcstx.cacheflow.com', 'enabled': True, > 'arches': 'i386 x86_64', 'task_load': 0.0, 'ready': True, 'user_id': 3, > 'id': 1} > 2008-05-07 06:10:05,750 [DEBUG] koji.build.TaskManager: disk space > available in '/var/lib/mock': 43829 MB > 2008-05-07 06:10:06,186 [DEBUG] koji.build.TaskManager: Load Data: > 2008-05-07 06:10:06,186 [DEBUG] koji.build.TaskManager: hosts: > [{'capacity': 2.0, 'name': 'koji.bcstx.cacheflow.com', 'channels': [1, > 2], 'arches': 'i386 x86_64', 'task_load': 0.0, 'id': 1}] > 2008-05-07 06:10:06,187 [DEBUG] koji.build.TaskManager: tasks: [] > 2008-05-07 06:10:06,187 [DEBUG] koji.build.TaskManager: bins: > {'1:noarch': 1, '2:noarch': 1, '1:x86_64': 1, '1:i386': 1, '2:x86_64': > 1, '2:i386': 1} > > /var/log/kojid.log (after I start kojira): > 2008-05-07 06:10:21,504 [DEBUG] koji.build.TaskManager: Local > buildroots: 0 > 2008-05-07 06:10:21,505 [DEBUG] koji.build.TaskManager: Active > buildroots: 0 > 2008-05-07 06:10:21,505 [DEBUG] koji.build.TaskManager: Expired/stray > buildroots: 0 > 2008-05-07 06:10:21,818 [DEBUG] koji.build.TaskManager: Task Load: 0.0 > 2008-05-07 06:10:21,818 [DEBUG] koji.build.TaskManager: Current tasks: > {} > 2008-05-07 06:10:22,138 [DEBUG] koji.build.TaskManager: hostdata: > {'capacity': 2.0, 'name': 'koji.bcstx.cacheflow.com', 'enabled': True, > 'arches': 'i386 x86_64', 'task_load': 0.0, 'ready': True, 'user_id': 3, > 'id': 1} > 2008-05-07 06:10:22,145 [DEBUG] koji.build.TaskManager: disk space > available in '/var/lib/mock': 43829 MB > 2008-05-07 06:10:22,586 [DEBUG] koji.build.TaskManager: Load Data: > 2008-05-07 06:10:22,586 [DEBUG] koji.build.TaskManager: hosts: > [{'capacity': 2.0, 'name': 'koji.bcstx.cacheflow.com', 'channels': [1, > 2], 'arches': 'i386 x86_64', 'task_load': 0.0, 'id': 1}] > 2008-05-07 06:10:22,587 [DEBUG] koji.build.TaskManager: tasks: [] > 2008-05-07 06:10:22,587 [DEBUG] koji.build.TaskManager: bins: > {'1:noarch': 1, '2:noarch': 1, '1:x86_64': 1, '1:i386': 1, '2:x86_64': > 1, '2:i386': 1} > 2008-05-07 06:10:37,895 [ERROR] koji.build: Session expired > 2008-05-07 06:10:37,896 [WARNING] koji.build: Shutting down, please > wait... > > > /var/log/kojira.log: > 2008-05-07 06:10:25,519 [DEBUG] koji.repo.manager: Reading current repo > data > 2008-05-07 06:10:25,654 [DEBUG] koji.repo.manager: Repo data: [] > 2008-05-07 06:10:25,654 [DEBUG] koji.repo.manager: Scanning filesystem > for repos > > > > > -- > Fedora-buildsys-list mailing list > Fedora-buildsys-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-buildsys-list From mikeb at redhat.com Wed May 7 16:46:20 2008 From: mikeb at redhat.com (Mike Bonnet) Date: Wed, 07 May 2008 12:46:20 -0400 Subject: koji.build: Session expired In-Reply-To: <1210177666.15042.18.camel@localhost.localdomain> References: <1210177495.15042.15.camel@localhost.localdomain> <1210177666.15042.18.camel@localhost.localdomain> Message-ID: <1210178780.3879.13.camel@localhost.localdomain> On Wed, 2008-05-07 at 11:27 -0500, Paul B Schroeder wrote: > Oh yea.. It should also be noted that I set this up using SSL > authentication, not kerberos.. > > Thanks again...Paul.. Are kojid and kojira using the same SSL cert for authentication? This would cause the problem you're seeing, as they would be sharing the same session, and when one of them logs out, the other would think it had been logged out as well. You need to use different SSL certs (with different CNs) for each user, including the daemons. > > On Wed, 2008-05-07 at 11:24 -0500, Paul B Schroeder wrote: > > Hello.. > > > > I'm running F8 with the latest koji-* packages: > > [root at koji koji]# rpm -qa 'koji*' > > koji-hub-1.2.2-2.fc8 > > koji-1.2.2-2.fc8 > > koji-utils-1.2.2-2.fc8 > > koji-web-1.2.2-2.fc8 > > koji-builder-1.2.2-2.fc8 > > > > I've been following the Koji Server HOWTO here: > > http://fedoraproject.org/wiki/Koji/ServerHowTo > > > > I've gotten all of the way through it, but I'm having issues when > > starting kojira. It doesn't stay running and it seems to somehow be > > causing kojid to shutdown as well. I've turned on debug for kojid and > > kojira. I see this in kojid.log: > > > > 2008-05-07 06:10:37,895 [ERROR] koji.build: Session expired > > 2008-05-07 06:10:37,896 [WARNING] koji.build: Shutting down, please > > wait... > > > > Below is a full output of what I see in those logs. Am I missing > > something simple? Anybody have any clue what's going wrong? > > > > Thanks in advance...Paul... > > > > > > /var/log/kojid.log (before I attempt to start kojira): > > 2008-05-07 06:10:04,662 [INFO] koji.build: Starting up > > 2008-05-07 06:10:05,125 [DEBUG] koji.build.TaskManager: Local > > buildroots: 0 > > 2008-05-07 06:10:05,125 [DEBUG] koji.build.TaskManager: Active > > buildroots: 0 > > 2008-05-07 06:10:05,126 [DEBUG] koji.build.TaskManager: Expired/stray > > buildroots: 0 > > 2008-05-07 06:10:05,438 [DEBUG] koji.build.TaskManager: Task Load: 0.0 > > 2008-05-07 06:10:05,438 [DEBUG] koji.build.TaskManager: Current tasks: > > {} > > 2008-05-07 06:10:05,743 [DEBUG] koji.build.TaskManager: hostdata: > > {'capacity': 2.0, 'name': 'koji.bcstx.cacheflow.com', 'enabled': True, > > 'arches': 'i386 x86_64', 'task_load': 0.0, 'ready': True, 'user_id': 3, > > 'id': 1} > > 2008-05-07 06:10:05,750 [DEBUG] koji.build.TaskManager: disk space > > available in '/var/lib/mock': 43829 MB > > 2008-05-07 06:10:06,186 [DEBUG] koji.build.TaskManager: Load Data: > > 2008-05-07 06:10:06,186 [DEBUG] koji.build.TaskManager: hosts: > > [{'capacity': 2.0, 'name': 'koji.bcstx.cacheflow.com', 'channels': [1, > > 2], 'arches': 'i386 x86_64', 'task_load': 0.0, 'id': 1}] > > 2008-05-07 06:10:06,187 [DEBUG] koji.build.TaskManager: tasks: [] > > 2008-05-07 06:10:06,187 [DEBUG] koji.build.TaskManager: bins: > > {'1:noarch': 1, '2:noarch': 1, '1:x86_64': 1, '1:i386': 1, '2:x86_64': > > 1, '2:i386': 1} > > > > /var/log/kojid.log (after I start kojira): > > 2008-05-07 06:10:21,504 [DEBUG] koji.build.TaskManager: Local > > buildroots: 0 > > 2008-05-07 06:10:21,505 [DEBUG] koji.build.TaskManager: Active > > buildroots: 0 > > 2008-05-07 06:10:21,505 [DEBUG] koji.build.TaskManager: Expired/stray > > buildroots: 0 > > 2008-05-07 06:10:21,818 [DEBUG] koji.build.TaskManager: Task Load: 0.0 > > 2008-05-07 06:10:21,818 [DEBUG] koji.build.TaskManager: Current tasks: > > {} > > 2008-05-07 06:10:22,138 [DEBUG] koji.build.TaskManager: hostdata: > > {'capacity': 2.0, 'name': 'koji.bcstx.cacheflow.com', 'enabled': True, > > 'arches': 'i386 x86_64', 'task_load': 0.0, 'ready': True, 'user_id': 3, > > 'id': 1} > > 2008-05-07 06:10:22,145 [DEBUG] koji.build.TaskManager: disk space > > available in '/var/lib/mock': 43829 MB > > 2008-05-07 06:10:22,586 [DEBUG] koji.build.TaskManager: Load Data: > > 2008-05-07 06:10:22,586 [DEBUG] koji.build.TaskManager: hosts: > > [{'capacity': 2.0, 'name': 'koji.bcstx.cacheflow.com', 'channels': [1, > > 2], 'arches': 'i386 x86_64', 'task_load': 0.0, 'id': 1}] > > 2008-05-07 06:10:22,587 [DEBUG] koji.build.TaskManager: tasks: [] > > 2008-05-07 06:10:22,587 [DEBUG] koji.build.TaskManager: bins: > > {'1:noarch': 1, '2:noarch': 1, '1:x86_64': 1, '1:i386': 1, '2:x86_64': > > 1, '2:i386': 1} > > 2008-05-07 06:10:37,895 [ERROR] koji.build: Session expired > > 2008-05-07 06:10:37,896 [WARNING] koji.build: Shutting down, please > > wait... > > > > > > /var/log/kojira.log: > > 2008-05-07 06:10:25,519 [DEBUG] koji.repo.manager: Reading current repo > > data > > 2008-05-07 06:10:25,654 [DEBUG] koji.repo.manager: Repo data: [] > > 2008-05-07 06:10:25,654 [DEBUG] koji.repo.manager: Scanning filesystem > > for repos > > > > > > > > > > -- > > Fedora-buildsys-list mailing list > > Fedora-buildsys-list at redhat.com > > https://www.redhat.com/mailman/listinfo/fedora-buildsys-list > > -- > Fedora-buildsys-list mailing list > Fedora-buildsys-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-buildsys-list From paul.schroeder at bluecoat.com Wed May 7 17:10:34 2008 From: paul.schroeder at bluecoat.com (Paul B Schroeder) Date: Wed, 07 May 2008 12:10:34 -0500 Subject: koji.build: Session expired In-Reply-To: <1210178780.3879.13.camel@localhost.localdomain> References: <1210177495.15042.15.camel@localhost.localdomain> <1210177666.15042.18.camel@localhost.localdomain> <1210178780.3879.13.camel@localhost.localdomain> Message-ID: <1210180234.15042.27.camel@localhost.localdomain> On Wed, 2008-05-07 at 12:46 -0400, Mike Bonnet wrote: > On Wed, 2008-05-07 at 11:27 -0500, Paul B Schroeder wrote: > > Oh yea.. It should also be noted that I set this up using SSL > > authentication, not kerberos.. > > > > Thanks again...Paul.. > > Are kojid and kojira using the same SSL cert for authentication? This > would cause the problem you're seeing, as they would be sharing the same > session, and when one of them logs out, the other would think it had > been logged out as well. You need to use different SSL certs (with > different CNs) for each user, including the daemons. Ah.. I generated separate certs, but they had the same CN. Seems to be up and running now. Thanks...Paul... From paul.schroeder at bluecoat.com Wed May 7 20:34:53 2008 From: paul.schroeder at bluecoat.com (Paul B Schroeder) Date: Wed, 07 May 2008 15:34:53 -0500 Subject: koji.build: Session expired In-Reply-To: <1210178780.3879.13.camel@localhost.localdomain> References: <1210177495.15042.15.camel@localhost.localdomain> <1210177666.15042.18.camel@localhost.localdomain> <1210178780.3879.13.camel@localhost.localdomain> Message-ID: <1210192493.15042.33.camel@localhost.localdomain> Okay.. I *thought* I had it working, but now it's not. At the very least, kojid doesn't appear to be shutting down anymore. Running kojira with --verbose and --debug doesn't appear to be of much help. I see these lines in the log file when starting kojira: 2008-05-07 10:28:24,540 [DEBUG] koji.repo.manager: Reading current repo data 2008-05-07 10:28:24,678 [DEBUG] koji.repo.manager: Repo data: [] 2008-05-07 10:28:24,678 [DEBUG] koji.repo.manager: Scanning filesystem for repos After starting, I then check to see if the process is running. But it's not.. Any more clues? Thanks...Paul... On Wed, 2008-05-07 at 12:46 -0400, Mike Bonnet wrote: > On Wed, 2008-05-07 at 11:27 -0500, Paul B Schroeder wrote: > > Oh yea.. It should also be noted that I set this up using SSL > > authentication, not kerberos.. > > > > Thanks again...Paul.. > > Are kojid and kojira using the same SSL cert for authentication? This > would cause the problem you're seeing, as they would be sharing the same > session, and when one of them logs out, the other would think it had > been logged out as well. You need to use different SSL certs (with > different CNs) for each user, including the daemons. > > > > > On Wed, 2008-05-07 at 11:24 -0500, Paul B Schroeder wrote: > > > Hello.. > > > > > > I'm running F8 with the latest koji-* packages: > > > [root at koji koji]# rpm -qa 'koji*' > > > koji-hub-1.2.2-2.fc8 > > > koji-1.2.2-2.fc8 > > > koji-utils-1.2.2-2.fc8 > > > koji-web-1.2.2-2.fc8 > > > koji-builder-1.2.2-2.fc8 > > > > > > I've been following the Koji Server HOWTO here: > > > http://fedoraproject.org/wiki/Koji/ServerHowTo > > > > > > I've gotten all of the way through it, but I'm having issues when > > > starting kojira. It doesn't stay running and it seems to somehow be > > > causing kojid to shutdown as well. I've turned on debug for kojid and > > > kojira. I see this in kojid.log: > > > > > > 2008-05-07 06:10:37,895 [ERROR] koji.build: Session expired > > > 2008-05-07 06:10:37,896 [WARNING] koji.build: Shutting down, please > > > wait... > > > > > > Below is a full output of what I see in those logs. Am I missing > > > something simple? Anybody have any clue what's going wrong? > > > > > > Thanks in advance...Paul... > > > > > > > > > /var/log/kojid.log (before I attempt to start kojira): > > > 2008-05-07 06:10:04,662 [INFO] koji.build: Starting up > > > 2008-05-07 06:10:05,125 [DEBUG] koji.build.TaskManager: Local > > > buildroots: 0 > > > 2008-05-07 06:10:05,125 [DEBUG] koji.build.TaskManager: Active > > > buildroots: 0 > > > 2008-05-07 06:10:05,126 [DEBUG] koji.build.TaskManager: Expired/stray > > > buildroots: 0 > > > 2008-05-07 06:10:05,438 [DEBUG] koji.build.TaskManager: Task Load: 0.0 > > > 2008-05-07 06:10:05,438 [DEBUG] koji.build.TaskManager: Current tasks: > > > {} > > > 2008-05-07 06:10:05,743 [DEBUG] koji.build.TaskManager: hostdata: > > > {'capacity': 2.0, 'name': 'koji.bcstx.cacheflow.com', 'enabled': True, > > > 'arches': 'i386 x86_64', 'task_load': 0.0, 'ready': True, 'user_id': 3, > > > 'id': 1} > > > 2008-05-07 06:10:05,750 [DEBUG] koji.build.TaskManager: disk space > > > available in '/var/lib/mock': 43829 MB > > > 2008-05-07 06:10:06,186 [DEBUG] koji.build.TaskManager: Load Data: > > > 2008-05-07 06:10:06,186 [DEBUG] koji.build.TaskManager: hosts: > > > [{'capacity': 2.0, 'name': 'koji.bcstx.cacheflow.com', 'channels': [1, > > > 2], 'arches': 'i386 x86_64', 'task_load': 0.0, 'id': 1}] > > > 2008-05-07 06:10:06,187 [DEBUG] koji.build.TaskManager: tasks: [] > > > 2008-05-07 06:10:06,187 [DEBUG] koji.build.TaskManager: bins: > > > {'1:noarch': 1, '2:noarch': 1, '1:x86_64': 1, '1:i386': 1, '2:x86_64': > > > 1, '2:i386': 1} > > > > > > /var/log/kojid.log (after I start kojira): > > > 2008-05-07 06:10:21,504 [DEBUG] koji.build.TaskManager: Local > > > buildroots: 0 > > > 2008-05-07 06:10:21,505 [DEBUG] koji.build.TaskManager: Active > > > buildroots: 0 > > > 2008-05-07 06:10:21,505 [DEBUG] koji.build.TaskManager: Expired/stray > > > buildroots: 0 > > > 2008-05-07 06:10:21,818 [DEBUG] koji.build.TaskManager: Task Load: 0.0 > > > 2008-05-07 06:10:21,818 [DEBUG] koji.build.TaskManager: Current tasks: > > > {} > > > 2008-05-07 06:10:22,138 [DEBUG] koji.build.TaskManager: hostdata: > > > {'capacity': 2.0, 'name': 'koji.bcstx.cacheflow.com', 'enabled': True, > > > 'arches': 'i386 x86_64', 'task_load': 0.0, 'ready': True, 'user_id': 3, > > > 'id': 1} > > > 2008-05-07 06:10:22,145 [DEBUG] koji.build.TaskManager: disk space > > > available in '/var/lib/mock': 43829 MB > > > 2008-05-07 06:10:22,586 [DEBUG] koji.build.TaskManager: Load Data: > > > 2008-05-07 06:10:22,586 [DEBUG] koji.build.TaskManager: hosts: > > > [{'capacity': 2.0, 'name': 'koji.bcstx.cacheflow.com', 'channels': [1, > > > 2], 'arches': 'i386 x86_64', 'task_load': 0.0, 'id': 1}] > > > 2008-05-07 06:10:22,587 [DEBUG] koji.build.TaskManager: tasks: [] > > > 2008-05-07 06:10:22,587 [DEBUG] koji.build.TaskManager: bins: > > > {'1:noarch': 1, '2:noarch': 1, '1:x86_64': 1, '1:i386': 1, '2:x86_64': > > > 1, '2:i386': 1} > > > 2008-05-07 06:10:37,895 [ERROR] koji.build: Session expired > > > 2008-05-07 06:10:37,896 [WARNING] koji.build: Shutting down, please > > > wait... > > > > > > > > > /var/log/kojira.log: > > > 2008-05-07 06:10:25,519 [DEBUG] koji.repo.manager: Reading current repo > > > data > > > 2008-05-07 06:10:25,654 [DEBUG] koji.repo.manager: Repo data: [] > > > 2008-05-07 06:10:25,654 [DEBUG] koji.repo.manager: Scanning filesystem > > > for repos > > > > > > > > > > > > > > > -- > > > Fedora-buildsys-list mailing list > > > Fedora-buildsys-list at redhat.com > > > https://www.redhat.com/mailman/listinfo/fedora-buildsys-list > > > > -- > > Fedora-buildsys-list mailing list > > Fedora-buildsys-list at redhat.com > > https://www.redhat.com/mailman/listinfo/fedora-buildsys-list > From mikeb at redhat.com Wed May 7 20:50:17 2008 From: mikeb at redhat.com (Mike Bonnet) Date: Wed, 07 May 2008 16:50:17 -0400 Subject: koji.build: Session expired In-Reply-To: <1210192493.15042.33.camel@localhost.localdomain> References: <1210177495.15042.15.camel@localhost.localdomain> <1210177666.15042.18.camel@localhost.localdomain> <1210178780.3879.13.camel@localhost.localdomain> <1210192493.15042.33.camel@localhost.localdomain> Message-ID: <1210193417.3879.23.camel@localhost.localdomain> On Wed, 2008-05-07 at 15:34 -0500, Paul B Schroeder wrote: > Okay.. I *thought* I had it working, but now it's not. At the very > least, kojid doesn't appear to be shutting down anymore. Running kojira > with --verbose and --debug doesn't appear to be of much help. I see > these lines in the log file when starting kojira: > > 2008-05-07 10:28:24,540 [DEBUG] koji.repo.manager: Reading current repo > data > 2008-05-07 10:28:24,678 [DEBUG] koji.repo.manager: Repo data: [] > 2008-05-07 10:28:24,678 [DEBUG] koji.repo.manager: Scanning filesystem > for repos > > After starting, I then check to see if the process is running. But it's > not.. Any more clues? Try running it with --fg and see if you can get a traceback. > Thanks...Paul... > > > > On Wed, 2008-05-07 at 12:46 -0400, Mike Bonnet wrote: > > On Wed, 2008-05-07 at 11:27 -0500, Paul B Schroeder wrote: > > > Oh yea.. It should also be noted that I set this up using SSL > > > authentication, not kerberos.. > > > > > > Thanks again...Paul.. > > > > Are kojid and kojira using the same SSL cert for authentication? This > > would cause the problem you're seeing, as they would be sharing the same > > session, and when one of them logs out, the other would think it had > > been logged out as well. You need to use different SSL certs (with > > different CNs) for each user, including the daemons. > > > > > > > > On Wed, 2008-05-07 at 11:24 -0500, Paul B Schroeder wrote: > > > > Hello.. > > > > > > > > I'm running F8 with the latest koji-* packages: > > > > [root at koji koji]# rpm -qa 'koji*' > > > > koji-hub-1.2.2-2.fc8 > > > > koji-1.2.2-2.fc8 > > > > koji-utils-1.2.2-2.fc8 > > > > koji-web-1.2.2-2.fc8 > > > > koji-builder-1.2.2-2.fc8 > > > > > > > > I've been following the Koji Server HOWTO here: > > > > http://fedoraproject.org/wiki/Koji/ServerHowTo > > > > > > > > I've gotten all of the way through it, but I'm having issues when > > > > starting kojira. It doesn't stay running and it seems to somehow be > > > > causing kojid to shutdown as well. I've turned on debug for kojid and > > > > kojira. I see this in kojid.log: > > > > > > > > 2008-05-07 06:10:37,895 [ERROR] koji.build: Session expired > > > > 2008-05-07 06:10:37,896 [WARNING] koji.build: Shutting down, please > > > > wait... > > > > > > > > Below is a full output of what I see in those logs. Am I missing > > > > something simple? Anybody have any clue what's going wrong? > > > > > > > > Thanks in advance...Paul... > > > > > > > > > > > > /var/log/kojid.log (before I attempt to start kojira): > > > > 2008-05-07 06:10:04,662 [INFO] koji.build: Starting up > > > > 2008-05-07 06:10:05,125 [DEBUG] koji.build.TaskManager: Local > > > > buildroots: 0 > > > > 2008-05-07 06:10:05,125 [DEBUG] koji.build.TaskManager: Active > > > > buildroots: 0 > > > > 2008-05-07 06:10:05,126 [DEBUG] koji.build.TaskManager: Expired/stray > > > > buildroots: 0 > > > > 2008-05-07 06:10:05,438 [DEBUG] koji.build.TaskManager: Task Load: 0.0 > > > > 2008-05-07 06:10:05,438 [DEBUG] koji.build.TaskManager: Current tasks: > > > > {} > > > > 2008-05-07 06:10:05,743 [DEBUG] koji.build.TaskManager: hostdata: > > > > {'capacity': 2.0, 'name': 'koji.bcstx.cacheflow.com', 'enabled': True, > > > > 'arches': 'i386 x86_64', 'task_load': 0.0, 'ready': True, 'user_id': 3, > > > > 'id': 1} > > > > 2008-05-07 06:10:05,750 [DEBUG] koji.build.TaskManager: disk space > > > > available in '/var/lib/mock': 43829 MB > > > > 2008-05-07 06:10:06,186 [DEBUG] koji.build.TaskManager: Load Data: > > > > 2008-05-07 06:10:06,186 [DEBUG] koji.build.TaskManager: hosts: > > > > [{'capacity': 2.0, 'name': 'koji.bcstx.cacheflow.com', 'channels': [1, > > > > 2], 'arches': 'i386 x86_64', 'task_load': 0.0, 'id': 1}] > > > > 2008-05-07 06:10:06,187 [DEBUG] koji.build.TaskManager: tasks: [] > > > > 2008-05-07 06:10:06,187 [DEBUG] koji.build.TaskManager: bins: > > > > {'1:noarch': 1, '2:noarch': 1, '1:x86_64': 1, '1:i386': 1, '2:x86_64': > > > > 1, '2:i386': 1} > > > > > > > > /var/log/kojid.log (after I start kojira): > > > > 2008-05-07 06:10:21,504 [DEBUG] koji.build.TaskManager: Local > > > > buildroots: 0 > > > > 2008-05-07 06:10:21,505 [DEBUG] koji.build.TaskManager: Active > > > > buildroots: 0 > > > > 2008-05-07 06:10:21,505 [DEBUG] koji.build.TaskManager: Expired/stray > > > > buildroots: 0 > > > > 2008-05-07 06:10:21,818 [DEBUG] koji.build.TaskManager: Task Load: 0.0 > > > > 2008-05-07 06:10:21,818 [DEBUG] koji.build.TaskManager: Current tasks: > > > > {} > > > > 2008-05-07 06:10:22,138 [DEBUG] koji.build.TaskManager: hostdata: > > > > {'capacity': 2.0, 'name': 'koji.bcstx.cacheflow.com', 'enabled': True, > > > > 'arches': 'i386 x86_64', 'task_load': 0.0, 'ready': True, 'user_id': 3, > > > > 'id': 1} > > > > 2008-05-07 06:10:22,145 [DEBUG] koji.build.TaskManager: disk space > > > > available in '/var/lib/mock': 43829 MB > > > > 2008-05-07 06:10:22,586 [DEBUG] koji.build.TaskManager: Load Data: > > > > 2008-05-07 06:10:22,586 [DEBUG] koji.build.TaskManager: hosts: > > > > [{'capacity': 2.0, 'name': 'koji.bcstx.cacheflow.com', 'channels': [1, > > > > 2], 'arches': 'i386 x86_64', 'task_load': 0.0, 'id': 1}] > > > > 2008-05-07 06:10:22,587 [DEBUG] koji.build.TaskManager: tasks: [] > > > > 2008-05-07 06:10:22,587 [DEBUG] koji.build.TaskManager: bins: > > > > {'1:noarch': 1, '2:noarch': 1, '1:x86_64': 1, '1:i386': 1, '2:x86_64': > > > > 1, '2:i386': 1} > > > > 2008-05-07 06:10:37,895 [ERROR] koji.build: Session expired > > > > 2008-05-07 06:10:37,896 [WARNING] koji.build: Shutting down, please > > > > wait... > > > > > > > > > > > > /var/log/kojira.log: > > > > 2008-05-07 06:10:25,519 [DEBUG] koji.repo.manager: Reading current repo > > > > data > > > > 2008-05-07 06:10:25,654 [DEBUG] koji.repo.manager: Repo data: [] > > > > 2008-05-07 06:10:25,654 [DEBUG] koji.repo.manager: Scanning filesystem > > > > for repos > > > > > > > > > > > > > > > > > > > > -- > > > > Fedora-buildsys-list mailing list > > > > Fedora-buildsys-list at redhat.com > > > > https://www.redhat.com/mailman/listinfo/fedora-buildsys-list > > > > > > -- > > > Fedora-buildsys-list mailing list > > > Fedora-buildsys-list at redhat.com > > > https://www.redhat.com/mailman/listinfo/fedora-buildsys-list > > From paul.schroeder at bluecoat.com Wed May 7 20:57:47 2008 From: paul.schroeder at bluecoat.com (Paul B Schroeder) Date: Wed, 07 May 2008 15:57:47 -0500 Subject: koji.build: Session expired In-Reply-To: <1210193417.3879.23.camel@localhost.localdomain> References: <1210177495.15042.15.camel@localhost.localdomain> <1210177666.15042.18.camel@localhost.localdomain> <1210178780.3879.13.camel@localhost.localdomain> <1210192493.15042.33.camel@localhost.localdomain> <1210193417.3879.23.camel@localhost.localdomain> Message-ID: <1210193867.15042.40.camel@localhost.localdomain> On Wed, 2008-05-07 at 16:50 -0400, Mike Bonnet wrote: > On Wed, 2008-05-07 at 15:34 -0500, Paul B Schroeder wrote: > > Okay.. I *thought* I had it working, but now it's not. At the very > > least, kojid doesn't appear to be shutting down anymore. Running kojira > > with --verbose and --debug doesn't appear to be of much help. I see > > these lines in the log file when starting kojira: > > > > 2008-05-07 10:28:24,540 [DEBUG] koji.repo.manager: Reading current repo > > data > > 2008-05-07 10:28:24,678 [DEBUG] koji.repo.manager: Repo data: [] > > 2008-05-07 10:28:24,678 [DEBUG] koji.repo.manager: Scanning filesystem > > for repos > > > > After starting, I then check to see if the process is running. But it's > > not.. Any more clues? > > Try running it with --fg and see if you can get a traceback. > Ah.. Yea.. Duh.. Somehow I missed that flag. Output below.. I created /mnt/koji/repos and it's definitely running now. Thanks...Paul... [root at koji koji]# kojira --force-lock --debug --verbose -c /etc/kojira/kojira.conf --fg 2008-05-07 10:47:32,264 [DEBUG] {19989} koji.repo.manager:179 Reading current repo data 2008-05-07 10:47:32,578 [DEBUG] {19989} koji.repo.manager:181 Repo data: [] 2008-05-07 10:47:32,578 [DEBUG] {19989} koji.repo.manager:200 Scanning filesystem for repos Traceback (most recent call last): File "/usr/sbin/kojira", line 497, in main() File "/usr/sbin/kojira", line 323, in main repomgr.pruneLocalRepos() File "/usr/sbin/kojira", line 203, in pruneLocalRepos for tag in os.listdir(topdir): OSError: [Errno 2] No such file or directory: '/mnt/koji/repos' From mikem at redhat.com Wed May 7 21:25:08 2008 From: mikem at redhat.com (Mike McLean) Date: Wed, 07 May 2008 17:25:08 -0400 Subject: koji.build: Session expired In-Reply-To: <1210193867.15042.40.camel@localhost.localdomain> References: <1210177495.15042.15.camel@localhost.localdomain> <1210177666.15042.18.camel@localhost.localdomain> <1210178780.3879.13.camel@localhost.localdomain> <1210192493.15042.33.camel@localhost.localdomain> <1210193417.3879.23.camel@localhost.localdomain> <1210193867.15042.40.camel@localhost.localdomain> Message-ID: <48221E34.3080303@redhat.com> Paul B Schroeder wrote: > Traceback (most recent call last): > File "/usr/sbin/kojira", line 497, in > main() > File "/usr/sbin/kojira", line 323, in main > repomgr.pruneLocalRepos() > File "/usr/sbin/kojira", line 203, in pruneLocalRepos > for tag in os.listdir(topdir): > OSError: [Errno 2] No such file or directory: '/mnt/koji/repos' kojira requires write access to your file store so that it can delete old, expired repos. You can either run it on the same machine as the hub or a different machine which has that filesystem somehow exported to it. If this is already the case, you may just need to specify topdir in kojira's config or make a symlink. From paul.schroeder at bluecoat.com Wed May 7 23:39:46 2008 From: paul.schroeder at bluecoat.com (Paul B Schroeder) Date: Wed, 07 May 2008 18:39:46 -0500 Subject: koji.build: Session expired In-Reply-To: <48221E34.3080303@redhat.com> References: <1210177495.15042.15.camel@localhost.localdomain> <1210177666.15042.18.camel@localhost.localdomain> <1210178780.3879.13.camel@localhost.localdomain> <1210192493.15042.33.camel@localhost.localdomain> <1210193417.3879.23.camel@localhost.localdomain> <1210193867.15042.40.camel@localhost.localdomain> <48221E34.3080303@redhat.com> Message-ID: <1210203586.21939.10.camel@localhost.localdomain> On Wed, 2008-05-07 at 17:25 -0400, Mike McLean wrote: > Paul B Schroeder wrote: > > Traceback (most recent call last): > > File "/usr/sbin/kojira", line 497, in > > main() > > File "/usr/sbin/kojira", line 323, in main > > repomgr.pruneLocalRepos() > > File "/usr/sbin/kojira", line 203, in pruneLocalRepos > > for tag in os.listdir(topdir): > > OSError: [Errno 2] No such file or directory: '/mnt/koji/repos' > > kojira requires write access to your file store so that it can delete > old, expired repos. You can either run it on the same machine as the hub > or a different machine which has that filesystem somehow exported to it. > > If this is already the case, you may just need to specify topdir in > kojira's config or make a symlink. I'm running all of this on one system for now. So it's not an issue yet. I've made "apache" the owner of /mnt/koji and everything below it so I could import packages. But that doesn't feel right though. I suppose I could/should run the web server as kojibuilder? From mikem at redhat.com Thu May 8 15:08:27 2008 From: mikem at redhat.com (Mike McLean) Date: Thu, 08 May 2008 11:08:27 -0400 Subject: koji.build: Session expired In-Reply-To: <1210203586.21939.10.camel@localhost.localdomain> References: <1210177495.15042.15.camel@localhost.localdomain> <1210177666.15042.18.camel@localhost.localdomain> <1210178780.3879.13.camel@localhost.localdomain> <1210192493.15042.33.camel@localhost.localdomain> <1210193417.3879.23.camel@localhost.localdomain> <1210193867.15042.40.camel@localhost.localdomain> <48221E34.3080303@redhat.com> <1210203586.21939.10.camel@localhost.localdomain> Message-ID: <4823176B.8090709@redhat.com> Paul B Schroeder wrote: >> If this is already the case, you may just need to specify topdir in >> kojira's config or make a symlink. > > I'm running all of this on one system for now. So it's not an issue > yet. So does /mnt/koji/repos not exist? > I've made "apache" the owner of /mnt/koji and everything below it so I > could import packages. But that doesn't feel right though. I suppose I > could/should run the web server as kojibuilder? I usually just use the apache user. From paul.schroeder at bluecoat.com Thu May 8 16:02:14 2008 From: paul.schroeder at bluecoat.com (Paul B Schroeder) Date: Thu, 08 May 2008 11:02:14 -0500 Subject: koji.build: Session expired In-Reply-To: <4823176B.8090709@redhat.com> References: <1210177495.15042.15.camel@localhost.localdomain> <1210177666.15042.18.camel@localhost.localdomain> <1210178780.3879.13.camel@localhost.localdomain> <1210192493.15042.33.camel@localhost.localdomain> <1210193417.3879.23.camel@localhost.localdomain> <1210193867.15042.40.camel@localhost.localdomain> <48221E34.3080303@redhat.com> <1210203586.21939.10.camel@localhost.localdomain> <4823176B.8090709@redhat.com> Message-ID: <1210262535.21939.26.camel@localhost.localdomain> On Thu, 2008-05-08 at 11:08 -0400, Mike McLean wrote: > Paul B Schroeder wrote: > >> If this is already the case, you may just need to specify topdir in > >> kojira's config or make a symlink. > > > > I'm running all of this on one system for now. So it's not an issue > > yet. > > So does /mnt/koji/repos not exist? I created it without much thought of who should own it (or where topdir should be for our environment). That's what led to the question below. > > > I've made "apache" the owner of /mnt/koji and everything below it so I > > could import packages. But that doesn't feel right though. I suppose I > > could/should run the web server as kojibuilder? > > I usually just use the apache user. A short blurb on this might be worth a mention in the HOWTOs... I'll likely do all of this again once I sort things out here. If I have time, I'll see what I can contribute to the HOWTO. Thanks...Paul... From paul.schroeder at bluecoat.com Thu May 8 21:09:38 2008 From: paul.schroeder at bluecoat.com (Paul B Schroeder) Date: Thu, 08 May 2008 16:09:38 -0500 Subject: koji add-group? Message-ID: <1210280978.21939.33.camel@localhost.localdomain> Hmm.. Strange.. I don't seem to have the add-group command (see further below). I had to do this via psql to be able to "koji add-group-pkg": koji=> insert into groups (name) values('build'); INSERT 0 1 koji=> select * from groups; id | name ----+------- 1 | build (1 row) koji=> insert into group_config (group_id, tag_id, display_name) values(1, 2, 'build'); INSERT 0 1 koji=> select * from group_config; group_id | tag_id | blocked | exported | display_name | is_default | uservisible | description | langonly | biarchonly | create_event | revoke_event | active ----------+--------+---------+----------+--------------+------------+-------------+-------------+----------+------------+--------------+--------------+-------- 1 | 2 | f | t | build | | | | | | 3413 | | t (1 row) koji=> select * from group_package_listing; group_id | tag_id | package | blocked | type | basearchonly | requires | create_event | revoke_event | active ----------+--------+---------+---------+---------+--------------+----------+--------------+--------------+-------- 1 | 2 | bash | f | default | | | 3414 | | t (1 row) ---------------------------------------------- [root at koji koji]# rpm -q koji koji-1.2.2-2.fc8 [root at koji koji]# koji add-group --help Available commands: build Build a package from source buildinfo Print basic information about a build cancel Cancel tasks and/or builds chain-build Build one or more packages from source download-build Download a built package help List available commands latest-pkg Print the latest packages for a tag list-api Print the list of XML-RPC APIs list-buildroot List the rpms used in or built in a buildroot list-groups Print the group listings list-hosts Print the host listing list-pkgs Print the package listing for tag or for owner list-tag-history Print a history of tag operations list-tag-inheritance Print the inheritance information for a tag list-tagged List the builds or rpms in a tag list-tags Print the list of tags list-targets List the build targets list-tasks Print the list of tasks list-untagged List untagged builds mock-config Create a mock config move-pkg 'Move' one or more packages between tags resubmit Retry a canceled or failed task, using the same parameter as the original task. rpminfo Print basic information about an RPM show-groups Show groups data for a tag tag-pkg Apply a tag to one or more packages taginfo Print basic information about a tag taskinfo Show information about a task untag-pkg Remove a tag from one or more packages watch-logs Watch logs in realtime watch-task Track progress of particular tasks (Type "koji --help" for help about global options or "koji --help" for help about a particular command's options.) Usage: koji [global-options] command [command-options-and-arguments] koji: error: Unknown command: add_group From mikeb at redhat.com Thu May 8 22:16:18 2008 From: mikeb at redhat.com (Mike Bonnet) Date: Thu, 08 May 2008 18:16:18 -0400 Subject: koji add-group? In-Reply-To: <1210280978.21939.33.camel@localhost.localdomain> References: <1210280978.21939.33.camel@localhost.localdomain> Message-ID: <1210284978.4408.50.camel@burren.bos.redhat.com> On Thu, 2008-05-08 at 16:09 -0500, Paul B Schroeder wrote: > Hmm.. Strange.. I don't seem to have the add-group command (see > further below). I had to do this via psql to be able to "koji > add-group-pkg": > > koji=> insert into groups (name) values('build'); > INSERT 0 1 > koji=> select * from groups; > id | name > ----+------- > 1 | build > (1 row) > koji=> insert into group_config (group_id, tag_id, display_name) > values(1, 2, 'build'); > INSERT 0 1 > koji=> select * from group_config; > group_id | tag_id | blocked | exported | display_name | is_default | > uservisible | description | langonly | biarchonly | create_event | > revoke_event | active > ----------+--------+---------+----------+--------------+------------+-------------+-------------+----------+------------+--------------+--------------+-------- > 1 | 2 | f | t | build | | > | | | | 3413 | | t > (1 row) > > koji=> select * from group_package_listing; > group_id | tag_id | package | blocked | type | basearchonly | > requires | create_event | revoke_event | active > ----------+--------+---------+---------+---------+--------------+----------+--------------+--------------+-------- > 1 | 2 | bash | f | default | | > | 3414 | | t > (1 row) > > > ---------------------------------------------- > > > [root at koji koji]# rpm -q koji > koji-1.2.2-2.fc8 > > [root at koji koji]# koji add-group --help > Available commands: > build Build a package from source > buildinfo Print basic information about a build > cancel Cancel tasks and/or builds > chain-build Build one or more packages from source > download-build Download a built package > help List available commands > latest-pkg Print the latest packages for a tag > list-api Print the list of XML-RPC APIs > list-buildroot List the rpms used in or built in a > buildroot > list-groups Print the group listings > list-hosts Print the host listing > list-pkgs Print the package listing for tag or for > owner > list-tag-history Print a history of tag operations > list-tag-inheritance Print the inheritance information for a tag > list-tagged List the builds or rpms in a tag > list-tags Print the list of tags > list-targets List the build targets > list-tasks Print the list of tasks > list-untagged List untagged builds > mock-config Create a mock config > move-pkg 'Move' one or more packages between tags > resubmit Retry a canceled or failed task, using the > same parameter as the original task. > rpminfo Print basic information about an RPM > show-groups Show groups data for a tag > tag-pkg Apply a tag to one or more packages > taginfo Print basic information about a tag > taskinfo Show information about a task > untag-pkg Remove a tag from one or more packages > watch-logs Watch logs in realtime > watch-task Track progress of particular tasks > (Type "koji --help" for help about global options > or "koji --help" for help about a particular command's > options.) > Usage: koji [global-options] command [command-options-and-arguments] > > koji: error: Unknown command: add_group That must have been added to koji-1.2.3. You can grab it from http://koji.fedoraproject.org/koji/buildinfo?buildID=28165 . It should work fine on F8. From mikem at redhat.com Thu May 8 22:22:50 2008 From: mikem at redhat.com (Mike McLean) Date: Thu, 08 May 2008 18:22:50 -0400 Subject: koji add-group? In-Reply-To: <1210280978.21939.33.camel@localhost.localdomain> References: <1210280978.21939.33.camel@localhost.localdomain> Message-ID: <48237D3A.5030102@redhat.com> Paul B Schroeder wrote: > Hmm.. Strange.. I don't seem to have the add-group command (see > further below). I had to do this via psql to be able to "koji > add-group-pkg": The add-group cli command was added in git almost a year ago. However, the stock koji build in the F8 repos is really, really old. As mikeb pointed out you can pull a later koji build from the koji.fp.o. Optionally, you could just build it yourself from a git clone. If you don't want /quite/ the bleeding edge, you could build from the koji-1.2.5-1.fc8 tag. > koji=> insert into groups (name) values('build'); > INSERT 0 Even if your cli doesn't have the add-group command, the hub still has the call. Rather than muck around in the db, you could have just run: $ koji call groupListAdd > [root at koji koji]# rpm -q koji > koji-1.2.2-2.fc8 yep. old, old, old. From enrico.scholz at informatik.tu-chemnitz.de Sun May 11 16:51:15 2008 From: enrico.scholz at informatik.tu-chemnitz.de (Enrico Scholz) Date: Sun, 11 May 2008 18:51:15 +0200 Subject: [MOCK/PATCH] Make logging line-buffered Message-ID: <1210524675-2687-1-git-send-email-enrico.scholz@informatik.tu-chemnitz.de> Current output processing reads data and puts them to logging without taking care about eol. This produces ugly and unreadable output like | checking whether to enable maintainer-specific portions of Makefiles... | no | checking build system type... | i386-redhat-linux-gnu Patch reads output into a buffer which is given to logging after a newline. Signed-off-by: Enrico Scholz --- py/mock/util.py | 46 +++++++++++++++++++++++++++++++++++----------- 1 files changed, 35 insertions(+), 11 deletions(-) diff --git a/py/mock/util.py b/py/mock/util.py index 9f0eb3a..6e3d88e 100644 --- a/py/mock/util.py +++ b/py/mock/util.py @@ -225,33 +225,57 @@ def condPersonality(per=None): def logOutput(fds, logger, returnOutput=1, start=0, timeout=0): output="" done = 0 + input = {} # set all fds to nonblocking for fd in fds: + input[fd] = '' flags = fcntl.fcntl(fd, fcntl.F_GETFL) if not fd.closed: fcntl.fcntl(fd, fcntl.F_SETFL, flags| os.O_NONBLOCK) while not done: - if (time.time() - start)>timeout and timeout!=0: + if timeout!=0 and (time.time() - start)>timeout: done = 1 break - i_rdy,o_rdy,e_rdy = select.select(fds,[],[],1) + i_rdy,o_rdy,e_rdy = select.select(fds,[],[],1) for s in i_rdy: # slurp as much input as is ready - input = s.read() - if input == "": + inp = s.read() + if inp == "": done = 1 break - if logger is not None: - for line in input.split("\n"): - if line == '': continue - logger.debug(chomp(line)) - for h in logger.handlers: - h.flush() + if returnOutput: - output += input + output += inp + + if logger is None: + continue + + assert('\n' not in input[s]) + input[s] += inp + if '\n' not in inp: + continue + + lines = input[s].split("\n") + input[s] = lines[len(lines)-1] + del lines[len(lines)-1] + + for line in lines: + if line == '': continue + logger.debug(chomp(line)) + for h in logger.handlers: + h.flush() + + if logger is not None: + for fd in fds: + if input[s]=='': continue + logger.debug(chomp(input[s])) + + for h in logger.handlers: + h.flush() + return output # logger = -- 1.5.4.1 From kanarip at kanarip.com Mon May 12 20:54:27 2008 From: kanarip at kanarip.com (Jeroen van Meeuwen) Date: Mon, 12 May 2008 22:54:27 +0200 Subject: [PATCH] Add anaconda-runtime to the package list for buildinstall In-Reply-To: <1208785697.3258.5.camel@localhost.localdomain> References: <1208766929-19553-1-git-send-email-markmc@redhat.com> <480C5635.5050605@kanarip.com> <1208776324.3445.133.camel@localhost.localdomain> <480C7E1A.9060509@kanarip.com> <1208785697.3258.5.camel@localhost.localdomain> Message-ID: <4828AE83.6080607@kanarip.com> Jesse Keating wrote: > On Mon, 2008-04-21 at 13:44 +0200, Jeroen van Meeuwen wrote: >> Or were you thinking something else? > [...snip...] > That's the fairly rough overview. > Revisiting this topic; I've got this implemented differently right now; I'm pointing buildinstall to one or more of the enabled repositories configured, as it's just using yum with a configuration file that can perfectly point at baseurls and mirrorlists. This does require some modifications to buildinstall though, and I'm not sure whether the anaconda guys would even consider it. Attached is a the modified buildinstall script taking multiple --repo parameters (currently only taking baseurls though). Kind regards, Jeroen van Meeuwen -kanarip -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: F9-buildinstall URL: From jkeating at redhat.com Mon May 12 21:01:50 2008 From: jkeating at redhat.com (Jesse Keating) Date: Mon, 12 May 2008 17:01:50 -0400 Subject: [PATCH] Add anaconda-runtime to the package list for buildinstall In-Reply-To: <4828AE83.6080607@kanarip.com> References: <1208766929-19553-1-git-send-email-markmc@redhat.com> <480C5635.5050605@kanarip.com> <1208776324.3445.133.camel@localhost.localdomain> <480C7E1A.9060509@kanarip.com> <1208785697.3258.5.camel@localhost.localdomain> <4828AE83.6080607@kanarip.com> Message-ID: <1210626110.24771.0.camel@localhost.localdomain> On Mon, 2008-05-12 at 22:54 +0200, Jeroen van Meeuwen wrote: > Revisiting this topic; > > I've got this implemented differently right now; I'm pointing > buildinstall to one or more of the enabled repositories configured, as > it's just using yum with a configuration file that can perfectly point > at baseurls and mirrorlists. This does require some modifications to > buildinstall though, and I'm not sure whether the anaconda guys would > even consider it. > > Attached is a the modified buildinstall script taking multiple --repo > parameters (currently only taking baseurls though). Didn't Will Woods submit a patch shortly after I posted this that allowed for passing multiple repos to buildinstall? -- Jesse Keating Fedora -- Freedom? is a feature! -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From kanarip at kanarip.com Mon May 12 21:12:41 2008 From: kanarip at kanarip.com (Jeroen van Meeuwen) Date: Mon, 12 May 2008 23:12:41 +0200 Subject: [PATCH] Add anaconda-runtime to the package list for buildinstall In-Reply-To: <1210626110.24771.0.camel@localhost.localdomain> References: <1208766929-19553-1-git-send-email-markmc@redhat.com> <480C5635.5050605@kanarip.com> <1208776324.3445.133.camel@localhost.localdomain> <480C7E1A.9060509@kanarip.com> <1208785697.3258.5.camel@localhost.localdomain> <4828AE83.6080607@kanarip.com> <1210626110.24771.0.camel@localhost.localdomain> Message-ID: <4828B2C9.2060103@kanarip.com> Jesse Keating wrote: > On Mon, 2008-05-12 at 22:54 +0200, Jeroen van Meeuwen wrote: >> Revisiting this topic; >> >> I've got this implemented differently right now; I'm pointing >> buildinstall to one or more of the enabled repositories configured, as >> it's just using yum with a configuration file that can perfectly point >> at baseurls and mirrorlists. This does require some modifications to >> buildinstall though, and I'm not sure whether the anaconda guys would >> even consider it. >> >> Attached is a the modified buildinstall script taking multiple --repo >> parameters (currently only taking baseurls though). > > Didn't Will Woods submit a patch shortly after I posted this that > allowed for passing multiple repos to buildinstall? > You're right, he did, on the anaconda-devel list. I've missed it ;-) Kind regards, Jeroen van Meeuwen -kanarip From katzj at redhat.com Mon May 12 21:13:10 2008 From: katzj at redhat.com (Jeremy Katz) Date: Mon, 12 May 2008 17:13:10 -0400 Subject: [PATCH] Add anaconda-runtime to the package list for buildinstall In-Reply-To: <4828B2C9.2060103@kanarip.com> References: <1208766929-19553-1-git-send-email-markmc@redhat.com> <480C5635.5050605@kanarip.com> <1208776324.3445.133.camel@localhost.localdomain> <480C7E1A.9060509@kanarip.com> <1208785697.3258.5.camel@localhost.localdomain> <4828AE83.6080607@kanarip.com> <1210626110.24771.0.camel@localhost.localdomain> <4828B2C9.2060103@kanarip.com> Message-ID: <1210626790.20164.43.camel@aglarond.local> On Mon, 2008-05-12 at 23:12 +0200, Jeroen van Meeuwen wrote: > Jesse Keating wrote: > > On Mon, 2008-05-12 at 22:54 +0200, Jeroen van Meeuwen wrote: > >> Revisiting this topic; > >> > >> I've got this implemented differently right now; I'm pointing > >> buildinstall to one or more of the enabled repositories configured, as > >> it's just using yum with a configuration file that can perfectly point > >> at baseurls and mirrorlists. This does require some modifications to > >> buildinstall though, and I'm not sure whether the anaconda guys would > >> even consider it. > >> > >> Attached is a the modified buildinstall script taking multiple --repo > >> parameters (currently only taking baseurls though). > > > > Didn't Will Woods submit a patch shortly after I posted this that > > allowed for passing multiple repos to buildinstall? > > > > You're right, he did, on the anaconda-devel list. I've missed it ;-) And fwiw, I applied the patch to anaconda master about 30 or 45 minutes ago :) Jeremy From jkeating at redhat.com Fri May 16 20:51:39 2008 From: jkeating at redhat.com (Jesse Keating) Date: Fri, 16 May 2008 16:51:39 -0400 Subject: Koji 1.3 release Message-ID: <1210971099.4060.34.camel@localhost.localdomain> I've revived the 1.3 milestone in the Koji Trac space ( https://fedorahosted.org/koji/milestone/1.3 ) and triaged all the existing Trac tickets and bugzillas against koji. I've added what I thought was appropriate to target for a 1.3 release in the near future (next 3~ weeks?). Please review and make sure what I've put on there is sane and add anything else reasonable to target for the next couple releases. I hope to get all the code committed in the next couple weeks, freeze/branch the source control and do some release testing and finally make a release for rawhide, F8/F9 updates, and perhaps even EPEL5. -- Jesse Keating Fedora -- Freedom? is a feature! -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From belegdol at gmail.com Wed May 28 07:01:20 2008 From: belegdol at gmail.com (Julian Sikorski) Date: Wed, 28 May 2008 09:01:20 +0200 Subject: Patch adding rpmbuild -bi to makefile.common Message-ID: <483D0340.4000803@gmail.com> Hello, this patch the install target to makefile common, completing the set of possible options. Julian P.S. Please CC me, I'm not subscribed. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: Makefile.common-install.patch URL: From wdierkes at 5dollarwhitebox.org Wed May 28 14:53:23 2008 From: wdierkes at 5dollarwhitebox.org (BJ Dierkes) Date: Wed, 28 May 2008 09:53:23 -0500 Subject: Koji server installation In-Reply-To: <23E35216F25BB24EADD5BD0D7BFA341171F4698F3D@G3W1112.americas.hpqcorp.net> References: <23E35216F25BB24EADD5BD0D7BFA341171F4698F3D@G3W1112.americas.hpqcorp.net> Message-ID: On Nov 15, 2007, at 10:17 AM, Degremont, Guillaume wrote: > > I am having some troubles deploying koji. The only document I have > found is the ServerHowTo (http://fedoraproject.org/wiki/Koji/ServerHowTo > ). Guillaume, I completely feel your pain, the first time I tried to setup Koji was a bit of hell due to the lack of documentation and proper 'howtos'. I haven't been using Koji for a while, and have only installed it twice so please excuse any ignorance on my part. That said: > However, when I try to use koji, I get the following error: > > [koji at murray ~]$ koji add-user userTest > Kerberos authentication failed: 'No credentials cache > found' (-1765328189) > [koji at murray ~]$ In the HowTo, did you follow the steps about creating the users/ passwords in PostGreSQL database directly, and getting PostGreSQL up and running? Last I used Koji the utilities did not handle adding users, so those operations have do be done via SQL within PostGres. > > > I have modified the /etc/koji.conf (though it is not mentioned in > the How To) as follows, to ensure it will use SSL: > > [root at murray ~]# more /etc/koji.conf > [koji] > ;configuration for koji cli tool > ;url of XMLRPC server > server = http://murray.mysite.hp.com/kojihub > ... Being that it is SSL, shouldn't these url addresses start with https:// rather than http://? Again, forgive me as I haven't setup Koji in a long time. > > My other problem is with the servers. I configured my apache and > started it to have the kojihub and kojiweb started. > I then want to perform some add--user, add-host commands. But I get > the message "unable to connect to server". 1) I know you mentioned that the w.x.y.z IP Addresses were replaced here in your email with dummy ones, same for hostnames. However, being that you are running everything on the same box, you may wish to consider using 'localhost'. For one, if this server is NATd or behind a firefall (on private IPs) then using the real IP/Hostname may not work for you. It would be best to use localhost, or the Primary IP that is configured on ETH0. Additionally, if you are using hostnames you want to verify that the hostname is resolving to the IP that is configured on the NIC (not necessary the IP that the hostname should point to publicly). Meaning if you are on a private network ensure that /etc/hosts is configured properly. > > > [root at murray ~]# koji --noauth add-host murray.mysite.hp.com i386 > x86_64 > Error: Unable to connect to server > > With the following logs from httpd: > [Thu Nov 15 10:28:51 2007] [error] [client X.X.X.X] PythonHandler > kojixmlrpc: Traceback (most recent call last): > [Thu Nov 15 10:28:51 2007] [error] [client X.X.X.X] PythonHandler > kojixmlrpc: File "/usr/lib/python2.4/site-packages/mod_python/ > apache.py", line 299, in HandlerDispatch\n result = object(req) > [Thu Nov 15 10:28:51 2007] [error] [client X.X.X.X] PythonHandler > kojixmlrpc: File "/usr/share/koji-hub/kojixmlrpc.py", line 278, in > handler\n context.cnx = > koji.db.connect(opts.get("KojiDebug",False)) > [Thu Nov 15 10:28:51 2007] [error] [client X.X.X.X] PythonHandler > kojixmlrpc: File "/usr/lib/python2.4/site-packages/koji/db.py", > line 128, in connect\n conn = pgdb.connect(**opts) > [Thu Nov 15 10:28:51 2007] [error] [client X.X.X.X] PythonHandler > kojixmlrpc: File "/usr/lib/python2.4/site-packages/pgdb.py", line > 383, in connect\n dbtty, dbuser, dbpasswd) > [Thu Nov 15 10:28:51 2007] [error] [client X.X.X.X] PythonHandler > kojixmlrpc: InternalError: could not connect to server: Connection > refused\n\tIs the server running on host "murray.mysite.hp.com" and > accepting\n\tTCP/IP connections on port 5432?\n > > > Do you know what it comes from ? Looking at the apache log entries it really looks like the issue is with the PostGreSQL server. Note the last log entry: > [Thu Nov 15 10:28:51 2007] [error] [client X.X.X.X] PythonHandler > kojixmlrpc: InternalError: could not connect to server: Connection > refused\n\tIs the server running on host "murray.mysite.hp.com" and > accepting\n\tTCP/IP connections on port 5432?\n Can you verify that PostGreSQL is running on host 'murrar.mysite.hp.com' (and that the address is resolvable and accessible just as stated.... meaning from the box that is running the web frontends, can you ping the server (this goes back to the last stuff I was mentioning about 'localhost' etc. Good luck. BJ -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.schroeder at bluecoat.com Sat May 31 23:04:29 2008 From: paul.schroeder at bluecoat.com (Paul B Schroeder) Date: Sat, 31 May 2008 18:04:29 -0500 Subject: corrupt rpmdb in mock-chroot Message-ID: <1212275069.3635.62.camel@localhost.localdomain> Hello all... On my x86_64 (CentOS 5.1) system I use mock to init an i386 chroot for both Fedora 8 and CentOS 5.1. The init appears to work fine, but when I drop into a mock-shell for either F8 or CentOS my rpm database is corrupt on both accounts: mock-chroot> rpm -qa rpmdb: Program version 4.3 doesn't match environment version error: db4 error(-30974) from dbenv->open: DB_VERSION_MISMATCH: Database environment version mismatch error: cannot open Packages index using db3 - (-30974) error: cannot open Packages database in /var/lib/rpm Rebuilding the rpm database seems to fix this, but it's a pain to be sure. Any ideas as to why I'm seeing this corruption when creating an i386 mock chroot from a x86_64 system? Also, FYI, when I do this for x86_64 chroots or if I do this from my i386 CentOS system, the rpm database does not get corrupt. Thanks...Paul...