The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

up2date not working

Discussion in 'General Discussion' started by Tagor, Nov 8, 2004.

  1. Tagor

    Tagor Well-Known Member

    Joined:
    Mar 6, 2004
    Messages:
    193
    Likes Received:
    0
    Trophy Points:
    16
    I am trying to run up2date -u from the command line. However after pressing <enter> it doesn't do anything. Now I received this log by mail. Can someone tell me how to fix this?

    --------------------- up2date Begin ------------------------



    **Unmatched Entries**
    [Sun Nov 7 10:41:40 2004] up2date updating login info
    [Sun Nov 7 10:41:40 2004] up2date logging into up2date server
    [Sun Nov 7 10:42:25 2004] up2date A socket error occurred: (110, 'Connection timed out'), attempt #1
    [Sun Nov 7 10:42:37 2004] up2date A socket error occurred: (4, 'Interrupted system call'), attempt #2
    [Sun Nov 7 10:42:46 2004] up2date A socket error occurred: (4, 'Interrupted system call'), attempt #3
    [Sun Nov 7 10:42:57 2004] up2date updating login info
    [Sun Nov 7 10:42:57 2004] up2date logging into up2date server
    [Sun Nov 7 10:42:59 2004] up2date A socket error occurred: (4, 'Interrupted system call'), attempt #1
    [Sun Nov 7 10:43:36 2004] up2date A socket error occurred: (110, 'Connection timed out'), attempt #4
    [Sun Nov 7 10:43:47 2004] up2date A socket error occurred: (110, 'Connection timed out'), attempt #2
    [Sun Nov 7 10:44:26 2004] up2date A socket error occurred: (110, 'Connection timed out'), attempt #5
    [Sun Nov 7 10:44:26 2004] up2date Error communicating with server. The message was:
    Connection timed out
    [Sun Nov 7 10:44:37 2004] up2date A socket error occurred: (110, 'Connection timed out'), attempt #3
    [Sun Nov 7 10:45:27 2004] up2date A socket error occurred: (110, 'Connection timed out'), attempt #4
    [Sun Nov 7 10:46:18 2004] up2date A socket error occurred: (110, 'Connection timed out'), attempt #5
    [Sun Nov 7 10:46:18 2004] up2date Error communicating with server. The message was:
    Connection timed out
    [Sun Nov 7 10:54:23 2004] up2date updating login info
    [Sun Nov 7 10:54:23 2004] up2date logging into up2date server
    [Sun Nov 7 10:55:08 2004] up2date A socket error occurred: (110, 'Connection timed out'), attempt #1
    [Sun Nov 7 10:55:16 2004] up2date A socket error occurred: (4, 'Interrupted system call'), attempt #2
    [Sun Nov 7 10:56:05 2004] up2date A socket error occurred: (110, 'Connection timed out'), attempt #3
    [Sun Nov 7 10:56:55 2004] up2date A socket error occurred: (110, 'Connection timed out'), attempt #4
    [Sun Nov 7 10:56:57 2004] up2date updating login info
    [Sun Nov 7 10:56:57 2004] up2date logging into up2date server
    [Sun Nov 7 10:57:42 2004] up2date A socket error occurred: (110, 'Connection timed out'), attempt #1
    [Sun Nov 7 10:57:45 2004] up2date A socket error occurred: (110, 'Connection timed out'), attempt #5
    [Sun Nov 7 10:57:45 2004] up2date Error communicating with server. The message was:
    Connection timed out
    [Sun Nov 7 10:58:32 2004] up2date A socket error occurred: (110, 'Connection timed out'), attempt #2
    [Sun Nov 7 10:59:11 2004] up2date A socket error occurred: (4, 'Interrupted system call'), attempt #3
    [Sun Nov 7 11:00:01 2004] up2date A socket error occurred: (110, 'Connection timed out'), attempt #4
    [Sun Nov 7 11:00:51 2004] up2date A socket error occurred: (110, 'Connection timed out'), attempt #5
    [Sun Nov 7 11:00:51 2004] up2date Error communicating with server. The message was:
    Connection timed out


    ---------------------- up2date End -------------------------
     
  2. chirpy

    chirpy Well-Known Member

    Joined:
    Jun 15, 2002
    Messages:
    13,475
    Likes Received:
    20
    Trophy Points:
    38
    Location:
    Go on, have a guess
    Could be a number of things related to RHN:

    1. Have you blocked outgoing ports 80 or 443 from the server?
    2. If not, it could be a temporary problem that may go away if you've only got this once
    3. You may have a locked rpm database - this is most simply cured by a reboot (there are other ways, but that should do it)
    4. There's a RHN subscription problem and you'll need to speack with your server provider if they provided your operating system for you.
     
Loading...

Share This Page