search

pry0cc / axiom

The dynamic infrastructure framework for everybody! Distribute the workload of many different scanning tools with ease, including nmap, ffuf, masscan, nuclei, meg and many more!
MIT License
4k stars 622 forks source link

[Axiom Issue] Usage of deleted Instances instead of new ones #469

Closed Sicks3c closed 2 years ago

Sicks3c commented 2 years ago

Summary

Hello There I would like to talk about an issue I'm facing regarding axiom I have spined up 10 instances for testing purposes and when I run any command the tool detect the one that I deleted

Description

I created 2 instances liskov* and deleted them and I spinned up another 10 kilby* now tool uses liskov instead of Kilby

Screen Shot 2021-10-11 at 11 33 29

Regards

0xtavian commented 2 years ago

@Sicks3c you'll have to select the instances you create with axiom-select before using them. In your case axiom-select kilby*.

Sicks3c commented 2 years ago

Hello @0xtavian

Thank you for quick response I didn't use the axiom-select command at all but I think this behavior got triggered when I tried to run 100 instances and I'm only allowed for 10 right now When I deleted everything and selected only 10 to spin it worked

Thanks anyways Regards

0xtavian commented 2 years ago

Np. So when you spin up instances axiom should automatically selecte them (unless using axiom-init --no-select). However if you canceled the initialization at some point maybe that part of the code didnt run. I've seen this before tbh. The best thing to so is double check the instances are selected after initialization.

Glad we got it sorted.