[Dxspider-support] Latest source of utter frustration

Joaquin . joaquin at cronux.net
Tue Apr 14 10:24:33 CEST 2020


Mike, status 24 is the same one I got when I stressed the cluster (see the
doc I sent you).
When the 900 connections were reached the cluster failed giving code 24 in
the systemd (in your case it points to "init"):

Apr  7 10:08:54 ea3cv-cluster3 systemd[1]: dxspider.service: Main process
exited, code=exited, status=24/n/a
Apr  7 10:08:54 ea3cv-cluster3 systemd[1]: dxspider.service: Failed with
result 'exit-code'.
Apr  7 10:08:54 ea3cv-cluster3 systemd[1]: dxspider.service: Service
RestartSec=100ms expired, scheduling restart.
Apr  7 10:08:54 ea3cv-cluster3 systemd[1]: dxspider.service: Scheduled
restart job, restart counter is at 1.
Apr  7 10:08:54 ea3cv-cluster3 systemd[1]: Stopped Dxspider DXCluster
service.
Apr  7 10:08:54 ea3cv-cluster3 systemd[1]: Started Dxspider DXCluster
service.

...
ACCESS 20200407 10:08:12 /home/sysop/spider/data/users.v3
ACCESS 20200407 10:08:12 /home/sysop/spider/data/users.v3
CLOSE_WRITE,CLOSE 20200407 10:08:53 /home/sysop/spider/data/users.v3
OPEN 20200407 10:08:53 /home/sysop/spider/data/users.v3
CLOSE_WRITE,CLOSE 20200407 10:08:53 /home/sysop/spider/data/users.v3
...

In the end did you expand the RAM of the VM?
Have you been able to check the status of the swap when it restarts?

Kin, EA3CV


El mar., 14 abr. 2020 a las 9:05, Joaquin . (<joaquin at cronux.net>) escribió:

> Hi Mike,
>
> I would use tools like "strace" and "sysdiag" to keep track of cluster.pl.
>
> Kin, EA3CV
>
> El mar., 14 abr. 2020 a las 2:32, Michael Carper, Ph.D. via
> Dxspider-support (<dxspider-support at tobit.co.uk>) escribió:
>
>> As of a bit more than a week ago, at about the same time each day (with
>> max users connected), the node abruptly restarts. This is totally
>> frustrating.
>>
>> [image: image.png]
>> I've checked all the crontabs... no events scheduled for that time.
>>
>> I look in the linux logfile and see this...
>>
>> # cat messages
>> Apr 12 15:21:58 wa9pie-2b init: dxspider main process (28416) terminated
>> with status 24
>> Apr 12 15:21:58 wa9pie-2b init: dxspider main process ended, respawning
>> Apr 13 16:14:45 wa9pie-2b init: dxspider main process (18493) terminated
>> with status 24
>> Apr 13 16:14:45 wa9pie-2b init: dxspider main process ended, respawning
>>
>> What gives??
>>
>> From what I can see, "status 24" is "stop issued from terminal."
>>
>> Frustrated.
>>
>> Mike, WA9PIE, VK4EIE
>> _______________________________________________
>> Dxspider-support mailing list
>> Dxspider-support at tobit.co.uk
>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20200414/4ac76d89/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 42439 bytes
Desc: not available
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20200414/4ac76d89/attachment-0001.png>


More information about the Dxspider-support mailing list