I had a problem with perforce yesterday. When I tried submitting my change list, perforce would apparently hang on one of the files. I controlled-C, and tried again. If I waited long enough, it timed out with the message:

Perforce client error TCP send failed Write: socket: Connection timed out Can't invoke remote operation 'lbr-WriteFile' TCP send failed Write: Socket: Succeed.

I tried several more times with no success. In the meantime, I was able to do another submit successfully, so Perforce was still working for the most part.

I could not figure out what the problem might be, so I removed the "bad" file from my change list, and submitted the remaining files successfully. I then submitted the "bad" file all by itself and it worked! The "bad" file is just an ordinary .cpp file (as are the other two files in the changelist).

So I am back in operation now, albeit somewhat disgruntled.

Does anyone have a clue as to what might have happened and whether I should worry? Perforce's website has one reference to an lbr-SubmitFile error that was due to a client problem on Windows.

Client Machine: Pentium running Debian (GNU/Linux) 2.4.0 kernel. Server Machine: Ditto p4d version: P4D/LINUX52X86/2001.1/24019

My server and client both have ample disk and memory.

I appreciate any ideas. Thanks.

bud