Errors while starting dionaea honeypot on raspberry pi 3

[MxResearch]

Hi,

I have configured dionaea honeypot on raspberry pi device as per steps mentioned on mhn forum. While starting dionaea by using command: sudo supervisorctl start dionaea on raspberry pi device following errors are reported: dionaea: ERROR (spawn error)

Log information

• /opt/dionaea/bin/dionaea:

  error while loading shared libraries: libev.so.4: cannot open shared object file: No such file or directory.

• 2017-11-10 05:23:42,331 CRIT Supervisor running as root (no user in config file) 2017-11-10 05:23:42,332 WARN No file matches via include "/etc/supervisor/conf.d/*.conf" 2017-11-10 05:23:42,426 INFO RPC interface 'supervisor' initialized 2017-11-10 05:23:42,427 CRIT Server 'unix_http_server' running without any HTTP authentication checking ... 2017-11-10 05:28:23,566 INFO spawned: 'dionaea' with pid 4756 2017-11-10 05:28:23,613 INFO exited: dionaea (exit status 127; not expected) 2017-11-10 05:28:24,622 INFO spawned: 'dionaea' with pid 4757 2017-11-10 05:28:24,831 INFO exited: dionaea (exit status 127; not expected) 2017-11-10 05:28:26,851 INFO spawned: 'dionaea' with pid 4761 2017-11-10 05:28:26,897 INFO exited: dionaea (exit status 127; not expected) 2017-11-10 05:28:29,910 INFO spawned: 'dionaea' with pid 4762 2017-11-10 05:28:30,121 INFO exited: dionaea (exit status 127; not expected) 2017-11-10 05:28:31,125 INFO gave up: dionaea entered FATAL state, too many start retries too quickly 2017-11-10 05:30:04,596 CRIT Supervisor running as root (no user in config file) 2017-11-10 05:30:04,601 WARN For [program:dionaea], redirect_stderr=true but stderr_logfile has also been set to a filename, the filename has been ignored 2017-11-10 05:30:04,602 INFO Included extra file "/etc/supervisor/conf.d/dionaea.conf" during parsing 2017-11-10 05:30:04,717 INFO RPC interface 'supervisor' initialized 2017-11-10 05:30:04,718 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2017-11-10 05:30:04,719 INFO supervisord started with pid 466 2017-11-10 05:30:05,727 INFO spawned: 'dionaea' with pid 685 2017-11-10 05:30:05,842 INFO exited: dionaea (exit status 127; not expected) 2017-11-10 05:30:06,855 INFO spawned: 'dionaea' with pid 739 2017-11-10 05:30:06,915 INFO exited: dionaea (exit status 127; not expected) 2017-11-10 05:30:08,927 INFO spawned: 'dionaea' with pid 775 2017-11-10 05:30:08,973 INFO exited: dionaea (exit status 127; not expected) 2017-11-10 05:30:11,986 INFO spawned: 'dionaea' with pid 838 2017-11-10 05:30:12,031 INFO exited: dionaea (exit status 127; not expected) 2017-11-10 05:30:12,034 INFO gave up: dionaea entered FATAL state, too many start retries too quickly

Need help in resolving the issue.

Thanks and regards

[d1str0]

Did you use the latest install script to install dionaea?

[MxResearch]

Hello,

Yes I have installed dionaea on raspberry pi device using latest mhn deploy raspberry pi script. Still no success in starting dionaea. Facing same aforementioned errors.

Are there any other configurations to be done or any other command to start dionaea ?

[steveblonquist]

I am seeing the exact same thing. Have you found a resolution?

[MxResearch]

@steveblonquist , No, not able to find any workaround to resolve the issue for dionaea.

Another solution to run dionaea honeypot on raspberry pi device is to use Honeeepi which is a honeypot sensor on Raspberry Pi which based on customized Raspbian OS.

Reference: https://redmine.honeynet.org/projects/honeeepi/wiki