koji-web 1.7 issues
 

I upgraded a F16 64-bit box from Koji 1.6.0 to 1.7.0 today. I used the
1.7.0 conf files as a template and replaced the default URLs with my
server's URLs (so I am using WSGI).

When I attempt to use the web interface I am having issues with
"Internal Server Error" messages popping up.

Example:
-Browse to foo.example.com/koji. Web page displays fine.
-Click on "Packages" link on the top header and "Internal Server Error"
is displayed.
-Click Back button. Click on "Builds" link and it displays fine.
-Click on "Packages" from "Builds" page and it displays fine.
-Click on "Summary" from "Packages" page and "Internal Server Error" is
displayed.

This same behavior occurs (in different steps) with the other links at
the top of the koji web interface.

My apache logs show python is failing to connect to some service when
the "Internal Server Error" occurs:
[snip Python traceback]
[Mon Jul 09 11:59:11 2012] [error] [client 172.17.100.41] gaierror:
[Errno -2] Name or service not known, referer:
http://foo.example.com/koji/packages

My /etc/kojiweb/web.conf file is pointing to the right URLs. I don't see
anything else wrong. Anything I might have missed?

Thanks,
Michael
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys

koji-web 1.7 issues
 

Michael Cronenworth wrote:
> My /etc/kojiweb/web.conf file is pointing to the right URLs. I don't see
> anything else wrong. Anything I might have missed?

I forgot to add these things I've tried:
-Restarted Apache
-Cleared Firefox cache

Also: The "Internal Server Error" page is not always displayed.
Sometimes clicking on "Packages" works. Other times clicking "Back" and
trying again works. *scratches head*
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys

koji-web 1.7 issues
 

On Mon, Jul 9, 2012 at 2:09 PM, Michael Cronenworth <mike@cchtml.com> wrote:


Michael Cronenworth wrote:

> My /etc/kojiweb/web.conf file is pointing to the right URLs. I don't see

> anything else wrong. Anything I might have missed?



I forgot to add these things I've tried:

-Restarted Apache

-Cleared Firefox cache



Also: The "Internal Server Error" page is not always displayed.

Sometimes clicking on "Packages" works. Other times clicking "Back" and

trying again works. *scratches head*
Just last week I had a similar issue here and turned out our DNS resolution was really flaky.
--
Giovanni



--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys

koji-web 1.7 issues
 

Giovanni Tirloni wrote:
> Just last week I had a similar issue here and turned out our DNS
> resolution was really flaky.

Unfortunately I can rule that out. The DNS server runs on the same box
and the address used for all koji conf files is listed in the /etc/hosts
file so no DNS resolution issue there.

I can easily duplicate the problem now by simply refreshing any koji web
page. After a few times I will hit "Internal Server Error". Another
refresh and I see the page. Rinse and repeat. It seems like a koji bug.

--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys

koji-web 1.7 issues
 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 09 Jul 2012 14:25:43 -0500
Michael Cronenworth <mike@cchtml.com> wrote:

> Giovanni Tirloni wrote:
> > Just last week I had a similar issue here and turned out our DNS
> > resolution was really flaky.
>
> Unfortunately I can rule that out. The DNS server runs on the same box
> and the address used for all koji conf files is listed in
> the /etc/hosts file so no DNS resolution issue there.
>
> I can easily duplicate the problem now by simply refreshing any koji
> web page. After a few times I will hit "Internal Server Error".
> Another refresh and I see the page. Rinse and repeat. It seems like a
> koji bug.

I really think that it is something in your environment.
koji.fedoraproject.org is running 1.7.0 using mod_wsgi and not seeing
the issue you are reporting. are you sure you switched both the koji
hub and koji web to mod_wsgi?

Dennis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)

iEYEARECAAYFAk/8j5gACgkQkSxm47BaWfeS9gCeK0wBqXcXWehbNOBuNDpIYigj
nYgAoI4YbasUu0BlX2d5l7AMj/BvF4wp
=EcaL
-----END PGP SIGNATURE-----
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys

koji-web 1.7 issues
 

Dennis Gilmore wrote:
> I really think that it is something in your environment.
> koji.fedoraproject.org is running 1.7.0 using mod_wsgi and not seeing
> the issue you are reporting. are you sure you switched both the koji
> hub and koji web to mod_wsgi?

I double checked my config. Looks fine.

When I tried to duplicate the web page problem today I was no longer
able to. Nothing has changed on the server. It must have been some sort
of cache that finally expired.

Thanks,
Michael


--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys

koji-web 1.7 issues
 

On 07/09/2012 01:05 PM, Michael Cronenworth wrote:

I upgraded a F16 64-bit box from Koji 1.6.0 to 1.7.0 today. I used the
1.7.0 conf files as a template and replaced the default URLs with my
server's URLs (so I am using WSGI).


Just to be clear.. the hub itself is working fine, right? All the cli
commands working? Build daemons running fine?



When I attempt to use the web interface I am having issues with
"Internal Server Error" messages popping up.

Example:
-Browse to foo.example.com/koji. Web page displays fine.


Is there no trailing slash? There should be (and the server should
redirect you if it is missing).



-Click on "Packages" link on the top header and "Internal Server Error"
is displayed.
-Click Back button. Click on "Builds" link and it displays fine.
-Click on "Packages" from "Builds" page and it displays fine.
-Click on "Summary" from "Packages" page and "Internal Server Error" is
displayed.


It sounds like the relative urls are misaligning. Pay close attention to
the exact urls that are failing. I suspect the failing "Packages" link
is "foo.example.com/packages" instead of the correct
"foo.example.com/koji/packages."


What is your /koji alias set to in your http conf? You might want to
check all possible http conf files to make sure it isn't redefined
elsewhere.



This same behavior occurs (in different steps) with the other links at
the top of the koji web interface.

My apache logs show python is failing to connect to some service when
the "Internal Server Error" occurs:
[snip Python traceback]


That snipped traceback may well be important.
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys

koji-web 1.7 issues
 

Mike McLean wrote:
> Just to be clear.. the hub itself is working fine, right? All the cli
> commands working? Build daemons running fine?

Cli commands were working without issue.

> Is there no trailing slash? There should be (and the server should
> redirect you if it is missing).

I snipped the slash in my e-mail. The server redirects me to
foo.example.com/koji/

>
> It sounds like the relative urls are misaligning. Pay close attention to
> the exact urls that are failing. I suspect the failing "Packages" link
> is "foo.example.com/packages" instead of the correct
> "foo.example.com/koji/packages."

The URLs were correct. If I pressed F5 (to refresh) the same URL the
page would display.

> What is your /koji alias set to in your http conf? You might want to
> check all possible http conf files to make sure it isn't redefined
> elsewhere.
>

I double checked everything, and as originally stated, used your
template conf files as my original file I worked from.

$ grep "Alias /koji" *conf
kojihub.conf:Alias /kojihub /usr/share/koji-hub/kojixmlrpc.py
kojihub.conf:Alias /kojifiles "/mnt/koji/"
kojiweb.conf:Alias /koji "/usr/share/koji-web/scripts/wsgi_publisher.py"
kojiweb.conf:Alias /koji-static/ "/usr/share/koji-web/static/"
$ pwd
/etc/httpd/conf.d

>
> That snipped traceback may well be important.

I could post the full one, but as I reported in my reply to Dennis the
issue has disappeared with no server configuration changes made since I
first reported this issue. My best guess is that Python was caching
something that Apache & Firefox restarts did not clear.
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys