[rudder-users] Unable to add the same node

[Olivier Desport]

Le 01/03/2013 09:59, Vincent Membré a écrit :
> Hello Olivier,
>
> Le 01/03/2013 09:41, Olivier Desport a écrit :
>>
>>
>>
>>
>> Le 01/03/2013 09:08, Jonathan Clarke a écrit :
>>> On 01/03/13 08:59, Olivier Desport wrote:
>>>>
>>>>
>>>>
>>>>
>>>> Le 28/02/2013 14:29, Jonathan Clarke a écrit :
>>>>> Hello Olivier,
>>>>>
>>>>> On 28/02/13 12:26, Olivier Desport wrote:
>>>>>> Hello,
>>>>>>
>>>>>> I'm working with Rudder 2.4. I've deleted a node in the web 
>>>>>> interface because I had to install a new server with the same 
>>>>>> name. When I try to add this node, it never appears in "Accept 
>>>>>> new node" menu. Can you tell me the way to clean this node in 
>>>>>> Postgre, LDAP and files ?
>>>>>>
>>>>>> The logs for this node on the Rudder server :
>>>>>>
>>>>>> Feb 28 12:21:47 celebrimbor cf-serverd[17935]: Accepting 
>>>>>> connection from "172.31.136.112"
>>>>>> Feb 28 12:21:47 celebrimbor cf-serverd[17935]:  REFUSAL of 
>>>>>> request from connecting host: (SYNCH 1362050507 STAT 
>>>>>> /var/rudder/share/d2abce4d-630e-4d05-932f-8e2b87942392/rules/cfengine-community)
>>>>>
>>>>> For the node to reappear in "Accept new nodes", it needs to send a 
>>>>> new inventory. However, by default this only happens at night 
>>>>> (between 0:00 and 6:00).
>>>>>
>>>>> You can force the node to run an inventory *now*, by running:
>>>>> /var/rudder/cfengine-community/bin/cf-agent -KI -Dforce_inventory
>>>>> (see 
>>>>> http://www.rudder-project.org/rudder-doc-2.4/rudder-doc.html#_inventory) 
>>>>>
>>>>>
>>>>> Then, it should appear in the Accept New Nodes screen (after 5-10 
>>>>> minutes).
>>>>>
>>>>> Let me know if this works for you!
>>>>
>>>> I've launched this command several times but there is still no 
>>>> pending node.
>>>
>>> Ah, that's funny. To clarify, this command should be run on the 
>>> node, not on the server. Is that what you tried?
>>>
>>> If that still does not work, try resetting the node's promises, by 
>>> running these commands (again, on the node, not on the server):
>>> http://www.rudder-project.org/rudder-doc-2.4/rudder-doc.html#_reinitialize_policies_for_a_node
>> It worked for one node but failed for the second one :
>>
>> INFO 
>> com.normation.inventory.provisioning.endpoint.FusionReportEndpoint - 
>> New input report: 'node-1-2013-02-28-14-14-07.ocs'
>> [2013-03-01 09:37:27] ERROR 
>> com.normation.inventory.provisioning.endpoint.FusionReportEndpoint - 
>> Error when trying to parse report:
>> Can't parse the input report, aborting
>> cause: Cannot parse uploaded file as an XML Fusion Inventory report
>>
>> [2013-03-01 09:37:27] ERROR 
>> com.normation.inventory.provisioning.endpoint.FusionReportEndpoint - 
>> Exception was:
>> org.xml.sax.SAXParseException: XML document structures must start and 
>> end within the same entity.
>>     at 
>> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195) 
>> ~[na:1.6.0_26]
>>
>>
> Really strange error for an inventory. Can't imagine why it happens
>
> Please, can you send us the inventory that does not work properly?
>
> You'll find it in /var/rudder/inventories/received (maybe in another 
> subdirectory of inventories)
>
> You can change some of the datas inside if you want to, we only need 
> the format of the inventory.


The second node finaly appeared in the interface. Yesterday, I've began 
to delete this node and tried to cancel the action on the interface. It 
could explain the above messages.

I think that the reinitialization of the policies on the nodes solved 
the problem.

Thanks for your precious help.

>
> Vincent
>
>
>
> _______________________________________________
> rudder-users mailing list
> rudder-users at lists.rudder-project.org
> http://www.rudder-project.org/mailman/listinfo/rudder-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.rudder-project.org/pipermail/rudder-users/attachments/20130301/7ff12264/attachment.html>