Jump to content

FHolzer

Members
  • Content Count

    56
  • Joined

  • Last visited

Profile Information

  • Location
    Austria

Recent Profile Visitors

923 profile views
  1. everything else seem's to be working perfectly fine with Centos8. (would be a shame if not ....)
  2. most of you errors are missing "common linux knowledge". Im not tryin to be offense - but you should probably get more linux skills before installing software like this. i dont see anything related to ESET. Also keep in mind that there so MANY Linux distros with different Package Versions. The Documentation is good - but you should know what you are doing and dont copy paste all commands without thinking. As example -> if you dont know where your my.cnf is located - you are missing common mysql/mariadb knowledge. If you dont know how to search for a file on linux -> you are
  3. what was the output of ausearch -c 'esets_mda' --raw | audit2allow -M my-esetsmda semodule -i my-esetsmda.pp ?
  4. OS: Centos 8 | 4.18.0-193.28.1.el8_2.x86_64 ESET ver: /opt/eset/esets/sbin/esets_daemon (esets) 4.5.16 Selinux: disabled [wwwi] agent_enabled = yes listen_addr = "10.0.1.15" listen_port = 3377 username = "esetlogin" password = "test1234" when i restart the esets process i get the following error: esets_daemon[3458]: error[0d820000]: Child process wwwi[3460] terminated with return code 127, won't be restarte cant anything related to error code 127. What i`m missing? Generally Exit Code 127 means something like "command is not found" It worked on several c
  5. had the same issue. thanks for creating the post @Krzysztof L. this year you saved me time Well i guess i did it the last 4 years @Marcos Can confirm it was a corrupt perseus / em002_32.dat
  6. Hi, i set up a whitelist via user_specific_configuration (user_config = "esets_smtp_spec.cfg") The `esets_smtp_spec.cfg` looks like this [black-list] action_av = "reject" [white-list] action_av = "accept" action_as = "accept" [|sndrname1@sndrdomain1.com] parent_id = "white-list" is there a wildcard way for whitelisting the whole domain? Will Something like this work? : [|sndrdomain1.com] parent_id = "white-list" also - the help page is referring to "For esets_smtp, refer to the esets_smtp(1) man page." Where can i find this man page online? sincerly
  7. wow - what an fast response. TY unfortunately i dont have an em001.dat [root@srvmail01 sbin]# cd /var/opt/eset/esets/lib/ [root@srvmail01 lib]# ll total 103720 drwxr-xr-x 3 esets esets 4096 14. Apr 2016 data -rw-r--r-- 1 esets esets 172409 30. Sep 13:30 em000_32.dat -rw-r--r-- 1 esets esets 1100402 23. Okt 14:57 em001_32.dat -rw-r--r-- 1 esets esets 70579835 24. Okt 17:42 em002_32.dat -rw-r--r-- 1 esets esets 1479292 10. Okt 14:43 em003_32.dat -rw-r--r-- 1 esets esets 2391100 8. Okt 12:40 em004_32.dat -rw-r--r-- 1 esets esets 323143 24. Sep 12:22 em005_32.dat -rw-r--r-- 1
  8. It looks like the Problem is back since October 29, 2018 status=deferred (connect to 127.0.0.1[127.0.0.1]:2526: Connection refused) Mail Security Version: 4.5.15 Signatures: [root@srvmail01 ~]# cd /opt/eset/esets/sbin/ [root@srvmail01 sbin]# ./esets_update --verbose Update is not necessary - the installed virus signature database is current. ESETS Update utility +-+--------------------+------------------------+------------------------+ | | Module | Available version | Installed version | +-+--------------------+------------------------+-
  9. hi @CircleSquare !! can you post us your output from ? cd /opt/eset/esets/sbin ./esets_update --verbose
  10. for now it looks stable. i will inform you if it crashes again. Thanks for your time!
  11. first yes looks like there was also a horus update. im on | horus | 7779 (20181029) | 7779 (20181029) | im not sure if the issue was resolved with that - since the error occurs from 10minutes after starting the daemon - up to 24hours and more. we will see. was there a fix in v7779 cause you are mentioning it ?
  12. what do you mean with ` including fresh info_get command logs ` ? Edit - oh you mean that -> https://support.eset.com/kb6159/?locale=en_US&viewlocale=en_US got you ---- also there is a new engine version again | | engine | 18293 (20181029) | 18293 (20181029) |
  13. just made an Virus Database Update again. It Updated the engine from 18289 to 18291. the Update is from today - so it looks like it just was released. [root@srvmail01 sbin]# ./esets_update --verbose Virus signature database has been updated successfully. ESETS Update utility +-+--------------------+------------------------+------------------------+ | | Module | Available version | Installed version | +-+--------------------+------------------------+------------------------+ | | loader | 1072 (20180813) | 1072 (20180813) | | | perseus
  14. It looks like the Problem is back since 25/10/2018. Also confirmed from the User Krzysztof L. Same error pattern as in the old topic. The daemon runs for 10 - 30 seconds and than is "dead" i Updated everything so far but problem persists. [root@srvmail01 ~]# /opt/eset/esets/sbin/esets_daemon --version /opt/eset/esets/sbin/esets_daemon (esets) 4.5.11 ./esets_update --verbose Update is not necessary - the installed virus signature database is current. ESETS Update utility +-+--------------------+------------------------+------------------------+ | | Module
×
×
  • Create New...