[Dxspider-support] problems when moving to dxspider

[Dirk Koopman]

On Tue, 2001-10-30 at 18:54, Filip Jonckers wrote:
> Hi guys ! 
> we had a lot of performance problems at on0nol during this weekends CQWW
> so I would 
> like to install The Spider.... 
> (Can Spider run fine on a Pentium 166MMX with 64Mb during a cqww ??) 
> This is my first installation of dx-spider so don't shoot me if I do
> something very stupid :-) 
> I've been using the clx cluster for several years and have been working
> with Linux since kernel 0.99 ... 
> I have a spare Pentium 166MMX (compaq deskpro) with 128Mb ram and Redhat
> 7.1 standard (fresh) installation 
> production will be running Redhat 7.2 as I just downloaded that one... 
> downloaded full version 1.48 via sourceforge.net .... 
> when building/installing the necessary modules I have a problem when
> running the tests for the Net::Telnet package 

The first thing I would do is get onto the CVS version. I shall be
issuing 1.49 as soon as my work pattern allows it. 1.48 has a couple of
quite serious problems (which won't affect it if you are just using it
as a 'leaf' test node).

> Manifying blib/man3/Net::Telnet.3pm
> [root at kenny Net-Telnet-3.02]# make test
> PERL_DL_NONLAZY=1 /usr/bin/perl -Iblib/arch -Iblib/lib
> -I/usr/lib/perl5/5.6.0/i386-linux -I/usr/lib/perl5/5.6.0 -e 'use
> Test::Harness qw(&runtests $verbose); $verbose=0; runtests @ARGV;' t/*.t
> t/select............NOK 3FAILED test 3 
> Failed 1/3 tests, 66.67% okay
> Failed Test Status Wstat Total Fail Failed List of failed
> ------------------------------------------------------------------------
> -------
> t/select.t 3 1 33.33% 3
> Failed 1/1 test scripts, 0.00% okay. 1/3 subtests failed, 66.67% okay.

This is normal (unfortunately). There seems to be a problem with the
tests. 

> ------------------------ 
> An error in the installation document: 
> section 1.5 Starting up for the first time: 
> section 1.6 "The client program" should be moved before: 
> Now issue the following command: 
> ./client 
> the program doesn't exist yet at that point..... :-) 
> and additionally.... 
> when starting "./client" you get an error "Must have at least a
> callsign" 
> and when I issue: 
> ./client on1tst 
> nothing happens and after a long time I get: Error on connect to
> localhost port 27754 (110) 
> yet, when I check the listener ports: 
> # netstat -ln | grep 27754
> tcp 0 0 127.0.0.1:27754 0.0.0.0:* LISTEN 
> hmm..... 
> using perl/console.pl is doing nothing (except the nice line at the
> bottom with the time and sysop callsign) 
> setup Listeners.pm on 0.0.0.0:7300 (defaults) 
> and telnet localhost 7300 is also doing nothing... 
> BUT... when I telnet form another system... it works !! 
> is this the result of the Net::Telnet problems above ? 

No, it might be because you have a 'medium' security firewall setup (the
default) on your RedHat box. You will either need to understand the
'lokkit' program or else do as I do and edit /etc/sysconfig/ipchains
manually (like it says in the file you shouldn't).

If it isn't that then I would need to ssh in and have a look.
  
But see below first...

> ------------------------ 
> some other questions: 
> are the AX25 libs/utils necessary when using dxspider ? 
> (cfr. change permissions on ax25_call ....) 

not if you only using IP connections. You only need the AX25 bits if you
are using AX25 :-)

> I don't have them on my test system .... 
> is it safe to use the same callsign in $mycall and $myalias ? 
> (let's say if your cluster is at home and you only have 1 callsign) 
> that's all for now :-) 

Sorry NO NO NO absolutely NOT!

They really MUST be different (but they can be the same callsign but
with SSIDs (eg $mycall = 'ON1AFN-6' and $myalias = 'ON1AFN'). You will
need to /spider/perl/update_sysop.pl after you have changed the file.
You may well find that the console.pl and client now work as well.
 
> As I do some programming in Perl myself (at work) I would like to
> contribute 
> some stuff myself in the future... 

Super! I look forward to that.

73 Dirk G1TLH