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

Update 7.202 -> 7.300 failed

DHeinze
Hi!

A customer form us can not update his ASG120 via Frontend, everytime the same error "Up2date failed" or something else. 

i tested "auisys.plx --rpmargs --force" in the console, but the kernel package failed:

Executing script hook : exec /var/up2date//sys-install/u2d-sys-7.300/./run_mail_convert_preinst_2 OK
    Running service script: /etc/init.d/mdw stop                               OK
    Installing rpm package: perl-MLDBM-2.01-185.2.i686.rpm              OK
    Installing rpm package: tcpdump-3.9.8-2.i686.rpm                       OK
    Installing rpm package: hwinfo-12.34-0.2.7.i686.rpm                    OK
    Installing rpm package: kernel-default-2.6.16.60-77.i686.rpm         Failed!
    Installing rpm package: libgpg-error-1.6-3.i686.rpm                      OK
    Installing rpm package: libgcrypt-1.4.0-13.2.1.i686.rpm                OK
    Installing rpm package: gmime-2.3.4-20.i686.rpm                         OK
    Installing rpm package: libevent-1.1-15.i686.rpm                           OK
    Installing rpm package: postgresql-8.3.3-9.i686.rpm                        OK
    Installing rpm package: perl-DBD-Pg-1.49-2.3.i686.rpm                      OK
    Installing rpm package: ulogd-2.0.0-16.i686.rpm                            OK

any idears what to do?

mfg Daniel Heinze


This thread was automatically locked due to age.
  • 0 in reply to NevesNET
    This helped me too.  I was stuck on 7.202 with installation pre-check failures in the up2date.log file.  The command line got me running up 7.304.

    Thanks,
    Paul.
  • 0 in reply to Rainer Wider

    I logged in as root and entered following command:
    auisys.plx --rpmargs --force

    This command installed first 7.300 and then 7.301.
    No Errors - and everything works [:)]
    But take care - it depends from the error you got before.


    Followed that advice; received email that 7.300 was successfully installed, but the ASG locked up (hard!) while trying to unpack 7.301. I will have to wait until I get home in a few hours to check the console and see if I simply need to soft reboot it (telinit 6) or if it's down "hard" and will need to be power cycled.
  • 0 in reply to MillardJK
    I just checked one of the ASGs that I support (not my personal unit) and it also fails to upgrade from 7.202 to 7.3x

    A little research, and I've discovered that up2date never downloaded the 7.300 package (look in /var/up2date/sys). Further, I can see it downloading right now, but in the last hour of downloading, it has retrieved less than 10% of the total package (>200MB).

    I'm going to d/l the package locally, then push it up manually and see if that'll make it run faster.
  • 0 in reply to MillardJK
    No joy. I keep getting an error while trying to install the7.300 kernel update for 7.202: 
    Installing rpm package: kernel-default-2.6.16.60-77.i686.rpm               Failed!


    Looks like I'll have to open a support case (on Monday).
  • 0 in reply to MillardJK
    Hi Jim,

    Have you tried rebooting the ASG before performing the update?  Also, are you running the force command (auisys.plx --rpmargs --force) from SSH, or are you using WebAdmin?
  • 0 in reply to Jack Daniel
    Have you tried rebooting the ASG before performing the update?
    Thanks; that suggestion tipped the scale. I'm now successsfuly at 7.305.
    Also, are you running the force command (auisys.plx --rpmargs --force) from SSH, or are you using WebAdmin?
    Based on my lack of results with WebAdmin on my personal unit, I didn't even try that. The force command did the trick. I also disabled unneeded services (PPTP, L2TP access) prior to rebooting so it would come up as clean as possible (in terms of memory utilization); this may have also contributed to success.
Cookie Information Banner