Hello community,
I do run Proxmox since few weeks and need to increase virus filtering performance.
I browse the forum and purchase an Avast license.
I follow the documentation : Proxmox Website
first chapter was fine (Installing Avast Antivirus for Linux)
second one pointing to Avast support (How do I insert a license file to Avast Security for Linux?)
was fine too,
I was able to create the file from the serial I got from Avast using the Documentation provided with the license Key.
restarting the service was not fine due to missing file license.avastlic
-> I chmod the file in 777 and try again to restart the service : Ok
then latest one : 'integration' was easy
On the GUI, nothing changes, no Avast tab.
I reboot the system,
read the logs,
need to add 'whitelist' file in /etc/avast/ to avoid error in messages.log
So now, I do not find any error anymore in the logs (messages & syslog) but do not 'see' anything related to Avast in the GUI.
Is this normal ?
neither service dedicated to this new Av.
so my questions are :
1. is this normal to do not find any tab / information ?
only this in syslog:
systemd[1]: Starting LSB: Avast antivirus service...
avast: main: Starting daemon
CRON[1378]: (root) CMD (/var/lib/avast/Setup/avast.vpsupdate 2>&1 | logger -t avast.vpsupdate -i -p daemon.warn)
2. how could I check (as in ClamAv tab) if I'm up to date, force update ...
3. do I need to edit the default conf. file in /etc/avast/ ?
4. is this normal behaviour ?
5. How do I edit/check the cron which is supposed to integrate the Avast update (cf. documentation)
Thanks,
I do run Proxmox since few weeks and need to increase virus filtering performance.
I browse the forum and purchase an Avast license.
I follow the documentation : Proxmox Website
first chapter was fine (Installing Avast Antivirus for Linux)
second one pointing to Avast support (How do I insert a license file to Avast Security for Linux?)
was fine too,
I was able to create the file from the serial I got from Avast using the Documentation provided with the license Key.
restarting the service was not fine due to missing file license.avastlic
-> I chmod the file in 777 and try again to restart the service : Ok
then latest one : 'integration' was easy
On the GUI, nothing changes, no Avast tab.
I reboot the system,
read the logs,
need to add 'whitelist' file in /etc/avast/ to avoid error in messages.log
So now, I do not find any error anymore in the logs (messages & syslog) but do not 'see' anything related to Avast in the GUI.
Is this normal ?
neither service dedicated to this new Av.
so my questions are :
1. is this normal to do not find any tab / information ?
only this in syslog:
systemd[1]: Starting LSB: Avast antivirus service...
avast: main: Starting daemon
CRON[1378]: (root) CMD (/var/lib/avast/Setup/avast.vpsupdate 2>&1 | logger -t avast.vpsupdate -i -p daemon.warn)
2. how could I check (as in ClamAv tab) if I'm up to date, force update ...
3. do I need to edit the default conf. file in /etc/avast/ ?
4. is this normal behaviour ?
5. How do I edit/check the cron which is supposed to integrate the Avast update (cf. documentation)
Code:
Point #3
; Avast configuration file
;
; Below are all available configuration options and their default values. Only
; the options in the OPTIONS section can be changed at runtime.
;
; RUN_DIR = "/var/run/avast"
; TEMP_DIR = "/tmp"
; DATA_DIR = "/var/lib/avast"
; SOCKET = "/var/run/avast/scan.sock"
; LICENSE = "/etc/avast/license.avastlic"
; WHITELIST = "/etc/avast/whitelist.txt"
; SUBMIT = "/var/lib/avast/Setup/submit"
;
; [OPTIONS]
; CREDENTIALS = 0
; STATISTICS = 1
; HEURISTICS = 1
; STREAMING_UPDATES = 1
Code:
point #4
Sep 30 19:35:36 mx4 systemd[1]: Stopping LSB: Avast antivirus service...
Sep 30 19:35:36 mx4 avast[1512]: Shutting down avast...:start-stop-daemon: matching only on non-root pidfile /var/run/avast/avast.pid is insecure
Sep 30 19:35:36 mx4 avast[1512]: failed!
Sep 30 19:35:36 mx4 systemd[1]: avast.service: Succeeded.
Sep 30 19:35:36 mx4 systemd[1]: Stopped LSB: Avast antivirus service.
Sep 30 19:35:36 mx4 systemd[1]: avast.service: Found left-over process 1227 (avast) in control group while starting unit. Ignoring.
Sep 30 19:35:36 mx4 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Sep 30 19:35:36 mx4 systemd[1]: Starting LSB: Avast antivirus service...
Sep 30 19:35:36 mx4 avast[1519]: Starting avast...:.
Sep 30 19:35:36 mx4 systemd[1]: Started LSB: Avast antivirus service.
Code:
Point #5
0 * * * * /var/lib/avast/Setup/avast.vpsupdate
Thanks,
Last edited: