thr3ads.net - Puppet users - [Puppet Users] help with err: Could not find node [Nov 2011]

If this information is useful, please help other people find it:
Share via:

weloki

2011-Nov-01 20:27 UTC

[Puppet Users] help with err: Could not find node

I''m running Ubuntu 10.04 LTS and I just installed Puppet and
puppetmasterd (both 0.25.4) along with the puppet-dashboard v1.2.0 and
Foreman 0.3. Puppet and the dashboard were working fine with just the
master server and a separate client until I installed and configured
Foreman. Now I keep getting the following errors...

On the puppet master server:

debug: Executing ''/usr/bin/env PUPPET_DASHBOARD_URL=http://localhost:
3000 /root/puppet-dashboard/bin/external_node puppet.mydomain.com''
err: Failed to find puppet.mydomain.com via exec: Execution of ''/usr/
bin/env PUPPET_DASHBOARD_URL=http://localhost:3000 /root/puppet-
dashboard/bin/external_node puppet.mydomain.com'' returned 126: /usr/
bin/env: /root/puppet-dashboard/bin/external_node: Permission denied
err: Could not find node ''puppet.mydomain.com''; cannot compile

On the client, doing puppetd -vtd:

debug: Failed to load library ''selinux'' for feature
''selinux''
debug: Puppet::Type::User::ProviderUser_role_add: file rolemod does
not exist
debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/
dscl does not exist
debug: Failed to load library ''ldap'' for feature
''ldap''
debug: Puppet::Type::User::ProviderLdap: feature ldap is missing
debug: Puppet::Type::User::ProviderPw: file pw does not exist
debug: /File[/var/lib/puppetmaster/ssl/certs/puppet.mydomain.com.pem]:
Autorequiring File[/var/lib/puppetmaster/ssl/certs]
debug: /File[/var/lib/puppetmaster/state/classes.txt]: Autorequiring
File[/var/lib/puppetmaster/state]
debug: /File[/var/lib/puppetmaster/state/state.yaml]: Autorequiring
File[/var/lib/puppetmaster/state]
debug: /File[/var/lib/puppetmaster/facts]: Autorequiring File[/var/lib/
puppetmaster]
debug: /File[/var/lib/puppetmaster/ssl]: Autorequiring File[/var/lib/
puppetmaster]
debug: /File[/var/lib/puppetmaster/ssl/crl.pem]: Autorequiring File[/
var/lib/puppetmaster/ssl]
debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet]
debug: /File[/var/lib/puppetmaster/ssl/certs]: Autorequiring File[/var/
lib/puppetmaster/ssl]
debug: /File[/var/run/puppetmaster/puppetd.pid]: Autorequiring File[/
var/run/puppetmaster]
debug: /File[/var/lib/puppetmaster/puppetmaster]: Autorequiring File[/
var/lib/puppetmaster]
debug: /File[/var/lib/puppetmaster/state]: Autorequiring File[/var/lib/
puppetmaster]
debug: /File[/var/lib/puppetmaster/ssl/public_keys]: Autorequiring
File[/var/lib/puppetmaster/ssl]
debug: /File[/var/lib/puppetmaster/client_yaml]: Autorequiring File[/
var/lib/puppetmaster]
debug: /File[/var/lib/puppetmaster/ssl/private]: Autorequiring File[/
var/lib/puppetmaster/ssl]
debug: /File[/var/lib/puppetmaster/ssl/certs/ca.pem]: Autorequiring
File[/var/lib/puppetmaster/ssl/certs]
debug: /File[/var/lib/puppetmaster/ssl/public_keys/
puppet.mydomain.com.pem]: Autorequiring File[/var/lib/puppetmaster/ssl/
public_keys]
debug: /File[/var/lib/puppetmaster/ssl/private_keys]: Autorequiring
File[/var/lib/puppetmaster/ssl]
debug: /File[/var/lib/puppetmaster/lib]: Autorequiring File[/var/lib/
puppetmaster]
debug: /File[/var/lib/puppetmaster/ssl/private_keys/
puppet.mydomain.com.pem]: Autorequiring File[/var/lib/puppetmaster/ssl/
private_keys]
debug: /File[/var/lib/puppetmaster/clientbucket]: Autorequiring File[/
var/lib/puppetmaster]
debug: /File[/var/lib/puppetmaster/state/graphs]: Autorequiring File[/
var/lib/puppetmaster/state]
debug: /File[/var/lib/puppetmaster/ssl/certificate_requests]:
Autorequiring File[/var/lib/puppetmaster/ssl]
debug: Finishing transaction 70213661363800 with 0 changes
debug: Using cached certificate for ca, good until Sun Oct 23 19:49:36
UTC 2016
debug: Using cached certificate for puppet.mydomain.com, good until
Sun Oct 23 20:00:26 UTC 2016
debug: Loaded state in 0.00 seconds
debug: Executing ''/etc/puppet/etckeeper-commit-pre''
debug: Using cached certificate for ca, good until Sun Oct 23 19:49:36
UTC 2016
debug: Using cached certificate for puppet.mydomain.com, good until
Sun Oct 23 20:00:26 UTC 2016
debug: Using cached certificate_revocation_list for ca, good until
debug: catalog supports formats: b64_zlib_yaml marshal pson raw yaml;
using pson
err: Could not retrieve catalog from remote server: Error 400 on
SERVER: Could not find node ''puppet-client0.mydomain.com'';
cannot
compile
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run

