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
worker has no heartbeat, restarting #547
Comments
Does iot also happen if you run seccubus like this:
|
I used seccubus service to start it and this was the log: then i used morbo and this is the log: |
So hypnotoad is rightfully killing haning child processes. The questions remains, why do child processes hang on Kali... |
@seccubus if there is anything I can do to test tell me! |
I just reinstalled the latest version from git (d6eb441 commit) on Kali and it seems that this problem is solved! |
Does you comment in #568 mean I have unknowing resolved this issue now? |
@seccubus I'm not sure but I encountered the issue when I upgraded from 2.28 to 2.38. After some investigation I saw that PERL5LIB only had "/opt/seccubus". So I did a clean installation and changed PERL5LIB to "/opt/seccubus:/opt/seccubus/lib" and the problem was fixed. So I guess the problem was about PERL5LIB. |
Yes, that is the same thing that I encountered between releases 2.38 and 2.40. Also it seems debian has changed perl's behaviour not to have the current directory in the default clean path anymore... Good, case closed for me, unless you object. BTW would you mind writing up how you installed on Kali as that is a common question. |
@seccubus |
with a clean installation on KALI, I repeatedly get this error in production.log while using GUI. And this causes GUI to become very slow and requests are not being answered. I don't get this error in Debian!
The text was updated successfully, but these errors were encountered: