[Dxspider-support] Building a replacement Cluster on new Infra - cant get link auto connect working?

[Kin]

Grant,

If the manual connection works for you, what you should do is to include in /local_cmd/crontab a line like this:

 

00,10,20,30,40,50 * * * * start_connect('vk5gr-2') unless connected(' vk5gr-2')

 

Kin EA3CV

 

De: Dxspider-support <dxspider-support-bounces at tobit.co.uk> En nombre de Grant via Dxspider-support
Enviado el: domingo, 26 de febrero de 2023 13:24
Para: dxspider-support at tobit.co.uk
CC: vk5gr.radio at gmail.com
Asunto: [Dxspider-support] Building a replacement Cluster on new Infra - cant get link auto connect working?

 

Folks,

 

I am in the process of finally upgrading the gate.vk5gr.id.au cluster to the latest versions. 

 

So far I have built v1.55 on new cloud infrastructure and got VK5GR-3 working. 

 

I am now trying to get it auto-call its link partner VK5GR-2 when the cluster starts up but it stubbornly refuses to do so. I have placed a vk5gr-2 connect script file into the /spider/connect directory containing:

 

sysop at dxcluster:/spider/connect$ ls -la

total 24

-rwxrwxrwx  1 sysop spider  132 Feb 26 20:02 vk5gr-2

 

 

--------------

timeout 15

abort (Busy|Sorry|Fail)

# don't forget to chmod 4775 netrom_call!

connect telnet gate.vk5gr.id.au 7300

'login' 'vk5gr-3'

--------------

 

I have also set vk5gr-3 as a set/spider node on the VK5GR-2 gate

 

When I enter “connect vk5gr-2“ into the console it happily connects and starts up the link – but for the life of me I can’t get it to do it automatically!

 

What am I missing please?

 

The installation instructions I have used were sourced from:

 

Install Dxspider on a Debian system – Packet-radio.net <https://packet-radio.net/install-dxspider-on-a-debian-system/> 

 

Everything during the install appears to have pretty much worked as advertised.

 

The system is running under "Ubuntu 22.04.2 LTS"

 

To get the cluster to auto-start as a service I have also created a service descriptor file under /etc/system/system 

 

sysop at dxcluster:/etc/systemd/system$ cat dxspider.service

[Unit]

Description=dxspider

After=syslog.target

 

[Service]

ExecStart=/usr/bin/perl -w /spider/perl/cluster.pl >/dev/tty7 &

Restart=always

RestartSec=120

WorkingDirectory=/spider/perl

User=sysop

SyslogIdentifier=dxspider

 

[Install]

WantedBy=multi-user.target

 

I have successfully gotten the cluster to start automatically following a reboot of the vps without issues – it is just the automatic initiation of the connections to other clusters that has me stumped. Comparing it to my old 1.50 installation on my Ubuntu 16.04 machine isn’t giving me any insights either ☹

 

In short – help! ☹

 

Regards,

Grant VK5GR

Sysop: gate.vk5gr.id.au:7300 

Email: vk5gr.radio at gmail.com <mailto:vk5gr.radio at gmail.com> 

 

P.S. Shortly when I have everything working, for those who are link partners, there will be a host IP address change here too as the server is moving into the cloud.

 

P.P.S. I understand there is a new mojo branch people want us to switch to as well. I will tackle that once I have the basic cluster running.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20230226/e3b38ed7/attachment-0001.htm>