Jump to content

Bazze

Members
  • Posts

    6
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Bazze

  1. Update: Today the warnings and errors are gone and no longer showing up. So seems that my certificate generated according to my last post worked fine after all, just took some time for the warnings & errors to clear...
  2. I've encountered the same issue when upgrading to version 7. I see from this thread that the root certificate needs to be included, but even after providing such a certificate I'm still getting the same error. Just to ensure that the full certificate chain is there I verified it using openssl verify command. I've also verified that the root certificate is present in /etc/ssl/certs/* folder (Ubuntu). See below. Verified the certificate: $ openssl verify -CAfile comodo-rsa-domain-validation-sha-2-w-root.ca-bundle my.domain.com.crt my.domain.com.crt: OK I then produced the pfx file using the following command: $ openssl pkcs12 -export -out my.domain.com.pfx -inkey my.domain.com.key -in my.domain.com.crt -certfile comodo-rsa-domain-validation-sha-2-w-root.ca-bundle Certificate was successfully generated and upon inspection using "openssl pkcs12 -info" command I can see that the full chain is in there. However, after applying this HTTPS certificate to the policy I'm still getting the error below. ModSslCertTools: P12 verification failed with error: unable to get local issuer certificate Any input on where I'm doing wrong would be much appreciated.
  3. For us, so far, the example given in this thread has been working great. /Volumes/GoogleDrive/*.* However, I'm now moving over to look at this issue for Windows users. How would one solve it there since volumes are only named with a letter? Seems like it's favoring "G:\" but I guess if it would already be occupied, it would choose another letter. So excluding the "G"-drive doesn't do the trick in all cases. Any ideas?
  4. Thanks @MartinK for the quick answer. Deleting /bin/systemctl did the trick, the installation was now successful.
  5. Hello! I'm dockerizing the ESET Remote Administrator and trying to get it to run locally, however, I'm facing an unknown error during installation as well as a "Failed to connect to bus" error. See installation log in the bottom of this post. Just below here I'll highlight the errors occurring. OS: Ubuntu 16.04 This error occurs at first installation attempt, the error number is different every time. Failed to get unit file state for eraserver.service: Unknown error 1778006384 The error below occurs at first installation attempt, but persist the next time I try the installation (and the status of the install is then in REPAIR instead). Failed to connect to bus: No such file or directory Complete output of first installation attempt. ESET Remote Administrator Server Installer (version: 6.5.417.0), Copyright © 1992-2017 ESET, spol. s r.o. - All rights reserved. Extracting archive, please wait... Archive extracted to /tmp/tmp.jHO0z5kSD5. Checking OpenSSL ... done [OpenSSL 1.0.2g 1 Mar 2016] Reading previous installation settings ... failure Checking installed version... done Status of current installation is: NEW Checking database connection ... done Loading GUID ... done [GUID = adec6e18-45b1-4556-990d-0fa85c98d273] Inserting root password ... done Generating certificates ... done Skipping static groups synchronization scheduling. Stopping service... Creating database ... done Storing ports into configuration ... done Storing server peer certificate to configuration ... done Moving scripts from '/tmp/tmp.jHO0z5kSD5/setup/Scripts' to /var/opt/eset/RemoteAdministrator/Server/Scripts/... done Moving ESET Modules from '/tmp/tmp.jHO0z5kSD5/setup/Modules' to /var/opt/eset/RemoteAdministrator/Server/Modules/... done Creating 'config' directory path: /etc/opt/eset/RemoteAdministrator/Server Creating 'libs' directory path: /opt/eset/RemoteAdministrator/Server Creating 'data' directory path: /var/opt/eset/RemoteAdministrator/Server Creating 'logs' directory path: /var/log/eset/RemoteAdministrator/Server Moving LangData.dat to /var/opt/eset/RemoteAdministrator/Server/Localization/LangData.dat... done Extracting ReportPrinter files... done Creating startup configuration file /etc/opt/eset/RemoteAdministrator/Server/StartupConfiguration.ini ... done Creating config file /etc/opt/eset/RemoteAdministrator/Server/config.cfg ... done Backing up contents of /opt/eset/RemoteAdministrator/Server Copying files to target destination: /opt/eset/RemoteAdministrator/Server Copying installer to target destination: /opt/eset/RemoteAdministrator/Server/setup/installer_backup.sh File ownership set to: root:root Setting auto-start service... Failed to get unit file state for eraserver.service: Unknown error 1778006384 Failed to connect to bus: No such file or directory I'm pretty stuck, can't really find anything online about this error and I was unable to pinpoint the issue by looking at the "server-linux-x86_64.sh" source code. Any tips or pushes in some direction would be very much appreciated! Thanks
×
×
  • Create New...