Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 2 subscribers
  • Views 498 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 fails from 5.004 -> 5.005

BarryG
After updating to 5.004 (from 5.001), I am now unable to update to 5.005:

Code:
Up2Date Service
Thu May 27 21:36:40 PDT 2004

000 Running Version: 5.004
001 System Up2Date: Started installation upto 5.005
002 Searching for update from 5.004 to 5.005 or higher
003 Verifying signature and decrypt (v 5.005) for //var/up2date/5.005.tar.gpg
004 Pre-Stop-Scripting ...
005 Started /var/up2date/5.005/rebooter in pre_stop mode
006 Ok
007 :: Stopping Self Monitor NG..done
008 :: Stopping MiddleWare..done
009 :: Stopping ConfDaemon..done
010 Ok
011 Post-Stop-Scripting ... Nothing to do
012 Starting Installer ...
013 Pre-Start-Scripting ... Nothing to do
014 System Up2Date failed: Error occured while running installer
015 Didnt dumpSystem Up2Date failed: Installer stopped due to internal error
016 System Up2Date: New System Up2Dates installed
017 no Up2date Packages installed.
Done


It then reboots, but is still 5.004.

I've tried several times, including shutting off all proxy services.

System is PII-500, 192MB RAM, 10GB disk.

/var/log/up2date.log:
Code:
2004:05:27-21:47:39 (none) ainstall[2071]: System Up2Date: Started installation upto 5.005
2004:05:27-21:48:21 (none) ainstall[2071]: astaro::logging:checkParameters() required parameters 'MESSSAGE' missing for logitem 'CRIT-345'
2004:05:27-21:48:21 (none) ainstall[2071]: System Up2Date failed: Installer stopped due to internal error 
2004:05:27-21:48:22 (none) ainstall[2071]: System Up2Date: New System Up2Dates installed


Code:
# df -h
Filesystem            Size  Used Avail Use% Mounted on
rootfs                595M  300M  265M  54% /
/dev/root             595M  300M  265M  54% /
tmpfs                  32M 1012K   32M   4% /opt/tmpfs
/dev/hda1             342M   15M  310M   5% /boot
/dev/hda5             2.5G  207M  2.2G   9% /var/storage
/dev/hda6             342M  267M   58M  83% /var/up2date
/dev/hda8             388M  226M  143M  62% /var/sec
/dev/hda9             3.4G   39M  3.2G   2% /var/log
/dev/hda10            312M  8.1M  288M   3% /tmp
none                   94M     0   94M   0% /var/shm



Thanks,
Barry


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

    This is a known issue, and is been fixed in 5.006.

    Download the update, and do the update manually.

    Max
  • 0 in reply to Max_Nilsen
    You mean d/l 5.006, and import it in thru the browser, and install it?

    Tried that... it still tried to load 5.005,
    so I tried deleting 5.005:
    rm -rf /var/up2date/5.001*

    and tried 5.006 again:
    Code:
    Up2Date Service
    Fri May 28 21:34:19 PDT 2004

    000 Running Version: 5.004
    001 System Up2Date: Started installation upto 5.006
    002 Searching for update from 5.004 to 5.005 or higher
    003 Verifying signature and decrypt (v 5.006) for //var/up2date/5.006.tar.gpg
    004 Your running Version 5.004 is not equal to the expected Version: 5.005
    005 Please download Version 5.005 first!
Reply
  • 0 in reply to Max_Nilsen
    You mean d/l 5.006, and import it in thru the browser, and install it?

    Tried that... it still tried to load 5.005,
    so I tried deleting 5.005:
    rm -rf /var/up2date/5.001*

    and tried 5.006 again:
    Code:
    Up2Date Service
    Fri May 28 21:34:19 PDT 2004

    000 Running Version: 5.004
    001 System Up2Date: Started installation upto 5.006
    002 Searching for update from 5.004 to 5.005 or higher
    003 Verifying signature and decrypt (v 5.006) for //var/up2date/5.006.tar.gpg
    004 Your running Version 5.004 is not equal to the expected Version: 5.005
    005 Please download Version 5.005 first!
Children
Cookie Information Banner