Bug #2642
Updated by Jonathan CLARKE almost 12 years ago
When a node (its uuid is db78b5ab-387a-418a-88a6-481ad71fc34c) send his inventory to the Rudder server for the first time, it displays i got an error about it's promises directory. This is normal, since it doesn't exist yet, but can be alarming for the user: <pre> rudder> Couldn't resolve filename /var/rudder/share/db78b5ab-387a-418a-88a6-481ad71fc34c/rules/cfengine-community from host 192.168.42.81 rudder> !!! System error for lstat: "No such file or directory" rudder> Couldn't stat filename /var/rudder/share/db78b5ab-387a-418a-88a6-481ad71fc34c requested by host 192.168.42.81 rudder> !!! System error for lstat: "No such file or directory" rudder> Access control in sync rudder> From (host=192.168.42.81,user=root,ip=192.168.42.81) rudder> REFUSAL of request from connecting host: (SYNCH 1341836740 STAT /var/rudder/share/db78b5ab-387a-418a-88a6-481ad71fc34c/rules/cfengine-community) </pre> We should change, or add, Should it not be created before ? Does the error message to say something like "This error is happenning because this node initial promises have changed since 2.4.0 ? That bug has not yet been accepted by detected in the Rudder server. Visit new 2.5.0 development environment after resolving the web interface to accept it." password conflicts