[Dxspider-support] client error

Dirk Koopman djk at tobit.co.uk
Wed Nov 30 22:55:41 GMT 2022


In mojo I stopped relying on whatever "localhost" is defined as. This 
distinction may not apply in the master branch (when I have finished try 
to make create_prefix.pl be a bit more intelligent about Hawaiian 
callsigns being used in Pittsburgh (sigh)), I'll check it out to see how 
it's defined. But explicitly setting these two values to 127.0.0.1 in 
your /spider/local/DXVars.pm and in /spider/local/Console.pm should sort 
it everywhere.

$main::clusteraddr //= '127.0.0.1';   # for the node
$main::clusteraddr //= '127.0.0.1';   # for the client

73 Dirk

In Listeners.pm:


On 30/11/2022 17:47, Boudewijn (Bob) Tenty via Dxspider-support wrote:
> I had the same error and it was how localhost was specified in 
> /etc/hosts, make sure localhost is only specified for 127.0.0.1  I had 
> it specified for 127.0.0.1
> and also for ::1 ipv6 and with netstat I found out that port 27754 
> defaulted to ipv6/tvp6.
>
> 73,
>
> Bob (Boudewijn) VE3TOK
>
> On 2022-11-30 07:58, Ricardo Suarez via Dxspider-support wrote:
>> Hello all.
>>
>> After updated to new dxspider version, client stops  with an error, 
>> the only way to connect with privileges now is console.pl, 
>> unconfortable for me...
>>
>> The error was:
>>
>> root at Voyager:/spider/src# ./client lu9da
>> Error on connect to 127.0.0.1 port 27754 (111)
>> root at Voyager:/spider/src#
>>
>>
>> Any idea?
>>
>> Regards
>>
>> Rick LU9DA
>>
>> _______________________________________________
>> Dxspider-support mailing list
>> Dxspider-support at tobit.co.uk
>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>




More information about the Dxspider-support mailing list