[Date Prev] [Date Index] [Date Next] [Thread Prev] [Thread Index] [Thread Next]

Re: conserver (22474): ERROR: [trfw01a] connect(5): No route to host: forcing down

Jason White jdwhite@menelos.com
Tue, 9 Apr 2013 23:12:42 GMT


On Apr 9, 2013, at 5:36 PM, "Stout, Brandon" <brandon@49ers.com> wrote:

> does anyone know what this error means?
> 
> conserver (22203): ERROR: [trfw01a] connect(5): No route to host: forcing down

It means the network routing tables on the console server are such that the it cannot find route to the IP address that cons01.fqdn.com resolves to.

You should be able to confirm this on the command line by first resolving cons01.fqdn.com and then trying to ping it.  A 'netstat -nr' will show you the routing tables.

I'm assuming that 'cons01.fqdn.com' isn't really what's in your conserver.cf.  If it is, that's likely your problem and you'd need to replace it with the host name or IP address of your Cyclades box.

-Jason

--
Jason White
jdwhite@menelos.com


> I am not sure if this is something internal to related to the application or if it has to do with DNS or something along those lines. 
> 
> Here is my conserver.cf
> 
> default cyclades        { type host; portbase 7000; portinc 1; }
> 
> break 1 { string "\z"; }
> break 2 { string "\r\d~\d^b"; delay 600; }
> break 3 { string "#."; }
> break 4 { string "+\d+\d+"; delay 300; }
> break 5 { string "\033c"; }
> 
> default * {
> 	logfile /var/log/consoles/&;
> 	timestamp 1hab;
> 	rw *;
> 	include full;
> 	master localhost;
> }
> 
> default cons01 {
> 	include cyclades;
> 	host cons01.fqdn.com;
> 	}
> 
> console trfw01a { include cons01; port 2; }
> 
> 
> access * {
>         trusted 127.0.0.1;
>         allowed 10.0.0.0/8;
> }
> 
> _______________________________________________
> users mailing list
> users@conserver.com
> https://www.conserver.com/mailman/listinfo/users