The previous crash didnšt write a dump because its working dir was in / (in a singularity container). I have since changed the working dir to a bind mount path so hopefully we will get a dump if this happen again.
--
Wei Yang | [log in to unmask] | 650-926-3338(O)
-----Original Message-----
From: Brian Bockelman <[log in to unmask]>
Date: Monday, April 2, 2018 at 3:48 PM
To: Wei Yang <[log in to unmask]>
Cc: Fabrizio Furano <[log in to unmask]>, Radu Popescu <[log in to unmask]>, xcache-l <[log in to unmask]>
Subject: Re: Xcache for CVMFS crash due to attack
>Hi Wei,
>
>Any chance you got a core dump from this?
>
>I am not tracking any known crashing bugs myself.
>
>RHEL6 or RHEL7?
>
>Brian
>
>Sent from my iPhone
>
>> On Apr 2, 2018, at 5:16 PM, Yang, Wei <[log in to unmask]> wrote:
>>
>> For the record:
>>
>> We have an instance of Xcache to serve CVMFS for SLAC batch nodes. It crashed this morning after receiving ~9.5K non-handshake connections from sn160.s02.sjc01.qualys.com in 5 seconds (did our friend Artem Harutyunyan used to work at Qualys? I know he left a long time ago).
>>
>> I don?t know if there is a remedy to this. I will setup a firewall rule before I restarting the Xcache.
>>
>> regards,
>> --
>> Wei Yang | [log in to unmask] | 650-926-3338(O)
>>
>> ########################################################################
>> Use REPLY-ALL to reply to list
>>
>> To unsubscribe from the XCACHE-L list, click the following link:
>> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XCACHE-L&A=1
>
########################################################################
Use REPLY-ALL to reply to list
To unsubscribe from the XCACHE-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XCACHE-L&A=1
|
