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.

a fatal error or timeout occurred while processing this directive

Discussion in 'General Discussion' started by brendanrtg, Oct 8, 2006.

  1. brendanrtg

    brendanrtg Well-Known Member

    Joined:
    Oct 4, 2006
    Messages:
    311
    Likes Received:
    0
    Trophy Points:
    16
    We need to move around 100 sites between 2 servers:

    WHM 10.8.0 cPanel 10.9.0-S38
    CentOS 4.4 i686 - WHM X v3.1.0

    However, when use use Copy Multiple Accounts, we get the following errors and no matter how we upgrade server software, system software, cpanel, we simply cannot resolve the problem:

    The errors are as follows:

    Packaging the account...
    pkgacct started.
    pkgacct version 4.2 - running with uid 0
    using time::hires for speedups
    We will be splitting the archive!!
    rdate: rdate: could not set system time: Operation not permitted
    Timeout ...
    [a fatal error or timeout occurred while processing this directive]Retrying....Packaging the account...
    pkgacct started.
    pkgacct version 4.2 - running with uid 0
    using time::hires for speedups
    We will be splitting the archive!!
    rdate: rdate: could not set system time: Operation not permitted


    Anyone with the same problem and have already sorted this out?
     
  2. AndyReed

    AndyReed Well-Known Member
    PartnerNOC

    Joined:
    May 29, 2004
    Messages:
    2,222
    Likes Received:
    3
    Trophy Points:
    38
    Location:
    Minneapolis, MN
    Run this command on both servers:
    rdate -s rdate.darkorb.net
     
  3. brendanrtg

    brendanrtg Well-Known Member

    Joined:
    Oct 4, 2006
    Messages:
    311
    Likes Received:
    0
    Trophy Points:
    16
    No luck, I tried a few rdate sources, all returns:

    rdate: rdate: could not set system time: Operation not permitted
     
  4. AndyReed

    AndyReed Well-Known Member
    PartnerNOC

    Joined:
    May 29, 2004
    Messages:
    2,222
    Likes Received:
    3
    Trophy Points:
    38
    Location:
    Minneapolis, MN
    Is this a VPS? If yes, you're out of luck :eek:

    rdate can not work on a VPS, because VPS does not have the privilege to change/update the server clock/time. The best possible solution is to create a symlink to your Time Zone on your VPS. So, you'll have to ask your host to get the node time synced.
     
  5. brendanrtg

    brendanrtg Well-Known Member

    Joined:
    Oct 4, 2006
    Messages:
    311
    Likes Received:
    0
    Trophy Points:
    16
    Yes, both are VPS and we have copied sites over before even with the rdate being not permitted.

    Our problem is not the rdate but the "timeout errors", which have in the past never been an issue.

    Here's a more descriptive error:

    We will be splitting the archive!!
    rdate: rdate: could not set system time: Operation not permitted
    Timeout ...
    (internal death) Sun Oct 8 10:15:03 2006 [3497] error: Died at whostmgr/bin/whostmgr2.pl line 5308, line 7.
    main::__ANON__('ALRM') called at whostmgr/bin/whostmgr2.pl line 5319
    eval {...} called at whostmgr/bin/whostmgr2.pl line 5304
    main::sshsession('Packaging the account', 'password', '/scripts/pkgacct a108sun "" --split', 0, '/scripts/sshcontrol', '--ctl', 'ssh', '--user', ...) called at whostmgr/bin/whostmgr2.pl line 19864
    main::remoteexec('txt', 'Packaging the account', 'password', 'xxxxxx', 'user', 'root', 'port', 22, ...) called at whostmgr/bin/whostmgr2.pl line 3664
    main::copyacct() called at whostmgr/bin/whostmgr2.pl line 479
    [a fatal error or timeout occurred while processing this directive]Packaging the account...
     
    #5 brendanrtg, Oct 8, 2006
    Last edited: Oct 8, 2006
Loading...

Share This Page