Hi Matevz,

I suspect that this is occurring in one of the plug-ins. This should cause 
an abort and a core file (make sure you have not set the core limit to 0) 
and would provide a trace-back. Alternatively,  you can run this under gdb 
to get it to stop when this occurs. Did any code related to the plug-ins 


-----Original Message----- 
From: Matevz Tadel
Sent: Monday, July 11, 2011 1:00 PM
To: xrootd-l
Subject: cmsd head disappearing


I noticed this a couple of times now ... cmsd process (running from trunk on 
Centos 5) just disappears, nothing useful in the logs. E.g., here is a log 
from cmsd that died within seconds of being started:

Ah, just got one on another machine which wrote some stuff out:

110711 12:41:25 2947 Admin_Login initial request: 'login p 15979 port 1094'
110711 12:41:25 2947 Update FrontEnd Parm1=1 Parm2=1094
110711 12:41:25 2947 State: Status changed to active
110711 12:41:25 2947 Inform xrootd status
110711 12:41:25 2947 do_Login:: Primary server 15979 logged in; data port is 
110711 12:41:26 2947 Dispatch manager.0:22@xrootd for state dlen=90
110711 12:41:26 2947 manager.0:22@xrootd do_State: 
pure virtual method called
terminate called without an active exception

Any clues? Can I do something to help trace it down?