I had to reinstall and now attempting to setup a local koji server again.
I am probably using a different version of koji than before, 1.2.6 rings a bell.
Anyway, I now have:
koji-hub-1.3.2-1.fc12.noarch koji-web-1.3.2-1.fc12.noarch koji-builder-1.3.2-1.fc12.noarch koji-1.3.2-1.fc12.noarch
I am just starting the process, but seeing database issues. running koj cli, I see "ServerOffline: database outage"
BUT, not every time. For example,
koji list-hosts ServerOffline: database outage koji list-hosts ServerOffline: database outage koji list-hosts Hostname Enb Rdy Load/Cap Arches Last Update kojibuilder Y N 0.0/2.0 i386 - kojibuilder1 Y N 0.0/2.0 i386 - kojibuilder2 Y N 0.0/2.0 i386 -
Also, hub and database are on small system.
Currently, web site is showing:
Error The web interface is having difficulty communicating with the main server. This most likely indicates a network issue. gaierror: [Errno -2] Name or service not known
Thoughts?
On 05/12/2010 09:11 AM, Doug Reiland wrote:
I had to reinstall and now attempting to setup a local koji server again.
I am probably using a different version of koji than before, 1.2.6 rings a bell.
Anyway, I now have:
koji-hub-1.3.2-1.fc12.noarch koji-web-1.3.2-1.fc12.noarch koji-builder-1.3.2-1.fc12.noarch koji-1.3.2-1.fc12.noarch
I am just starting the process, but seeing database issues. running koj cli, I see "ServerOffline: database outage"
BUT, not every time. For example,
Have you checked the hub logs and postgres logs for errors?
After 1.2.6, we added a config file for the hub (instead of just using PythonOption lines in the httpd config). You may just need to migrate your config.
I'm not sure why the failure is inconsistent. Did you restart your httpd server after upgrading?
koji list-hosts ServerOffline: database outage koji list-hosts ServerOffline: database outage koji list-hosts Hostname Enb Rdy Load/Cap Arches Last Update kojibuilder Y N 0.0/2.0 i386 - kojibuilder1 Y N 0.0/2.0 i386 - kojibuilder2 Y N 0.0/2.0 i386 -
Also, hub and database are on small system.
Currently, web site is showing:
Error The web interface is having difficulty communicating with the main server. This most likely indicates a network issue. gaierror: [Errno -2] Name or service not known
Thoughts?
buildsys mailing list buildsys@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/buildsys
It is now working. I took the DBHost entry out of /etc/koji-hub/hub.conf. I guess it defaults to localhost.
I had my system name there. I am not sure why it would work/fail inconsistently. I have 2 entries in pg_hba.conf, one for localhost and one for subnet so maybe subnet is wrong and some times I get lucky it is uses the localhost entry.
Thanks for reply.
On Wed, May 12, 2010 at 5:34 PM, Mike McLean mikem@redhat.com wrote:
On 05/12/2010 09:11 AM, Doug Reiland wrote:
I had to reinstall and now attempting to setup a local koji server again.
I am probably using a different version of koji than before, 1.2.6 rings a bell.
Anyway, I now have:
koji-hub-1.3.2-1.fc12.noarch koji-web-1.3.2-1.fc12.noarch koji-builder-1.3.2-1.fc12.noarch koji-1.3.2-1.fc12.noarch
I am just starting the process, but seeing database issues. running koj cli, I see "ServerOffline: database outage"
BUT, not every time. For example,
Have you checked the hub logs and postgres logs for errors?
After 1.2.6, we added a config file for the hub (instead of just using PythonOption lines in the httpd config). You may just need to migrate your config.
I'm not sure why the failure is inconsistent. Did you restart your httpd server after upgrading?
koji list-hosts ServerOffline: database outage koji list-hosts ServerOffline: database outage koji list-hosts Hostname Enb Rdy Load/Cap Arches Last Update kojibuilder Y N 0.0/2.0 i386 - kojibuilder1 Y N 0.0/2.0 i386 - kojibuilder2 Y N 0.0/2.0 i386 -
Also, hub and database are on small system.
Currently, web site is showing:
Error The web interface is having difficulty communicating with the main server. This most likely indicates a network issue. gaierror: [Errno -2] Name or service not known
Thoughts?
buildsys mailing list buildsys@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/buildsys
-- buildsys mailing list buildsys@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/buildsys
On 05/13/2010 10:52 AM, Doug Reiland wrote:
It is now working. I took the DBHost entry out of /etc/koji-hub/hub.conf. I guess it defaults to localhost.
It doesn't default to localhost, it defaults to None. If you don't pass an explicit dbhost when making the database connection then it uses a local Unix domain socket to connect. If you specify a hostname, even localhost, then it uses a tcp connection (which your postgres server might not be configured to accept).
I had my system name there. I am not sure why it would work/fail inconsistently. I have 2 entries in pg_hba.conf, one for localhost and one for subnet so maybe subnet is wrong and some times I get lucky it is uses the localhost entry.
My working theory is that you did not restart your httpd after updating and managed to wind up with some httpd processes running the old code and some running the new.
buildsys@lists.fedoraproject.org
-
Doug Reiland -
Mike McLean