[tomcat update - manual or AIO installer ?]

hi martin, 

tomcat installer file with name apache-tomcat-9.0.54-windows-x64.zip  exist in extracted dir structure.
setup structure was run extracted  from current downloaded ESET AIO instaler zip . same situation - greyed update when setup runs from iso installer. 

installation history is not quaranted , but i think AIO upgrades was made from 6 to 7 to  9 version.

would help setup logs , but i cant find any. 

we need to solve tomcat upgrade , so upgrade will continue in manual way. 

thanks for your effor to with my problem. 

[tomcat update - manual or AIO installer ?]

in AIO installer in thirdparty folder is newer version  - tomcat installer 9.0.54, on server is 9.0.35 version.
it stay greyed if tomcat installer is replaced with latest tomcat 9.0.62

are some logs to detect greyed out reason  ?

or manual upgrade is only way ? 

[tomcat update - manual or AIO installer ?]

hello,

we need update tomcat to latest version due corporate policy. other Eset Protect products like web console,...  are  up to date and udpated regulary by tasks. but current tomcat is 9.0.35, so it's out.  

there's no  info how current Eset PRotect upgrade was made , via AIO installer or manual upgrade. 
is  somewhere info about upgrade/installation path  ? 

I'm folloving steps in doc for AIO update https://help.eset.com/protect_install/90/en-US/upgrading_apache_tomcat_windows_allinone.html , but last AIO installer has unavailable/ greyed upgrade option , when mouse hover over greyed Upgrade option, Everything is Up to date is shown. 

what is recommended steps to detect reason why upgrade is unavailable ? is there some logs ? 

switch to manual tomcat update will break AIO updates/upgrades path in future - is this presumption  correct ?

thanks for advice

 

 

[Bad link to update server Nod32 on linux]

hello 

i've just installed Eset Nod32 Antivirus 4 on Fedora 28. Now I need to connect it to local update mirror. 

mirror is synchronizing all product include ep4 . But after new update server is defined,  GUI gives me " Bad link to update server  " (in slovak: Zla linka na aktualizacny server). update server is in url format https://e6.domain.xx/updates-4  . /updates-4 path is virtual directory pointing to mirror tool folder with updates for v4 products.   Access is password protected and in config username and password are correct. it's verified by browser window.   

I've try v6 product directory too, but no success. 

When automatic update servers are set, updates are ok. but no with local copy. 

on windows clients Eset Antivirus 6 local update  works fine with url https://e6.domain.xx/updates-4.   

Linux GUI doesnt show any  error message, on disk there are no detailed trace  files too. 

Any hint to get trace files or correct url for local update servers ? 

 

thanks