Error 400 On Server Could Not Find Node Cannot Compile
Contents |
von GoogleAnmeldenAusgeblendete FelderNach Gruppen oder Nachrichten suchen
Sign in Pricing Blog Support Search GitHub This repository Watch 19 Star 46 Fork 22 kalamuna/kalastack Code Issues 22 Pull requests 1 Projects 0
Error: Could Not Retrieve Catalog; Skipping Run
Wiki Pulse Graphs New issue Could not retrieve catalog from remote could not retrieve catalog from remote server error 400 on server failed when searching for node server: Error 400 on SERVER: Could not find node 'kala.e823cb0a-daff-459a-a2fd-37d61808551b.f04083c46d392c7c7276a3570a96d095.box'; cannot compile #5 Closed andrewmallis opened this Issue warning: not using cache on failed catalog Apr 10, 2013 · 10 comments Projects None yet Labels None yet Milestone 2.0 Assignees pirog 4 participants Kalamuna member andrewmallis commented Apr 10, 2013 $ https://groups.google.com/d/topic/foreman-users/6ue54bBPuv8 vagrant up kalabox --provision-with=shell,puppet_server output: The following SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed! FACTER_vagrant='1' FACTER_kalauser='vagrant' FACTER_kalahost='192.168.42.1' puppet agent --verbose --debug --test --server kalabox.kalamuna.com --detailed-exitcodes || [ $? -eq 2 ] pirog was assigned Apr 10, 2013 Kalamuna member pirog commented Apr 10, 2013 why do you think this has to https://github.com/kalamuna/kalastack/issues/5 do with facter? Kalamuna member pirog commented Apr 10, 2013 because the actual issue is: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find node 'kala.e823cb0a-daff-459a-a2fd-37d61808551b.f04083c46d392c7c7276a3570a96d095.box'; cannot compile renaming issue. Kalamuna member pirog commented Apr 10, 2013 i would try this whole thing from scratch and report back chriz001 commented Apr 18, 2013 same problem here, my first sign of a problem is this stdin: is not a tty ... dpkg-preconfigure: unable to re-open stdin: No such file or directory ... followed by the same error. Kalamuna member andrewmallis commented Apr 18, 2013 we're having a bit of an issue between the box communication and the puppet server. You can try to build the box (temporarily) using the method described in the wiki with the local puppet definitions. Or, hang tight till we solve this issue! $ vagrant up kalabox --provision-with=shell,puppet n.b. the stdin warning is unrelated to the build process chriz001 commented Apr 18, 2013 Kalabox 2 Hello. That Worked! Will give it another go when the communication issues are s
SERVER : Could not find class” edit module classes asked 2015-04-09 04:10:20 -0500 mudasar 1 ●1 ●1 ●1 https://ask.puppet.com/question/16531/puppet-error-400-on-server-could-not-find-class/ There are TOO many post and solution for this problem, but still i am not able to solve it. I am using puppet 3.7.5 Following is details root@p1:/etc/puppet/manifests# https://www.mail-archive.com/puppet-users@googlegroups.com/msg25680.html ls -l total 8 -rw-r--r-- 1 root root 40 Apr 9 12:37 nodes.pp -rw-r--r-- 1 root root 18 Apr 9 11:58 site.pp root@p1:/etc/puppet/manifests# cat nodes.pp node 'wa.ro.XXX' { could not include mytest } root@p1:/etc/puppet/manifests# cat site.pp import 'nodes.pp' Module path root@p1:/etc/puppet/manifests# puppet master --configprint modulepath /etc/puppet/modules:/usr/share/puppet/modules root@p1:/etc/puppet# tree -L 2 -d modules modules - configfiles -- files -- manifests - services -- files -- manifests root@p1:/etc/puppet# cat modules/services/manifests/init.pp class mytest { file { '/tmp/puppettestfgt56666' : mode => 0644, content => "This Learning Puppet VM's IP address error 400 on is ${ipaddress}", } } On agent root@wa:/var/cache# puppet agent --no-daemonize --onetime --verbose Info: Retrieving plugin Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class mytest for wa.ro.XXX on node wa.ro.XXX Notice: Using cached catalog Info: Applying configuration version '1428561896' Notice: Finished catalog run in 0.07 seconds edit retag flag offensive close merge delete add a comment 1 answer Sort by » oldest newest most voted 2 answered 2015-04-09 07:43:19 -0500 llowder 2877 ●16 ●34 ●71 http://blog.keepingyou... You don't have the right module layout. The autoloader is very particular about where it looks for classes. You have the class mytest defined in a location where it is looking for services. You need to either make a module named mytest and move modules/services/manifests/init.pp to modules/mytest/manifests/init.pp or rename the file to mytest.pp and the class to services::mytest. You may wish to review the following docs as well: The Beginner's Guide To Modules Module Fundamentals - Specfically the Module Layout section. edit flag off
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