On Wed, 28 Apr 2010, Christine Caulfield wrote: >> (Needless to say, the servers all have plenty of RAM free...) >> > > There was a memory leak in clvmd up to 2.0.56 that might be having an impact > here if there are a lot of clvmd operation being done. eg. monitoring > software that polls active LVs frequently. > > That's all I can think of off-hand that might cause that
If it's running out of memory, it's not using up regular RAM - these machines have 32 GB of memory, and they all have at least several gigs of free memory. Also, this happens immediately after restarting clvmd. I turned up clvmd's logging (with clvmd -C -d 2); the lines relevant to this request don't seem to have much in the way of useful debugging: Got new connection on fd 5 Read on local socket 5, len = 28 creating pipe, [9, 10] Creating pre&post thread in sub thread: client = 0x69f010 Sub thread ready for work. doing PRE command LOCK_VG 'V_xenvg' at 1 (client=0x69f010) lock_resource 'V_xenvg-1', flags=0, mode=1 Created pre&post thread, state = 0 Writing status 12 down pipe 10 Waiting for next pre command read on PIPE 9: 4 bytes: status: 12 background routine status was 12, sock_client=0x69f010 Send local reply Is there another debugging knob I should turn up? Maybe corosync/openais logging? Thanks, --Quentin _______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