My puppet.conf:

[main]
logdir=$vardir/puppetmaster
vardir=/var/lib/puppetmaster
ssldir=$vardir/puppetmaster/ssl
rundir=/var/run/puppetmaster
factpath=$vardir/lib/facter
pluginsync=false
templatedir=$confdir/templates
prerun_command=/etc/puppet/etckeeper-commit-pre
postrun_command=/etc/puppet/etckeeper-commit-post
reports=log, foreman

[puppetmasterd]
modulepath = /etc/puppet/modules
certname=puppet
reports = store, puppet_dashboard
node_terminus = exec
external_nodes = /usr/bin/env PUPPET_DASHBOARD_URL=http://localhost:
3000 /root/puppet-dashboard/bin/external_node

[puppetd]
server=puppet
vardir=/var/lib/puppetmaster
ssldir=$vardir/ssl
report = true

In site.pp I do have:

node default {
  ...
}

And in nodes.pp:

node basenode {
  ...
}

# Define the nodes (puppets)
node ''puppet-client0.mydomain.com'' inherits basenode {
}

Any help would be greatly appreciated. Thanks in advance.

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Christopher Wood

2011-Nov-01 20:38 UTC

head link

Re: [Puppet Users] help with err: Could not find node

At the top of your email:

Could not find node ''puppet.mydomain.com''

At the bottom of your email:

node default {
}
node basenode {
}
node ''puppet-client0.mydomain.com'' inherits basenode {
}

Does it work when you explicitly define this node?

node ''puppet.mydomain.com'' {
}


