[Dxspider-support] Latest source of utter frustration

[Dirk Koopman]

Firstly

SIGXCPU
The SIGXCPU signal is sent to a process when it has used up the CPU for 
a duration that exceeds a certain predetermined user-settable value.[16] 
The arrival of a SIGXCPU signal provides the receiving process a chance 
to quickly save any intermediate results and to exit gracefully, before 
it is terminated by the operating system using the SIGKILL signal.

[16] refers to the information on getrlimit and setrlimit. Reading the 
manual says:

RLIMIT_CPU
This is the maximum amount of CPU time, in seconds, used by a process. 
If this limit is exceeded, SIGXCPU shall be generated for the process. 
If the process is catching or ignoring SIGXCPU, or all threads belonging 
to that process are blocking SIGXCPU, the behavior is unspecified.

This parameter can be altered. But I am wondering whether you are 
hitting the limits of the vCPU that is set in the machine running this VM?

Also there is a default limit on the number of sockets a process may 
have of 1024. Now, in the old days (and on Windows boxes with default 
limits of 64 (!)), it would just refuse to accept new ones. It (now) 
*may* be that this causes this signal. In any case you should increase 
the maximum no of sockets the process will take. Do a "ulimit -n" and 
you see the default is still 1024. You will need to increase the limit.

You should probably also consider this StackOverflow answer: 
https://stackoverflow.com/questions/410616/increasing-the-maximum-number-of-tcp-ip-connections-in-linux

Dirk


On 14/04/2020 01:29, Michael Carper, Ph.D. via Dxspider-support wrote:
> 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.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/b0d6db57/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/b0d6db57/attachment-0001.png>