[chef] Re: Re: Re: Re: Re: Can't re-create node after restoring CouchDB

[AJ Christensen < >]

Right, clients' public keys not stored on disk, AFAIK, (?) -- stored in Couch.

As I mentioned, you probably did not take a consistent backup, or
there was some problem with restoring a document. Have you inspected
all documents using the _clients design document? I would anticipate
finding a dodgy document, removing/editing it, and being able to
proceed.

--AJ

On 27 March 2013 09:05, Ranjib Dey 
<
 >
 wrote:
> fujin, the public keys of the clients are not stored? whats does knife
> client list enumerates then?
>
>
> On Tue, Mar 26, 2013 at 1:03 PM, AJ Christensen 
> <
 >
>  wrote:
>>
>> You might have not taken a consistent backup?
>>
>> Clients aren't stored on the file-system -- only cookbook manifests
>> (IIRC), and only in chef10, it's different (Bookshelf) in chef11.
>>
>> Jump into your database and delete the matching client documents.
>>
>> --AJ
>>
>> On 27 March 2013 09:01, Jochen Lillich 
>> <
 >
>>  wrote:
>> > Ranjib Dey wrote:
>> >
>> >> delete the client from chef server using knife (knife client delete
>> >> <node name>), and delete the old client.pem from the node itself. then
>> >> run chef-client on the node, and it will reregister itself.
>> >
>> > I already tried that, but there is no client with that name:
>> >
>> >     $ knife client delete MYNODE
>> >     Do you really want to delete MYNODE? (Y/N) y
>> >     ERROR: JSON::ParserError: 743: unexpected token at 'null'
>> >
>> > Neither `knife client list` nor the CouchDB web UI display the client
>> > name.
>> >
>> > That's why I asked if there could be something outside CouchDB (maybe
>> > the server filesystem) that prevents re-creating the client. Some kind of
>> > remains from my node creation today.
>> >
>> > Thanks,
>> >   Jochen
>> >
>
>