One big problem I notice with WHM transfer.

I noticed this on the last server I moved from, and again tonight when I tried to move 20 odd accounts.

The time out value in ssh, by default, I think is 2? minutes, so if the pkgacct process takes longer than 2 minutes, it times out.

The pkgacct process carries on on the source server and the destination server restarts the process again, thus, starting yet another pkgacct process.

Tonight I noticed there were 5 pkgacct processes for the same (largish) domain, which actually ended up killing my source server.

I'm still waiting on BurstNet to find out what's gone wrong, but it's been inaccessible for an hour now, heh.

 

Hiya, I'll get back to you on that when/if the server comes back up

From memory, I chose the default options for transfering, using the root login

It starts off ok, then gets to the bit where it says something like Copying maildir/www folder, at which point a pkgacct process seems to start on the source server

Because it's taking so long to package it up, the destination transfer says something about an SSH/SSL? time out, then it restarts the process, but in doing so, it starts another pkgacct process on the source server, even though one is already running, so it just ends up bogging the server down.

In my case, I was unable to terminate pkgacct processes, so it just seemed to crash my server heh.

 

Well, not sure what's happened, but the kernels are all missing.

It appears that all of the kernels were removed from this server. While the grub prompt still has our BurstNET kernel listed, trying to boot it reports file not found. At this point the only option would be to reinstall the server. The standard fee for this service is $25.00 USD. This fee is waived for reinstalls due to hardware failure.

Ah well.