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@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@redhat.com https://www.redhat.com/mailman/listinfo/fedora-buildsys-list

-- Fedora-buildsys-list mailing list Fedora-buildsys-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-buildsys-list

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@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@redhat.com https://www.redhat.com/mailman/listinfo/fedora-buildsys-list

-- Fedora-buildsys-list mailing list Fedora-buildsys-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-buildsys-list

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@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 <module> 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'

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 <module> 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?

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...