Here is the output on the master side when running in debug mode and attempting to do a puppet agent -t on the client
http://pastie.org/private/klrgqlxbxqw82cii6diq On Saturday, September 6, 2014 12:42:39 PM UTC-4, Felix.Frank wrote: > > On 09/05/2014 10:39 PM, Alex Wacker wrote: > > I am currently having the following problem and have not been able to > > track down the cause in all my searches online. I have a script file > > located in a module I have written that the client appears to be > > unable to get. > Hi, > > does the master perhaps not have permissions to read that file? > > For debugging, it may be helpful to run a debug session master side. The > easiest way is to stop the master (or apache) and run as root > > puppet master --no-daemonize --verbse --debug > > If you cannot just stop your master, you can also run the same debug > master with an alternative port (--masterport option) but will also have > to specify an alternate PID file and possibly override other clashing > settings. > > HTH, > Felix > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/18504e0e-4c0b-423c-8ae6-4ebd496f1fc7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
