[Date Prev] [Date Index] [Date Next] [Thread Prev] [Thread Index] [Thread Next]
Bryan Stansell bryan@conserver.com
Fri, 5 Jun 2009 17:30:03 GMT
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. So, it's sending a redirect but redirecting to itself (under an alternate identity?). I'd look at the following output for clues: conserver -DS conserver -V console -D <console> If it's a name mismatch problem, perhaps just looking at the 'master' entries (if there are any) in your conserver.cf file and making sure they map to an ip address on your host would be a good first start. Feel free to send me (directly) any of the info above to help poke around and figure this out. It *seems* like a configuration issue, but it's always possible it's something else. Bryan On Thu, Jun 04, 2009 at 10:48:39PM -0400, Chris Ross wrote: > If I run "console -x", I simply get no output. If I try to console > to a console, I get a brief pause followed by: > > console: forwarding level too deep! > > Interestingly, I'm also seeing the following in the log: > > [Thu Jun 4 22:46:46 2009] conserver (1139): ERROR: FileRead(): SSL > error on fd > > Any idea what's gone wrong? The console and conserver binaries > should be built with the same version of openssl as are on the machine > at the moment. Any other ideas as to what might be causing this issue? > > Thanks... > > - Chris > > _______________________________________________ > users mailing list > users@conserver.com > https://www.conserver.com/mailman/listinfo/users