Re: [etch-users] How can I debug what happens on Etch server when a client does --list-files

[Jason H. <jh...@ap...>]

On Jun 6, 2011, at 9:09 AM, Johnston, Nathaniel wrote:

> Jason,
> 
> OK, so I am correct that the functional base of the etch repository is "$etchserverbase/[output of $etchserverbase/nodetagger]/source"?

Yes

> For example, if $etchserverbase was set to /etc/etchserver13 and nodetagger returns "foo" then to configure /etc/motd on a remote node I would set up "/etc/etchserver13/foo/source/etc/motd/"?

Yes

> In the example scenario above, where would the Etch server expect to find nodes.xml?  I believe it would be in the same directory as the "source" subdirectory, i.e. /etc/etchserver13/foo/nodes.xml.

Yes

> However, when I see hosts try to check in, I see log messages like:
> 
> No entry found for node edgenode-02p.internal in nodes.xml
> 
> In nodes.xml there is an entry for this host: 
> 
>        <node name="edgenode-02p.internal">
>                <group> edge_hosts </group>
>        </node>

That's definitely odd.  Double-check the etchdebug.log file and make sure the line like "Using /etc/etchserver/trunk as tagged base for node <blah>" matches up with your expectations.

> Does the etch server drop a log message to indicate whether it got node group association from the nodes.xml or from the nodegrouper script?

Yes, in etchdebug.log (when the client is run with --debug).  You'll get a set of lines that look like the following.  In retrospect the phrase "native groups" isn't super obvious, but those are groups from nodes.xml.

Native groups for node <blah>: 
Added groups for node <blah> due to node group hierarchy: 
Added groups for node <blah> due to external node grouper: 
Total groups for node <blah>: