monotone-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Monotone-devel] [BUG] while using the sync command after a propagate


From: Benoît PIERRE
Subject: [Monotone-devel] [BUG] while using the sync command after a propagate
Date: Mon, 5 Mar 2007 10:15:57 +0100

mtn serve crashed with the following output:

 mtn: finding items to synchronize:
 mtn: ticks: c="certificates"/256, k="keys"/1, r="revisions"/64
 mtn:
 mtn: fatal: std::logic_error: roster.cc:1198: invariant
'I(left_i->second->self == right_i->second->self)' violated

mtn -d server.mtn db check:

mtn: files
mtn:  6014
mtn: rosters
mtn:     355
mtn: revisions
mtn:       268
mtn: fatal: std::logic_error: database_check.cc:346: invariant
'I(checked_rosters[*i].found)' violated

(/home/bpierre/.monotone/dump attached)

mtn --full-version:

monotone 0.33 (base revision: cfebc8eb7049def476cc5fd61fef64eb14120e68)
Running on          : Linux 2.6.17-11-generic #2 SMP Thu Feb 1
19:52:28 UTC 2007 i686
C++ compiler        : GNU C++ version 4.1.2 20061115 (prerelease)
(Debian 4.1.1-21)
C++ standard library: GNU libstdc++ version 20061115
Boost version       : 1_33_1
Changes since base revision:
format_version "1"

new_manifest [0a01d89014dd718be7b60c71601679d8e8d8368f]

old_revision [cfebc8eb7049def476cc5fd61fef64eb14120e68]

 Generated from data cached in the distribution;
 further changes may have been made.

The attached jpg describe the state of the DB before the sync. What
happened on the client is changes from the branch whose head is
339bfcd5 (which is also the head of another branch whose changes had
just been propagated from) were propagated to branch whose head is
43d2d1c6, and then a sync command was issued to the server, who
crashed.

I tried restarting the server and sync again, with no luck. I then
tried to check the DB which gave another error (and the attached dump,
sorry, first one got overwritten I guess). After this, I tried
regenerate_caches, then serve and sync again, and everything worked
fine... Another db check did not report any problem.
--
A: Because it destroys the flow of conversation.
Q: Why is top posting dumb?

Attachment: mtn-bug.jpg
Description: JPEG image

Attachment: dump
Description: Binary data


reply via email to

[Prev in Thread] Current Thread [Next in Thread]