You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I check in on my honeypot every so often to find out that it's gone down for quite some time. it'll almost always be down when I go to check in on it after more than a few days. I'm looking for ideas on how to pinpoint what is causing it to crash.
To Reproduce
Trying to figure out how to reproduce, looking for ideas on debugging it
Expected behavior
Cowrie process stays active and does not crash / die.
Server (please complete the following information):
Ubuntu 18.04.2 LTS
The text was updated successfully, but these errors were encountered:
Checking the log files is the best way to figure out what might have caused the crash. If you see anything unusual something that shouldn't have caused the crash then let us know about it.
So the log files is where to start, and you can increase the debug level at the Twisted levels as well, I think. But after that you'll have to go to the code level.
To do the debug in Twisted, run twistd with the spew option:
--spew Print an insanely verbose log of everything that happens.
Useful when debugging freezes or locks in complex code.
Describe the bug
I check in on my honeypot every so often to find out that it's gone down for quite some time. it'll almost always be down when I go to check in on it after more than a few days. I'm looking for ideas on how to pinpoint what is causing it to crash.
To Reproduce
Trying to figure out how to reproduce, looking for ideas on debugging it
Expected behavior
Cowrie process stays active and does not crash / die.
Server (please complete the following information):
The text was updated successfully, but these errors were encountered: