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 freezes at "Provisioner" option. #605

Closed RodricBr closed 2 years ago

RodricBr commented 2 years ago

Image:

image

I can't press enter, or type anything, it just freezes and all I could do was cancel the process (CTRL+C). Tested on a Debian 11 x64 and on a Ubuntu 22.04 x64 machine.

0xtavian commented 2 years ago

@RodricBr that’s odd. Question if you press control+c, then reload your shell ( via running bash or running zsh if you installed omz or zsh), and finally try running axiom-build again, does it work? You could also select the provisioner via the command line by running axiom-build default for example. What’s your shell? bash, zsh or oh-my-zsh?

0xtavian commented 2 years ago

Also, Ubuntu 22.04 unfortunately isn’t supported atm. If you can use Ubuntu 20.04 that would be preferable. The only issue with Ubuntu 22.04 is that by default the version of python is 3.10, which doesn’t play nicely with Interlace. There are plenty of workarounds to the interlace issue mentioned in their repo. Just keep in mind you’ll have to that extra step once to get exec/scan etc working if you stick with Ubuntu 22.04 https://github.com/codingo/Interlace/issues/167

RodricBr commented 2 years ago

What’s your shell? bash, zsh or oh-my-zsh?

My current shell is bash.


Also, Ubuntu 22.04 unfortunately isn’t supported atm. If you can use Ubuntu 20.04 that would be preferable.

Yeah... thanks, that seems to resolve the problem, I used Ubuntu 20.04 and it worked as expected!

Also, this is what the program prints out after one hour of waiting, if this can be useful to you. (On Ubuntu 22.04) image

0xtavian commented 2 years ago

@RodricBr Thanks, yeah there is definitely some bug here. I am able to reproduce. The workaround is unfortunately when axiom-configure calls axiom-build, you'll have to control+c and then run axiom-build again. I'll look into it over the weekend. Thanks for bringing this up!

jackson-jackson commented 2 years ago

I've got the same issue.

0xtavian commented 2 years ago

@jackson-jackson @RodricBr can you please update to the latest code and try again? It seems I was able to identify the issue. Run axiom-update to update to the latest code. If you've made any local changes you might have run cd $HOME/.axiom ; git status and restore any files it complains about, then run axiom-update again. Thank you both!

jackson-jackson commented 2 years ago

@oxtavian, that worked. Thanks for the insanely fast fix :)

RodricBr commented 2 years ago

@0xtavian Yeah, it seems like the bug was fixed, thanks for the help, and keep up the good work!