Skip to main content

Some errors and problems I have received in whm

Comments

8 comments

  • cPRex Jurassic Moderator
    Hello! Can you let us know what the database transfer errors were inside the Transfer Tool when you first moved the account? That could be the key to the problem.
    0
  • erdinckoc
    Hello! Can you let us know what the database transfer errors were inside the Transfer Tool when you first moved the account? That could be the key to the problem. [/ALINTI] Starting "TRANSFER" for "Account" "xxxx". Copy Destination: /home Remote server type: "WHM1164". Initiating a remote API (Application Programming Interface) connection in order to package the account in a background process " The system failed to initiate a remote background package account due to an error: pass, accesshash, or api_token is a required parameter at /usr/local/cpanel/3rdparty/perl/532/lib/perl5/cpanel_lib/cPanel/PublicAPI.pm line 139. cPanel::PublicAPI::new("cPanel::PublicAPI", "user", "root", "accesshash", undef, "usessl", 1, "ssl_verify_mode", ...) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Items/AccountRemoteRoot.pm line 542 Whostmgr::Transfers::Session::Items::AccountRemoteRoot::_run_whm_api(Whostmgr::Transfers::Session::Items::AccountRemoteRoot=HASH(0x3e59370), "start_background_pkgacct", HASH(0x3d9a3e8)) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Items/AccountRemoteRoot.pm line 594 Whostmgr::Transfers::Session::Items::AccountRemoteRoot::_call_remote_background_pkgacct_with_internal_data(Whostmgr::Transfers::Session::Items::AccountRemoteRoot=HASH(0x3e59370)) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Items/AccountRemoteRoot.pm line 322 Whostmgr::Transfers::Session::Items::AccountRemoteRoot::__ANON__() called at /usr/local/cpanel/3rdparty/perl/532/lib/perl5/cpanel_lib/Try/Tiny.pm line 100 eval {...} called at /usr/local/cpanel/3rdparty/perl/532/lib/perl5/cpanel_lib/Try/Tiny.pm line 91 Try::Tiny::try(CODE(0x3d8fcb0), Try::Tiny::Catch=REF(0x3d8efa8)) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Items/AccountRemoteRoot.pm line 326 Whostmgr::Transfers::Session::Items::AccountRemoteRoot::_remote_background_pkgacct(Whostmgr::Transfers::Session::Items::AccountRemoteRoot=HASH(0x3e59370)) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Items/AccountRemoteRoot.pm line 288 Whostmgr::Transfers::Session::Items::AccountRemoteRoot::_remote_pkgacct_decision(Whostmgr::Transfers::Session::Items::AccountRemoteRoot=HASH(0x3e59370)) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Item.pm line 359 Whostmgr::Transfers::Session::Item::__ANON__() called at /usr/local/cpanel/3rdparty/perl/532/lib/perl5/cpanel_lib/Try/Tiny.pm line 100 eval {...} called at /usr/local/cpanel/3rdparty/perl/532/lib/perl5/cpanel_lib/Try/Tiny.pm line 91 Try::Tiny::try(CODE(0x3e5a300), Try::Tiny::Catch=REF(0x3e59790)) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Item.pm line 388 Whostmgr::Transfers::Session::Item::exec_path(Whostmgr::Transfers::Session::Items::AccountRemoteRoot=HASH(0x3e59370), ARRAY(0x3eee368), ARRAY(0x3e5a270), 1) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Items/AccountRemoteRoot.pm line 186 Whostmgr::Transfers::Session::Items::AccountRemoteRoot::transfer(Whostmgr::Transfers::Session::Items::AccountRemoteRoot=HASH(0x3e59370)) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Processor.pm line 658 Whostmgr::Transfers::Session::Processor::__ANON__() called at /usr/local/cpanel/Whostmgr/Transfers/Session.pm line 1484 Whostmgr::Transfers::Session::__ANON__() called at /usr/local/cpanel/3rdparty/perl/532/lib/perl5/cpanel_lib/Try/Tiny.pm line 100 eval {...} called at /usr/local/cpanel/3rdparty/perl/532/lib/perl5/cpanel_lib/Try/Tiny.pm line 91 Try::Tiny::try(CODE(0x3eee260), Try::Tiny::Catch=REF(0x3eee428)) called at /usr/local/cpanel/Whostmgr/Transfers/Session.pm line 1488 Whostmgr::Transfers::Session::exec_with_output_directed_to_fh(Whostmgr::Transfers::Session=HASH(0x3cfb010), GLOB(0x3eee5a8), CODE(0x3eee4b8)) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Processor.pm line 674 Whostmgr::Transfers::Session::Processor::_process_dequeued_item(Whostmgr::Transfers::Session::Processor=HASH(0x3da59c0)) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Processor.pm line 554 Whostmgr::Transfers::Session::Processor::_process_items(Whostmgr::Transfers::Session::Processor=HASH(0x3da59c0)) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Processor.pm line 508 Whostmgr::Transfers::Session::Processor::__ANON__() called at /usr/local/cpanel/Cpanel/ForkAsync.pm line 68 eval {...} called at /usr/local/cpanel/Cpanel/ForkAsync.pm line 68 Cpanel::ForkAsync::do_in_child(CODE(0x3d4fdd8)) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Processor.pm line 510 Whostmgr::Transfers::Session::Processor::_spawn_child(Whostmgr::Transfers::Session::Processor=HASH(0x3da59c0), 1, Whostmgr::Transfers::Session=HASH(0x3cfb010)) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Processor.pm line 292 Whostmgr::Transfers::Session::Processor::_process_child(Whostmgr::Transfers::Session::Processor=HASH(0x3da59c0), Whostmgr::Transfers::Session=HASH(0x3cfb010), 0) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Processor.pm line 240 Whostmgr::Transfers::Session::Processor::_process_child_with_output_redirection(Whostmgr::Transfers::Session::Processor=HASH(0x3da59c0), Whostmgr::Transfers::Session=HASH(0x3cfb010), 0, "xxxxcopya20220120230218v7N") called at /usr/local/cpanel/Whostmgr/Transfers/Session/Processor.pm line 205 Whostmgr::Transfers::Session::Processor::__ANON__() called at /usr/local/cpanel/Cpanel/ForkAsync.pm line 68 eval {...} called at /usr/local/cpanel/Cpanel/ForkAsync.pm line 68 Cpanel::ForkAsync::do_in_child(CODE(0x3d78348)) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Processor.pm line 207 Whostmgr::Transfers::Session::Processor::start(Whostmgr::Transfers::Session::Processor=HASH(0x3da59c0)) called at bin/start_transfer.pl line 57 main::__ANON__() called at /usr/local/cpanel/3rdparty/perl/532/lib/perl5/cpanel_lib/Try/Tiny.pm line 100 eval {...} called at /usr/local/cpanel/3rdparty/perl/532/lib/perl5/cpanel_lib/Try/Tiny.pm line 91 Try::Tiny::try(CODE(0x3cfae30), Try::Tiny::Catch=REF(0x1f5baa0)) called at bin/start_transfer.pl line 72

    0
  • cPRex Jurassic Moderator
    Thanks for that information. To me, that just looks like the transfer failed in general. I would recommend running this command on the Source machine: /scripts/pkgacct username
    where "username" is the cPanel account username, and seeing what the errors are on the Source server directly. Once that is resolved you can try to transfer the account again.
    0
  • erdinckoc
    Thanks for that information. To me, that just looks like the transfer failed in general. I would recommend running this command on the Source machine: /scripts/pkgacct username
    where "username" is the cPanel account username, and seeing what the errors are on the Source server directly. Once that is resolved you can try to transfer the account again.

    On the target server before writing to you for i in $(ls /var/cpanel/users); do /scripts/pkgacct $i;i took a backup on the server with the help of the done command and transferred it to another server and opened it, I can perform the transfer without problems, but why do I get an error with the whm tools tool, although I have tried many times, the whm to whm tool does not transfer mysql users.
    0
  • erdinckoc
    In addition, how can I collectively change the nameserver records of users belonging to two resellers I need such a command the nameserver records of the domains I move are in the cpanel ns1.cprapid.com it looks like it.
    0
  • cPRex Jurassic Moderator
    We would likely need a ticket opened with a support team to investigate this more, as we would need to see the issue on the server. Could you create a support ticket and then post the number here?
    0
  • erdinckoc
    how can I change other batch nameserver records.
    0
  • cPRex Jurassic Moderator
    There aren't any tools to make a mass update of values inside the DNS zones. You would either need to do them one at a time or create a custom script to make that change.
    0

Please sign in to leave a comment.