[Dxspider-support] DxSpider and FC3 Problem
Dirk Koopman
djk at tobit.co.uk
Sun Nov 6 16:53:21 GMT 2005
On Sun, 2005-11-06 at 10:38 -0500, Jim Snider wrote:
> Well, netstat didn't return anything about 27754.
>
> I commented out the line in inittab that restarts the system so I could
> control it manually. I rebooted the machine and went in to start it by
> hand. Here's what I got back
>
> ------------
> [sysop at w8bs perl]$ ./cluster.pl
> Copyright (c) 1998-2002 Dirk Koopman G1TLH
> DXSpider Version 1.51, build 57.263 started
> loading prefixes ...
> US Database loaded
> loading band data ...
> loading user file system ...
> starting listeners ...
> Internal port: localhost 27754
> External Port: 0.0.0.0 7300
It's listening to port 7300 for incoming connections.
telnet localhost 7300
should get you a sysop login.
> load badwords: Ok
> Starting Dupe system
> Read in Messages
> Read in Aliases
> Start WWV
> Start WCY
> Starting DX Spot system
> Start Protocol Engines ...
> DXChannel N8OJ created (1)
> reading existing message headers ...
> load badmsg: Ok
> load forward: Ok
> load swop: Ok
> reading cron jobs ...
> cron: reading /spider/cmd/crontab
> cron: adding 1 0 * * 3 DXUser::export("$main::data/user_asc")
> cron: adding 5 0 * * * DXDebug::dbgclean()
> cron: adding 0 3 * * * Spot::daily()
> cron: reading /spider/local_cmd/crontab
> cron: adding 0,10,20,30,40,50 * * * * start_connect('n3ra') unless
> connected('n3ra')
> reading database descriptors ...
> doing local initialisation ...
> orft we jolly well go ...
> queue msg (0)
> --------------
>
> Now, it looks OK to me but I cannot connect to the dxspider via ./client
> or telnetting to this box on port 7300.
As this is linux, you should be able to do (as root, as it gives you the
most info): netstat -tap
This will show you all the TCP ports that are either connected or
listening
and you will see something like:-
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 *:7301 *:* LISTEN 23991/perl
tcp 0 0 localhost:27754 *:* LISTEN 23991/perl
tcp 0 0 *:http *:* LISTEN 4465/httpd
tcp 0 0 *:981 *:* LISTEN 2919/rpc.statd
tcp 0 0 *:ipp *:* LISTEN 2963/cupsd
tcp 0 0 *:https *:* LISTEN 4465/httpd
tcp 0 0 *:microsoft-ds *:* LISTEN 4211/smbd
tcp 0 0 dirk3.int.tobi:microsoft-ds xxx:1025 ESTABLISHED 23037/smbd
tcp 0 0 dirk3.int.tobit.co.uk:27754 dirk3.int.tobit.co.uk:59170 ESTABLISHED 23991/perl
tcp 0 0 dirk3.int.tobit.co.uk:44824 xxx:imaps ESTABLISHED 22548/evolution-2.2
tcp 0 0 dirk3.int.tobit.co.uk:59170 dirk3.int.tobit.co.uk:27754 ESTABLISHED 23992/perl
tcp 0 0 dirk3.int.tobit.co.uk:55841 dirk3.int.tobit.co.uk:ipp TIME_WAIT -
tcp 0 0 dirk3.int.tobit.co.uk:40598 dirk3.int.tobit.co.uk:2143 ESTABLISHED 22548/evolution-2.2
You will notice several lines ending in 'perl', the lines in state
'LISTEN' belong to the ./cluster.pl that I am running. The other lines
are various connections, one outgoing and the other incoming from a
'console.pl' instance.
An * in the 'local address' column on a listener means that it is
listening on all interfaces. You can see from the above that it is only
listening to 'localhost' on port 27754. 'localhost' may be shown as the
full name of your machine because that is how most linux distro set
up /etc/hosts. Oh and I am using port 7301 rather than 7300 because I
can have several instances of the node running at once, with the same
code but different data areas and callsigns.
Dunno whether this actually helps at all but hopefully it is
informative.
Dirk G1TLH
More information about the Dxspider-support
mailing list