[Box Backup] Failed to get write lock

[Brian Burton]

First let me say that boxbackup is an excellent tool.  I've been using v0.10 for some time
and have been very happy with it so far.  Lately, however, I have begun to receive an
error in my logs every few minutes.  I see a large amount of traffic between the client
and server but I also see this message in the server log every 1-2 minutes:

qMay  1 08:33:51 tesla bbstored[6899]: Incoming connection from 207.255.222.10 port 37633
(handling in child 12083)
May  1 08:33:51 tesla bbstored[12083]: Certificate CN: BACKUP-42
May  1 08:33:51 tesla bbstored[12083]: Receive Version(0x1)
May  1 08:33:51 tesla bbstored[12083]: Receive Version(0x1)
May  1 08:33:51 tesla bbstored[12083]: Send Version(0x1)
May  1 08:33:51 tesla bbstored[12083]: Send Version(0x1)
May  1 08:33:51 tesla bbstored[12083]: Receive Login(0x42,0x0)
May  1 08:33:51 tesla bbstored[12083]: Receive Login(0x42,0x0)
May  1 08:33:55 tesla bbstored[12083]: Failed to get write lock (for Client ID 00000042)
May  1 08:33:55 tesla bbstored[12083]: Send Error(0x3e8,0x4)
May  1 08:33:55 tesla bbstored[12083]: Send Error(0x3e8,0x4)
May  1 08:33:55 tesla bbstored[12083]: Connection statistics for BACKUP-42: IN=60 OUT=60
TOTAL=120
May  1 08:33:55 tesla bbstored[12083]: in server child, exception Connection TLSReadFailed
(Probably a network issue between client and server.) (7/34) -- terminating child


On the client side of the connection I see this:

May  1 08:33:51 newton bbackupd[9367]: Beginning scan of local files
May  1 08:33:51 newton bbackupd[9367]: Opening connection to server
tesla.burton-computer.com...
May  1 08:33:55 newton bbackupd[9367]: Exception caught (Connection
Protocol_UnexpectedReply (Server probably reported an error
.) 7/47), reset state and waiting to retry...


Last night I terminated the bbstored on the server and restarted it.  Following the
restart I saw a long exchange of information in the server log files (Receive
ListDirectory, Send Success) that seemed to indicate that things were back to normal.  But
then after a while this error began to reoccur.   The error message indicates a
communication issue between client and server but that "Failed to get write lock" error
sounds more like a local file issue.

Can anyone offer any insight into what may be happening here?  I'll be happy to offer more
information if needed.  The client and server are both intel linux boxes.  Neither has
been upgraded recently.

Thanks!
++Brian