RE: Problems with conserver after OS upgrade

Hm!   OS Upgrade?   Check your HOSTS file.   Various unix's implement
the local host name differently.   If your node is phred, and its IP is
say, 141.107.223.14, there are two variations of host file layouts you
will see:

127.0.0.1		localhost.localdomain localhost phred

OR:

127.0.0.1		localhost.localdomain localhost
141.107.223.14	phred.my.domain phred

There are arguments for and against where to stick the local host name
(phred) - I have seen both, and I have seen applications break in one
versus the other.     One very strong possibility is you had the hosts
file one way, and the um, "OS Upgrade" put it back the other way.

Something to look for.

--kcb




-----Original Message-----
From: users-bounces@conserver.com [mailto:users-bounces@conserver.com]
On Behalf Of Bryan Stansell
Sent: Friday, June 05, 2009 12:30 PM
To: Conserver Users's Mailing List
Subject: Re: Problems with conserver after OS upgrade

Well, this could be an interesting failure mode with the SSL code, or
something changed such that conserver no longer believes it's running on
the host that's supposed to manage the consoles...................