Jitesh Shah wrote:
On Thu, 2009-01-22 at 17:17 +0100, Oliver Falk wrote:
Mike McLean wrote:
I wonder if it would log this error in a way you know what's going on :-)
Jitesh, can you check the logs as suggested by Mike, although it's fixed
now, I'd like to know if you see the error
Jitesh Shah wrote:
I checked the logs. There is just a python traceback and the actual
error ServerOffline: Database Outage' (This is with KojiDebug off)
'just' a python traceback? Often these are the key to the mystery.
--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
Oliver Falk wrote:
The settings in /etc/httpd/conf.d/kojihub.conf are correct I guess?
Esp. DBName, DBUser, DBHost? And your /var/lib/pgsql/data/pg_hba.conf is
also OK?
And you can connect via command line? psql -U DBUser -h DBHost
DBName?
... and the psql command is run on the same
Toshio Kuratomi wrote:
Oliver Falk wrote:
The settings in /etc/httpd/conf.d/kojihub.conf are correct I guess?
Esp. DBName, DBUser, DBHost? And your /var/lib/pgsql/data/pg_hba.conf is
also OK?
And you can connect via command line? psql -U DBUser -h DBHost
DBName?
... and the psql command is
Hi,
So, I had koji running and building packages for me for nearly a
fortnight. And it worked like a charm!
I double-checked all the configuration and it is intact. There is the
and entry in pg_hba.conf that trusts koji.
I run psql command from the koji user on the same machine where
koji-hub is
Jitesh Shah wrote:
Hi,
So, I had koji running and building packages for me for nearly a
fortnight. And it worked like a charm!
I double-checked all the configuration and it is intact. There is the
and entry in pg_hba.conf that trusts koji.
I run psql command from the koji user on the
Hi,
Yes, I can successfully connect to the psql database using tcp sockets
too. Here is the snippet of the interaction in the terminal.
[k...@linux-dev ~]$ psql -U koji -h localhost -d koji
Welcome to psql 8.2.11, the PostgreSQL interactive terminal.
Type: \copyright for distribution terms
Mike McLean wrote:
Oliver Falk wrote:
You have not written if you have tried to restart Apache. koji(hub)
has no auto-reconnect if it looses connection to the database. So if
for whatever reason it lost the connection to PostgreSQL, it will
never reconnect. You have to manually restart
Mike McLean wrote:
Jitesh Shah wrote:
On a different note, how does one debug a script which uses rpc calls
and the error is on the server side? i.e. the debugger will run on the
caller side, so, how do we debug the script that is executed on the
server? (Except inserting write-to-file commands
Mike McLean schrieb:
Oliver Falk wrote:
Mike McLean wrote:
Actually, it does reconnect now.
Since which version?
The change is in commit 58b7313d. Should be in 1.2.6
https://fedorahosted.org/koji/changeset/58b7313d0af0e0ac1fe804cd9f247486b3130cab
Well, thx. Good to know this is 'fixed'.
On Thu, 2009-01-22 at 17:17 +0100, Oliver Falk wrote:
Mike McLean wrote:
I wonder if it would log this error in a way you know what's going on :-)
Jitesh, can you check the logs as suggested by Mike, although it's fixed
now, I'd like to know if you see the error there...
I checked the
Hi,
I've been running a local koji instance at my workplace. It worked
absolutely fine for a fortnight. But, since Monday, I am getting this
error : ServerOffline: database outage for any CLI command that I try
to execute.
I initially suspected that it might be because koji cannot connect to
the
Hi Jitesh!
Jitesh Shah wrote:
Hi,
I've been running a local koji instance at my workplace. It worked
absolutely fine for a fortnight. But, since Monday, I am getting this
error : ServerOffline: database outage for any CLI command that I try
to execute.
I initially suspected that it might be
Hi,
Thank you for the quick reply Oliver.
So, this morning I moved to a newer version of koji. Reconfigured
everything (restarted apache after re-configuring koji-hub) and quite
surprisingly, I still get the same error!
So, if reinitialising both, postgresql and koji, doesn't do the trick, I
Jitesh Shah wrote:
So, this morning I moved to a newer version of koji. Reconfigured
everything (restarted apache after re-configuring koji-hub) and quite
surprisingly, I still get the same error!
So, if reinitialising both, postgresql and koji, doesn't do the trick, I
wonder what might have
15 matches
Mail list logo
