[Unexplained crashes of Eset Linux Mail Security for servers]

11 hours ago, J.J. said:

Hello

I would suggest man pages every agent have man page, for example you can usecommand man esets.cfg

Also I prepared and exported all of them to pdf, It would be more comfortable. Here you can download them:

hxxp://ftp.nod.sk/~jedovnicky/esets_manpages.zip

I was thinking of some text on an introductory level, for non-experts.

But thank you for your help!

[Unexplained crashes of Eset Linux Mail Security for servers]

6 minutes ago, Rincewind said:

Have you enabled pre-release updates in the config (/etc/opt/eset/esets/esets.cfg)?
av_prerelease_updates = yes

Otherwise you will not receive the fixed module.

I had not. Thank you.
(This product is terribly tricky. Where can I read how to master all this? The manual is definitely too short)

[Unexplained crashes of Eset Linux Mail Security for servers]

I did

rm -rf /var/opt/eset/esets/lib/*
/opt/eset/esets/sbin/esets_update --verbose
systemctl start esets

But eset crashed 3 minutes later

[Unexplained crashes of Eset Linux Mail Security for servers]

I think I managed to pack all the files.

[Unexplained crashes of Eset Linux Mail Security for servers]

@Peter+J.J.

I have uploaded the eset_daemon.txt files to the same location as yesterday.

But whe trying to tar the /tmp/bt* files I run into problems:

linuxzwo:~ # tar cvfz /root/btesetsdaemon.tar.gz /tmp/bt*
-bash: /bin/tar: Die Argumentliste ist zu lang

The last line means "list of files to tar too long". I am unexperienced. What can I do?

 

[Unexplained crashes of Eset Linux Mail Security for servers]

@J.J.

I have done as required. Where to upload the file? In here no tgz allowed as it seems...

[Unexplained crashes of Eset Linux Mail Security for servers]

Hi, I am more and more frustrated by the unstability of this product.

Before Xmas I had the problem described here:

I solved the issue as suggested in the thread.

Now it seems that the problems are back again although nothing on my system was changed.

linuxzwo:~ # systemctl status esets.service 
● esets.service - ESET Scanner Daemon
   Loaded: loaded (/etc/systemd/system/esets.service; enabled; vendor preset: disabled)
   Active: inactive (dead) since Di 2021-01-26 10:55:25 CET; 54min ago
  Process: 1125 ExecStart=/opt/eset/esets/sbin/esets_daemon (code=exited, status=0/SUCCESS)
 Main PID: 1361 (code=exited, status=0/SUCCESS)

Jan 26 10:54:51 linuxzwo esets_daemon[1361]: error[05510000]: Child process esets_daemon[1362] did not handle signal 11, restart in 0 seconds
Jan 26 10:54:54 linuxzwo esets_daemon[1361]: error[05510000]: Child process esets_daemon[2327] did not handle signal 6, restart in 0 seconds
Jan 26 10:54:58 linuxzwo esets_daemon[1361]: error[05510000]: Child process esets_daemon[2340] did not handle signal 6, restart in 0 seconds
Jan 26 10:55:01 linuxzwo esets_daemon[1361]: error[05510000]: Child process esets_daemon[2353] did not handle signal 6, restart in 0 seconds
Jan 26 10:55:04 linuxzwo esets_daemon[1361]: error[05510000]: Child process esets_daemon[2366] did not handle signal 6, restart in 0 seconds
Jan 26 10:55:08 linuxzwo esets_daemon[1361]: error[05510000]: Child process esets_daemon[2379] did not handle signal 6, restart in 0 seconds
Jan 26 10:55:11 linuxzwo esets_daemon[1361]: error[05510000]: Child process esets_daemon[2392] did not handle signal 6, restart in 0 seconds
Jan 26 10:55:15 linuxzwo esets_daemon[1361]: error[05510000]: Child process esets_daemon[2405] did not handle signal 6, restart in 0 seconds
Jan 26 10:55:18 linuxzwo esets_daemon[1361]: error[05510000]: Child process esets_daemon[2418] did not handle signal 6, restart in 0 seconds
Jan 26 10:55:21 linuxzwo esets_daemon[1361]: error[05510000]: Child process esets_daemon[2431] did not handle signal 6, restart in 0 seconds

What should I do to return to stability?

I have configured Eset to run as MDA, the other components are Postfix, Dovecot and Fetchmail.

My version is 4.5.16

linuxzwo:~ # uname -r
4.15.7-2.g353046a-default
linuxzwo:~ # cat /etc/*-release
NAME="openSUSE Leap"
VERSION="42.3"

 

[ESET Mail Security v4.5.9 crashes]

Thank you. Interestingly, the situation has changed since yesterday. I disabled the systemd 'dumpcore' setting and since then no crashes anymore.

[ESET Mail Security v4.5.9 crashes]

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

 

[ESET Mail Security v4.5.9 crashes]

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

 

 

[ESET Mail Security v4.5.9 crashes]

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.

 

[ESET Mail Security v4.5.9 crashes]

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.