Skip to main content

Transfer Tool warnings

ca2236
Hello, I am getting the below warnings after using the transfer tool to transfer a site from one of our servers to another. I have two questions. 1) is there a way to get it to not delete the site? I am concerned because if the copy doesn't go well, I don't want the source site deleted, Additionally, in 99% of the cases, I don't want the source site deleted anyway. Furthermore, as a note, the button says copy (not move) :) If there isn't a way to keep it from deleting, this would be a good option to add. As there are many many reasons you would only want to copy and not delete the source. 2) are the Mysql warnings anything to be concerned about? Both transfer/restore sides say 100% and I can see the site listed there. Transfer from "server.company.net" Summary TRANSFER: 1 completed, 1 had warnings, and 0 failed. RESTORE: 1 completed, 1 had warnings, and 0 failed. TRANSFER: Account "acctname": Warnings The system failed to remove "acctname""s remote account archive via the API (Application Programming Interface) because of an error (Could not connect to https://server.company.net:2087/json-api/delete_account_archives: Could not connect to 'server.company.net:2087': Connection timed out ). The system will now try to delete the account via SSH (Secure Shell) instead. RESTORE: Account "acctname": Warnings The "MysqlRemoteNotes" restore module failed because of an error: "/home/cpanelpkgrestore.TMP.work.cde8a086/safe_to_read_archive/contents/mysql_host_notes.json" is empty. at /usr/local/cpanel/Cpanel/JSON.pm line 252. Cpanel::JSON::_LoadFile("/home/cpanelpkgrestore.TMP.work.cde8a086/safe_to_read_archive"..., 0, 0, undef, 0) called at /usr/local/cpanel/Cpanel/JSON.pm line 203 Cpanel::JSON::LoadFile("/home/cpanelpkgrestore.TMP.work.cde8a086/safe_to_read_archive"...) called at /usr/local/cpanel/Whostmgr/Transfers/Systems/MysqlRemoteNotes.pm line 104 Whostmgr::Transfers::Systems::MysqlRemoteNotes::unrestricted_restore(Whostmgr::Transfers::Systems::MysqlRemoteNotes=HASH(0x8107128)) called at /usr/local/cpanel/Whostmgr/Transfers/Systems.pm line 128 Whostmgr::Transfers::Systems::restore(Whostmgr::Transfers::Systems::MysqlRemoteNotes=HASH(0x8107128)) called at /usr/local/cpanel/Whostmgr/Transfers/AccountRestoration.pm line 227 Whostmgr::Transfers::AccountRestoration::__ANON__() called at /usr/local/cpanel"or::_process_child_with_output_redirection(Whostmgr::Transfers::Session::Processor=HASH(0x3665e78), Whostmgr::Transfers::Session=HASH(0x35cd4d0), 0, "servercompanyynetcopya20200914212400jihz") called at /usr/local/cpanel/Whostmgr/Transfers/Session/Processor.pm line 203 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(0x3626e50)) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Processor.pm line 205 Whostmgr::Transfers::Session::Processor::start(Whostmgr::Transfers::Session::Processor=HASH(0x3665e78)) called at bin/start_transfer.pl line 57 main::__ANON__() called at /usr/local/cpanel/3rdparty/perl/530/lib/perl5/cpanel_lib/Try/Tiny.pm line 97 eval {...} called at /usr/local/cpanel/3rdparty/perl/530/lib/perl5/cpanel_lib/Try/Tiny.pm line 88 Try::Tiny::try(CODE(0x35cd5a8), Try::Tiny::Catch=REF(0x1a43510)) called at bin/start_transfer.pl line 72 HTTP/1.1 404 Not Found Content-Length: 0 Date: Mon, 14 Sep 2020 21:38:29 GMT The WebSocket handshake failed because of an error: Connect timeout

Comments

18 comments

