Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 2 subscribers
  • Views 2266 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

savi up2date not working

BramKortleven
Due to http proxy restarting and the smtp proxy having issues with the antivirus (had to disable ALL antivirus scanning to have http and smtp proxy running) I was trying to update all engines, system and definitions, but am faced with the following when trying to do
auisys.plx --verbose[/QOUTE] 

The log tells me:
astaro:/home/login # auisys.plx --verbose
'verbose' mode implicits set noqueue option!
no HA system or cluster node
removing '/var/up2date/aptp-install'
removed directory: `/var/up2date/aptp-install'
removing '/var/up2date/avira3-install'
removed directory: `/var/up2date/avira3-install'
removing '/var/up2date/clvbrowser-install'
removed directory: `/var/up2date/clvbrowser-install'
removing '/var/up2date/geoip-install'
removed directory: `/var/up2date/geoip-install'
removing '/var/up2date/ipsbundle-install'
removed directory: `/var/up2date/ipsbundle-install'
removing '/var/up2date/man9-install'
removed directory: `/var/up2date/man9-install'
removing '/var/up2date/ohelp9-install'
removed directory: `/var/up2date/ohelp9-install'
removing '/var/up2date/savi-install'
removed directory: `/var/up2date/savi-install'
removing '/var/up2date/sys-install'
removed directory: `/var/up2date/sys-install'
Starting Up2Date Package Installer
No suitable packages of type  found, skipping
No suitable packages of type  found, skipping
No suitable packages of type  found, skipping
No suitable packages of type  found, skipping
No suitable packages of type  found, skipping
No suitable packages of type  found, skipping
No suitable packages of type  found, skipping
Install u2d packages 
Starting installing up2date packages for type 'aptp'
Installing up2date package: /var/up2date/aptp/u2d-aptp-9.4539.tgz.gpg
Verifying up2date package signature
Unpacking installation instructions
parsing installation instructions
Unpacking up2date package container
Running pre-installation checks
Package u2d-aptp-9-4539.i686.rpm is already installed, skipping
Starting up2date package installation
    Executing script hook : exec /usr/local/bin/patterndist aptp               OK
    Running syncing step 0                                                     OK
    Running syncing step 1                                                     OK
Install u2d packages 
Starting installing up2date packages for type 'savi'
Installing up2date package: /var/up2date/savi/u2d-savi-9.6386-6406.patch.tgz.gpg
Verifying up2date package signature
Unpacking installation instructions
parsing installation instructions
This is a patch. Setting required_version to 9.6386
You are currently running Version 9.6363, but Version 9.6386 is required for this up2date package.
A serious error occured during installation! (20)


running 
audld.plx
 only gives me
no HA system or cluster node
Starting Up2Date Package Downloader
patch up2date possible
Authenticating ...
Authentication successful!
Starting Up2Date Download
Starting sync mode for 'savi'
  Downloading Up2Date Package http://79.125.21.244/asg/v9/savi/u2d-savi-9.6386-6406.patch.tgz.gpg
    ++++++++++++   100% - 420535 bytes received
Fileset synchronous
Starting sync mode for 'aptp'
  Downloading Up2Date Package http://79.125.21.244/asg/v9/aptp/u2d-aptp-9.4539.tgz.gpg
    ++++++++++++++   100% - 2360690 bytes received
Fileset synchronous


Is there any command you can run to 'fake' the version of the savi signature, so it re-deploys the 9.6363 and higher updates?


This thread was automatically locked due to age.
Parents
  • 0
    Hi Bob,

    he ran 'su' instead of 'su -', which means he's root but the current directory doesn't get changed, etc.

    the '#' in the prompt indicates root.


    loginuser@fw:/home/login > su
    Password:
    fw:/home/login # id
    uid=0(root) gid=0(root) groups=0(root),890(xorp)
    fw:/home/login #


    Barry
Reply
  • 0
    Hi Bob,

    he ran 'su' instead of 'su -', which means he's root but the current directory doesn't get changed, etc.

    the '#' in the prompt indicates root.


    loginuser@fw:/home/login > su
    Password:
    fw:/home/login # id
    uid=0(root) gid=0(root) groups=0(root),890(xorp)
    fw:/home/login #


    Barry
Children
No Data
Share Feedback
×

Submitted a Tech Support Case lately from the Support Portal?

Unfiltered HTML