FHolzer

The Logging is 2 Hours behind. Which makes "sense" since im located in Austria (Central European Summer Time = GMT+2 ) BUT - the time on the Server is correct. Every other Log is correct , just the MDMCore (and Agent) Logs (trace.log) is wrong. Where can i adjust this ? Or is it a bug ?

Oh - i forgot something. On the Same Host Eset Mail Security is installed. So basically i installed Eset Mail Security, the Agent and then MDMCore. Dont know if this can produce an error. --------- Also in "/var/log/eset/RemoteAdministrator/MDMCore/status.html" everything is Green/OK with current Times. looks good. Same goes for the Agent.

Hi, I Installed MDMCore on an Linux Server (Centos 6) From Log (IP Adresses and FQDNs disguised) 2016-04-11 18:07:14 I [1] -------------------------------------------------------------------------------- 2016-04-11 18:07:14 I [1] MDMCore version: 6.3.110.0 2016-04-11 18:07:14 I [1] Running MDMCore... 2016-04-11 18:07:14 I [1] Loading ESET modules from /var/opt/eset/RemoteAdministrator/MDMCore/Modules/ 2016-04-11 18:07:14 I [1] CE2 module initialization 2016-04-11 18:07:15 I [1] Config: server connection: "10.0.x.x", port 2222 2016-04-11 18:07:15 I [1] Config: host: "mxx.xxxxxx.com", port 9981, enrollment port 9980 2016-04-11 18:07:15 I [1] Setting log level from CE to warning 2016-04-11 18:07:15 W [1] Cannot parse APNS cert, iOS enrollment and push notifications will not work 2016-04-11 18:07:18 I [1] Logging to directory /var/log/eset/RemoteAdministrator/MDMCore/Proxy/ i added a Enrollment URL and added a new Device (with IMEI) Worked Fine. Enrollment URL is Reachable via Android Device. in ERA the "Last seen Status" updates - so Device is Communicating ? BUT - i cant Activate the Product via a Task. For Testing Purpose i activated it manually - but i cant start any other task then either. The loggin is also confusing. Some things are logged to /var/log/eset/RemoteAdministrator/MDMCore/trace.log Some other things to /var/log/eset/RemoteAdministrator/MDMCore/Proxy/trace.log Also, the Timestamp is wrong (2 hours behind) - where can i adjust this ? (OS Time is right) The Only thing that pops up sometimes is : 2016-04-15 11:57:26 E [7] Uncaught exception: Net Exception, NodSsl returned an error 200. Peer But absolutly Random - not when i have triggered a Task.

Why would you use AMAVISD anyway ?? From the Documentation

The *.dat Files are for ESET Log Collector. hxxp://www.eset.com/sg/download/utilities/detail/family/236/

yum install glibc.i686 and it will work.