I was too fast, I apologize, this indeed has nothing do with Jim's
problem. What i ment was:
icl_com/clx_rte_init.cc: Error in cluster configuration file. Node gb7mbc, route 0, digi 0.
This error in io.log is seen if the problem described below occurs.
Sorry again.
Jim> Hey Arnold,
Jim> That is not the case. In fact I haven't touched my cluster_par in a while.
Jim> This error has been happening for weeks now. If you look in io.lo, you can
Jim> see where it is trying to connect, but it times out before it gets a
Jim> connection established. Can you think of anything else?
Jim> 73's
Jim> Jim
>> -----Original Message-----
>> From: Arnold Bosch [mailto:xzxhi.aqpmdvxe@mailit.tunk.net]
>> Sent: Tuesday, December 01, 1998 10:08 AM
>> To: Jim Wilcox; 'CLX List'
>> Subject: Re[2]: Timeout on script connection
>>
>>
>> Hello Jim,
>>
>> Tuesday 1 december 1998, you wrote:
>>
>> Jim> Hey Ben,
>>
>> Jim> Can you tell me what generates the following
>> message in io.lo:
>>
>> Jim> Nov 29 05:26:28 ihs1 syslog: icl_com/clx_rte.cc: Timeout
>> for k4uj route 0.
>>
>> This means that k4uj is in your ~/config/cluster_par file (probably
>> added after clx was already started). However clx has this node
>> already in his route list (see: sh/c/n) and refuses to let you connect
>> to this node, or let this node connect you.
>>
>> Shutdown and start clx and this node can connect you, or you can
>> connect this node again.
>>
>> Jim> If I can find this out, I can fix my problem.
>>
>> '73 Arnold.
>>
>> Jim> 73's
>> Jim> Jim
>>
>>
>>
>>
>> Best regards,
>> Arnold mailto:ejikpgz@teekanne.de
>>
>>
Best regards,
Arnold mailto:qlmmgaqe@roskapostia.tunk.net