Date Votes
  • andrew.n
    The system is not trying to remove the account from the source server but the backup it made to transfer over the account. The connection timed out error could be due to a firewall on the source server? Make sure the destination server' IP is whitelisted and give it another try.
    0
  • cPanelLauren
    What transfer setting are you using? A firewall on either of them blocking the transfer could have caused that timeout as well.
    0
  • ca2236
    Thanks Everyone I can double check the firewall, How about for the MySQL error part?
    0
  • andrew.n
    This could be connected to the firewall part so I suggest you to give it a try I'm sure the MySQL error won't appear anymore either.
    0
  • ca2236
    ok, that was on the restore, so that is checking the local server?
    0
  • andrew.n
    Yes
    0
  • ca2236
    Thanks, I appreciate your time and patience with my questions, but if the warnings are on the local server, that wouldn't be due to a firewall with the source server. Are the local restore warnings something I need to be concerned with?
    0
  • andrew.n
    I meant the local server is the source server so you should check the server from which you are restoring the account.
    0
  • ca2236
    Rather than open a new thread, I am working out these errors, I found a port that needed to be open. However, what does this error mean and how it relates to transferring accounts and if it is safe to ignore. (there is a lot more to this warning, just this is the main part I think) Restoring Remote MySQL comments MysqlRemoteNotes "/home/cpanelpkgrestore.TMP.work.17f35ead/safe_to_read_archive/contents/mysql_host_notes.json" is empty. at /usr/local/cpanel/Cpanel/JSON.pm line 252. Cpanel::JSON::_LoadFile("/home/cpanelpkgrestore.TMP.work.17f35ead/safe_to_read_archive"..., 0, 0, undef, 0) called at /usr/local/cpanel/Cpanel/JSON.pm line 203 from a more detailed view of this warning: The system already restored all of the required content. LinkedNodes MysqlRemoteNotes Restoring Remote MySQL comments MysqlRemoteNotes "/home/cpanelpkgrestore.TMP.work.17f35ead/safe_to_read_archive/contents/mysql_host_notes.json" is empty.
    0
  • ca2236
    I'm wondering if according to this link
    0
  • cPRex Jurassic Moderator
    Hey there! It does indicate the file is empty, so that seems to be just a warning it is providing.
    0
  • ca2236
    Does the hosts notes come from the remote mysql entry, or does it come from somewhere else? Unless a 3rd (or 4th) times a charm, an account we were getting that error on successfully transferred once I filled out the comment filed in the remote mysql entry. What is weird though is that it seems hit or miss as I was able to transfer another site just fine without the highlighted comment field filled out.
    0
  • RitikBarnwal

    i am also getting this issue on migration time

    The system failed to remove “codivant”’s remote account archive via the API (Application Programming Interface) because of an error (pass, accesshash, or api_token is a required parameter at /usr/local/cpanel/3rdparty/perl/536/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 562 Whostmgr::Transfers::Session::Items::AccountRemoteRoot::_run_whm_api(Whostmgr::Transfers::Session::Items::AccountRemoteRoot=HASH(0x3398938), "delete_account_archives", HASH(0x376d7c8)) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Items/AccountRemoteRoot.pm line 965 eval {...} called at /usr/local/cpanel/Whostmgr/Transfers/Session/Items/AccountRemoteRoot.pm line 961 Whostmgr::Transfers::Session::Items::AccountRemoteRoot::_remove_remote_cpmove_files_via_api(Whostmgr::Transfers::Session::Items::AccountRemoteRoot=HASH(0x3398938), "/home") called at /usr/local/cpanel/Whostmgr/Transfers/Session/Items/AccountRemoteRoot.pm line 1002 Whostmgr::Transfers::Session::Items::AccountRemoteRoot::_remove_remote_cpmove_files(Whostmgr::Transfers::Session::Items::AccountRemoteRoot=HASH(0x3398938)) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Item.pm line 359 Whostmgr::Transfers::Session::Item::__ANON__() called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Try/Tiny.pm line 100 eval {...} called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Try/Tiny.pm line 91 Try::Tiny::try(CODE(0x3399ff8), Try::Tiny::Catch=REF(0x3398908)) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Item.pm line 388 Whostmgr::Transfers::Session::Item::exec_path(Whostmgr::Transfers::Session::Items::AccountRemoteRoot=HASH(0x3398938), ARRAY(0x3398a70), ARRAY(0x3399f68), 1) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Items/AccountRemoteRoot.pm line 206 Whostmgr::Transfers::Session::Items::AccountRemoteRoot::transfer(Whostmgr::Transfers::Session::Items::AccountRemoteRoot=HASH(0x3398938)) 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/536/cpanel-lib/Try/Tiny.pm line 100 eval {...} called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Try/Tiny.pm line 91 Try::Tiny::try(CODE(0x344ba10), Try::Tiny::Catch=REF(0x341df50)) called at /usr/local/cpanel/Whostmgr/Transfers/Session.pm line 1488 Whostmgr::Transfers::Session::exec_with_output_directed_to_fh(Whostmgr::Transfers::Session=HASH(0x32dc250), GLOB(0x3399628), CODE(0x2a057c8)) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Processor.pm line 674 Whostmgr::Transfers::Session::Processor::_process_dequeued_item(Whostmgr::Transfers::Session::Processor=HASH(0x3394ff8)) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Processor.pm line 554 Whostmgr::Transfers::Session::Processor::_process_items(Whostmgr::Transfers::Session::Processor=HASH(0x3394ff8)) 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 72 eval {...} called at /usr/local/cpanel/Cpanel/ForkAsync.pm line 72 Cpanel::ForkAsync::do_in_child(CODE(0x333b8c8)) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Processor.pm line 510 Whostmgr::Transfers::Session::Processor::_spawn_child(Whostmgr::Transfers::Session::Processor=HASH(0x3394ff8), 1, Whostmgr::Transfers::Session=HASH(0x32dc250)) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Processor.pm line 292 Whostmgr::Transfers::Session::Processor::_process_child(Whostmgr::Transfers::Session::Processor=HASH(0x3394ff8), Whostmgr::Transfers::Session=HASH(0x32dc250), 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(0x3394ff8), Whostmgr::Transfers::Session=HASH(0x32dc250), 0, "server1codivancopya202404161459426Ay") 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 72 eval {...} called at /usr/local/cpanel/Cpanel/ForkAsync.pm line 72 Cpanel::ForkAsync::do_in_child(CODE(0x336ce20)) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Processor.pm line 207 Whostmgr::Transfers::Session::Processor::start(Whostmgr::Transfers::Session::Processor=HASH(0x3394ff8)) called at bin/start_transfer.pl line 57 main::__ANON__() called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Try/Tiny.pm line 100 eval {...} called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Try/Tiny.pm line 91 Try::Tiny::try(CODE(0x32dbea8), Try::Tiny::Catch=REF(0x2826ea8)) called at bin/start_transfer.pl line 72 ). The system will now try to delete the account via SSH (Secure Shell) instead.

    0
  • cPRex Jurassic Moderator

    RitikBarnwal - that does look like a slightly different error than what we say previous posted, but has the same resul.

    There are several reasons that can cause this behavior.  Do you see any additional data on the Source server when you check the log at /var/cpanel/transfer_sessions/################ where "#########" is the recent log?  That may show additional data about what is happening, such as high load on the machine or a failed connection.

    0
  • RitikBarnwal

     

    getting this 

    [root@server1 transfer_sessions]# cat whmxfer.sqlite
    ���4�;tablesessionssessionsCREATE TABLE `sessions` ("sessionid" char(255)  NOT NULL ,
    "initiator" char(255)  DEFAULT 'unknown',
    "creator" char(255)  DEFAULT 'root',
    "pid" bigint(20)  DEFAULT '0',
    "version" double  DEFAULT '0',
    "target_host" char(255)  DEFAULT NULL,
    "source_host" char(255)  DEFAULT NULL,
    "state" bigint(20)  DEFAULT '0',
    "starttime" datetime  DEFAULT NULL,
    "endtime" datetime  DEFAULT NULL,
    PRIMARY KEY ("sessionid"))/Cindexsqlite_autoindex_sessions_1sessions
    [root@server1 transfer_sessions]#

    0
  • cPRex Jurassic Moderator

    That wouldn't be what we're looking for.  You could use the WHM >> Review Transfers and Restores area to see recent logs about that process.

    0
  • RitikBarnwal

    on old server have no logs available but in new server i am get this

    TRANSFER: 1 completed, 1 had warnings, and 0 failed.
    RESTORE: 1 completed, 1 had warnings, and 0 failed.
    The system failed to remove “codivant”’s remote account archive via the API (Application Programming Interface) because of an error (pass, accesshash, or api_token is a required parameter at /usr/local/cpanel/3rdparty/perl/536/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 562 Whostmgr::Transfers::Session::Items::AccountRemoteRoot::_run_whm_api(Whostmgr::Transfers::Session::Items::AccountRemoteRoot=HASH(0x3c76e20), "delete_account_archives", HASH(0x4065c78)) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Items/AccountRemoteRoot.pm line 965 eval {...} called at /usr/local/cpanel/Whostmgr/Transfers/Session/Items/AccountRemoteRoot.pm line 961 Whostmgr::Transfers::Session::Items::AccountRemoteRoot::_remove_remote_cpmove_files_via_api(Whostmgr::Transfers::Session::Items::AccountRemoteRoot=HASH(0x3c76e20), "/home") called at /usr/local/cpanel/Whostmgr/Transfers/Session/Items/AccountRemoteRoot.pm line 1002 Whostmgr::Transfers::Session::Items::AccountRemoteRoot::_remove_remote_cpmove_files(Whostmgr::Transfers::Session::Items::AccountRemoteRoot=HASH(0x3c76e20)) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Item.pm line 359 Whostmgr::Transfers::Session::Item::__ANON__() called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Try/Tiny.pm line 100 eval {...} called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Try/Tiny.pm line 91 Try::Tiny::try(CODE(0x3c784e0), Try::Tiny::Catch=REF(0x3c772d0)) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Item.pm line 388 Whostmgr::Transfers::Session::Item::exec_path(Whostmgr::Transfers::Session::Items::AccountRemoteRoot=HASH(0x3c76e20), ARRAY(0x3c76f58), ARRAY(0x3c78450), 1) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Items/AccountRemoteRoot.pm line 206 Whostmgr::Transfers::Session::Items::AccountRemoteRoot::transfer(Whostmgr::Transfers::Session::Items::AccountRemoteRoot=HASH(0x3c76e20)) 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/536/cpanel-lib/Try/Tiny.pm line 100 eval {...} called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Try/Tiny.pm line 91 Try::Tiny::try(CODE(0x3d4de00), Try::Tiny::Catch=REF(0x3d20030)) called at /usr/local/cpanel/Whostmgr/Transfers/Session.pm line 1488 Whostmgr::Transfers::Session::exec_with_output_directed_to_fh(Whostmgr::Transfers::Session=HASH(0x3bddfe0), GLOB(0x3d1f748), CODE(0x3d1fb38)) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Processor.pm line 674 Whostmgr::Transfers::Session::Processor::_process_dequeued_item(Whostmgr::Transfers::Session::Processor=HASH(0x3c96e68)) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Processor.pm line 554 Whostmgr::Transfers::Session::Processor::_process_items(Whostmgr::Transfers::Session::Processor=HASH(0x3c96e68)) 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 72 eval {...} called at /usr/local/cpanel/Cpanel/ForkAsync.pm line 72 Cpanel::ForkAsync::do_in_child(CODE(0x3c3d8b0)) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Processor.pm line 510 Whostmgr::Transfers::Session::Processor::_spawn_child(Whostmgr::Transfers::Session::Processor=HASH(0x3c96e68), 1, Whostmgr::Transfers::Session=HASH(0x3bddfe0)) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Processor.pm line 292 Whostmgr::Transfers::Session::Processor::_process_child(Whostmgr::Transfers::Session::Processor=HASH(0x3c96e68), Whostmgr::Transfers::Session=HASH(0x3bddfe0), 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(0x3c96e68), Whostmgr::Transfers::Session=HASH(0x3bddfe0), 0, "server1codivancopya20240416145942Ez7") 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 72 eval {...} called at /usr/local/cpanel/Cpanel/ForkAsync.pm line 72 Cpanel::ForkAsync::do_in_child(CODE(0x3c6ee10)) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Processor.pm line 207 Whostmgr::Transfers::Session::Processor::start(Whostmgr::Transfers::Session::Processor=HASH(0x3c96e68)) called at bin/start_transfer.pl line 57 main::__ANON__() called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Try/Tiny.pm line 100 eval {...} called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Try/Tiny.pm line 91 Try::Tiny::try(CODE(0x3bddea8), Try::Tiny::Catch=REF(0x2826ea8)) called at bin/start_transfer.pl line 72 ). The system will now try to delete the account via SSH (Secure Shell) instead.
    0
  • cPRex Jurassic Moderator

    It looks like the same error log we already knew.  We'd likely need to see a ticket with access to both the Source and Destination machines in order to determine what may have went wrong.

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post