On Mar 20, 2009, at 10:54 AM, Jeff wrote:
>
> Hi folks,
>
> I've searched around the group and couldn't find something that would
> specifically answer my problem. I was trying to use puppetrun to force
> an update on a specific host machine but ended up with the following
> error:
>
> # puppetrun --host client1.int
> Triggering client1.int
> err: Could not call puppetrunner.run: #<RuntimeError: HTTP-Error: 500
> Internal Server Error >
> Host client1.int failed: HTTP-Error: 500 Internal Server Error
> client1.int finished with exit code 2
> Failed: client1.int
>
> I turned on verbose logging on the receiving side, and all I saw was:
>
> # puppetd --no-daemonize --listen --verbose --no-client
> info: Starting handler for Runner
> info: Starting server for Puppet version 0.24.7
> info: Listening on port 8139
> info: access[puppetrunner]: allowing puppet access
>
> Appreciate if you guys can point me in the right direction.
I'm pretty confident no-client doesn't do what you want when used in
conjunction with puppetrun. There's no way to only run from puppetrun
and no other time, at this point.
--
One of the Ten Commandments for Technicians:
(7) Work thou not on energized equipment, for if thou dost, thy
fellow workers will surely buy beers for thy widow and
console her in other ways.
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com
--~--~---------~--~----~------------~-------~--~----~
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+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
