First off: Thanks for the reply.

Keep in mind you might have some permission issues. 
>
> You are starting smart-proxy most likely as domain admin for testing?  
>
If you want to run smart-proxy with DNS and/or DHCP, and your proxy 
> needs to connect to the network. I've created a special user for that 
> purpose, you'll want this user to be member of DHCP Administrators and 
> DNS Administrators at least. 
>
>
This was done as well as making sure the service account had the"run as 
service" permissions on the host as being a local admin during the test 
process (not something I'd normally do, but I got annoyed).
 

> Then, test this user by: 
> runas /user=<doamin>\<smartproxyuser> cmd 
>
> And use this terminal to run smart proxy. Once all checks out, smart 
> proxy should run. Take care it can read settings and write log files ect. 
>
> Our Service command line: 
> C:\Ruby200-x64\bin\ruby -C c:/TheForeman/smart-proxy 
> "c:\TheForeman\smart-proxy\bin\smart-proxy-win-service" 
>
>
This is very similar to my call, only I'm piggy backing on a sensu ruby 
that is installed ... I may try swinging it over embedded puppet or a 
standalone like you have.
 

>
> There was an issue with the service, IIRC it needs to be called via 
> bundle exec, starting with 1.14. 
> Indeed, it is - I think PR's are welcome! 
>
> Our smart-proxy is running fine since I use foreman - all versions from 
> 1.8. 
>
>
If I can figure out how to get this working I may take the extra step of 
putting the whole thing in a container otherwise at least a puppet module. 
 Just been beating my head on this one for awhile.

Thanks for the insight, Ill try comming off the sensu-ruby and double check 
permissions.

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to