Bug #6290
closed
ERROR message after update "could not parse rudder user (tag OWNER) from rudder specific inventory"
Description
I guess this affects existing nodes, maybe they lack some kind of "default" tag.
Since it is an "ERROR" I'm trying to find how it comes to happen.
Already updated all agents to 3.0.x but that doesn't change it. It seems there's some post-update action I'm missing.
I haven't found tag-specific docs yet so grin my assumption is that this either is normally handled by the update procedure or it's not an ERROR but just some info.
@[2015-02-21 11:36:05] INFO com.normation.inventory.provisioning.endpoint.FusionReportEndpoint - New input report: 'rudderc1-2014-09-07-14-14-56.ocs'
[2015-02-21 11:36:05] INFO com.normation.inventory.provisioning.endpoint.FusionReportEndpoint - Report 'rudderc1-2014-09-07-14-14-56.ocs' parsed in 191 milliseconds, sending to save engine.
[2015-02-21 11:36:06] INFO com.normation.inventory.provisioning.endpoint.FusionReportEndpoint - Report file processed in 960 milliseconds
[2015-02-21 12:06:06] INFO com.normation.inventory.provisioning.endpoint.FusionReportEndpoint - New input report: 'rudderc2-2014-08-24-17-43-01.ocs'
[2015-02-21 12:06:06] INFO com.normation.inventory.provisioning.endpoint.FusionReportEndpoint - Report 'rudderc2-2014-08-24-17-43-01.ocs' parsed in 136 milliseconds, sending to save engine.
[2015-02-21 12:06:07] INFO com.normation.inventory.provisioning.endpoint.FusionReportEndpoint - Report file processed in 689 milliseconds
[2015-02-21 12:27:01] INFO com.normation.inventory.provisioning.endpoint.FusionReportEndpoint - New input report: 'rudders1-2014-08-10-16-05-30.ocs'
[2015-02-21 12:27:01] ERROR com.normation.inventory.provisioning.fusion.FusionReportUnmarshaller - Error when parsing rudder specific inventory, continue but used report without those datas: could not parse rudder specific inventory <- could not parse rudder user (tag OWNER) from rudder specific inventory
[2015-02-21 12:27:01] INFO com.normation.inventory.provisioning.endpoint.FusionReportEndpoint - Report 'rudders1-2014-08-10-16-05-30.ocs' parsed in 217 milliseconds, sending to save engine.
[2015-02-21 12:27:01] INFO com.normation.inventory.provisioning.endpoint.FusionReportEndpoint - New input report: 'rudderc4-2014-09-07-14-19-29.ocs'
[2015-02-21 12:27:02] ERROR com.normation.inventory.provisioning.fusion.FusionReportUnmarshaller - Error when parsing rudder specific inventory, continue but used report without those datas: could not parse rudder specific inventory <- could not parse rudder user (tag OWNER) from rudder specific inventory
[2015-02-21 12:27:02] INFO com.normation.inventory.provisioning.endpoint.FusionReportEndpoint - Report 'rudderc4-2014-09-07-14-19-29.ocs' parsed in 456 milliseconds, sending to save engine.
[2015-02-21 12:27:02] INFO com.normation.inventory.provisioning.endpoint.FusionReportEndpoint - New input report: 'rudderc3-2014-08-24-19-36-50.ocs'
[2015-02-21 12:27:02] INFO com.normation.inventory.provisioning.endpoint.FusionReportEndpoint - Report file processed in 993 milliseconds
[2015-02-21 12:27:03] ERROR com.normation.inventory.provisioning.fusion.FusionReportUnmarshaller - Error when parsing rudder specific inventory, continue but used report without those datas: could not parse rudder specific inventory <- could not parse rudder user (tag OWNER) from rudder specific inventory
[2015-02-21 12:27:03] INFO com.normation.inventory.provisioning.endpoint.FusionReportEndpoint - Report 'rudderc3-2014-08-24-19-36-50.ocs' parsed in 494 milliseconds, sending to save engine.
[2015-02-21 12:27:03] INFO com.normation.inventory.provisioning.endpoint.FusionReportEndpoint - New input report: 'rudderc1-2014-09-07-14-14-56.ocs'
[2015-02-21 12:27:03] INFO com.normation.inventory.provisioning.endpoint.FusionReportEndpoint - Report file processed in 821 milliseconds
[2015-02-21 12:27:03] INFO com.normation.inventory.provisioning.endpoint.FusionReportEndpoint - Report 'rudderc1-2014-09-07-14-14-56.ocs' parsed in 550 milliseconds, sending to save engine.
[2015-02-21 12:27:03] INFO com.normation.inventory.provisioning.endpoint.FusionReportEndpoint - New input report: 'rudderc2-2014-08-24-17-43-01.ocs'
[2015-02-21 12:27:04] ERROR com.normation.inventory.provisioning.fusion.FusionReportUnmarshaller - Error when parsing rudder specific inventory, continue but used report without those datas: could not parse rudder specific inventory <- could not parse rudder user (tag OWNER) from rudder specific inventory
[2015-02-21 12:27:04] INFO com.normation.inventory.provisioning.endpoint.FusionReportEndpoint - Report 'rudderc2-2014-08-24-17-43-01.ocs' parsed in 441 milliseconds, sending to save engine.
[2015-02-21 12:27:04] INFO com.normation.inventory.provisioning.endpoint.FusionReportEndpoint - Report file processed in 778 milliseconds
[2015-02-21 12:27:05] INFO com.normation.inventory.provisioning.endpoint.FusionReportEndpoint - Report file processed in 862 milliseconds
[2015-02-21 12:27:05] INFO com.normation.inventory.provisioning.endpoint.FusionReportEndpoint - Report file processed in 477 milliseconds
@
My next attempt would be re-running the update script on the server in case something botched the update procedure (which completed OK).
(I had outdated postgresql at the time, which is now fixed)
Updated by Nicolas CHARLES almost 10 years ago
- Status changed from New to Discussion
- Assignee set to Florian Heigl
- Target version set to 3.0.2
Hi Florian
Thanks for your bug report. I tried to reproduce this, whithout success.
Could you give me more details about rudders1-2014-08-10-16-05-30.ocs and the node that generated it ?
Notably:
- which OS/architecture ?
- does this file contain a "OWNER" tag
- the name of the file should ocntains the uuid, but here it contains a name; so I gather that your server is not a 3.0.x server; am I correct?
Updated by Vincent MEMBRÉ almost 10 years ago
- Category set to 26
OWNER tag in Rudder specific data is defined by running command "whoami" on the node.
Is it available on your nodes ?
As Nicolas said, is it possible to get an inventory generated by one of your Nodes? (Maybe you want to send it privately vincent.membre@normation.com)
Updated by Vincent MEMBRÉ almost 10 years ago
I think this is not related to update to 3.0 (we have not change fusion inventory version in 3.0, it was the same in 2.11)
Updated by Florian Heigl almost 10 years ago
this can be closed:
It was an update issue.
The rudder-techniques package had not updated to a 3.x version and so the base techniques delivered to the system and used by the root server itself had been heavily incompatible.
After updating the package & repeating the update techniques steps it took a short period and then the system completely stabilized.
(In memoriam of Sun Microsystems I suggest this be marketed as unpredicted self healing)
Updated by François ARMAND almost 10 years ago
- Status changed from Discussion to Rejected
Closed as unpredicted self healing :)
Updated by Benoît PECCATTE almost 10 years ago
- Category changed from 26 to Web - Nodes & inventories