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.

Update fails with exit code 65200

Discussion in 'General Discussion' started by reltringham, May 7, 2013.

  1. reltringham

    reltringham Member

    Joined:
    Feb 16, 2005
    Messages:
    6
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    Auckland, New Zealand
    I ran the script /scripts/upcp to update CPanel/WHM, and it failed with exit code 65200. This problem happens every time that I have run /scripts/upcp yesterday and today, at different times of the day. Searching for the exit code in these forums, and the Internet in general, have not provided solutions beyond checking settings that are already in place and apparently correct.

    Terminal output of /scripts/upcp is:
    Code:
    [20130508.145935]   Detected cron=0 (Terminal detected)
    ----------------------------------------------------------------------------------------------------
    => Log opened from /scripts/upcp at Wed May  8 14:59:35 2013
    [20130508.145935]   Detected cron=0 (Terminal detected)
    [20130508.145935]   mtime on upcp is 1346772792 (Wed Sep  5 03:33:12 2012)
    => Log closed Wed May  8 14:59:35 2013
    ----------------------------------------------------------------------------------------------------
    => Log opened from /usr/local/cpanel/scripts/updatenow at Wed May  8 14:59:35 2013
    [20130508.145935]   Detected version '11.32.4.15' from version file.
    => Log closed Wed May  8 15:01:37 2013
    [20130508.150137] E Running `/usr/local/cpanel/scripts/updatenow --upcp --log=/var/cpanel/updatelogs/update.1367981975.log` failed, exited with code 65280
    => Log closed Wed May  8 15:01:37 2013
    Contents of /var/cpanel/updatelogs/update.1367886201.log:

    Code:
    ----------------------------------------------------------------------------------------------------
    => Log opened from /scripts/upcp at Wed May  8 14:59:35 2013
    [20130508.145935]   Detected cron=0 (Terminal detected)
    [20130508.145935]   mtime on upcp is 1346772792 (Wed Sep  5 03:33:12 2012)
    => Log closed Wed May  8 14:59:35 2013
    ----------------------------------------------------------------------------------------------------
    => Log opened from /usr/local/cpanel/scripts/updatenow at Wed May  8 14:59:35 2013
    [20130508.145935]   Detected version '11.32.4.15' from version file.
    => Log closed Wed May  8 15:01:37 2013
    [20130508.150137] E Running `/usr/local/cpanel/scripts/updatenow --upcp --log=/var/cpanel/updatelogs/update.1367981975.log` failed, exited with code 65280
    => Log closed Wed May  8 15:01:37 2013
    Current software versions (from WHM):
    WHM 11.32.4 (build 15)
    CENTOS 5.8 x86_64

    Any ideas?

    --
    Richard.
     
    #1 reltringham, May 7, 2013
    Last edited: May 7, 2013
  2. cPanelNick

    cPanelNick Administrator
    Staff Member

    Joined:
    Mar 9, 2015
    Messages:
    3,426
    Likes Received:
    2
    Trophy Points:
    38
    cPanel Access Level:
    DataCenter Provider
    Please open a ticket using the link in my signature.
     
  3. reltringham

    reltringham Member

    Joined:
    Feb 16, 2005
    Messages:
    6
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    Auckland, New Zealand
    I've created ticket #4089755

    Thanks for your reply, Nick.

    --
    Richard.
     
  4. reltringham

    reltringham Member

    Joined:
    Feb 16, 2005
    Messages:
    6
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    Auckland, New Zealand
    In case anyone else has a similar problem: DNS was incorrectly resolving external domains, in particular cpanel.net.
     
  5. Infopro

    Infopro cPanel Sr. Product Evangelist
    Staff Member

    Joined:
    May 20, 2003
    Messages:
    14,478
    Likes Received:
    203
    Trophy Points:
    63
    Location:
    Pennsylvania
    cPanel Access Level:
    Root Administrator
    Twitter:
    Thanks for updating the thread, Richard. :)
     
Loading...

Share This Page