Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 38 replies
  • Subscribers 9 subscribers
  • Views 40999 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos Linux don't accept the configuration " UpdatePeriodMinutes "

Henrique RJ

Hello


After recent update Sophos Free Linux don't accept more the configuration when I put in " UpdatePeriodMinutes " (#/opt/sophos-av/bin/savconfig UpdatePeriodMinutes 1440 ) 1440 minutes ( 24 hours ).

Now it update every 4 hours.


Any solution ?


Thanks



This thread was automatically locked due to age.
  • 0 in reply to Henrique RJ

    Looking at the other log I see that savd is being restarted very frequently, so this may be related to your issues.

    In SAV: UpdatePeriodMinutes is relative to the start of savd.

    In 9.14:

    • The first update (check) happened UpdatePeriodMinutes after savd starts.
    • savupdate restricts Sophos updates to no more than once per hour.

    In 9.15:

    • The first update (check) happens 5-10 minutes after savd starts.
    • Subsequent update (checks) happen UpdatePeriodMinutes after the previous update.
    • savupdate doesn't restrict Sophos updates.

     

    This was a deliberate change to support temporary machines and new installs, which weren't getting updates quickly enough.

     

    I suspect this might explain some of what you are seeing, since I was in the other log you gave me that savd is being restarted very frequently.

     

  • 0 in reply to DouglasLeeder

    DouglasLeeder said:

    Looking at the other log I see that savd is being restarted very frequently, so this may be related to your issues.

    In SAV: UpdatePeriodMinutes is relative to the start of savd.

    In 9.14:

    • The first update (check) happened UpdatePeriodMinutes after savd starts.
    • savupdate restricts Sophos updates to no more than once per hour.

    In 9.15:

    • The first update (check) happens 5-10 minutes after savd starts.
    • Subsequent update (checks) happen UpdatePeriodMinutes after the previous update.
    • savupdate doesn't restrict Sophos updates.

     

    This was a deliberate change to support temporary machines and new installs, which weren't getting updates quickly enough.

     

    I suspect this might explain some of what you are seeing, since I was in the other log you gave me that savd is being restarted very frequently.

     

     

     

    confuse ...

     

    This problem begining after version update ( 9.14 to 9.15 in 21th the current month ).

     

    This the fact !!!

  • 0 in reply to Henrique RJ

    I has solved it.

    I adjusted for 60 minutes and reboot da system.

    Then I aguard the Sophos update normaly including 60 minutes after.

    Right after adjust for 1440 minutes ( 24h ) and now it work perfectely.

    It was probably some bug

     

    Thank you all !!!

  • 0 in reply to Henrique RJ

    The problem return after reboot !!!

     

  • 0 in reply to Henrique RJ

    Hello

    I am not satisfied with this every hour update,  so I changed also

     

    /opt/sophos-av/bin/savconfig query UpdatePeriodMinutes
    1440

     

    Here is how I managed

    Modify the script /opt/sophos-av/engine/.sav-update.systemd.start.sh

    Last line is now

     

    exec "$SAVUPDATE" >>"$SAV_UPDATE_LOG" 2>&1 </dev/null || true

     

    Modify the /lib/systemd/system/sav-update.service

     

    # Copyright 2004-2017 Sophos Limited.
    # All rights reserved.

    [Service]
    Type=oneshot
    ExecStartPre=/opt/sophos-av/engine/.sav-update.systemd.prestart.sh
    ExecStart=/opt/sophos-av/engine/.sav-update.systemd.start.sh
    ExecStartPost=-/opt/sophos-av/engine/.sav-update.systemd.poststart.sh
    ExecStop=/opt/sophos-av/engine/.sav-update.systemd.stop.sh
    TimeoutStartSec=0
    TimeoutStopSec=60
    Restart=no

    [Install]
    WantedBy=multi-user.target

    [Unit]
    Description="Sophos Anti-Virus update"
    # author "Sophos Limited, Oxford, England, http://www.sophos.com"
    RequiresMountsFor="/opt/sophos-av"
    Documentation=man:sav-update
    # Attendre le démarrge de protect-service
    After=sav-protect.service

    # SfL-Upstart-Job-Class: boot

    ```

    Enable it

     

    systemctl enable sav-update.service

     

    That way I have only one update after boot

     

    systemctl status sav-update
    ● sav-update.service - "Sophos Anti-Virus update"
    Loaded: loaded (/lib/systemd/system/sav-update.service; enabled; vendor preset: enabled)
    Active: inactive (dead) since Wed 2018-06-27 16:16:26 CEST; 1h 8min ago
    Docs: man:sav-update
    Process: 3885 ExecStop=/opt/sophos-av/engine/.sav-update.systemd.stop.sh (code=exited, status=0/SUCCESS)
    Process: 3884 ExecStartPost=/opt/sophos-av/engine/.sav-update.systemd.poststart.sh (code=exited, status=0/SUCCESS)
    Process: 3788 ExecStart=/opt/sophos-av/engine/.sav-update.systemd.start.sh (code=exited, status=0/SUCCESS)
    Process: 3786 ExecStartPre=/opt/sophos-av/engine/.sav-update.systemd.prestart.sh (code=exited, status=0/SUCCESS)
    Main PID: 3788 (code=exited, status=0/SUCCESS)

    juin 27 16:15:13 debian systemd[1]: Starting "Sophos Anti-Virus update"...
    juin 27 16:16:26 debian systemd[1]: Started "Sophos Anti-Virus update".

     

    systemctl status sav-protect
    ● sav-protect.service - "Sophos Anti-Virus daemon"
    Loaded: loaded (/lib/systemd/system/sav-protect.service; enabled; vendor preset: enabled)
    Active: active (running) since Wed 2018-06-27 16:10:40 CEST; 1h 14min ago
    Docs: man:sav-protect
    Process: 3036 ExecStartPost=/opt/sophos-av/engine/.sav-protect.systemd.poststart.sh (code=exited, status=0/SUCCESS)
    Process: 2954 ExecStartPre=/opt/sophos-av/engine/.sav-protect.systemd.prestart.sh (code=exited, status=0/SUCCESS)
    Main PID: 3035 (savd)
    Tasks: 23 (limit: 4299)
    Memory: 787.2M
    CGroup: /system.slice/sav-protect.service
    ├─3035 savd etc/savd.cfg
    ├─3880 savscand --incident=unix://tmp/incident --namedscan=unix://root@tmp/namedscansprocessor.1 --ondemandcontrol
    └─3893 savscand --incident=unix://tmp/incident socketpair://49/56 --threads=2

    juin 27 16:09:57 debian systemd[1]: Starting "Sophos Anti-Virus daemon"...
    juin 27 16:10:11 debian savd[3035]: savd.daemon: SAVD-STARTED
    juin 27 16:10:37 debian savd[3035]: savd.daemon: ONACCESS-ENABLED talpa
    juin 27 16:10:40 debian systemd[1]: Started "Sophos Anti-Virus daemon".
    juin 27 16:12:18 debian savd[3035]: savscand.control.log: EXTRA-SCANNER-STARTED
    juin 27 16:12:24 debian savd[3035]: savscand.control.log: EXTRA-SCANNER-STOPPED
    juin 27 16:16:26 debian savd[3035]: update.updated: UPDATING_FROM_VERSION 9.15.0 3.72.1 5.52
    juin 27 16:16:26 debian savd[3035]: update.updated: Updating Sophos Anti-Virus....
    Updating SAVScan on-demand scanner
    Updating Virus Engine and Data
    Updating Manifest
    Update completed.
    juin 27 16:16:26 debian savd[3035]: update.updated: UPDATED_TO_VERSION 9.15.0 3.72.1 5.52
    juin 27 16:16:26 debian savd[3035]: update.updated: SUCCESSFULLY_UPDATED_FROM sdds:SOPHOS

     

     

  • 0 in reply to grand toubab

    Hi  

     

    Exists some solution that I configure for not update after boot ?

    Now it update every boot and respect configuration of 1440 minutes ( 24h ).

    Terefore, the proccess loaded at boot for preload are afected.

     

    Thanks very much.

  • 0 in reply to Haridoss Sreenivasan

    Haridoss Sreenivasan said:

    Hi Henrique,

    Please allow me to check on this and update you.

     

    Hello

     

    Any news ?

  • 0 in reply to Henrique RJ

    savupdate will run during sav-protect start up script if:

    1. On-Access is enabled
    2. Talpa is an enabled on-access method
    3. SAV doesn't have a Talpa Binary Pack available

    savupdate will run 5-10 minutes after savd starts up, unless updating is disabled.

     

  • 0 in reply to DouglasLeeder

    DouglasLeeder said:

    savupdate will run during sav-protect start up script if:

    1. On-Access is enabled
    2. Talpa is an enabled on-access method
    3. SAV doesn't have a Talpa Binary Pack available

    savupdate will run 5-10 minutes after savd starts up, unless updating is disabled.

     

     

    But how disable update after 5-10 minutes boot system without deactivat on-access ?

  • 0 in reply to Henrique RJ

    Perfect

     

    root@debian:/opt/sophos-av/bin# ls
    _ savconfig savdctl savdstatus savlog savscan savsetup savupdate
    root@debian:/opt/sophos-av/bin# ./savdstatus
    Sophos Anti-Virus is active and on-access scanning is running
    root@debian:/opt/sophos-av/bin# systemctl status sav-protect -l -n 50 --no-pager
    ● sav-protect.service - "Sophos Anti-Virus daemon"
    Loaded: loaded (/lib/systemd/system/sav-protect.service; enabled; vendor preset: enabled)
    Active: active (running) since Thu 2018-06-28 09:59:03 CEST; 28min ago
    Docs: man:sav-protect
    Process: 2825 ExecStartPost=/opt/sophos-av/engine/.sav-protect.systemd.poststart.sh (code=exited, status=0/SUCCESS)
    Process: 2706 ExecStartPre=/opt/sophos-av/engine/.sav-protect.systemd.prestart.sh (code=exited, status=0/SUCCESS)
    Main PID: 2824 (savd)
    Tasks: 24 (limit: 4299)
    Memory: 662.9M
    CGroup: /system.slice/sav-protect.service
    ├─2824 savd etc/savd.cfg
    ├─2910 savscand --incident=unix://tmp/incident --namedscan=unix://root@tmp/namedscansprocessor.0 --ondemandcontrol=socketpair://45/46 socketpair://43/44 --threads=2
    └─3317 savscand --incident=unix://tmp/incident socketpair://49/50 --threads=2

    juin 28 09:58:11 debian systemd[1]: Starting "Sophos Anti-Virus daemon"...
    juin 28 09:58:20 debian savd[2824]: savd.daemon: SAVD-STARTED
    juin 28 09:58:58 debian savd[2824]: savd.daemon: ONACCESS-ENABLED talpa
    juin 28 09:59:03 debian systemd[1]: Started "Sophos Anti-Virus daemon".
    juin 28 09:59:11 debian savd[2824]: savscand.control.log: EXTRA-SCANNER-STARTED
    juin 28 09:59:17 debian savd[2824]: savscand.control.log: EXTRA-SCANNER-STOPPED
    juin 28 10:05:51 debian savd[2824]: update.check: SUCCESSFULLY_UPDATED_FROM sdds:SOPHOS

     


    root@debian:/opt/sophos-av/bin# systemctl status sav-update -l -n 50 --no-pager
    ● sav-update.service - "Sophos Anti-Virus update"
    Loaded: loaded (/lib/systemd/system/sav-update.service; enabled; vendor preset: enabled)
    Active: inactive (dead) since Thu 2018-06-28 10:05:51 CEST; 22min ago
    Docs: man:sav-update
    Process: 4395 ExecStop=/opt/sophos-av/engine/.sav-update.systemd.stop.sh (code=exited, status=0/SUCCESS)
    Process: 4394 ExecStartPost=/opt/sophos-av/engine/.sav-update.systemd.poststart.sh (code=exited, status=0/SUCCESS)
    Process: 4361 ExecStart=/opt/sophos-av/engine/.sav-update.systemd.start.sh (code=exited, status=0/SUCCESS)
    Process: 4359 ExecStartPre=/opt/sophos-av/engine/.sav-update.systemd.prestart.sh (code=exited, status=0/SUCCESS)
    Main PID: 4361 (code=exited, status=0/SUCCESS)

    juin 28 10:05:05 debian systemd[1]: Starting "Sophos Anti-Virus update"...
    juin 28 10:05:51 debian systemd[1]: Started "Sophos Anti-Virus update".
    root@debian:/opt/sophos-av/bin#

Unfiltered HTML