Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 3 subscribers
  • Views 1429 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 Time Out

tony21
I have Astaro 1.811 installed, and when i try to run Up2date i got:
Malfunctioning gpg!
gpg with PID 20257 has been running for more then 5 minutes.
Killing PID 20257...

The problem is that the download can't be completed in just 5 minutes, it need more time.

Please advice it there's something i can do with this or i should download Astaro 1.920, and if so, my backup of the settings of the 1.811 will work with newer versions?

Thank You!


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

    this is a known Problem in 1.811.
    Type as "root" "touch /etc/no-superdaemon/gpg" and start up2date again.
    It happens if ASL has only small bandwidth
    during the update process.
    read you
    o|iver
  • 0 in reply to oliver.desch
    Running an evaluation of 1.811.  When I try to run up2date I see:

     
    Up2Date Service
    Wed Aug 1 15:53:42 /etc/localtime 2001
    000 Getting update list from server 128.242.218.125, port 222...

    and then, after about five minutes I see:

     
    This is a Error. You should not be here ....
    Please retry the operation and contact your vendor
    Wrong SID check!
     

    Note: I did "touch /etc/no-superdaemon/gpg" as recommended in the previous message, but it did not change the symptoms.

    Sakshale
  • 0 in reply to sakshale
    Some followup information, which may bare on the problem.  The test system is suprisingly loaded down... The CPU Utilization graph is pegged!


    cpu MHz         : 166
    bogomips        : 330.95
     
    argos:/proc # cat loadavg
    1.95 1.85 1.82 2/56 16933
    argos:/proc #

    MemTotal:        95148 kB
    MemFree:         14472 kB
    SwapTotal:      128516 kB
    SwapFree:       119060 kB

    The hogg appears to be the qmail program.
Reply
  • 0 in reply to sakshale
    Some followup information, which may bare on the problem.  The test system is suprisingly loaded down... The CPU Utilization graph is pegged!


    cpu MHz         : 166
    bogomips        : 330.95
     
    argos:/proc # cat loadavg
    1.95 1.85 1.82 2/56 16933
    argos:/proc #

    MemTotal:        95148 kB
    MemFree:         14472 kB
    SwapTotal:      128516 kB
    SwapFree:       119060 kB

    The hogg appears to be the qmail program.
Children
Unfiltered HTML