Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 6 replies
  • Subscribers 8 subscribers
  • Views 5730 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

Need Help getting Updated past 9.309-3

nam2long

I can't update past 9.309-3 because Sophos updater only shows version 9.310-11 and every time I try to update I am told in the logs that 9.310-9 is required first. I keep trying to upload this but it always shows the 9.310-11. I have SSH'ed into /var/up2date/sys and cleared everything redoing the upload process and every time this 9.310-11 shows up. I have tried a factory reset and doing an auto update but I can't do that due to lack of disk space. I figured I would just keep updating in batches but I am stuck on 9.309-3.

I have included the up2date log below:

2018:07:22-11:58:14 PONYBOY auisys[9231]: [INFO-301] New Firmware Up2Date is ready for installation
2018:07:22-11:58:36 PONYBOY auisys[9231]: Up2Date Package Installer finished, exiting
2018:07:22-11:58:36 PONYBOY auisys[9231]: id="3716" severity="info" sys="system" sub="up2date" name="Up2Date Package Installer finished, exiting"
2018:07:22-11:59:10 PONYBOY auisys[9426]: no HA system or cluster node
2018:07:22-11:59:10 PONYBOY auisys[9426]: waiting for db_verify to return (30 seconds max)
2018:07:22-11:59:12 PONYBOY auisys[9426]: removing '/var/up2date/aptp-install'
2018:07:22-11:59:12 PONYBOY auisys[9426]: removing '/var/up2date/avira3-install'
2018:07:22-11:59:12 PONYBOY auisys[9426]: removing '/var/up2date/cadata-install'
2018:07:22-11:59:12 PONYBOY auisys[9426]: removing '/var/up2date/geoip-install'
2018:07:22-11:59:12 PONYBOY auisys[9426]: removing '/var/up2date/ipsbundle-install'
2018:07:22-11:59:12 PONYBOY auisys[9426]: removing '/var/up2date/man9-install'
2018:07:22-11:59:12 PONYBOY auisys[9426]: removing '/var/up2date/ohelp9-install'
2018:07:22-11:59:12 PONYBOY auisys[9426]: removing '/var/up2date/sys-install'
2018:07:22-11:59:12 PONYBOY auisys[9426]: Starting Up2Date Package Installer
2018:07:22-11:59:12 PONYBOY auisys[9426]: Install u2d packages <sys>
2018:07:22-11:59:12 PONYBOY auisys[9426]: Starting installing up2date packages for type 'sys'
2018:07:22-11:59:12 PONYBOY auisys[9426]: Installing up2date package: /var/up2date/sys/u2d-sys-9.310009-310011.tgz.gpg
2018:07:22-11:59:12 PONYBOY auisys[9426]: Verifying up2date package signature
2018:07:22-11:59:12 PONYBOY auisys[9426]: Unpacking installation instructions
2018:07:22-11:59:12 PONYBOY auisys[9426]: parsing installation instructions
2018:07:22-11:59:12 PONYBOY auisys[9426]: >=========================================================================
2018:07:22-11:59:12 PONYBOY auisys[9426]: You are currently running Version 9.309003, but Version 9.310009 is required for this up2date package.
2018:07:22-11:59:12 PONYBOY auisys[9426]:
2018:07:22-11:59:12 PONYBOY auisys[9426]: 1. Modules::Logging::msg:46() /</sbin/auisys.plx>Modules/Logging.pm
2018:07:22-11:59:12 PONYBOY auisys[9426]: 2. Modules::Auisys::Installer::Systemstep::install:149() /</sbin/auisys.plx>Modules/Auisys/Installer/Systemstep.pm
2018:07:22-11:59:12 PONYBOY auisys[9426]: 3. Modules::Auisys::Up2DatePackages::install:143() /</sbin/auisys.plx>Modules/Auisys/Up2DatePackages.pm
2018:07:22-11:59:12 PONYBOY auisys[9426]: 4. Modules::Auisys::QueueIterator::process_qfiles:81() /</sbin/auisys.plx>Modules/Auisys/QueueIterator.pm
2018:07:22-11:59:12 PONYBOY auisys[9426]: 5. main::main:300() auisys.pl
2018:07:22-11:59:12 PONYBOY auisys[9426]: 6. main::top-level:35() auisys.pl
2018:07:22-11:59:12 PONYBOY auisys[9426]: |=========================================================================
2018:07:22-11:59:12 PONYBOY auisys[9426]: id="371J" severity="error" sys="system" sub="up2date" name="Fatal: Version conflict: required version: 9.310009 <=> current version: 9.309003" status="failed" action="install" package="sys"
2018:07:22-11:59:12 PONYBOY auisys[9426]:
2018:07:22-11:59:12 PONYBOY auisys[9426]: 1. Modules::Logging::alf:100() /</sbin/auisys.plx>Modules/Logging.pm
2018:07:22-11:59:12 PONYBOY auisys[9426]: 2. Modules::Auisys::Installer::Systemstep::install:152() /</sbin/auisys.plx>Modules/Auisys/Installer/Systemstep.pm
2018:07:22-11:59:12 PONYBOY auisys[9426]: 3. Modules::Auisys::Up2DatePackages::install:143() /</sbin/auisys.plx>Modules/Auisys/Up2DatePackages.pm
2018:07:22-11:59:12 PONYBOY auisys[9426]: 4. Modules::Auisys::QueueIterator::process_qfiles:81() /</sbin/auisys.plx>Modules/Auisys/QueueIterator.pm
2018:07:22-11:59:12 PONYBOY auisys[9426]: 5. main::main:300() auisys.pl
2018:07:22-11:59:12 PONYBOY auisys[9426]: 6. main::top-level:35() auisys.pl
2018:07:22-11:59:12 PONYBOY auisys[9426]: [CRIT-311] Firmware Up2Date installation failed
2018:07:22-11:59:33 PONYBOY auisys[9426]: |=========================================================================
2018:07:22-11:59:33 PONYBOY auisys[9426]: A serious error occured during installation! (20)
2018:07:22-11:59:33 PONYBOY auisys[9426]:
2018:07:22-11:59:33 PONYBOY auisys[9426]: 1. Modules::Logging::msg:46() /</sbin/auisys.plx>Modules/Logging.pm
2018:07:22-11:59:33 PONYBOY auisys[9426]: 2. main::main:310() auisys.pl
2018:07:22-11:59:33 PONYBOY auisys[9426]: 3. main::top-level:35() auisys.pl

 

 

P.S I changed the hostname in the logs to PONYBOY cause it popped in my head first lol



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

    I tried to upgrade from 9.408 to 9.506 in one evening.  Ran into trouble when one of the updates crashed midstream.   The two-factor commit that is supposed to guarantee clean updates did not work for my particular failure.  I called Support in a panic.   They assured me that the best move was the following:

    • Save a backup of the configuration to your PC.
    • Rebuild from the 9.506 CD.
    • Import the configuration backup from your PC.

    I was a nervous wreck when I started, but it worked beautifully.  Configurations are designed to be upward compatible, and mine was. 

    I saved a lot of time over applying each update sequentially, and I eliminated all of the internal clutter associated with all of those intermediate updates, so I have more disk space.   

    Choosing versions:

    I have great hope for 9.510, but it is very new.   If you do not target that version, I would recommend:  9.506, 9.408, or something earlier in the 9.4x sequence.   Hopefully the 9.506 CD is still available for download.

     

  • 0 in reply to DouglasFoster

    Indeed the configuration backups work very well.  Even when restored to different hardware. Two catches. 

    1) None of the log files are saved.  Not important in a home environment, but could be in a business where records need to be kept for x amount of time.
    2) Interfaces may get mapped differently on different hardware.

    I run my utm virtualized so migrating to new hardware involved making a backup of the VM (veeam worked very well for this), then restoring it to host on the new pc.

    I had to play around a bit with the vm's pci assignments to get the nic mapping to my satisfaction.  I'm of the mindset, the first physical port (quad port card) should be wan, not lan!@#).  After all was said and done I essentially had my old install in its entirety on the new host. To boot, the new host is faster/more powerful so I can enable more security features like full https scanning with dual engines.  The ui is snappier too.

    Old hardware i5 5250u (dual core with ht), new hardware i5 6500 (true quad core, slightly faster ghz too iirc). 4GB of ram allocated in both.

    Typical power consumption (per killawat meter) is around 20-25 watts on this dell optiplex 7040 sff.  Not bad, the old box was around 15 watts.

    The whole networking gear is around 40 watts (includes the pc, a 5 port dumb switch, netgear r7000 for wifi AP, obi200, and the ONT (fiber<>ethernet converter).  Note there's no gateway - it's only used briefly to authenticate the ONT then removed from use.

Reply
  • 0 in reply to DouglasFoster

    Indeed the configuration backups work very well.  Even when restored to different hardware. Two catches. 

    1) None of the log files are saved.  Not important in a home environment, but could be in a business where records need to be kept for x amount of time.
    2) Interfaces may get mapped differently on different hardware.

    I run my utm virtualized so migrating to new hardware involved making a backup of the VM (veeam worked very well for this), then restoring it to host on the new pc.

    I had to play around a bit with the vm's pci assignments to get the nic mapping to my satisfaction.  I'm of the mindset, the first physical port (quad port card) should be wan, not lan!@#).  After all was said and done I essentially had my old install in its entirety on the new host. To boot, the new host is faster/more powerful so I can enable more security features like full https scanning with dual engines.  The ui is snappier too.

    Old hardware i5 5250u (dual core with ht), new hardware i5 6500 (true quad core, slightly faster ghz too iirc). 4GB of ram allocated in both.

    Typical power consumption (per killawat meter) is around 20-25 watts on this dell optiplex 7040 sff.  Not bad, the old box was around 15 watts.

    The whole networking gear is around 40 watts (includes the pc, a 5 port dumb switch, netgear r7000 for wifi AP, obi200, and the ONT (fiber<>ethernet converter).  Note there's no gateway - it's only used briefly to authenticate the ONT then removed from use.

Children
No Data
Unfiltered HTML