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.

problem with /scripts/ucpc --force

Discussion in 'General Discussion' started by eigh, Jan 19, 2006.

  1. eigh

    eigh Member

    Joined:
    Jul 25, 2005
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    1
    I'm trying to get a dnsonly cpanel server up and running so I can do clustering with my existing cpanel server.

    As per the suggestion of a post elsewhere on this forum, I have to run /scripts/ucpc --force.

    When I do this, however, the script outputs a series of 7 periods and then a newline over and over and over. Its been going on for approx 5 hours now with no change... so my screen looks like this:

    .......
    .......
    .......
    .......
    .......
    .......
    .......
    .......
    etc...

    I ran TOP to see what was going on in the background, and a process called realperlinstall is taking up 99% of the CPU.

    Does anyone have any suggestions as to how I can resolve this problem?

    Thanks,

    -- Jason
     
  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
    Issues with realperinstaller are mentioned here:
    http://forums.cpanel.net/showthread.php?t=48237

    You might be able to get away with just killing the perlinstaller process(es) and seeing if it continues OK. Otherwise, you're going to need to get perl up to v5.8.7 with the latest CPAN module (1.8.3 IIRC) before starting the cPanel installation.
     
  3. eigh

    eigh Member

    Joined:
    Jul 25, 2005
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    1
    next step . . .

    as soon as I killed the process, it outputted

    .......
    .....Done
    chkservdsetup-dnsonly........
    ........
    ........

    and continues to add different output... so that probably fixed the immediate problem.. I'll follow up on the forum later on if I get any other problems.

    -- Jason
     
Loading...

Share This Page