|
|
 |
« on: January 04, 2011, 01:35:58 PM » |
|
Hi there,
Some agents are experiencing problems and we found out the guilty to be a line termination character "^M". It's not the first time it happened, I think the browser used to remote configurate the .conf file must have some configuration that's directly impacting on this. Does anyone knows the right setup to get rid of this?
Tks! :-)
|
|
|
|
|
Logged
|
|
|
|
|
|
|
 |
« Reply #1 on: January 04, 2011, 09:53:50 PM » |
|
Humm, made some tests here, there're two scenarios:
1. Apply the policy to an agent: generates ^M (carriage return) on .conf - NOT OK 2. Manually edit the .conf through web console (as the remote config feature is enabled): .conf - OK
Any ideas?
|
|
|
|
|
Logged
|
|
|
|
|
|
|
 |
« Reply #2 on: January 11, 2011, 07:03:41 PM » |
|
Hi Robas,
This is a bug that we have resolved in the new version 3.2 of Pandora FMS. A workaround would be to delete the agent of the policy and create it again into the policy.
Cheers.
|
|
|
|
|
Logged
|
|
|
|
|
|
|
 |
« Reply #3 on: January 11, 2011, 09:20:37 PM » |
|
I suspected this could be an already corrected known issue... We're waiting some time before upgrading it to 3.2. The workaroung I'm using is the following:
1. Apply the police 2. Remotely edit the agent's .conf, by adding any comment 3. Save the .conf
This way the agent's .conf doesn't get the ^M.
Thanks a lot :-)
|
|
|
|
|
Logged
|
|
|
|
|
|
|
 |
« Reply #4 on: January 12, 2011, 12:35:01 PM » |
|
Good workaround Robas.
Thanks!
|
|
|
|
|
Logged
|
|
|
|
|
|