Transfer Problems

[Bright]

Hi guys,
I am transferring a bunch of sites over to our server for a client and have successfuly transferred all bar one, it keeps giving this error message:

UNLINKED
Checksum Matches!
MOVE IS GOOD!
Extracting tarball....
gzip: stdin: unexpected end of file
/bin/tar: Child returned status 1
/bin/tar: Error exit delayed from previous errors
Done
Extracting Domain....Done
Sorry, the copy failed. Unable to find the cpanel user file
Extract Failed
Invalid Account

Any Ideas

cPanel.net Support Ticket Number:

[mccmikey]

Related articles:

http://forums.cpanel.net/showthread....anel+user+file

Promising-looking:

http://forums.cpanel.net/showthread....anel+user+file

Possibly related:

http://forums.cpanel.net/showthread....anel+user+file

http://forums.cpanel.net/showthread....anel+user+file

http://forums.cpanel.net/showthread....anel+user+file

http://forums.cpanel.net/showthread....anel+user+file

cPanel.net Support Ticket Number:

cPanel.net Support Ticket Number:

[pingo]

Related articles:

Lol, we got a search agent at the board.

John

cPanel.net Support Ticket Number:

[gertiebeth]

Originally posted by mccmikey
Related articles:

http://forums.cpanel.net/showthread....anel+user+file

Promising-looking:

http://forums.cpanel.net/showthread....anel+user+file

Possibly related:

http://forums.cpanel.net/showthread....anel+user+file

http://forums.cpanel.net/showthread....anel+user+file

http://forums.cpanel.net/showthread....anel+user+file

http://forums.cpanel.net/showthread....anel+user+file

cPanel.net Support Ticket Number:

cPanel.net Support Ticket Number:

Thanks for the links mccmikey, but I'm still having trouble...

I have a 20+gig site that I am having trouble transfering to a new server. (cPanel to cPanel) I am able to create a backup on the old server and, using the scp command, get it over to the new server. BUT, once the tarball is on the new server (location: /backup/cpbackup/weekly), it will not restore using the WHM restore function. Everything sets up correctly and the restore begins, but the transfer just stops after the tarball is extracted. I have checked the error logs and they say nothing.

So, my question is, is there another way to restore the entire site manually so I don't have to change user ftp/email/mysql passwords? The site in question has 200 or so user accounts on it and I would rather leave the site on the old server than have to manually email all the users for their passwords.

Thanks in advance for any help on this issue. If you need me I'll be here -> My Wit's End.

No support ticket number yet... I'm going to try the forum first. Thanks!

cPanel.net Support Ticket Number:

[SageBrian]

I had something similar. Rather than search for the 'correct' solution, I manually broke up the files and then moved then.

Example:
20gigs of stuff.
I separate into maybe 20 separate folders, each 1 gig.
Moved all folders to area out of /home/account/
Transfer 'account' to new server using WHM
Tar the saved folders folders.
Wget folders to new server.
UnTar, and move to proper location on new server.


Not perfect or most effecient, but worked.

Brian

cPanel.net Support Ticket Number:

[gertiebeth]

Originally posted by SageBrian
I had something similar. Rather than search for the 'correct' solution, I manually broke up the files and then moved then.

Example:
20gigs of stuff.
I separate into maybe 20 separate folders, each 1 gig.
Moved all folders to area out of /home/account/
Transfer 'account' to new server using WHM
Tar the saved folders folders.
Wget folders to new server.
UnTar, and move to proper location on new server.


Not perfect or most effecient, but worked.

Brian

cPanel.net Support Ticket Number:

Yes, I thought about this too SageBrian. The only problem is that then we would experience downtime. BUT, it is definitly something I will try as a last resort.

Appreciate the help!!

cPanel.net Support Ticket Number:

[NNNils]

Same problem here, with a rather big site.

It seems after some border in size, transfer won't succeed, maybe...

[NNNils]

I just found a work around that worked for me:

remove the logfiles from /usr/local/apache/domlogs for the particular domain and try again.