[Box Backup] in server child, exception Server (3/45)

[Ben Summers]

On 2 Feb 2004, at 22:47, Eduardo Alvarenga wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Mon, 2 Feb 2004, Ben Summers wrote:
>
>>>  Feb 2 15:33:19 cvs bbstored[188]: in server child, exception Server
>>> (3/45) -- terminating child
>>>  --
>>>
>>>  It happens with EVERY machine I have. Apparently the backups are ok,
>>>  but I very doubt this is a normal behavior.
>>
>> I wouldn't expect to see this particular error at all. Could you turn
>> on extended logging, and see what happens just before this error?
>
>  Here it is:
>
>  Feb  2 19:45:20 cvs bbstored[13898]: Receive 
> ListDirectory(0x6b6,0xffffffff,0xc,true)
>  Feb  2 19:45:20 cvs bbstored[13898]: Send Success(0x6b6)
>  Feb  2 19:45:20 cvs bbstored[13898]: Sending stream, size 1457
>  Feb  2 19:45:20 cvs bbstored[13898]: Receive 
> ListDirectory(0x6cb,0xffffffff,0xc,true)
>  Feb  2 19:45:20 cvs bbstored[13898]: Send Success(0x6cb)
>  Feb  2 19:45:20 cvs bbstored[13898]: Sending stream, size 985
>  Feb  2 19:45:21 cvs bbstored[13898]: Receive 
> StoreFile(0x6cb,0x3ce26838f99b0,0x3ce26838f99b0,0x0,OPAQUE)
>  Feb  2 19:45:21 cvs bbstored[13898]: Receiving stream, size uncertain
>  Feb  2 19:45:27 cvs bbstored[13898]: Send Error(0x3e8,0x6)
>  Feb  2 19:45:27 cvs bbstored[13898]: in server child, exception 
> Server (3/45) -- terminating child
>
>
>  I suspect in the "size uncertain" message.

This is nothing to worry about, it simply means that the size of the 
data the client is sending isn't known when it starts. (This is because 
it compresses the data as it sends it.)

>  I have very huge files here +500MB. Any issues?

Possibly. I'll try out some large files.

But in the meantime, could you

1) Enable ExtendedLogging on the clients. You should then see what file 
they're failing on, as the client will show the actual filename instead 
of "OPAQUE" -- the server can't tell what the filenames are.

2) Verify a store, and see if it's missing anything.

Thanks,

Ben