Jump to content


  • Content Count

  • Joined

  • Last visited

Profile Information

  • Gender
  • Location
  1. Hi all, i was following this thread because it's an interesting discussion and this is what i think: it would be nice to have a kind of "pseudo code" to manage task and triggers inside web console, just to let some more complex operations Mirko
  2. Hi Martink, I think I've solved! 1: shutdown container, edit config file and add this, just because if you run lxc on a systemd it won't auto set systemd for guests (argh!!) lxc.autodev = 1 lxc.kmsg = 0 Reference: Debian Jessie and lxc containers (https://www.debian.org/releases/stable/i386/release-notes/ch-information.en.html#issues-lxc-jessie-host) 2: wget serverinstall from eset and run it as root (it shows a initcl error, but systemd starts) 3: reboot lxc just for check and eraserver service is running. 4: deploy agent from webconsole (liveinstaller). 5: run agent installe
  3. Now I am almost sure it is problem with upstart which was introduced in 6.3. There containers (lxc, docker) are not able to handle upstart or systemd services properly, they are either completely mocked or requires advanced configuration to work properly. ERA installers are detecting upstart by searching for command "initctl" -> once found, fully operational upstart is expected. In case you will be able to confirm that it is problem with upstart service initialization, only solution we were able to come with is to fool upstart detection by temporarily renaming/removing initctl command =
  4. Component upgrade from Webconsole failed (check in trace.log of agent) 2016-02-02 19:28:59 Error: CSystemConnectorModule [Thread 7fcd40ca6700]: ReadUpgradeStatus: Upgrade infrastructure task failed: Error upgrading with installer '/tmp/6ef7-2323-55c2-747a/Server-Linux-x86_64.sh': Command failed (exit code: 1) 2016-02-02 19:40:36 Error: CSystemConnectorModule [Thread 7fccab7fe700]: UpgradeInfrastructure: Error upgrading with installer '/tmp/1b23-2b21-d641-8d84/Server-Linux-x86_64.sh': Command failed (exit code: 1) Please note timing, it was 20.40 when i launched the task (i think it's just u
  5. From EraServerInstaller.log - It seems ok, but no server service from 2016-02-01 13.07 - I've just done a reboot and still get "Login failed not connected" I can just manually start Era server from /opt/eset/RemoteAdministrator/Server/setup/eraserver start/restart and so i can log into webconsole The same was for the agent, so i manually started from /opt/eset/RemoteAdministrator/Agent/setup/eraagent start/restart Now I'll try a Remote Administrator Components Upgrade - hope it'll fix all services on boot problems Other suggestions? EraServerInstaller.log 2016-02-01 13:16
  6. Muting: ERA and webconsole are all 6.3.x (managed upgrade from 6.2.x via webconsole components upgrade asa eset released new versions, it was all fine without using CLI) The only strange data in audit log is about UPDATE MODULES It seems a task performed by system (system user - system - native user yes) and get always failed!!
  7. 2016-02-01 13:17:04 Error: CSystemConnectorModule [Thread 7f99edffb700]: UpgradeInfrastructure: Error upgrading with installer '/tmp/6ef7-2323-55c2-747a/Server-Linux$ <--- ?!?!? Never asked for server upgrade ?!?!? 2016-02-01 13:18:02 Error: CReplicationModule [Thread 7f99ef7fe700]: CReplicationManager: Replication (network) connection to 'host: "" port: 2222' faile$ Probably solved or at least got services running: after that upgrade (but i never asked for server upgrades!!!) all services went down, messing up mysql too. Just forced eset service manually (/opt/eset/Rem
  8. Hi all, I've already read about problems with mysql db, etc, etc. but i don't find a way to solve. It was all good today, but something got wrong after a scan task on 27 clients. ODBC should be ok ( hxxp://help.eset.com/era_install/63/en-US/index.html?odbc_configuration.htm- done it and got "odbcinst: Driver installed. Usage count increased to 2" ), nothing has been changed, except for mysql update on debian (done just 1 hour ago) latest server trace.log: 2016-02-01 13:16:57 Information: AutomationModule [Thread 7f3520282740]: Facade: Trigger has been unloaded [SHUTDOWN=1, UUID=
  9. Simply download .sh to you machine, login and run it from shell Mirko Thanks for you reply... If I do as you said then the agent file will be downloaded from the ESET repository and it will consume internet bandwidth to install in each and every client workstation which I don't want. As I said earlier that I have shared Agent installer file in my network on windows PC and I want to replace the path from repository.eset.com to my shared network path in EraAgentInstaller.sh file. Ok, sorry for that, looking to EraAgentInstaller.sh it uses WGET to download from repository
  10. Simply download .sh to you machine, login and run it from shell Mirko
  11. Ok, that one is the "on the fly" solution, but don't you think it'd be nice to have a Dynamic group auto checking for latest products from eset servers?? - it's a proposal for future era releases
  12. So no answer?!? Ok, i've manually done it (take a look to the images - computers and dynamic groups template), but it'd be useful to get software version not equal to "latest" than changing it for every new ESET new version release. With Era Web Console you've already got this info (look at the dashboard for eset products), so it should be simple to implement. Don't you agree?? Mirko
  13. Hi all, I've just managed to upgrade ERA Server and agent on linux server to the latest 6.x version by a client task (Debian server has got his agent, so i could update all via web console), but i'm not able to manage lan clients outdated products. I'd like to create a dynamic group like that one from the dashboard (Eset applications - Outdated products) and attach it a trigger (something link "when you get computer with product outdated install new version of eset agent and eset enpoint antivirus), but if i check for dynamic groups I can only create a trigger looking for a specific versi
  • Create New...