<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7653.38">
<TITLE>Re: Koji: ServerOffline</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Hi,<BR>
Thank you for the quick reply Oliver.<BR>
<BR>
So, this morning I moved to a newer version of koji. Reconfigured<BR>
everything (restarted apache after re-configuring koji-hub) and quite<BR>
surprisingly, I still get the same error!<BR>
<BR>
So, if reinitialising both, postgresql and koji, doesn't do the trick, I<BR>
wonder what might have gone wrong.<BR>
(Just as a matter of curiosity, I even checked with ipcs that there are<BR>
no dangling shared memory segments. There aren't any.)<BR>
<BR>
Jitesh<BR>
<BR>
On Thu, 2009-01-22 at 08:16 +0100, Oliver Falk wrote:<BR>
> Hi Jitesh!<BR>
><BR>
> Jitesh Shah wrote:<BR>
> > Hi,<BR>
> > I've been running a local koji instance at my workplace. It worked<BR>
> > absolutely fine for a fortnight. But, since Monday, I am getting this<BR>
> > error : "ServerOffline: database outage" for any CLI command that I try<BR>
> > to execute.<BR>
> ><BR>
> > I initially suspected that it might be because koji cannot connect to<BR>
> > the database. But, I checked that I can login to the database through<BR>
> > command-line.<BR>
> > >> psql<BR>
> ><BR>
> > Also, I wrote a small script in python which mimics koji's method of<BR>
> > connecting to the database (with reference<BR>
> > to /usr/lib/python2.5/site-packages/koji/db.py) and it works fine!<BR>
> ><BR>
> > Just to make sure, I restarted postgresql service in vain.<BR>
> > Re-initialised the database (Remove /var/lib/pgsql and run "service<BR>
> > postgresql initdb" and all the other steps) to no avail.<BR>
> ><BR>
> > I started seeing this problem after a run of the koji-shadow script. It<BR>
> > exited abnormally giving this very error. Since then, I cannot even<BR>
> > access koji-cli.. neither koji-web.<BR>
> ><BR>
> > I have been tracing through the koji scripts and I see that the SSL<BR>
> > login succeeds and then the very first rpc call: "getAPIVersion" fails.<BR>
> > Wireshark shows that the koji-hub replies with "Connection: close" to<BR>
> > the getAPIVersion call.<BR>
> ><BR>
> > Any idea as to what is going wrong?<BR>
> > Any pointers?<BR>
><BR>
> You have not written if you have tried to restart Apache. koji(hub) has<BR>
> no auto-reconnect if it looses connection to the database. So if for<BR>
> whatever reason it lost the connection to PostgreSQL, it will never<BR>
> reconnect. You have to manually restart Apache!<BR>
><BR>
> -of<BR>
><BR>
> --<BR>
> Fedora-buildsys-list mailing list<BR>
> Fedora-buildsys-list@redhat.com<BR>
> <A HREF="https://www.redhat.com/mailman/listinfo/fedora-buildsys-list">https://www.redhat.com/mailman/listinfo/fedora-buildsys-list</A><BR>
</FONT>
</P>
</BODY>
</HTML>