Dingolino 1 Posted October 29, 2018 Share Posted October 29, 2018 Hi folks, I am having problems with ESET Mail Security v4.5.9 since Friday. Installed in March this year and everything was fine for months. And now all of a sudden the daemon seems to crash. It has happened several times since the first occurence. linuxzwo:/home/jb # systemctl status esets.service ● esets.service - ESET Scanner Daemon Loaded: loaded (/etc/systemd/system/esets.service; enabled; vendor preset: disabled) Active: inactive (dead) since Mo 2018-10-29 07:45:50 CET; 2h 1min ago Process: 1184 ExecStart=/opt/eset/esets/sbin/esets_daemon (code=exited, status=0/SUCCESS) Main PID: 1406 (code=exited, status=0/SUCCESS) Okt 29 07:45:30 linuxzwo esets_daemon[1699]: summ[06a30203]: vdb=39187, agent=mda, name="from: xxxxx to: xxxx with subject xxx, hop="accepted" Okt 29 07:45:30 linuxzwo esets_daemon[1699]: summ[06a30204]: vdb=39187, agent=mda, name="from: xxxx to: xxx with subject xxxx Okt 29 07:45:32 linuxzwo esets_daemon[1406]: error[057e0000]: Child process esets_daemon[1699] did not handle signal 6, restart in 0 seconds Okt 29 07:45:34 linuxzwo esets_daemon[1406]: error[057e0000]: Child process esets_daemon[1718] did not handle signal 6, restart in 0 seconds Okt 29 07:45:37 linuxzwo esets_daemon[1406]: error[057e0000]: Child process esets_daemon[1729] did not handle signal 6, restart in 0 seconds Okt 29 07:45:40 linuxzwo esets_daemon[1406]: error[057e0000]: Child process esets_daemon[1740] did not handle signal 6, restart in 0 seconds Okt 29 07:45:42 linuxzwo esets_daemon[1406]: error[057e0000]: Child process esets_daemon[1751] did not handle signal 6, restart in 0 seconds Okt 29 07:45:45 linuxzwo esets_daemon[1406]: error[057e0000]: Child process esets_daemon[1762] did not handle signal 6, restart in 0 seconds Okt 29 07:45:47 linuxzwo esets_daemon[1406]: error[057e0000]: Child process esets_daemon[1773] did not handle signal 6, restart in 0 seconds Hint: Some lines were ellipsized, use -l to show in full. I am on OpenSuse 42.3 with Postfix, fetchmail and Dovecot. And I chose the method where Eset acts as a MDA. Any idea what is wrong here? Any help is appreciated, I am an inexperienced user. Link to comment Share on other sites More sharing options...
Krzysztof L. 2 Posted October 29, 2018 Share Posted October 29, 2018 Hi Dingolino, You are not alone with this problem, this is fresh bug, go here --> Link to comment Share on other sites More sharing options...
ESET Moderators Peter Randziak 1,161 Posted October 29, 2018 ESET Moderators Share Posted October 29, 2018 Hello @Dingolino, please upgrade to the latest 4.5.11 version in the first place and than please continue as I wrote in the other thread https://forum.eset.com/topic/17346-esets_daemon-freeze-2018-version/?do=findComment&comment=85894 Regards, P.R. Link to comment Share on other sites More sharing options...
Dingolino 1 Posted October 29, 2018 Author Share Posted October 29, 2018 (edited) Thank you Krzysztof and Peter. Will update asap. But as for the remainder, I am not sure if I can manage such difficult jobs. As I said I am not a pro. Edited October 29, 2018 by Dingolino Link to comment Share on other sites More sharing options...
Dingolino 1 Posted October 30, 2018 Author Share Posted October 30, 2018 I did my update to v4.5.11. When I now look into systemd log I see messages from systemd-coredump indicating that core dumps are produced (without me having changed the call to eset as Peter has suggested yesterday). I now have lots of files like the ones below: -rw-r----- 1 root root 10502144 30. Okt 10:29 .#core.esets_daemon.0.1af8ba5fb87b4893bf02a64ba5a6c120.10384.1540891725000000.xzf32f3637adfa293c -rw-r----- 1 root root 217649152 30. Okt 10:29 .#core.esets_daemon.0.1af8ba5fb87b4893bf02a64ba5a6c120.10398.15408917470000000c2ff099ac94582b -rw-r----- 1 root root 5890048 30. Okt 10:29 .#core.esets_daemon.0.1af8ba5fb87b4893bf02a64ba5a6c120.10398.1540891747000000.xz419af4a21962c356 -rw-r----- 1 root root 217649152 30. Okt 10:29 .#core.esets_daemon.0.1af8ba5fb87b4893bf02a64ba5a6c120.10418.154089176500000006a0a6b8ac5302aa -rw-r----- 1 root root 1105920 30. Okt 10:29 .#core.esets_daemon.0.1af8ba5fb87b4893bf02a64ba5a6c120.10418.1540891765000000.xze7c7e507a1b64c4b -rw-r----- 1 root root 74861752 30. Okt 10:09 core.esets_daemon.0.1af8ba5fb87b4893bf02a64ba5a6c120.8918.1540890206000000.xz -rw-r----- 1 root root 75023712 30. Okt 10:10 core.esets_daemon.0.1af8ba5fb87b4893bf02a64ba5a6c120.8938.1540890226000000.xz -rw-r----- 1 root root 74936776 30. Okt 10:10 core.esets_daemon.0.1af8ba5fb87b4893bf02a64ba5a6c120.8952.1540890248000000.xz -rw-r----- 1 root root 75048260 30. Okt 10:10 core.esets_daemon.0.1af8ba5fb87b4893bf02a64ba5a6c120.8967.1540890268000000.xz What shall I do know? I am afraid now that my hard disk will overflow soon? Also the machine seems rather slowed down (probably because these dumps consume a lot of capacity). Below is my esets.service file for systemd v228 [Unit] Description=ESET Scanner Daemon After=network.target [Service] ExecStart=/opt/eset/esets/sbin/esets_daemon ExecReload=/bin/kill -HUP $MAINPID KillMode=process PIDFile=/var/run/esets_daemon.pid Restart=always RestartSec=5 StartLimitInterval=0 Type=forking StandardOutput=syslog+console StandardError=syslog+console SyslogLevel=err [Install] WantedBy=multi-user.target Link to comment Share on other sites More sharing options...
Dingolino 1 Posted October 30, 2018 Author Share Posted October 30, 2018 And of course I have these error messages in huge amounts... linuxzwo:/var/lib/systemd/coredump # journalctl -u esets.service --since today -- Logs begin at Do 2018-05-24 12:39:35 CEST, end at Di 2018-10-30 10:52:51 CET. -- Okt 30 07:53:40 linuxzwo systemd[1]: Starting ESET Scanner Daemon... Okt 30 07:53:47 linuxzwo systemd[1]: Started ESET Scanner Daemon. Okt 30 07:54:35 linuxzwo esets_daemon[1498]: error[05da0000]: Child process esets_daemon[1499] did not handle signal 6, restart in 0 seconds Okt 30 07:54:38 linuxzwo esets_daemon[1498]: error[05da0000]: Child process esets_daemon[1576] did not handle signal 6, restart in 0 seconds Okt 30 07:54:42 linuxzwo esets_daemon[1498]: error[05da0000]: Child process esets_daemon[1590] did not handle signal 6, restart in 0 seconds Okt 30 07:54:46 linuxzwo esets_daemon[1498]: error[05da0000]: Child process esets_daemon[1618] did not handle signal 6, restart in 0 seconds Okt 30 07:54:51 linuxzwo esets_daemon[1498]: error[05da0000]: Child process esets_daemon[1632] did not handle signal 6, restart in 0 seconds Okt 30 07:54:58 linuxzwo esets_daemon[1498]: error[05da0000]: Child process esets_daemon[1646] did not handle signal 6, restart in 0 seconds Okt 30 07:55:05 linuxzwo esets_daemon[1498]: error[05da0000]: Child process esets_daemon[1660] did not handle signal 6, restart in 0 seconds Okt 30 07:55:13 linuxzwo esets_daemon[1498]: error[05da0000]: Child process esets_daemon[1674] did not handle signal 6, restart in 0 seconds Okt 30 07:55:22 linuxzwo esets_daemon[1498]: error[05da0000]: Child process esets_daemon[1692] did not handle signal 6, restart in 0 seconds Okt 30 07:55:32 linuxzwo esets_daemon[1498]: error[05da0000]: Child process esets_daemon[1706] did not handle signal 6, restart in 0 seconds Link to comment Share on other sites More sharing options...
ESET Moderators Peter Randziak 1,161 Posted October 31, 2018 ESET Moderators Share Posted October 31, 2018 Hello @Dingolino, thank you for the core files, I will have them checked by the devs. On Monday at around 20:20 CET we released Advanced antispam module 7779 (which is revert to 7777) so the crashes should stop after an update. Regards, P.R. Link to comment Share on other sites More sharing options...
Dingolino 1 Posted October 31, 2018 Author Share Posted October 31, 2018 Thank you. Interestingly, the situation has changed since yesterday. I disabled the systemd 'dumpcore' setting and since then no crashes anymore. Link to comment Share on other sites More sharing options...
ESET Moderators Peter Randziak 1,161 Posted October 31, 2018 ESET Moderators Share Posted October 31, 2018 Hello @Dingolino, I makes sense as we reverted the Advanced antispam module, which is probably causing it,... Regards, P.R. Link to comment Share on other sites More sharing options...
ESET Moderators Peter Randziak 1,161 Posted November 6, 2018 ESET Moderators Share Posted November 6, 2018 Hello guys, we were able to find the root cause of the crash, will be fixed in next Advanced antispam module. We apologize for the inconvenience caused. Regards, P.R. Link to comment Share on other sites More sharing options...
Recommended Posts