On Aug 28, 2015, at 9:00 AM, Gates, John H <[log in to unmask]> wrote:

Also, there's a long list of destructors that aren't being called, including the one that should release the lock. I think this isn't being deleted.
XrdSsiProvider *XrdSsiProviderServer = new lsst::qserv::xrdsvc::SsiProviderServer;

On 08/27/15 20:54, Becla, Jacek wrote:

[log in to unmask]" type="cite" class=""> For the record, I have a fix in DM-3618

John, FYI, AndyS is restarting xrootd in wmgr because apparently that is the only way to force xrootd to refresh chunk inventory (at the moment)

Jacek

On Aug 27, 2015, at 7:39 PM, Becla, Jacek <[log in to unmask]> wrote:

John

Your latest code is giving me troubles. Integration test killed xrootd, the tail of the log is similar to what you observed intermittently:

[2015-08-27T21:32:13.084-0500] [0x7f92c2df8720] INFO root (build/xrdsvc/SsiService.cc:142) - Cleaning up scratchDb: qservScratch.

[2015-08-27T21:32:13.086-0500] [0x7f92c2df8720] WARN root (build/wdb/ChunkResource.cc:302) - memLockStatus LOCKED_OTHER wrong uid. Expected 29962 got 28572 err=

[2015-08-27T21:32:13.086-0500] [0x7f92c2df8720] WARN root (build/wdb/ChunkResource.cc:316) - Memory tables were not released cleanly! LockStatus=LOCKED_OTHER

[2015-08-27T21:32:13.086-0500] [0x7f92c2df8720] DEBUG root (build/wdb/ChunkResource.cc:272) - execLockSql CREATE DATABASE IF NOT EXISTS q_memoryLockDb;CREATE TABLE IF NOT EXISTS q_memoryLockDb.memoryLockTbl ( keyId INT UNIQUE, uid INT ) ENGINE = MEMORY;

[2015-08-27T21:32:13.086-0500] [0x7f92c2df8720] DEBUG root (build/wdb/ChunkResource.cc:272) - execLockSql INSERT INTO q_memoryLockDb.memoryLockTbl (keyId, uid) VALUES(1, 29962 )

[2015-08-27T21:32:13.086-0500] [0x7f92c2df8720] ERROR root (build/wdb/ChunkResource.cc:373) - Lock failed, exiting. query=INSERT INTO q_memoryLockDb.memoryLockTbl (keyId, uid) VALUES(1, 29962 ) err=Error 1062: Duplicate entry '1' for key 'keyId' Unable to execute query: INSERT INTO q_memoryLockDb.memoryLockTbl (keyId, uid) VALUES(1, 29962 )

I saved full log here:

/home/becla/qserv-run/2015_08/var/log/worker/xrootd.log

I hope we will be able to resolve it very soon, if we won’t, backup plan:

a) back off all changes

b) disable the code that is causing xrootd to die while you investigate

I’ll try to debug it tonight

Jacek

Use REPLY-ALL to reply to list

To unsubscribe from the QSERV-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1

Use REPLY-ALL to reply to list

To unsubscribe from the QSERV-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1