Back Midas Rome Roody Rootana
  Midas DAQ System  Not logged in ELOG logo
Entry  26 Apr 2017, Francesco Renga, Forum, Problem with logger at run start 
    Reply  26 Apr 2017, Stefan Ritt, Forum, Problem with logger at run start 
       Reply  26 Apr 2017, Francesco Renga, Forum, Problem with logger at run start 
    Reply  02 May 2017, Konstantin Olchanski, Forum, Problem with logger at run start 
Message ID: 1287     Entry time: 02 May 2017     In reply to: 1279
Author: Konstantin Olchanski 
Topic: Forum 
Subject: Problem with logger at run start 
> Wed Apr 26 23:03:12 2017 [mhttpd,ERROR] [midas.c:9106:rpc_client_connect,ERROR] cannot connect to host "scar
> lett", port 44858: connect() returned -1, errno 113 (No route to host)

Forgot to reply to this: if you read the error messages, you will see the actual problem is "no route to host". Next step
is to ping the same hostname or try "telnet hostname 22" (cut-and-paste the hostname from the error message
to avoid the common pitfall of not seeing a typo, i.e. ping host00 works while midas connect to hostOO does not (zero vs capital-o)).
In your case you had the wrong hostname ("foo" and "foo.localdomain" resolve to different IP addresses, one works the other
one does not). You can also try to use the IP address instead of hostname, this will avoid hostname resolution problems
(inconsistency between /etc/hosts and hostnames in DNS is very easy to have when using self-made private networks).

K.O.
ELOG V3.1.4-2e1708b5