Massive DNS Only FAIL
so, I have been using cPanel DNS only for years, and it's working solid.
On Saturday I added a new server to the DNS cluster and migrated some accounts successfully. Imagine my surprise when I learned this morning that some of the DNS zones had reset to the default DNS zone file in cPanel instead of migrating the DNS zone file over from the old server. It seems to be random, and there is no consistency, some transferred successfully, some reset. What a mess.
To complicate matters further, I purchased the cPanel license with OVH with the server and I can't submit a ticket to cPanel directly anymore to sort this . . .
The old server was CloudLinux v7.9.0 STANDARD standard cPanel Version 110.0.34 and the new server is AlmaLinux v8.10.0 STANDARD standard cPanel Version 120.0.10
I don't know the first place where I should begin to troubleshoot this, and I have another 250 accounts to migrate, and cant' be manually spot checking this kind of basic stuff . . .
-
Hey there! I'm sorry to hear about these issues with the transfer! The most odd and interesting part to me is that you've said some have moved over just fine, and some have not - that's going to be the key here. Is there anything in common with the ones that didn't get moved properly?
0 -
I am very baffled. Is there a log on account transfers that gives more details than the transfer log to determine what happened?
It's almost like the transfer got confused by an old SOA and overwrote with the default DNS template or something.
The only consistent thing is that all the accounts that failed originate from the same source server.
0 -
Yes, you would be able to see that log in WHM >> Review Transfers and Restores as that would show the entire log just as what you would have seen while watching it live inside the Transfer Tool.
0 -
sooo , here is what I'm finding.
I went back to check the old suspended cPanel account of one of the "failed" DNS zone file transfers because it was still on the old server, and to my surprise, I found that the zone file on the old server was the out of date version. It matched exactly what was on the new server which means the transfer tool copied exactly what was on the old server to the new server.
So the zone file on the old web server was older than the copy that was serving from the DNS cluster. And when I did the transfer, the serial number probably updated and overwrote my zone file with this old default one.
So it seems like it might be a SOA serial number issue, but how am I getting a DNS zone file on the web server that is older than the version running in the DNS cluster, and how do I sync the zone down to the web server from the DNS cluster. It would seem like syncing all zones to all servers would have done this.
Furthermore, is there any way possible to tell which accounts this is affecting short of manually comparing the DNS zone on the web server compared to the one on the nameserver.0 -
I'm glad you at least found something, because I didn't have any good guesses on my end.
Depending on your sync settings you wouldn't send data from the DNS servers to the webservers, but if you do then it's important to note that the data will get replicated across all webservers as well, not just the webserver the zone comes from.
I don't have another way to detect this besides manually checking the serial numbers, though.
It might be best to submit a ticket so this can be examined.
0 -
ok, before this comment gets lost, I'm not able to put a ticket in directly with cPanel because this license was bought via OVH
I will try to describe what is going on, see if I make sense.
On the old server, what I see in /var/named/domain.com does not match what I see in WHM > DNS Functions > DNS Zone Manager . . .
What I see on the old server /var/named is an old zone with an old serial number from a few days ago. On the nameservers, and on other servers in the cluster I see the latest DNS record. I checked another offending domain and found the exact same scenario.
For syncing both nameservers are set as Standalone, and all the web servers are set as Synchronize Changes.
Checking further then, I see the serial number for all the zones that reset are all the same serial number 2024062103 which matches the date the transfer was initiated from the new server.
It's like the Transfer tool reset the DNS zone to default on the old server, and then synced it to the new local server, which then updated the DNS cluster and overwrote the actual zone. I could find a backup of the syste_files.tar just to verify what the old DNS zone contents really were on the local server but I'm pretty sure at this point.
The log of one account transfer is below. I have sanitized it for privacy
<log>
starting “RESTORE” for “Account” “exampledomain”.
Restore File: /home/cpmove-exampledomain.tar.gz.part00001
Restore Reseller Privs: no
Restricted mode: no
Live transfer: yes
Target “/home” on host “new.server.com” has 1.69 TB free and requires at least 9.5 GB free, which includes space for temporary files.
Target “/home” on host “new.server.com” has 185,260,533 inodes free and requires at least 26,608 inodes free, which includes space for temporary files.
The “Reseller” restore module has the following areas disabled by request: “all”
ArchiveManager
Preparing archive for restoration …
Calculating disk space needed …
Done.
Target “/home/cpanelpkgrestore.TMP.work.69052212/unsafe_to_read_archive” on host “new.server.com” has 1.69 TB free and requires at least 10.6 MB free, which includes space for temporary files.
This archive’s payload appears to be in the archive’s “cpmove-exampledomain” directory.
ArchiveManager
The system successfully prepared the archive for restoration.
PreRestoreActions
PreRestoreActions
Account
Force Mode: no
Dedicated IP Address: no
Checking input data...Forced Dns is enabled. Validating Username......Done Validating IP......Done Validating Contact Email......Done ...Done Checking for database conflicts......Done Checking for account enhancements......Done WWWAcct 12.6.0 (c) 2024 cPanel, L.L.C.... +===================================+ | New Account Info | +===================================+ | Domain: exampledomain.com | Ip: new.server.ip (n) | HasCgi: n | UserName: exampledomain | PassWord: HIDDEN | CpanelMod: jupiter | HomeRoot: /home | Quota: unlimited | NameServer1: ns1.mycustomnameserver.com | NameServer2: ns2.mycustomnameserver.com | NameServer3: | NameServer4: | Contact Email: joe@exampledomain.com | Package: SuperBiz_exampledomain_exampledomain | Feature List: default | Account Enhancements: None | Language: en +===================================+ ...Done Custom Account Data Provided: no Running pre creation script (/usr/local/cpanel/scripts/prewwwacct)......Done Setting up System User...Removing Shell Access (n) Success...Done Setting up Userdata......Done Setting up Home Directory......Done Setting up Mail...valiases ...vdomainaliases ...vfilters ......Done Setting up Calendar and Contacts......Done Configuring DNS...Zone exampledomain.com has been successfully added ...Done Verifying MX Records and Setting up Databases...Reconfiguring Mail Routing: LOCAL MAIL EXCHANGER: This server will serve as a primary mail exchanger for exampledomain.com's mail.: This configuration has been automatically detected based on your mx entries. ...Done Updating Authentication Databases......Done Setting passwords......Done Updating the userdata cache......Done Creating bandwidth datastore......Done Updating the dedicated IP address usage cache......Done Generating and installing DKIM keys......Done Enabling Apache SpamAssassin™......Done Enabling Apache SpamAssassin™ Spam Box......Done Sending Account Information......Done Running post creation scripts (/usr/local/cpanel/scripts/legacypostwwwacct, /usr/local/cpanel/scripts/postwwwacct, /usr/local/cpanel/scripts/postwwwacctuser)......Done wwwacct creation finished Account Creation Complete!!!...Account Creation Ok...Done
Account
Account created
CpUser
Restoring cPanel user file.
Updating Caches …
CpUser
CpUser data restored
Homedir
Streaming home directory from source server …
receiving incremental file list
…100 % …
sent 485.79K bytes received 10.13G bytes 27.48M bytes/sec
total size is 10.12G speedup is 1.00
Homedir
Homedir restored
IPAddress
IPAddress
Package
Package
The package exists on the system.
FeatureList
FeatureList
Feature list exists.
Domains
Retrieving and sanitizing main userdata …
Parsing domain databases …
…Subdomains…
…ParkedDomains…
…AddonDomains…
Restoring Domains …
Updating internal databases…
Domains
Domains restored
OldHomedirs
Linking old home directories
OldHomedirs
BrandCustomizations
Restoring customization data
BrandCustomizations
Roundcube
Roundcube update from 1.6.6.3-1.cp120~el8 to 1.6.6.3-1.cp120~el8 in progress. Roundcube updated to 1.6.6.3-1.cp120~el8
Roundcube
MysqlRemoteNotes
MysqlRemoteNotes
Mysql
Preparing MySQL restore …
Restoring MySQL databases
Restoring the database “exampledomain_site” as “exampledomain_site” …
The system has created a new database named “exampledomain_site”.
Granting “exampledomain” access to “exampledomain_site” with temporary password …
Spawning restoration subprocess for “exampledomain_site” …
Restoring database in subprocess (PID 3092531) …
The WebSocket handshake succeeded: wss://old.server.ip:2087/websocket/MysqlDump?character_set=utf8mb4&dbname=exampledomain_site&include_data=1
The remote MySQL dump ended successfully.
Transfer complete. Awaiting subprocess completion …
Connecting to SQL server (/var/lib/mysql/mysql.sock) as “exampledomain” in order to restore “exampledomain_site” …
Disabling InnoDB strict mode for database restore for “exampledomain_site” …
Restoring database data for “exampledomain_site” …
Processing SQL statements …
The database restoration subprocess for “exampledomain_site” has ended.
The system has restored the contents of the database “exampledomain_site”.
Restoring MySQL database mappings
Restoring MySQL privileges
Restoring MySQL grants
Restoring MySQL access hosts
Storing MySQL Grants
Mysql
AutoSSL
AutoSSL
BackupConfig
Restoring backup config …
Updated backup config for “exampledomain”.
Restoring legacy backup config …
Updated legacy backup config for “exampledomain”.
BackupConfig
CustomLocale
CustomLocale
OK
DKIM
DKIM
DKIM restored
DigestShadow
DigestShadow
Integration
Restoring the integration link for the application “WHMCS_clientarea_announcements” …
Restoring the integration link for the application “WHMCS_clientarea_billing_info” …
Restoring the integration link for the application “WHMCS_clientarea_downloads” …
Restoring the integration link for the application “WHMCS_clientarea_emails” …
Restoring the integration link for the application “WHMCS_clientarea_invoices” …
Restoring the integration link for the application “WHMCS_clientarea_knowledgebase” …
Restoring the integration link for the application “WHMCS_clientarea_network_status” …
Restoring the integration link for the application “WHMCS_clientarea_product_details” …
Restoring the integration link for the application “WHMCS_clientarea_profile” …
Restoring the integration link for the application “WHMCS_clientarea_shopping_cart_domain_register” …
Restoring the integration link for the application “WHMCS_clientarea_shopping_cart_domain_transfer” …
Restoring the integration link for the application “WHMCS_clientarea_submit_ticket” …
Restoring the integration link for the application “WHMCS_clientarea_tickets” …
Restoring the integration link for the application “WHMCS_clientarea_upgrade” …
Integration
LinkedNodesSubarchives
LinkedNodesSubarchives
Logs
Logs
Mail
Restoring Mail files
Resetting Quotas to sane values
Mail
MailFix
Fixing mail permissions
Converting to maildir if needed
MailFix
MailLimits
Restoring mail limits (if any)
MailLimits
Mailman
Restoring Mailman lists
Mailman
Mailman Restored
Password
Restoring password …
Password for “exampledomain” has been changed.
Password
Postgres
Preparing PostgreSQL restore …
This system does not have PostgreSQL.
Postgres
PublicContact
PublicContact
PublicHtmlSymlinks
PublicHtmlSymlinks
Shell
Restoring shell
Setting the user’s shell to “/bin/bash” …
Shell
SpamAssassin
SpamAssassin
Ran SpamAssassin check
Subaccount
Subaccount
Ran Subaccount database checks
Unsuspend
Unsuspending .htaccess files for domains exampledomain.com.
Unsuspend
VhostIncludes
Restoring custom virtualhost templates…
VhostIncludes
WebCalls
WebCalls
WebDiskHomedir
WebDiskHomedir
userdata
Restoring userdata…
Restoring userdata for “exampledomain.com” …
userdata
Cron
Restoring crontab
Cron
Ftp
Restoring ftp password file
Resyncing FTP Passwords
1
Ftp
Htaccess
Looking for “.htaccess” files …
Updating “exampledomain”’s “.htaccess” files …
Updating the system’s web virtual host configuration cache and “.htaccess” files …
Repairing “/home/exampledomain/public_html/.htaccess” for EasyApache 4 …
The system mapped “/home/exampledomain/public_html/.htaccess” to the virtual host “exampledomain.com” …
Repairing “/home/exampledomain/public_html/wp-content/plugins/really-simple-ssl/testssl/cloudflare/.htaccess” for EasyApache 4 …
The htaccess file “/home/exampledomain/public_html/wp-content/plugins/really-simple-ssl/testssl/cloudflare/.htaccess” is not in a document root …
Repairing “/home/exampledomain/public_html/wp-content/plugins/really-simple-ssl/testssl/cloudfront/.htaccess” for EasyApache 4 …
The htaccess file “/home/exampledomain/public_html/wp-content/plugins/really-simple-ssl/testssl/cloudfront/.htaccess” is not in a document root …
Repairing “/home/exampledomain/public_html/wp-content/plugins/really-simple-ssl/testssl/envhttps/.htaccess” for EasyApache 4 …
The htaccess file “/home/exampledomain/public_html/wp-content/plugins/really-simple-ssl/testssl/envhttps/.htaccess” is not in a document root …
Repairing “/home/exampledomain/public_html/wp-content/plugins/really-simple-ssl/testssl/loadbalancer/.htaccess” for EasyApache 4 …
The htaccess file “/home/exampledomain/public_html/wp-content/plugins/really-simple-ssl/testssl/loadbalancer/.htaccess” is not in a document root …
Repairing “/home/exampledomain/public_html/wp-content/plugins/really-simple-ssl/testssl/serverhttps1/.htaccess” for EasyApache 4 …
The htaccess file “/home/exampledomain/public_html/wp-content/plugins/really-simple-ssl/testssl/serverhttps1/.htaccess” is not in a document root …
Repairing “/home/exampledomain/public_html/wp-content/plugins/really-simple-ssl/testssl/serverhttpson/.htaccess” for EasyApache 4 …
The htaccess file “/home/exampledomain/public_html/wp-content/plugins/really-simple-ssl/testssl/serverhttpson/.htaccess” is not in a document root …
Repairing “/home/exampledomain/public_html/wp-content/plugins/really-simple-ssl/testssl/serverhttpxforwardedssl1/.htaccess” for EasyApache 4 …
The htaccess file “/home/exampledomain/public_html/wp-content/plugins/really-simple-ssl/testssl/serverhttpxforwardedssl1/.htaccess” is not in a document root …
Repairing “/home/exampledomain/public_html/wp-content/plugins/really-simple-ssl/testssl/serverhttpxforwardedsslon/.htaccess” for EasyApache 4 …
The htaccess file “/home/exampledomain/public_html/wp-content/plugins/really-simple-ssl/testssl/serverhttpxforwardedsslon/.htaccess” is not in a document root …
Repairing “/home/exampledomain/public_html/wp-content/plugins/really-simple-ssl/testssl/serverhttpxproto/.htaccess” for EasyApache 4 …
The htaccess file “/home/exampledomain/public_html/wp-content/plugins/really-simple-ssl/testssl/serverhttpxproto/.htaccess” is not in a document root …
Repairing “/home/exampledomain/public_html/wp-content/plugins/really-simple-ssl/testssl/serverport443/.htaccess” for EasyApache 4 …
The htaccess file “/home/exampledomain/public_html/wp-content/plugins/really-simple-ssl/testssl/serverport443/.htaccess” is not in a document root …
Repairing “/home/exampledomain/public_html/wp-content/updraft/.htaccess” for EasyApache 4 …
The htaccess file “/home/exampledomain/public_html/wp-content/updraft/.htaccess” is not in a document root …
Htaccess
EasyApache4 was repaired in .htaccess files.
SSL
The SSL certificate is now installed onto the domain “exampledomain.com” using the IP address “new.server.ip”.
SSL
LocalConfig
LocalConfig
Vhosts
Refreshing vhosts and restarting apache
Vhosts
ZoneFile
Restoring DNS zones
Fetching existing zones.
Restoring zone: “exampledomain.com”.
Local Zone Updates: “exampledomain.com”
ZoneFile
DNSSEC
DNSSEC
MailRouting
Update mail routing
REMOTE MAIL EXCHANGER: This server will NOT serve as a mail exchanger for exampledomain.com's mail.This configuration has been automatically detected based on your mx entries.
MailRouting
SPF
Updating SPF Records
SPF
ProxySubdomains
Update service subdomains for “exampledomain”.
exampledomain.com [no changes needed]
ProxySubdomains
PublishZones
Altering old.server.ip’s “exampledomain” account …
Pointing “exampledomain.com”’s DNS records to the new server … …
[xferpoint] server:old.server.hostname user:exampledomain
[xferpoint] Per request, skipping creation of dynamic content block.
[xferpoint] Updating IP addresses in DNS …
The system updated “3” entries.
[xferpoint] Setting nameservers (ns1.mycustomnameserver.com ns2.mycustomnameserver.com) …
[xferpoint] complete
Done
Updating mail routing on the source server … …
Setting mail handling for exampledomain.com to : secondary
Done
Disabling logins on the source server … …
Locking password for user exampledomain.
passwd: Success
Updating FTP passwords for exampledomain
FTP password files updated.
FTP vhost passwords synced
Done
Syncing zones to the dns cluster
Cluster Zone Updates: “exampledomain.com”
Reloading zones
PublishZones
DNSAuthority
DNSAuthority
ManualMX
Configuring manual MX entries on the source server (old.server.ip) …
ManualMX
Manual MX entries configured.
ResyncHomedir
Streaming home directory from source server …
receiving incremental file list
sent 141.38K bytes received 796.74K bytes 268.03K bytes/sec
total size is 10.12G speedup is 10,789.18
…100 % …
ResyncHomedir
Homedir restored
ServiceProxy
Configuring the source server (old.server.ip) to proxy services to the new account …
Terminating “exampledomain”’s mailbox sessions on “old.server.ip” …
ServiceProxy
MailSync
MailSync
FileProtect
FileProtect
NativeDAV
Converting data from Horde to Native CPDAVD format...
Updating free/busy data...
NativeDAV
NobodyFiles
NobodyFiles
PostRestoreActions
Updating Caches …
Updating Nameserver IP Address Report
Syncing contact information
[2024-06-21 11:35:49 -0400] warn [Internal Warning while parsing [stdin] 3087933] defaultdir has been rejected since it is an absolute path outside the user’s homedir at /usr/local/cpanel/Cpanel/NVData.pm line 385.
at /usr/local/cpanel/Cpanel/NVData.pm line 385.
Cpanel::NVData::_validate_name_is_valid("defaultdir", "/home/advanced") called at /usr/local/cpanel/Cpanel/NVData.pm line 355
Cpanel::NVData::_get("defaultdir") called at /usr/local/cpanel/Whostmgr/Transfers/Systems/PostRestoreActions.pm line 228
Whostmgr::Transfers::Systems::PostRestoreActions::__ANON__() called at /usr/local/cpanel/Cpanel/AccessIds/ReducedPrivileges.pm line 96
eval {...} called at /usr/local/cpanel/Cpanel/AccessIds/ReducedPrivileges.pm line 96
Cpanel::AccessIds::ReducedPrivileges::call_as_user(CODE(0xa1ce358), "exampledomain") called at /usr/local/cpanel/Whostmgr/Transfers/Systems/PostRestoreActions.pm line 239
Whostmgr::Transfers::Systems::PostRestoreActions::_update_nvdata_defaultdir(Whostmgr::Transfers::Systems::PostRestoreActions=HASH(0xa07ade8)) called at /usr/local/cpanel/Whostmgr/Transfers/Systems/PostRestoreActions.pm line 109
Whostmgr::Transfers::Systems::PostRestoreActions::unrestricted_restore(Whostmgr::Transfers::Systems::PostRestoreActions=HASH(0xa07ade8)) called at /usr/local/cpanel/Whostmgr/Transfers/Systems.pm line 129
Whostmgr::Transfers::Systems::restore(Whostmgr::Transfers::Systems::PostRestoreActions=HASH(0xa07ade8)) called at /usr/local/cpanel/Whostmgr/Transfers/AccountRestoration.pm line 271
Whostmgr::Transfers::AccountRestoration::__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(0xa1f6eb8), Try::Tiny::Catch=REF(0x7df5750)) called at /usr/local/cpanel/Whostmgr/Transfers/AccountRestoration.pm line 275
Whostmgr::Transfers::AccountRestoration::_call_one_restore_module_without_archive_prep_check(Whostmgr::Transfers::AccountRestoration=HASH(0x3cd83e0), "PostRestoreActions") called at /usr/local/cpanel/Whostmgr/Transfers/AccountRestoration.pm line 614
Whostmgr::Transfers::AccountRestoration::_call_one_restore_module_with_notices(Whostmgr::Transfers::AccountRestoration=HASH(0x3cd83e0), "PostRestoreActions") called at /usr/local/cpanel/Whostmgr/Transfers/AccountRestoration.pm line 586
Whostmgr::Transfers::AccountRestoration::_run_restore_system_module(Whostmgr::Transfers::AccountRestoration=HASH(0x3cd83e0), HASH(0x3cecba8), HASH(0x3ce5040)) called at /usr/local/cpanel/Whostmgr/Transfers/AccountRestoration.pm line 552
Whostmgr::Transfers::AccountRestoration::_run_restore_modules(Whostmgr::Transfers::AccountRestoration=HASH(0x3cd83e0), HASH(0x3cecba8)) called at /usr/local/cpanel/Whostmgr/Transfers/AccountRestoration.pm line 485
Whostmgr::Transfers::AccountRestoration::_restore_package(Whostmgr::Transfers::AccountRestoration=HASH(0x3cd83e0)) called at /usr/local/cpanel/Whostmgr/Transfers/AccountRestoration.pm line 97
eval {...} called at /usr/local/cpanel/Whostmgr/Transfers/AccountRestoration.pm line 97
Whostmgr::Transfers::AccountRestoration::restore_package(Whostmgr::Transfers::AccountRestoration=HASH(0x3cd83e0)) called at /usr/local/cpanel/Whostmgr/Backup/Restore.pm line 84
eval {...} called at /usr/local/cpanel/Whostmgr/Backup/Restore.pm line 84
Whostmgr::Backup::Restore::load_transfers_then_restorecpmove("overwrite_all_dbs", 0, "remote_hostname", "old.server.hostname", "replaceip", "all", "file", "cpmove-exampledomain.tar.gz.part00001", ...) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Items/AccountBase.pm line 201
Whostmgr::Transfers::Session::Items::AccountBase::_restore_package(Whostmgr::Transfers::Session::Items::AccountRemoteRoot=HASH(0x3cd29d0)) 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(0x3b0b908), Try::Tiny::Catch=REF(0x3cd29e8)) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Item.pm line 388
Whostmgr::Transfers::Session::Item::exec_path(Whostmgr::Transfers::Session::Items::AccountRemoteRoot=HASH(0x3cd29d0), ARRAY(0x3cd2790), ARRAY(0x3b0aa88), 1) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Items/AccountBase.pm line 39
Whostmgr::Transfers::Session::Items::AccountBase::restore(Whostmgr::Transfers::Session::Items::AccountRemoteRoot=HASH(0x3cd29d0)) 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(0x3c44740), Try::Tiny::Catch=REF(0x3cd2580)) called at /usr/local/cpanel/Whostmgr/Transfers/Session.pm line 1488
Whostmgr::Transfers::Session::exec_with_output_directed_to_fh(Whostmgr::Transfers::Session=HASH(0x3a6faf8), GLOB(0x3b0a248), CODE(0x3b09c78)) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Processor.pm line 674
Whostmgr::Transfers::Session::Processor::_process_dequeued_item(Whostmgr::Transfers::Session::Processor=HASH(0x3b2ee58)) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Processor.pm line 554
Whostmgr::Transfers::Session::Processor::_process_items(Whostmgr::Transfers::Session::Processor=HASH(0x3b2ee58)) 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(0x3b7e708)) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Processor.pm line 510
Whostmgr::Transfers::Session::Processor::_spawn_child(Whostmgr::Transfers::Session::Processor=HASH(0x3b2ee58), "/bin/bash\x{a}", Whostmgr::Transfers::Session=HASH(0x3a6faf8)) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Processor.pm line 292
Whostmgr::Transfers::Session::Processor::_process_child(Whostmgr::Transfers::Session::Processor=HASH(0x3b2ee58), Whostmgr::Transfers::Session=HASH(0x3a6faf8), 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(0x3b2ee58), Whostmgr::Transfers::Session=HASH(0x3a6faf8), 0, "5116184136copya202406211527052vnJIIY") 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(0x3b06e00)) called at /usr/local/cpanel/Whostmgr/Transfers/Session/Processor.pm line 207
Whostmgr::Transfers::Session::Processor::start(Whostmgr::Transfers::Session::Processor=HASH(0x3b2ee58)) 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(0x3a75eb8), Try::Tiny::Catch=REF(0x28279d8)) called at bin/start_transfer.pl line 72
[A warning occurred while processing this directive.]
PostRestoreActions
Quota
Restoring quota
Quota
APITokens
APITokens
AuthnLinks
AuthnLinks
LinkedNodes
LinkedNodes
BandwidthData
Restoring Bandwidth Data
BandwidthData
Suspend
The user “exampledomain” was not suspended. The system will not suspend the restored user.
Suspend
Team
The user “exampledomain” does not have a team configuration file. The system will not create the team file for the restored user.
Team
Removing copied archive “/home/cpmove-exampledomain.tar.gz.part00001” from the local server …
Success.
</log>0 -
Are we sure this all can't be explained by Live Transfer? Here's the entry showing this in the log:
PublishZones
Altering old.server.ip’s “exampledomain” account …
Pointing “exampledomain.com”’s DNS records to the new server … …and here's the explanation of what that does, if you aren't familiar with it:
https://docs.cpanel.net/whm/transfers/transfer-tool/#live-transfer
0 -
no, that link describes the typical process of the old IP address being updated to the new IP address. This is what the transfer did correctly for some of the accounts that migated. For others, it did what I described above.
What I'm seeing is that the Transfer Tool appears to have reset the DNS zone completely back to te default DNS zone template. Office365 MX records and the DKIM selectors went missing along with any records customers added for Sophos or VPNs etc.
0 -
I don't have a good explanation for that as I wouldn't expect that to happen. Any custom records should be retained and anything using the default IP should get adjusted to the new server.
It would likely be best to create that ticket with your host to start an investigation.
0
Please sign in to leave a comment.
Comments
9 comments