Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wodle command test #1057

Closed
bah07 opened this issue Aug 3, 2018 · 0 comments
Closed

Wodle command test #1057

bah07 opened this issue Aug 3, 2018 · 0 comments
Assignees
Labels
type/bug Something isn't working
Projects

Comments

@bah07
Copy link
Contributor

bah07 commented Aug 3, 2018

We have detected some issues related to this module:

  • When configuring more than one block of Wodle Command only works last one. e.g:
<wodle name="command">
  <disabled>no</disabled>
  <tag>test1</tag>
  <command>/bin/echo `date`:"First wodle command"</command>
  <interval>15s</interval>
  <ignore_output>no</ignore_output>
  <run_on_start>yes</run_on_start>
  <timeout>0</timeout>
</wodle>

<wodle name="command">
  <disabled>no</disabled>
  <tag>test2</tag>
  <command>/bin/echo `date`:"First wodle command"</command>
  <interval>1d</interval>
  <ignore_output>no</ignore_output>
  <run_on_start>yes</run_on_start>
  <timeout>0</timeout>
</wodle>

In log don't appear test1 tag:

2018/08/03 14:13:24 wazuh-modulesd: INFO: Process started.
2018/08/03 14:13:24 wazuh-modulesd:command: INFO: Module command:test2 started
  • The second failure detected is related to the timeout parameter. It does not work if ignore_output is enabled. With next configuration:
<wodle name="command">
  <disabled>no</disabled>
  <tag>test1</tag>
  <command>/bin/bash /home/borja/testingwazuh/wodlecommand/noprint.sh</command>
  <interval>15s</interval>
  <ignore_output>no</ignore_output>
  <run_on_start>yes</run_on_start>
  <timeout>5</timeout>
</wodle>

Works fine and get next message error:

2018/08/03 14:22:47 wazuh-modulesd:command: INFO: Module command:test1 started
2018/08/03 14:22:53 wazuh-modulesd:command: ERROR: test1: Internal calling. Exiting...

But if change option ignore_output yo yes, the Internal calling. Exiting never appear.

NOTE: Change error message when killing process.

@bah07 bah07 added the type/bug Something isn't working label Aug 3, 2018
@bah07 bah07 self-assigned this Aug 3, 2018
@bah07 bah07 added this to To do in Wazuh 3.5 via automation Aug 3, 2018
@vikman90 vikman90 removed this from To do in Wazuh 3.5 Aug 8, 2018
@vikman90 vikman90 added this to To do in Wazuh 3.6 via automation Aug 8, 2018
@vikman90 vikman90 assigned cristgl and unassigned bah07 Aug 13, 2018
@vikman90 vikman90 added this to To do in Wazuh 3.5.1 via automation Aug 13, 2018
@vikman90 vikman90 removed this from To do in Wazuh 3.6 Aug 13, 2018
@vikman90 vikman90 moved this from To do to In progress in Wazuh 3.5.1 Aug 14, 2018
Wazuh 3.5.1 automation moved this from In progress to Done Aug 17, 2018
@vikman90 vikman90 reopened this Aug 20, 2018
Wazuh 3.5.1 automation moved this from Done to In progress Aug 20, 2018
Wazuh 3.5.1 automation moved this from In progress to Done Aug 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Something isn't working
Projects
No open projects
Wazuh 3.5.1
  
Done
Development

No branches or pull requests

5 participants