On Tue, Nov 01, 2011 at 01:27:40PM -0700, weloki wrote:> I''m running Ubuntu 10.04 LTS and I just installed Puppet and
> puppetmasterd (both 0.25.4) along with the puppet-dashboard v1.2.0 and
> Foreman 0.3. Puppet and the dashboard were working fine with just the
> master server and a separate client until I installed and configured
> Foreman. Now I keep getting the following errors...
> 
> On the puppet master server:
> 
> debug: Executing ''/usr/bin/env
PUPPET_DASHBOARD_URL=http://localhost:
> 3000 /root/puppet-dashboard/bin/external_node puppet.mydomain.com''
> err: Failed to find puppet.mydomain.com via exec: Execution of
''/usr/
> bin/env PUPPET_DASHBOARD_URL=http://localhost:3000 /root/puppet-
> dashboard/bin/external_node puppet.mydomain.com'' returned 126:
/usr/
> bin/env: /root/puppet-dashboard/bin/external_node: Permission denied
> err: Could not find node ''puppet.mydomain.com''; cannot
compile
> 
> On the client, doing puppetd -vtd:
> 
> debug: Failed to load library ''selinux'' for feature
''selinux''
> debug: Puppet::Type::User::ProviderUser_role_add: file rolemod does
> not exist
> debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/
> dscl does not exist
> debug: Failed to load library ''ldap'' for feature
''ldap''
> debug: Puppet::Type::User::ProviderLdap: feature ldap is missing
> debug: Puppet::Type::User::ProviderPw: file pw does not exist
> debug: /File[/var/lib/puppetmaster/ssl/certs/puppet.mydomain.com.pem]:
> Autorequiring File[/var/lib/puppetmaster/ssl/certs]
> debug: /File[/var/lib/puppetmaster/state/classes.txt]: Autorequiring
> File[/var/lib/puppetmaster/state]
> debug: /File[/var/lib/puppetmaster/state/state.yaml]: Autorequiring
> File[/var/lib/puppetmaster/state]
> debug: /File[/var/lib/puppetmaster/facts]: Autorequiring File[/var/lib/
> puppetmaster]
> debug: /File[/var/lib/puppetmaster/ssl]: Autorequiring File[/var/lib/
> puppetmaster]
> debug: /File[/var/lib/puppetmaster/ssl/crl.pem]: Autorequiring File[/
> var/lib/puppetmaster/ssl]
> debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet]
> debug: /File[/var/lib/puppetmaster/ssl/certs]: Autorequiring File[/var/
> lib/puppetmaster/ssl]
> debug: /File[/var/run/puppetmaster/puppetd.pid]: Autorequiring File[/
> var/run/puppetmaster]
> debug: /File[/var/lib/puppetmaster/puppetmaster]: Autorequiring File[/
> var/lib/puppetmaster]
> debug: /File[/var/lib/puppetmaster/state]: Autorequiring File[/var/lib/
> puppetmaster]
> debug: /File[/var/lib/puppetmaster/ssl/public_keys]: Autorequiring
> File[/var/lib/puppetmaster/ssl]
> debug: /File[/var/lib/puppetmaster/client_yaml]: Autorequiring File[/
> var/lib/puppetmaster]
> debug: /File[/var/lib/puppetmaster/ssl/private]: Autorequiring File[/
> var/lib/puppetmaster/ssl]
> debug: /File[/var/lib/puppetmaster/ssl/certs/ca.pem]: Autorequiring
> File[/var/lib/puppetmaster/ssl/certs]
> debug: /File[/var/lib/puppetmaster/ssl/public_keys/
> puppet.mydomain.com.pem]: Autorequiring File[/var/lib/puppetmaster/ssl/
> public_keys]
> debug: /File[/var/lib/puppetmaster/ssl/private_keys]: Autorequiring
> File[/var/lib/puppetmaster/ssl]
> debug: /File[/var/lib/puppetmaster/lib]: Autorequiring File[/var/lib/
> puppetmaster]
> debug: /File[/var/lib/puppetmaster/ssl/private_keys/
> puppet.mydomain.com.pem]: Autorequiring File[/var/lib/puppetmaster/ssl/
> private_keys]
> debug: /File[/var/lib/puppetmaster/clientbucket]: Autorequiring File[/
> var/lib/puppetmaster]
> debug: /File[/var/lib/puppetmaster/state/graphs]: Autorequiring File[/
> var/lib/puppetmaster/state]
> debug: /File[/var/lib/puppetmaster/ssl/certificate_requests]:
> Autorequiring File[/var/lib/puppetmaster/ssl]
> debug: Finishing transaction 70213661363800 with 0 changes
> debug: Using cached certificate for ca, good until Sun Oct 23 19:49:36
> UTC 2016
> debug: Using cached certificate for puppet.mydomain.com, good until
> Sun Oct 23 20:00:26 UTC 2016
> debug: Loaded state in 0.00 seconds
> debug: Executing ''/etc/puppet/etckeeper-commit-pre''
> debug: Using cached certificate for ca, good until Sun Oct 23 19:49:36
> UTC 2016
> debug: Using cached certificate for puppet.mydomain.com, good until
> Sun Oct 23 20:00:26 UTC 2016
> debug: Using cached certificate_revocation_list for ca, good until
> debug: catalog supports formats: b64_zlib_yaml marshal pson raw yaml;
> using pson
> err: Could not retrieve catalog from remote server: Error 400 on
> SERVER: Could not find node
''puppet-client0.mydomain.com''; cannot
> compile
> warning: Not using cache on failed catalog
> err: Could not retrieve catalog; skipping run
> 
> My puppet.conf:
> 
> [main]
> logdir=$vardir/puppetmaster
> vardir=/var/lib/puppetmaster
> ssldir=$vardir/puppetmaster/ssl
> rundir=/var/run/puppetmaster
> factpath=$vardir/lib/facter
> pluginsync=false
> templatedir=$confdir/templates
> prerun_command=/etc/puppet/etckeeper-commit-pre
> postrun_command=/etc/puppet/etckeeper-commit-post
> reports=log, foreman
> 
> [puppetmasterd]
> modulepath = /etc/puppet/modules
> certname=puppet
> reports = store, puppet_dashboard
> node_terminus = exec
> external_nodes = /usr/bin/env PUPPET_DASHBOARD_URL=http://localhost:
> 3000 /root/puppet-dashboard/bin/external_node
> 
> [puppetd]
> server=puppet
> vardir=/var/lib/puppetmaster
> ssldir=$vardir/ssl
> report = true
> 
> In site.pp I do have:
> 
> node default {
>   ...
> }
> 
> And in nodes.pp:
> 
> node basenode {
>   ...
> }
> 
> # Define the nodes (puppets)
> node ''puppet-client0.mydomain.com'' inherits basenode {
> }
> 
> Any help would be greatly appreciated. Thanks in advance.
> 
> -- 
> You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
> 
> 
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

weloki

2011-Nov-01 20:56 UTC

head link

[Puppet Users] Re: help with err: Could not find node

When I put that line in nodes.pp I get:

err: Could not retrieve catalog from remote server: Connection refused
- connect (2)


On Nov 1, 4:38 pm, Christopher Wood <christopher_w...@pobox.com>
wrote:> At the top of your email:
>
> Could not find node ''puppet.mydomain.com''
>
> At the bottom of your email:
>
> node default {}
> node basenode {
> }
>
> node ''puppet-client0.mydomain.com'' inherits basenode {
>
> }
>
> Does it work when you explicitly define this node?
>
> node ''puppet.mydomain.com'' {
>
> }
> On Tue, Nov 01, 2011 at 01:27:40PM -0700, weloki wrote:
> > I''m running Ubuntu 10.04 LTS and I just installed Puppet and
> > puppetmasterd (both 0.25.4) along with the puppet-dashboard v1.2.0 and
> > Foreman 0.3. Puppet and the dashboard were working fine with just the
> > master server and a separate client until I installed and configured
> > Foreman. Now I keep getting the following errors...
>
> > On the puppet master server:
>
> > debug: Executing ''/usr/bin/env
PUPPET_DASHBOARD_URL=http://localhost:
> > 3000 /root/puppet-dashboard/bin/external_node
puppet.mydomain.com''
> > err: Failed to find puppet.mydomain.com via exec: Execution of
''/usr/
> > bin/env PUPPET_DASHBOARD_URL=http://localhost:3000/root/puppet-
> > dashboard/bin/external_node puppet.mydomain.com'' returned
126: /usr/
> > bin/env: /root/puppet-dashboard/bin/external_node: Permission denied
> > err: Could not find node ''puppet.mydomain.com'';
cannot compile
>
> > On the client, doing puppetd -vtd:
>
> > debug: Failed to load library ''selinux'' for feature
''selinux''
> > debug: Puppet::Type::User::ProviderUser_role_add: file rolemod does
> > not exist
> > debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/
> > dscl does not exist
> > debug: Failed to load library ''ldap'' for feature
''ldap''
> > debug: Puppet::Type::User::ProviderLdap: feature ldap is missing
> > debug: Puppet::Type::User::ProviderPw: file pw does not exist
> > debug: /File[/var/lib/puppetmaster/ssl/certs/puppet.mydomain.com.pem]:
> > Autorequiring File[/var/lib/puppetmaster/ssl/certs]
> > debug: /File[/var/lib/puppetmaster/state/classes.txt]: Autorequiring
> > File[/var/lib/puppetmaster/state]
> > debug: /File[/var/lib/puppetmaster/state/state.yaml]: Autorequiring
> > File[/var/lib/puppetmaster/state]
> > debug: /File[/var/lib/puppetmaster/facts]: Autorequiring
File[/var/lib/
> > puppetmaster]
> > debug: /File[/var/lib/puppetmaster/ssl]: Autorequiring File[/var/lib/
> > puppetmaster]
> > debug: /File[/var/lib/puppetmaster/ssl/crl.pem]: Autorequiring File[/
> > var/lib/puppetmaster/ssl]
> > debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet]
> > debug: /File[/var/lib/puppetmaster/ssl/certs]: Autorequiring
File[/var/
> > lib/puppetmaster/ssl]
> > debug: /File[/var/run/puppetmaster/puppetd.pid]: Autorequiring File[/
> > var/run/puppetmaster]
> > debug: /File[/var/lib/puppetmaster/puppetmaster]: Autorequiring File[/
> > var/lib/puppetmaster]
> > debug: /File[/var/lib/puppetmaster/state]: Autorequiring
File[/var/lib/
> > puppetmaster]
> > debug: /File[/var/lib/puppetmaster/ssl/public_keys]: Autorequiring
> > File[/var/lib/puppetmaster/ssl]
> > debug: /File[/var/lib/puppetmaster/client_yaml]: Autorequiring File[/
> > var/lib/puppetmaster]
> > debug: /File[/var/lib/puppetmaster/ssl/private]: Autorequiring File[/
> > var/lib/puppetmaster/ssl]
> > debug: /File[/var/lib/puppetmaster/ssl/certs/ca.pem]: Autorequiring
> > File[/var/lib/puppetmaster/ssl/certs]
> > debug: /File[/var/lib/puppetmaster/ssl/public_keys/
> > puppet.mydomain.com.pem]: Autorequiring
File[/var/lib/puppetmaster/ssl/
> > public_keys]
> > debug: /File[/var/lib/puppetmaster/ssl/private_keys]: Autorequiring
> > File[/var/lib/puppetmaster/ssl]
> > debug: /File[/var/lib/puppetmaster/lib]: Autorequiring File[/var/lib/
> > puppetmaster]
> > debug: /File[/var/lib/puppetmaster/ssl/private_keys/
> > puppet.mydomain.com.pem]: Autorequiring
File[/var/lib/puppetmaster/ssl/
> > private_keys]
> > debug: /File[/var/lib/puppetmaster/clientbucket]: Autorequiring File[/
> > var/lib/puppetmaster]
> > debug: /File[/var/lib/puppetmaster/state/graphs]: Autorequiring File[/
> > var/lib/puppetmaster/state]
> > debug: /File[/var/lib/puppetmaster/ssl/certificate_requests]:
> > Autorequiring File[/var/lib/puppetmaster/ssl]
> > debug: Finishing transaction 70213661363800 with 0 changes
> > debug: Using cached certificate for ca, good until Sun Oct 23 19:49:36
> > UTC 2016
> > debug: Using cached certificate for puppet.mydomain.com, good until
> > Sun Oct 23 20:00:26 UTC 2016
> > debug: Loaded state in 0.00 seconds
> > debug: Executing ''/etc/puppet/etckeeper-commit-pre''
> > debug: Using cached certificate for ca, good until Sun Oct 23 19:49:36
> > UTC 2016
> > debug: Using cached certificate for puppet.mydomain.com, good until
> > Sun Oct 23 20:00:26 UTC 2016
> > debug: Using cached certificate_revocation_list for ca, good until
> > debug: catalog supports formats: b64_zlib_yaml marshal pson raw yaml;
> > using pson
> > err: Could not retrieve catalog from remote server: Error 400 on
> > SERVER: Could not find node
''puppet-client0.mydomain.com''; cannot
> > compile
> > warning: Not using cache on failed catalog
> > err: Could not retrieve catalog; skipping run
>
> > My puppet.conf:
>
> > [main]
> > logdir=$vardir/puppetmaster
> > vardir=/var/lib/puppetmaster
> > ssldir=$vardir/puppetmaster/ssl
> > rundir=/var/run/puppetmaster
> > factpath=$vardir/lib/facter
> > pluginsync=false
> > templatedir=$confdir/templates
> > prerun_command=/etc/puppet/etckeeper-commit-pre
> > postrun_command=/etc/puppet/etckeeper-commit-post
> > reports=log, foreman
>
> > [puppetmasterd]
> > modulepath = /etc/puppet/modules
> > certname=puppet
> > reports = store, puppet_dashboard
> > node_terminus = exec
> > external_nodes = /usr/bin/env PUPPET_DASHBOARD_URL=http://localhost:
> > 3000 /root/puppet-dashboard/bin/external_node
>
> > [puppetd]
> > server=puppet
> > vardir=/var/lib/puppetmaster
> > ssldir=$vardir/ssl
> > report = true
>
> > In site.pp I do have:
>
> > node default {
> >   ...
> > }
>
> > And in nodes.pp:
>
> > node basenode {
> >   ...
> > }
>
> > # Define the nodes (puppets)
> > node ''puppet-client0.mydomain.com'' inherits basenode
{
> > }
>
> > Any help would be greatly appreciated. Thanks in advance.
>
> > --
> > You received this message because you are subscribed to the Google
Groups "Puppet Users" group.
> > To post to this group, send email to puppet-users@googlegroups.com.
> > To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
> > For more options, visit this group
athttp://groups.google.com/group/puppet-users?hl=en.
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Christopher Wood

2011-Nov-01 20:59 UTC

head link

Re: [Puppet Users] Re: help with err: Could not find node

On Tue, Nov 01, 2011 at 01:56:53PM -0700, weloki wrote:> When I put that line in nodes.pp I get:
> 
> err: Could not retrieve catalog from remote server: Connection refused
> - connect (2)
So what dit he puppetmaster say about this agent run?

Also, keep digging into your own email. You may have file permission issues:

returned 126: /usr/bin/env: /root/puppet-dashboard/bin/external_node: Permission
denied
 > On Nov 1, 4:38 pm, Christopher Wood <christopher_w...@pobox.com>
> wrote:
> > At the top of your email:
> >
> > Could not find node ''puppet.mydomain.com''
> >
> > At the bottom of your email:
> >
> > node default {}
> > node basenode {
> > }
> >
> > node ''puppet-client0.mydomain.com'' inherits basenode
{
> >
> > }
> >
> > Does it work when you explicitly define this node?
> >
> > node ''puppet.mydomain.com'' {
> >
> > }
> > On Tue, Nov 01, 2011 at 01:27:40PM -0700, weloki wrote:
> > > I''m running Ubuntu 10.04 LTS and I just installed Puppet
and
> > > puppetmasterd (both 0.25.4) along with the puppet-dashboard
v1.2.0 and
> > > Foreman 0.3. Puppet and the dashboard were working fine with just
the
> > > master server and a separate client until I installed and
configured
> > > Foreman. Now I keep getting the following errors...
> >
> > > On the puppet master server:
> >
> > > debug: Executing ''/usr/bin/env
PUPPET_DASHBOARD_URL=http://localhost:
> > > 3000 /root/puppet-dashboard/bin/external_node
puppet.mydomain.com''
> > > err: Failed to find puppet.mydomain.com via exec: Execution of
''/usr/
> > > bin/env PUPPET_DASHBOARD_URL=http://localhost:3000/root/puppet-
> > > dashboard/bin/external_node puppet.mydomain.com''
returned 126: /usr/
> > > bin/env: /root/puppet-dashboard/bin/external_node: Permission
denied
> > > err: Could not find node ''puppet.mydomain.com'';
cannot compile
> >
> > > On the client, doing puppetd -vtd:
> >
> > > debug: Failed to load library ''selinux'' for
feature ''selinux''
> > > debug: Puppet::Type::User::ProviderUser_role_add: file rolemod
does
> > > not exist
> > > debug: Puppet::Type::User::ProviderDirectoryservice: file
/usr/bin/
> > > dscl does not exist
> > > debug: Failed to load library ''ldap'' for
feature ''ldap''
> > > debug: Puppet::Type::User::ProviderLdap: feature ldap is missing
> > > debug: Puppet::Type::User::ProviderPw: file pw does not exist
> > > debug:
/File[/var/lib/puppetmaster/ssl/certs/puppet.mydomain.com.pem]:
> > > Autorequiring File[/var/lib/puppetmaster/ssl/certs]
> > > debug: /File[/var/lib/puppetmaster/state/classes.txt]:
Autorequiring
> > > File[/var/lib/puppetmaster/state]
> > > debug: /File[/var/lib/puppetmaster/state/state.yaml]:
Autorequiring
> > > File[/var/lib/puppetmaster/state]
> > > debug: /File[/var/lib/puppetmaster/facts]: Autorequiring
File[/var/lib/
> > > puppetmaster]
> > > debug: /File[/var/lib/puppetmaster/ssl]: Autorequiring
File[/var/lib/
> > > puppetmaster]
> > > debug: /File[/var/lib/puppetmaster/ssl/crl.pem]: Autorequiring
File[/
> > > var/lib/puppetmaster/ssl]
> > > debug: /File[/etc/puppet/puppet.conf]: Autorequiring
File[/etc/puppet]
> > > debug: /File[/var/lib/puppetmaster/ssl/certs]: Autorequiring
File[/var/
> > > lib/puppetmaster/ssl]
> > > debug: /File[/var/run/puppetmaster/puppetd.pid]: Autorequiring
File[/
> > > var/run/puppetmaster]
> > > debug: /File[/var/lib/puppetmaster/puppetmaster]: Autorequiring
File[/
> > > var/lib/puppetmaster]
> > > debug: /File[/var/lib/puppetmaster/state]: Autorequiring
File[/var/lib/
> > > puppetmaster]
> > > debug: /File[/var/lib/puppetmaster/ssl/public_keys]:
Autorequiring
> > > File[/var/lib/puppetmaster/ssl]
> > > debug: /File[/var/lib/puppetmaster/client_yaml]: Autorequiring
File[/
> > > var/lib/puppetmaster]
> > > debug: /File[/var/lib/puppetmaster/ssl/private]: Autorequiring
File[/
> > > var/lib/puppetmaster/ssl]
> > > debug: /File[/var/lib/puppetmaster/ssl/certs/ca.pem]:
Autorequiring
> > > File[/var/lib/puppetmaster/ssl/certs]
> > > debug: /File[/var/lib/puppetmaster/ssl/public_keys/
> > > puppet.mydomain.com.pem]: Autorequiring
File[/var/lib/puppetmaster/ssl/
> > > public_keys]
> > > debug: /File[/var/lib/puppetmaster/ssl/private_keys]:
Autorequiring
> > > File[/var/lib/puppetmaster/ssl]
> > > debug: /File[/var/lib/puppetmaster/lib]: Autorequiring
File[/var/lib/
> > > puppetmaster]
> > > debug: /File[/var/lib/puppetmaster/ssl/private_keys/
> > > puppet.mydomain.com.pem]: Autorequiring
File[/var/lib/puppetmaster/ssl/
> > > private_keys]
> > > debug: /File[/var/lib/puppetmaster/clientbucket]: Autorequiring
File[/
> > > var/lib/puppetmaster]
> > > debug: /File[/var/lib/puppetmaster/state/graphs]: Autorequiring
File[/
> > > var/lib/puppetmaster/state]
> > > debug: /File[/var/lib/puppetmaster/ssl/certificate_requests]:
> > > Autorequiring File[/var/lib/puppetmaster/ssl]
> > > debug: Finishing transaction 70213661363800 with 0 changes
> > > debug: Using cached certificate for ca, good until Sun Oct 23
19:49:36
> > > UTC 2016
> > > debug: Using cached certificate for puppet.mydomain.com, good
until
> > > Sun Oct 23 20:00:26 UTC 2016
> > > debug: Loaded state in 0.00 seconds
> > > debug: Executing
''/etc/puppet/etckeeper-commit-pre''
> > > debug: Using cached certificate for ca, good until Sun Oct 23
19:49:36
> > > UTC 2016
> > > debug: Using cached certificate for puppet.mydomain.com, good
until
> > > Sun Oct 23 20:00:26 UTC 2016
> > > debug: Using cached certificate_revocation_list for ca, good
until
> > > debug: catalog supports formats: b64_zlib_yaml marshal pson raw
yaml;
> > > using pson
> > > err: Could not retrieve catalog from remote server: Error 400 on
> > > SERVER: Could not find node
''puppet-client0.mydomain.com''; cannot
> > > compile
> > > warning: Not using cache on failed catalog
> > > err: Could not retrieve catalog; skipping run
> >
> > > My puppet.conf:
> >
> > > [main]
> > > logdir=$vardir/puppetmaster
> > > vardir=/var/lib/puppetmaster
> > > ssldir=$vardir/puppetmaster/ssl
> > > rundir=/var/run/puppetmaster
> > > factpath=$vardir/lib/facter
> > > pluginsync=false
> > > templatedir=$confdir/templates
> > > prerun_command=/etc/puppet/etckeeper-commit-pre
> > > postrun_command=/etc/puppet/etckeeper-commit-post
> > > reports=log, foreman
> >
> > > [puppetmasterd]
> > > modulepath = /etc/puppet/modules
> > > certname=puppet
> > > reports = store, puppet_dashboard
> > > node_terminus = exec
> > > external_nodes = /usr/bin/env
PUPPET_DASHBOARD_URL=http://localhost:
> > > 3000 /root/puppet-dashboard/bin/external_node
> >
> > > [puppetd]
> > > server=puppet
> > > vardir=/var/lib/puppetmaster
> > > ssldir=$vardir/ssl
> > > report = true
> >
> > > In site.pp I do have:
> >
> > > node default {
> > >   ...
> > > }
> >
> > > And in nodes.pp:
> >
> > > node basenode {
> > >   ...
> > > }
> >
> > > # Define the nodes (puppets)
> > > node ''puppet-client0.mydomain.com'' inherits
basenode {
> > > }
> >
> > > Any help would be greatly appreciated. Thanks in advance.
> >
> > > --
> > > You received this message because you are subscribed to the
Google Groups "Puppet Users" group.
> > > To post to this group, send email to
puppet-users@googlegroups.com.
> > > To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
> > > For more options, visit this group
athttp://groups.google.com/group/puppet-users?hl=en.
> 
> -- 
> You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
> 
> 
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

jcbollinger

2011-Nov-02 12:59 UTC

head link

[Puppet Users] Re: help with err: Could not find node

On Nov 1, 3:27 pm, weloki <wel...@gmail.com>
wrote:> I''m running Ubuntu 10.04 LTS and I just installed Puppet and
> puppetmasterd (both 0.25.4) along with the puppet-dashboard v1.2.0 and
> Foreman 0.3. Puppet and the dashboard were working fine with just the
> master server and a separate client until I installed and configured
> Foreman. Now I keep getting the following errors...
>
> On the puppet master server:
>
> debug: Executing ''/usr/bin/env
PUPPET_DASHBOARD_URL=http://localhost:
> 3000 /root/puppet-dashboard/bin/external_node puppet.mydomain.com''
> err: Failed to find puppet.mydomain.com via exec: Execution of
''/usr/
> bin/env PUPPET_DASHBOARD_URL=http://localhost:3000/root/puppet-
> dashboard/bin/external_node puppet.mydomain.com'' returned 126:
/usr/
> bin/env: /root/puppet-dashboard/bin/external_node: Permission denied
> err: Could not find node ''puppet.mydomain.com''; cannot
compile

That''s (above) the part that matters; the client log is normal for the
case when the server fails to compile a catalog.  In the above bit,
the part that stands out to me is "/root/puppet-dashboard/bin/
external_node: Permission denied".  It appears that whatever user
attempts to run Dashboard''s external node classifier does not have
permission to do so (and that would probably be whatever user the HTTP
server on port 3000 is running as).

Overall, it seems strange to install both Foreman and Dashboard.  I
use neither, but my understanding was that they are alternatives, not
supplementary.

Good Luck,

John

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Jeff

2011-Nov-02 17:19 UTC

head link

Re: [Puppet Users] Re: help with err: Could not find node

Update: It was indeed a permissions issue with regard to the external node
classifier. I simply moved the puppet-dashboard directory out of /root and
put it in /opt and everything works fine now. The thing I can''t figure
out
is that it was working fine in the /root dir until I installed and
configured Foreman, which I wanted to try alongside the puppetlabs
dashboard to compare them. I assumed they would not conflict with each
other.

Thank you both for your help :)



On Wed, Nov 2, 2011 at 8:59 AM, jcbollinger
<John.Bollinger@stjude.org>wrote:
>
>
> On Nov 1, 3:27 pm, weloki <wel...@gmail.com> wrote:
> > I''m running Ubuntu 10.04 LTS and I just installed Puppet and
> > puppetmasterd (both 0.25.4) along with the puppet-dashboard v1.2.0 and
> > Foreman 0.3. Puppet and the dashboard were working fine with just the
> > master server and a separate client until I installed and configured
> > Foreman. Now I keep getting the following errors...
> >
> > On the puppet master server:
> >
> > debug: Executing ''/usr/bin/env
PUPPET_DASHBOARD_URL=http://localhost:
> > 3000 /root/puppet-dashboard/bin/external_node
puppet.mydomain.com''
> > err: Failed to find puppet.mydomain.com via exec: Execution of
''/usr/
> > bin/env PUPPET_DASHBOARD_URL=http://localhost:3000/root/puppet-
> > dashboard/bin/external_node puppet.mydomain.com'' returned
126: /usr/
> > bin/env: /root/puppet-dashboard/bin/external_node: Permission denied
> > err: Could not find node ''puppet.mydomain.com'';
cannot compile
>
>
> That''s (above) the part that matters; the client log is normal for
the
> case when the server fails to compile a catalog.  In the above bit,
> the part that stands out to me is "/root/puppet-dashboard/bin/
> external_node: Permission denied".  It appears that whatever user
> attempts to run Dashboard''s external node classifier does not have
> permission to do so (and that would probably be whatever user the HTTP
> server on port 3000 is running as).
>
> Overall, it seems strange to install both Foreman and Dashboard.  I
> use neither, but my understanding was that they are alternatives, not
> supplementary.
>
>
> Good Luck,
>
> John
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

jcbollinger

2011-Nov-02 20:01 UTC

head link

[Puppet Users] Re: help with err: Could not find node

On Nov 2, 12:19 pm, Jeff <wel...@gmail.com> wrote:> Update: It was indeed a permissions issue with regard to the external node
> classifier. I simply moved the puppet-dashboard directory out of /root and
> put it in /opt and everything works fine now.

Great!

> The thing I can''t figure out
> is that it was working fine in the /root dir until I installed and
> configured Foreman, which I wanted to try alongside the puppetlabs
> dashboard to compare them. I assumed they would not conflict with each
> other.

I believe both provide external node classifiers, and the Puppetmaster
can only use one such at a time.  Right now, for you, it looks like
Dashboard''s is the chosen one.  You may still be able to try out some
of Foreman''s other features, but you cannot have the full
functionality of both packages available at the same time for the same
Puppetmaster.

In any event, I suspect that the problem you encountered was not
directly related to installing Foreman.  Generally speaking, non-root
processes should not be able to access anything under /root, and
nothing about the Puppetmaster, Dashboard, or Foreman should run as
root.  If you do mistakenly run parts of the stack as root (e.g. by
manually starting one or more of the daemons as root) then they have
permissions they should not have, such as to access root''s files.

John

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Nigel Kersten

2011-Nov-02 23:26 UTC

head link

Re: [Puppet Users] Re: help with err: Could not find node

On Wed, Nov 2, 2011 at 1:01 PM, jcbollinger
<John.Bollinger@stjude.org>wrote:
>
>
> On Nov 2, 12:19 pm, Jeff <wel...@gmail.com> wrote:
> > Update: It was indeed a permissions issue with regard to the external
> node
> > classifier. I simply moved the puppet-dashboard directory out of /root
> and
> > put it in /opt and everything works fine now.
>
>
> Great!
>
>
> > The thing I can''t figure out
> > is that it was working fine in the /root dir until I installed and
> > configured Foreman, which I wanted to try alongside the puppetlabs
> > dashboard to compare them. I assumed they would not conflict with each
> > other.
>
>
> I believe both provide external node classifiers, and the Puppetmaster
> can only use one such at a time.  Right now, for you, it looks like
> Dashboard''s is the chosen one.  You may still be able to try out
some
> of Foreman''s other features, but you cannot have the full
> functionality of both packages available at the same time for the same
> Puppetmaster.
>
It''s entirely possible to spend some time writing a wrapper ENC that
calls
both, and collates the results together.

I don''t really advise having two sources of truth for your node
definitions
though :)

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Puppet users - Nov 2011 - help with err: Could not find node

[Puppet Users] help with err: Could not find node

Re: [Puppet Users] help with err: Could not find node

[Puppet Users] Re: help with err: Could not find node

Re: [Puppet Users] Re: help with err: Could not find node

[Puppet Users] Re: help with err: Could not find node

Re: [Puppet Users] Re: help with err: Could not find node

[Puppet Users] Re: help with err: Could not find node

Re: [Puppet Users] Re: help with err: Could not find node