On 4/24/14, 11:22 AM, Felix Frank wrote:
Uhm, why is this in the "Sharing Puppet Functions" thread?
Sorry, didn't know it belonged elsewhere. My bad.
Anyway, this looks like a bug. Can you reproduce this? I'll gladly report it if you'd like to save the hassle, but I'll need to reproduce.
Very easily reproducible. I was reproducing it for four days. The module I was trying to write initialized the /var/www/html Web content directory with a index.html. Try mistyping something in the source path that should normally go to the module's file directory (bloody trifocals). BTW this is puppet and server 3.5.1 with current dependencies on CentOS-6.5.
Chris
Regards, Felix On 04/24/2014 04:56 PM, Chris Johnson wrote:Hi. Had the following error in my messages log from the puppet gent daemon, i.e. the client side: {/Stage{main}/web_server/File{/var/www/html/index.html]) Could not evaluate: Could not retrieve file metadata for puppet://modules/web_services/client1/html/index.html: Connection refused - connect(2) Now maybe I wouldn't be quite so annoyed if I hadn't been chasing file protocols and network problems for four days on this one. And the computer gods know I've google it enough and seen all kinds of responses. Please, please, please would it be too much trouble for a simple "file or directory not found" error instead? That's what the problem was. But I just spend four days googling this and try to find nonexistent network problems among other things. I like the idea of puppet especially with a huge install client base or compute cluster etc. But come on guys. Is it too much task for simpler more direct and meaningful error reporting? Chris.
-- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/53593089.6090906%40gmail.com. For more options, visit https://groups.google.com/d/optout.
