Hi, I have a koji server running locally at my workplace. Recently, I am unable to execute any koji cli command (or I am unable to access the web interface too, for that matter). I get the following error:
"[kojiadmin@linux-dev koji]$ koji list-tags ServerOffline: database outage"
Wireshark shows that the very first xmlrpc call "getAPIVersion" fails with this error. I couldn't find any logs for koji. I can still access the database through commandline and the database is intact. The role "kojiadmin" exists and has all the proper permissions (koji was working!.. so, the setup is good)
Any pointers??
(Note: Please redirect me to the proper list if this isn't the one. Its just that I couldn't find any other lists discussing koji :) )
Jitesh
On Tue, Jan 20, 2009 at 10:32 AM, Jitesh Shah jiteshs@marvell.com wrote:
Hi, I have a koji server running locally at my workplace. Recently, I am unable to execute any koji cli command (or I am unable to access the web interface too, for that matter). I get the following error:
"[kojiadmin@linux-dev koji]$ koji list-tags ServerOffline: database outage"
that means koji can't connect to its database to fetch requested information. Also , check your koji-hub eta
Hi, Yes, I have already double-checked my koji-hub configuration. Both the DBUser and DBName are correct. Infact, I had been running koji here for more than a fortnight and it worked like a charm.
Also, I can connect with to the psql database using the same values as in DBName and DBUser variables through commandline. So, what might cause the failure when invoked through python scripts?
Jitesh
On Tue, 2009-01-20 at 10:48 +0100, Xavier Lamien wrote:
On Tue, Jan 20, 2009 at 10:32 AM, Jitesh Shah jiteshs@marvell.com wrote:
Hi, I have a koji server running locally at my workplace. Recently, I am unable to execute any koji cli command (or I am unable to access the web interface too, for that matter). I get the following error:
"[kojiadmin@linux-dev koji]$ koji list-tags ServerOffline: database outage"
that means koji can't connect to its database to fetch requested information. Also , check your koji-hub eta
-- Xavier.t Lamien -- http://fedoraproject.org/wiki/XavierLamien GPG-Key ID: F3903DEB Fingerprint: 0F2A 7A17 0F1B 82EE FCBF 1F51 76B7 A28D F390 3DEB
On Tue, Jan 20, 2009 at 11:09 AM, Jitesh Shah jiteshs@marvell.com wrote:
Hi, Yes, I have already double-checked my koji-hub configuration. Both the DBUser and DBName are correct. Infact, I had been running koji here for more than a fortnight and it worked like a charm.
did you do any update since ?
Also, I can connect with to the psql database using the same values as in DBName and DBUser variables through commandline. So, what might cause the failure when invoked through python scripts?
Do you also tried to figure out what happen in the DB side when invoked your cmd-line ?
On Tue, 2009-01-20 at 11:26 +0100, Xavier Lamien wrote:
On Tue, Jan 20, 2009 at 11:09 AM, Jitesh Shah jiteshs@marvell.com wrote:
Hi, Yes, I have already double-checked my koji-hub configuration. Both the DBUser and DBName are correct. Infact, I had been running koji here for more than a fortnight and it worked like a charm.
did you do any update since ?
Nope ... didn't update koji!
Also, I can connect with to the psql database using the same values as in DBName and DBUser variables through commandline. So, what might cause the failure when invoked through python scripts?
Do you also tried to figure out what happen in the DB side when invoked your cmd-line ?
As I mentioned earlier, it works fine through commandline!
Update: I suspect that the issue is related to failed transactions. The file /usr/share/koji-hub/kojixmlrpc.py suggests that the koji.db.connect fails. I had been running koji-shadow script and it failed mysteriously. I see this "ServerOffline: Database outage" message from that point on. I think the rollback() in koji.db.connect fails due to some not-yet-known reason. I am looking into it further.
Jitesh
Hi, The problem isn't related to failed transactions, as I suspected earlier. However, I restarted postgresql in vain. Then, reinstalled postgresql to no avail.
I also, removed and reinstalled koji and reconfigured it, but I still get the same "ServerOffline" error. I am out of things to do.
Any pointers as to why this might be happening?
Jitesh
On Tue, 2009-01-20 at 16:35 +0530, Jitesh Shah wrote:
On Tue, 2009-01-20 at 11:26 +0100, Xavier Lamien wrote:
On Tue, Jan 20, 2009 at 11:09 AM, Jitesh Shah jiteshs@marvell.com wrote:
Hi, Yes, I have already double-checked my koji-hub configuration. Both the DBUser and DBName are correct. Infact, I had been running koji here for more than a fortnight and it worked like a charm.
did you do any update since ?
Nope ... didn't update koji!
Also, I can connect with to the psql database using the same values as in DBName and DBUser variables through commandline. So, what might cause the failure when invoked through python scripts?
Do you also tried to figure out what happen in the DB side when invoked your cmd-line ?
As I mentioned earlier, it works fine through commandline!
Update: I suspect that the issue is related to failed transactions. The file /usr/share/koji-hub/kojixmlrpc.py suggests that the koji.db.connect fails. I had been running koji-shadow script and it failed mysteriously. I see this "ServerOffline: Database outage" message from that point on. I think the rollback() in koji.db.connect fails due to some not-yet-known reason. I am looking into it further.
Jitesh
On Wed, Jan 21, 2009 at 1:53 AM, Jitesh Shah jiteshs@marvell.com wrote:
Any pointers as to why this might be happening?
fedora-buildsys-list might get you better response.