Article ID: 114571, created on Aug 15, 2012, last review on Aug 15, 2012

  • Applies to:
  • H-Sphere

Symptoms

Account move stays in the “Transferring content” stage for a long time and the following records are constantly written to the hsphere.log:
 
[root@cp ~]# grep 'processing result = RE-STARTED' /var/log/hsphere/hsphere.log
2012-05-15 14:39:09,181 [transfer] DEBUG cron.TransferCron - rsync job 150 processing result = RE-STARTED
2012-05-15 14:49:09,384 [transfer] DEBUG cron.TransferCron - rsync job 150 processing result = RE-STARTED
2012-05-15 14:59:09,549 [transfer] DEBUG cron.TransferCron - rsync job 150 processing result = RE-STARTED
2012-05-15 15:09:09,727 [transfer] DEBUG cron.TransferCron - rsync job 150 processing result = RE-STARTED
2012-05-15 15:19:09,871 [transfer] DEBUG cron.TransferCron - rsync job 150 processing result = RE-STARTED
2012-05-15 15:29:10,092 [transfer] DEBUG cron.TransferCron - rsync job 150 processing result = RE-STARTED
2012-05-15 15:39:10,288 [transfer] DEBUG cron.TransferCron - rsync job 150 processing result = RE-STARTED
2012-05-15 15:44:10,333 [transfer] DEBUG cron.TransferCron - rsync job 150 processing result = RE-STARTED
2012-05-15 15:54:10,516 [transfer] DEBUG cron.TransferCron - rsync job 150 processing result = RE-STARTED
2012-05-15 16:04:11,024 [transfer] DEBUG cron.TransferCron - rsync job 150 processing result = RE-STARTED
2012-05-15 16:14:10,828 [transfer] DEBUG cron.TransferCron - rsync job 150 processing result = RE-STARTED


Cause

Rsync is not working on the destination server

Resolution

Try to telnet to the destination server to port 873. If you are unable to do so, then you need to start rsync daemon on that server:
[root@target /]# /hsphere/shared/scripts/rsync.sh start
If you are unable to do so, delete the
/hsphere/local/var/rsync/rsync.pid
file and repeat the rsync starting attempt.

6311ae17c1ee52b36e68aaf4ad066387 f213b9fa8759d57bee5d547445806fe7

Email subscription for changes to this article
Save as PDF