Bazaar

'Connection Closed: Unexpected end of message' when checking in code.

Bug #1193156 reported by James Thorrold
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar
New
Undecided
Unassigned

Bug Description

Hi,

I keep receiving the following error message when checking in code:

bzr: ERROR: Connection closed: Unexpected end of message. Please check connectivity and permissions, and report a bug if problems persist.

Bazaar has been working flawlessly up until now. I can still checkout code, view logs etc. everything except checkin seems to work. I don't think it's a permission issue, as the user we use to commit code owns the repo folders/files.

I have attached both local and server bazaar logs.

One way I have found that fixes this is to delete and re-create the repo on the bazaar server, but this is infeasible and this error happens too frequently.

My bazaar setup is very simple and is pretty much default:

I have one server running bazaar which stores the main repo. Other machines checkin/checkout source code from that server.
To connect to the bzr server, we use ssh (bzr+ssh).

Please let me know if there are any questions about my setup or if there are possible fixes I can try.

Thanks,
James.

Revision history for this message
James Thorrold (jthorrold) wrote :
Revision history for this message
James Thorrold (jthorrold) wrote :

local bzr log

Revision history for this message
James Thorrold (jthorrold) wrote :

Have tried commiting files on the server itself, it doesn't seem to increment the revision number. This is the output from bzr commit -m "test message" :

user@server:~/staging/trunk$ bzr commit -m "test message"
Committing to: /home/user/staging/trunk/
added .bzrignore
modified www/test.txt

Killedng data locally - Stage:repacking texts:texts 217/644

Once the commit command is run, the lock is still in place, I cannot commit any other files unless I run: bzr break-lock --force.

Any ideas?

Revision history for this message
James Thorrold (jthorrold) wrote :

Have done some more digging. It seems this issue happens when I reach revision 9 and then try to commit code (effectively the transition from rev. 9 to rev. 10).

I'm completely lost at what to try and fix, i've chowned the .bzr folders to the correct user (just incase) and even made the contents and folder writeable to all - all have made no difference.

Jelmer Vernooij (jelmer)
tags: added: check-for-breezy
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.