monotone-devel
[Top][All Lists]
Advanced

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

[Monotone-devel] fatal: database schema has changed


From: Jeremy Cowgar
Subject: [Monotone-devel] fatal: database schema has changed
Date: Mon, 14 Mar 2005 15:02:48 -0500

I have a windows box and linux box hosting a project named "Goofing"...
obviously to learn Monotone. I am going through the tutorial and came up
to the part of setting up the network and sync'ing changes. The first
sync went just fine, but when I try to sync again, I get:

--- SERVER:

$ monotone --db=~/goof.db serve 192.168.0.138
com.advancedpricing.goofing
monotone: rebuilding merkle trees for collection
com.advancedpricing.goofing
monotone: including branch com.advancedpricing.goofing
monotone: [keys: 2] [rcerts: 8] 
monotone: beginning service on 192.168.0.138 : 5253
monotone: accepted new client connection from 192.168.0.175:1886
monotone: fd 6 (peer 192.168.0.175:1886) exchanged goodbyes and flushed
output, disconnecting
monotone: accepted new client connection from 192.168.0.175:1887
monotone: discarding debug log
monotone: fatal: std::runtime_error: db query [SELECT keydata FROM
public_keys where id = '%q']: sqlite error database schema has changed
monotone: this is almost certainly a bug in monotone.
monotone: please send this error message, the output of 'monotone
--full-version',
monotone: and a description of what you were doing to
address@hidden

--- CLIENT:

C:\Develop\goofing>monotone sync 192.168.0.138
com.advancedpricing.goofing
monotone: rebuilding merkle trees for collection
com.advancedpricing.goofing
monotone: including branch com.advancedpricing.goofing
monotone: [keys: 2] [rcerts: 12]
monotone: connecting to 192.168.0.138
monotone: read from fd 1932 (peer 192.168.0.138) failed, disconnecting

C:\Develop\goofing>

If I restart the server, and issue the same command on the client,
everything works fine. Both systems report a version of:

monotone 0.16 (base revision: ce860bae312c4bb8483d5b3b2a8cd3bebe2323d5)

Thanks for any help,

Jeremy Cowgar





reply via email to

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