In the meantime I tried copying the _replicator database to another instance, where I could delete the entry without problems. However it still doesn't work on the initial instance. If one of the committers is interested, I could organize either remote access via HTTP, or shell access to the machine it is running on.
-- Stefan On Fri, Mar 2, 2012 at 4:30 PM, Stefan Kögl <[email protected]> wrote: > On Fri, Mar 2, 2012 at 4:06 PM, Jan Lehnardt <[email protected]> wrote: >> I just created a replication doc under 1.1.1 and then copied the >> _replicator.couch file to a 1.2.x. On update I the expected result >> Robert also got ("Only the replicator can edit replication documents >> that are in the triggered state.". a curl -X DELETE on the doc with >> ?rev=4-abcd... (no quotes) also worked. > > The document was created with 1.2.x, from around the time of the second RC. > > I also tried with quotes and got > > $ curl -sv -X DELETE > "http://stefan:*********@127.0.0.1:5984/_replicator/mygpo?rev=\"131-57b4da8d3163468cb0bbf4fd30c87832\""; > * About to connect() to 127.0.0.1 port 5984 (#0) > * Trying 127.0.0.1... connected > * Connected to 127.0.0.1 (127.0.0.1) port 5984 (#0) > * Server auth using Basic with user 'stefan' >> DELETE /_replicator/mygpo?rev="131-57b4da8d3163468cb0bbf4fd30c87832" HTTP/1.1 >> Authorization: Basic ************************** >> User-Agent: curl/7.19.7 (x86_64-pc-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8k >> zlib/1.2.3.3 libidn/1.15 >> Host: 127.0.0.1:5984 >> Accept: */* >> > < HTTP/1.1 500 Internal Server Error > < Server: CouchDB/1.2.0 (Erlang OTP/R14B04) > < Date: Fri, 02 Mar 2012 15:18:31 GMT > < Content-Type: text/plain; charset=utf-8 > < Content-Length: 44 > < Cache-Control: must-revalidate > < > {"error":"unknown_error","reason":"badarg"} > * Connection #0 to host 127.0.0.1 left intact > * Closing connection #0 > > After that I also tried compacting the _replicator database, but also > that didn't change anything. > > > -- Stefan
