ok found it was patch submited we did not have in our release for svc/services.py that
grabs ip (REMOTE_ADDR) apologies for the distraction ...
cheers,
simon
Simon Woolsgrove <simon(a)woolsgrove.com> wrote:
many thanks ... yep python based, tracked issue down to trigger not
being passed ip by run_install_triggers . would you happen to know how the ip is obtained
as we are seeing some strange results with ip being sent, or an ip that is not in record
or no ip?
cheers
simon
James Cammarata <jimi(a)sngx.net> wrote:
>On Wed, Jul 4, 2012 at 9:09 AM, Simon Woolsgrove <simon(a)woolsgrove.com> wrote:
>>
>> What do I need to do to enable log messages from any of the triggers ? we have
some in house triggers and even those provided do not log e.g logger.debug logger.info
etc..
>
>Are they python-based triggers or shell-based ones that live in
>/var/log/cobbler/triggers? The python ones are typically installed in
>the modules/ directory under site-packages/cobbler.
>
>If they're the python ones (and I'm assuming they are), a logger
>object is passed in to the run() command and you can use that to log
>messages that will show up in /var/log/cobbler/cobbler.log. For shell
>based triggers, just use the logger CLI command and you can send it to
>whatever facility you want.
>_______________________________________________
>cobbler mailing list
>cobbler(a)lists.fedorahosted.org
>https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler