search

quarkslab / irma

IRMA is an asynchronous & customizable analysis system for suspicious files.
https://irma.quarkslab.com
Apache License 2.0
269 stars 55 forks source link

Quarkslab box not found #47

Closed seantree closed 6 years ago

seantree commented 6 years ago

Bringing machine 'default' up with 'virtualbox' provider... ==> default: Box 'quarkslab/debian-9.0.0-amd64' could not be found. Attempting to find and install... default: Box Provider: virtualbox default: Box Version: 20180312 The box 'quarkslab/debian-9.0.0-amd64' could not be found or could not be accessed in the remote catalog. If this is a private box on HashiCorp's Atlas, please verify you're logged in via vagrant login. Also, please double-check the name. The expanded URL and error message are shown below:

URL: ["https://atlas.hashicorp.com/quarkslab/debian-9.0.0-amd64"] Error: The requested URL returned error: 404 Not Found

ch0k0bn commented 6 years ago

box latest version for virtualbox is v201802220. Without any version specified vagrant should download this one. If you have set a particular version in your environment file or in Vagrantfile could you please remove it and try again ?

If you are updating from a previous environment or using an old version of vagrant, you are maybe affected by this bug and you could try the suggested workaround or updating vagrant.

seantree commented 6 years ago

Now after fixing the above problem by upgrading the vagrnat I am facing the below issue:

TASK [setup] *** 2018-03-19T10:04:24.453688 (delta: 0.212292) elapsed: 0.214935 **** fatal: [brain.irma]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: Connection timed out during banner exchange\r\n", "unreachable": true}

PLAY RECAP ***** brain.irma : ok=0 changed=0 unreachable=1 failed=0

2018-03-19T10:06:29.119054 (delta: 124.665333) elapsed: 124.880301 **** =============================================================================== Ansible failed to complete successfully. Any error output should be visible above. Please fix these errors and try again.

ch0k0bn commented 6 years ago

it seems to be vbox related. Try to boot it again and see in Virtualbox gui the status of the vm. Check also the virtual network status. Recent tests was done with vbox5 i dont know which version/OS do you run.

ch0k0bn commented 6 years ago

any updates on your issue ?

seantree commented 6 years ago

now I am getting different errors :(