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

Hadoop exploiter launches multiple times #655

Closed
VakarisZ opened this issue May 22, 2020 · 1 comment · Fixed by #3120
Closed

Hadoop exploiter launches multiple times #655

VakarisZ opened this issue May 22, 2020 · 1 comment · Fixed by #3120
Labels
Bug An error, flaw, misbehavior or failure in the Monkey or Monkey Island. Complexity: Medium Impact: Low

Comments

@VakarisZ
Copy link
Contributor

Describe the bug

Hadoop exploiter somehow queues up multiple monkey executions and launches them one after each other.

To Reproduce

Steps to reproduce the behavior:

  1. Exploit machine with hadoop exploiter
  2. Observe that monkey binary was launched more times than machine was exploited

Expected behavior

Hadoop should only run monkey once for each exploitation

@VakarisZ VakarisZ added Bug An error, flaw, misbehavior or failure in the Monkey or Monkey Island. Complexity: Medium Impact: Low labels Jan 22, 2021
@mssalvatore
Copy link
Collaborator

A lot of research has been done on this. See #1781 (comment)

This is fixed by #1782 and #1781

mssalvatore added a commit that referenced this issue Mar 16, 2023
Hadoop's speculative execution feature has lead to a number of
difficulties. See #655, #1781, and #2578. Of concern is that the issue
where Hadoop sends a SIGKILL to the first process (#2578) could cause
significant issues when implementing agent OTP authentication (#3077).

Setting max-app-attempts to 1 resolves these issues.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug An error, flaw, misbehavior or failure in the Monkey or Monkey Island. Complexity: Medium Impact: Low
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants