FHolzer

Members
  • Content count

    40
  • Joined

  • Last visited

About FHolzer

  • Rank
    N/A

Recent Profile Visitors

256 profile views
  1. esets_daemon freeze

    i dont know, it was just a common sys-admin thought i didnt used the prerelease-update - i changed the files manually.
  2. esets_daemon freeze

    also, de error sound different, it was delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]:2526: Connection refused in the past and not
  3. esets_daemon freeze

    did you recheck you versions ? (automatically updated, etc)
  4. esets_daemon freeze

    Ty Peter! installed it and will test it. appreciate your work - and dont worry, the best (and every) software has bugs hope we figured the problem - my customers already go crazy ^^ for the record: [root@mail sbin]# ./esets_update --verbose Update is not necessary - the installed virus signature database is current. ESETS Update utility +-+--------------------+------------------------+------------------------+ | | Module | Available version | Installed version | +-+--------------------+------------------------+------------------------+ | | loader | 1069 (20161122) | 1069 (20161122) | | | perseus | 1532 (20171031) | 1532 (20171031) | | | engine | 16530 (20171206) | 16530 (20171206) | | | archiver | 1270 (20171113) | 1270 (20171113) | | | heuristic | 1184 (20171110) | 1184 (20171110) | | | cleaner | 1150 (20171031) | 1150 (20171031) | | | horus | 6556 (20171206) | 6556 (20171206) | | | dblite | 1095 (20171206) | 1095 (20171206) | +-+--------------------+------------------------+------------------------+
  5. esets_daemon freeze

    My Last Response from ESET was on 22.11.2017 with the information: which translates to "we have no glue yet but we will inform you if we find a solution"
  6. esets_daemon freeze

    thank you for the workaround, Still - this isnt an open source or free product. I payed for the smpt scan - i need a fix for it.
  7. esets_daemon freeze

    for me its a litte hard do reproduce the error. Yes its still there - but it happens in a time span of Days to weeks. not hours/minutes like for others. but sure, i can try it.
  8. esets_daemon freeze

    Just had this Error myself again. - so its not fixed with 4.5.9 it worked around 7days straight with no problem. Im in contact with ESET Support again - will inform you guys about the progress.
  9. esets_daemon freeze

    so far - no. All i got from ESET is and was -> it should be fixed in 4.5.9 so far i didnt had the error anymore. all you can do is open an offical Support Ticket, collect your logs, send it to ESET, wait and hope. Can you post your installed versions with cd /opt/eset/esets/sbin ./esets_update --verbose and also daemon version with /opt/eset/esets/sbin/esets_daemon --version
  10. esets_daemon freeze

    it should be fixed by today. (02.11.2017) Developers informed me that 4.5.9 was released today which includes a bugfix for this problem.
  11. esets_daemon freeze

    do be honest, this Bug is so critical - it should never happend. But it did - Twice in 1 Year. Im not sure if i should resell Linux Products from ESET in the Future - since im not sure if the product is stable enough. All i have now are angry Customers who complain about "no working Mailserver" - AGAIN. But lets hope They can fix it very soon or i need to uninstall it.
  12. esets_daemon freeze

    it just happend again. CentOS: centos-release-7-3.1611.el7.centos.x86_64 Mail Security Version: /opt/eset/esets/sbin/esets_daemon (esets) 4.5.7 Components: [root@mail sbin]# ./esets_update --verbose Update is not necessary - the installed virus signature database is current. ESETS Update utility +-+--------------------+------------------------+------------------------+ | | Module | Available version | Installed version | +-+--------------------+------------------------+------------------------+ | | loader | 1069 (20161122) | 1069 (20161122) | | | perseus | 1530 (20170920) | 1530 (20170920) | | | engine | 16236 (20171013) | 16236 (20171013) | | | archiver | 1269 (20170913) | 1269 (20170913) | | | heuristic | 1180 (20170914) | 1180 (20170914) | | | cleaner | 1142 (20170814) | 1142 (20170814) | | | horus | 6282 (20171013) | 6282 (20171013) | | | dblite | 1093 (20170725) | 1093 (20170725) | +-+--------------------+------------------------+------------------------+ Error in maillog: relay=127.0.0.1[127.0.0.1]:2526, delay=1651, delays=1351/0.02/300/0, dsn=4.4.2, status=deferred (conversation with 127.0.0.1[127.0.0.1] timed out while receiving the initial server greeting) Status eset Daemon: [root@mail ~]# systemctl status esets ● esets.service - ESET Scanner Daemon Loaded: loaded (/usr/lib/systemd/system/esets.service; enabled; vendor preset: disabled) Active: active (running) since Wed 2017-10-11 19:39:29 CEST; 1 day 20h ago Process: 859 ExecStart=/opt/eset/esets/sbin/esets_daemon (code=exited, status=0/SUCCESS) Main PID: 2578 (esets_daemon) CGroup: /system.slice/esets.service ├─2578 /opt/eset/esets/sbin/esets_daemon ├─2679 /opt/eset/esets/sbin/esets_daemon ├─2680 /opt/eset/esets/lib/esets_smtp ├─2681 /opt/eset/esets/lib/esets_wwwi └─2691 /opt/eset/esets/lib/esets_smtp Oct 13 14:00:26 mail.xxxx-xxxx.com esets_daemon[2679]: summ[0a7701e4]: vdb=35048, agent=smtp, name="from: "xxxx" <sss@ssss.com> to: "xxx" <xxxx@xxxx-xxxx.com> …d" Oct 13 14:00:26 mail.xxxx-xxxx.com esets_smtp[2691]: summ[0a830101]: action="accepted" Oct 13 14:07:15 mail.xxxx-xxxx.com esets_daemon[2679]: summ[0a7702e5]: vdb=35048, agent=smtp, name="from: "xxxx <sss@xxxx-xxxx.com> to: "xxx, xxx" <xxx.xxr@…d" Oct 13 14:07:15 mail.xxxx-xxxx.com esets_smtp[2691]: summ[0a830201]: action="accepted" Oct 13 14:13:29 mail.xxxx-xxxx.com esets_daemon[2679]: summ[0a7701e6]: vdb=35048, agent=smtp, name="from: "xxx" <xxx@xxxx.xxx.com> to: office@xxxx-xxxx.com with subject Jetzt K...p="accepted" Oct 13 14:13:29 mail.xxxx-xxxx.com esets_smtp[2691]: summ[0a830201]: action="accepted" Oct 13 14:14:24 mail.xxxx-xxxx.com esets_daemon[2679]: summ[0a7702e7]: vdb=35048, agent=smtp, name="from: "xxx" <info26@xxxx.es> to: office@xxxx-xxxx.com with subject Curs...p="accepted" Oct 13 14:14:24 mail.xxxx-xxxx.com esets_smtp[2691]: summ[0a830101]: action="accepted" Oct 13 14:26:51 mail.xxxx-xxxx.com esets_daemon[2679]: summ[0a7701e8]: vdb=35048, agent=smtp, name="from: "xxxx" <xxx@xxx.de> to: xxxx <xxx@sss…d" Oct 13 14:26:51 mail.xxxx-xxxx.com esets_smtp[2691]: summ[0a830101]: action="accepted" Hint: Some lines were ellipsized, use -l to show in full. PIDs running: [root@mail ~]# ps -C esets_daemon PID TTY TIME CMD 2578 ? 00:00:07 esets_daemon 2679 ? 01:46:52 esets_daemon you cant restart/stop the service via systemctl systemctl stop esets via /etc/init.d/esets stop its working (kind of) - its stops one of the PIDs. [root@mail ~]# /etc/init.d/esets stop Stopping esets (via systemctl): [ OK ] [root@mail ~]# ps -C esets_daemon PID TTY TIME CMD 2679 ? 01:46:53 esets_daemon you have to kill the remaining PID: [root@mail ~]# kill -9 2679 [root@mail ~]# ps -C esets_daemon PID TTY TIME CMD After that you can start the daemons again: [root@mail ~]# systemctl start esets [root@mail ~]# systemctl status esets ● esets.service - ESET Scanner Daemon Loaded: loaded (/usr/lib/systemd/system/esets.service; enabled; vendor preset: disabled) Active: active (running) since Fri 2017-10-13 16:06:31 CEST; 10s ago Process: 53297 ExecStart=/opt/eset/esets/sbin/esets_daemon (code=exited, status=0/SUCCESS) Main PID: 53298 (esets_daemon) CGroup: /system.slice/esets.service ├─53298 /opt/eset/esets/sbin/esets_daemon ├─53299 /opt/eset/esets/sbin/esets_daemon ├─53300 /opt/eset/esets/lib/esets_smtp ├─53301 /opt/eset/esets/lib/esets_wwwi └─53312 /opt/eset/esets/lib/esets_smtp Oct 13 16:06:27 mail.xxxxx.com systemd[1]: Starting ESET Scanner Daemon... Oct 13 16:06:31 mail.xxxxx.com systemd[1]: Started ESET Scanner Daemon. Both daemons started - check it -> [root@mail ~]# ps -C esets_daemon PID TTY TIME CMD 53298 ? 00:00:00 esets_daemon 53299 ? 00:00:00 esets_daemon after that everything works fine again. (real tests and maillog check)
  13. esets_daemon freeze

    Hi Michal. Thanks for your effort! Please keep us informed. ------------ I Just had this Error on a Centos 6.x with a 4.5.3 Version. Im not sure if its related. (i personally dont think so) Versions: +-+--------------------+------------------------+------------------------+ | | Module | Available version | Installed version | +-+--------------------+------------------------+------------------------+ | | loader | 1069 (20161122) | 1069 (20161122) | | | perseus | 1530 (20170920) | 1530 (20170920) | | | engine | 16234 (20171013) | 16234 (20171013) | | | archiver | 1269 (20170913) | 1269 (20170913) | | | heuristic | 1180 (20170914) | 1180 (20170914) | | | cleaner | 1145 (20170906) | 1145 (20170906) | | | horus | 3616 (20160429) | 3616 (20160429) | +-+--------------------+------------------------+------------------------+ Looks like its the old 4.5.3 Bug (no Horus Update) - but it worked for over a year now without a problem. And 4.5.7 keeps failing - so i dont will upgrade it for now.
  14. esets_daemon freeze

    The Error Came back since update to 4.5.7 All Version before it worked fine (over 2 years - 0 restarts needed) So its definitively a 4.5.7 Bug. for me the error occours from time to time now (from 8hours to 20 days) This is log when the freeze starts: (conversation with 127.0.0.1[127.0.0.1] timed out while receiving the initial server greeting) this can we find if we try to restart the esets daemons (delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]:2526: Connection refused) And STILL how to read the esets LOG under /var/log/esets/ (*.dat) files. Why is there no REAL Error logging (besides the maillog and the syslog?)