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

make staging not working on macOS #3847

Closed
redshiftzero opened this issue Oct 4, 2018 · 0 comments
Closed

make staging not working on macOS #3847

redshiftzero opened this issue Oct 4, 2018 · 0 comments
Assignees

Comments

@redshiftzero
Copy link
Contributor

Description

I was running through the docs added in #3835, and discovered that the make staging target doesn't currently work as intended on macOS.

Btw we shouldn't remove the Vagrantfile in #3208 until we've tested the new makefile targets on both macOS and Linux (generally people are testing on the latter but not the former).

Steps to Reproduce

  1. Check out latest develop
  2. make build-debs
  3. make staging

Expected Behavior

Staging machines are provisioned without issue

Actual Behavior

    TASK [ossec : Add firewall exemption for OSSEC agent registration (both servers)] ***
    ok: [mon-staging] => (item={u'chain': u'INPUT', u'proto': u'tcp', u'cstate': u'NEW,ESTABLISHED,RELATED', u'jump': u'ACCEPT', u'source': u'app-staging', u'match': u'state', u'dest_port': 1515})
    ok: [app-staging] => (item={u'chain': u'OUTPUT', u'proto': u'tcp', u'cstate': u'NEW,ESTABLISHED,RELATED', u'jump': u'ACCEPT', u'dest': u'10.0.1.3', u'match': u'state', u'dest_port': 1515})
    ok: [mon-staging] => (item={u'chain': u'OUTPUT', u'proto': u'tcp', u'cstate': u'ESTABLISHED,RELATED', u'jump': u'ACCEPT', u'dest': u'app-staging', u'source_port': 1515, u'match': u'state'})
    ok: [app-staging] => (item={u'chain': u'INPUT', u'proto': u'tcp', u'cstate': u'ESTABLISHED,RELATED', u'jump': u'ACCEPT', u'source': u'10.0.1.3', u'source_port': 1515, u'match': u'state'})
    
    TASK [ossec : Register OSSEC agent.] *******************************************
    fatal: [app-staging]: FAILED! => {"changed": true, "cmd": ["/var/ossec/bin/agent-auth", "-m", "10.0.1.3", "-p", "1515", "-A", "app-staging", "-P", "/var/ossec/etc/authd.pass"], "delta": "0:00:00.063895", "end": "2018-10-04 22:02:11.911442", "failed_when_result": true, "rc": 0, "start": "2018-10-04 22:02:11.847547", "stderr": "2018/10/04 22:02:11 ossec-authd: INFO: Started (pid: 9378).\n2018/10/04 22:02:11 INFO: Connected to 10.0.1.3 at address 10.0.1.3, port 1515", "stderr_lines": ["2018/10/04 22:02:11 ossec-authd: INFO: Started (pid: 9378).", "2018/10/04 22:02:11 INFO: Connected to 10.0.1.3 at address 10.0.1.3, port 1515"], "stdout": "INFO: Using specified password.\nINFO: Connected to 10.0.1.3:1515\nINFO: Using agent name as: app-staging\nINFO: Send request to manager. Waiting for reply.\nERROR: Unable to create key. Either wrong password or connection not accepted by the manager.\nINFO: Connection closed.", "stdout_lines": ["INFO: Using specified password.", "INFO: Connected to 10.0.1.3:1515", "INFO: Using agent name as: app-staging", "INFO: Send request to manager. Waiting for reply.", "ERROR: Unable to create key. Either wrong password or connection not accepted by the manager.", "INFO: Connection closed."]}

Comments

Note that the provider is correct (virtualbox-staging) here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants