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

Up2date Install 7.403 fails

Buggrit
I logged on to a domestic customer's unit this morning and found that it had stopped updating at 7.402 and was failing at 7.403. I started the update again and again it failed.

So having read the forums here I've tried SSH login to ROOT to run the "auisys.plx --rpmargs --force" but although that looks like it is getting there, it too fails at the line: "testing install packages: ep-chproot-pop3-7.4.111.i686.rpm"

Is it possible to flush the update distribution folder and start the download of 7.403 again?  If it is possible, how would one go about doing that and where is the folder?

Is there any other way to get the updates past this point?

your help would be most appreciated.


This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to Buggrit
    I'm now manually forcing the re-download of the packages back to that folder using the command:
    wget ftp://ftp.astaro.de/pub/ASG/v7/up2date/u2d-sys-7.403.tgz.gpg

    And will do the same for the other deleted packages.

    Will post back with results....
  • 0 in reply to Buggrit
    Right... The download of 7.403 succeeded. I then ran auisys.plx but the install failed again at:
    "Testing install package: ep-chroot-pop3-7.4-111.i686.rpm                   Failed!"

    I notice that the other packages have now also re-downloaded (7.404 - 7.501)

    What can I do to get past 7.403??? Any help would be greatly appreciated.

    Thanks in advance.

    JB

    P.S. Just a thought but I'm going to switch off the POP3 Proxy and see if that makes a difference...?
  • 0 in reply to Buggrit
    latest...
    I switched off the POP3 Proxy and did a forced install from the SSH CLI (ausys.plx --rpmargs --force) but again it failed at:
    " Testing install package: ep-chroot-pop3-7.4-111.i686.rpm                Failed!"

    I really am at my wits-end now.  Any suggestions would be good right now...

    JB
  • 0 in reply to Buggrit
    I'd start a support case with Astaro.  I've seen this sort of thing happen before when, sometime in the past, Support installed a debug or test version of  a module to solve a problem, and somehow future updates would not replace that module.  Normally the command line you've been using does the job.

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

Cookie Information Banner