Re: [Monotone-devel] monotone crashes

[Ulf Ochsenfahrt]

The migration doesn't work, so mtn check doesn't work either (at least
not with this version). I created the other one directly before the
sync, and db check gives me 7 errors, but none serious (or are they?).

mtn: files
mtn: 4,554
mtn:
mtn:
mtn: rosters
mtn:     759
mtn:
mtn:
mtn: revisions
mtn:       759
mtn:
mtn:
mtn: markings
mtn:      759
mtn:
mtn:
mtn: ancestry
mtn:      804
mtn:
mtn:
mtn: keys
mtn:    8
mtn: certs
mtn: 3,128
mtn:
mtn:
mtn: heights
mtn:     759
mtn:
mtn:
mtn: height relations
mtn:              804
mtn:
mtn:
mtn: file 0310c09c1b5f335c6ce0dd080a54dd09b5de6c84 unreferenced
mtn: revision 119ea14b5de617e4ed269bcd63dfff5558c978c2 missing branch cert
mtn: revision 2fc330746d1df2c5af4d647eeb8f0622a785e211 missing branch cert
mtn: revision 39808803ece4b665ca81f0718872473321b00915 missing branch cert
mtn: revision 56cf654b67e1dcc43f036ab514a5d9b48eed0941 missing branch cert
mtn: revision 81ea5058064d673f5f47105ecc3337c0a9321bb9 missing branch cert
mtn: revision c41da775e6153cbacb9ed8a60f16c4171d9db76d missing branch cert
mtn: warning: 1 unreferenced files
mtn: warning: 6 missing certs
mtn: check complete: 4,592 files; 767 rosters; 767 revisions; 8 keys;
3,160 certs; 768 heights
mtn: total problems detected: 7 (6 serious)
mtn: error: serious problems detected

The missing branch certs are most likely because I synced a branch
that had revisions in a branch which I didn't sync (does that make
sense to you?). Like, I sync de.ofahrt.* and it pulls in revisions
from de.original.branch.

Anyway, I'll be gone for the christmas holidays. No more debugging
until the 31st.

Merry christmas everyone,

-- Ulf

On Sun, Dec 21, 2008 at 11:49 PM, Thomas Keller <address@hidden> wrote:
> Ulf Ochsenfahrt schrieb:
>> Hi everyone,
>>
>> using monotone 0.41 (base revision:
>> 9b264ec9247ce99cd1fdc5293e869c1a60b01c4c), I get two different
>> (probably unrelated) crashes on two different databases. Both are
>> repeatable.
>>
>> When I try to sync my university database with the monotone server I
>> setup in the office, I get:
>>
>> terminate called after throwing an instance of 'informative_failure'
>>   what():  error: wanted 1 rows got 0 in query: SELECT data FROM
>> revisions WHERE id = ?
>> mtn: fatal signal: Aborted
>> this is almost certainly a bug in monotone.
>
> This rather sounds like a database inconsistency to me. Have you tried
> to run mtn db check?
>
> The error messages you get are obviously very bad - if its really a
> database inconsistency, maybe we should run a couple of basic checks
> each time we open a database (check referenced data, counts, stuff like
> that), if this is not already done, and hint the user to call mtn db
> check in case we find stuff?
>
> Thomas.