Article ID: 123257, created on Oct 24, 2014, last review on Oct 24, 2014

  • Applies to:
  • Virtual Automation 6.0

Symptoms

"Migrate Server to Container" operation hangs on rsync stage:

Jun 04, 2014 04:49:58 PM    Starting the process    Completed
Jun 04, 2014 04:49:58 PM    Click here to open/close the operation details.Import Container     Completed
Jun 04, 2014 04:49:59 PM    Operation is started     
Jun 04, 2014 04:50:07 PM    Disk usage: required 6861M, available 10662M     
Jun 04, 2014 04:50:07 PM    Starting rsync...    
Jun 04, 2014 05:05:21 PM    Rsync processing files   39%

Checking the process on the source node reveals a particular file, on which the procedure got stuck:

# ps auxfwww | grep rsync | grep -v grep
root     40253 20.3  0.4   9524  8696 ?        S    12:04  54:02      \_ /var/vzagent.tmp/usr/local/share/vzlinmigrate/rsync --server --sender -ESHa --numeric-ids --delete . /
# lsof -p 40253
COMMAND   PID USER   FD   TYPE    DEVICE        SIZE/OFF       NODE NAME
...
rsync   40253 root    3r   REG    0,3 140737486262272 4026532025 /var/named/run-root/proc/kcore
...

The file belong to "Bind" package.

Cause

Due to its specifics, Bind DNS server keeps a copy of the "/proc" filesystem in its chrooted area "/var/named/run-root". The filesystem is virtual and contains special files, which cannot be migrated and cause "rsync" to hang.

Resolution

Exclude "/var/named/run-root/proc" in the wizard before starting the migration.

Search Words

Rsync processing files

server to container migration stuck

319940068c5fa20655215d590b7be29b 2897d76d56d2010f4e3a28f864d69223 0889ab60fa6494de107aa7338c3c38b6

Email subscription for changes to this article
Save as PDF