Difference between revisions of "Migration fails"
(initial edition) |
(second reason added: inotidy in VE) |
||
| Line 13: | Line 13: | ||
=== Reason === | === Reason === | ||
| − | The VE | + | The VE which you wish to migrate uses some iptables modules, that are not |
loaded on destination node. Consequently <tt>iptables-restore</tt> fails. | loaded on destination node. Consequently <tt>iptables-restore</tt> fails. | ||
| Line 23: | Line 23: | ||
* http://bugzilla.openvz.org/show_bug.cgi?id=631 | * http://bugzilla.openvz.org/show_bug.cgi?id=631 | ||
* http://forum.openvz.org/index.php?t=tree&th=2756&mid=14198&&rev=&reveal= | * http://forum.openvz.org/index.php?t=tree&th=2756&mid=14198&&rev=&reveal= | ||
| + | |||
| + | == Reason #2 == | ||
| + | === Symptomps === | ||
| + | The system runs <tt>028stab031</tt> or older kernels and | ||
| + | after giving <tt>vzmigrate -v --online <ip address> <veid></tt> | ||
| + | the following message appears: | ||
| + | <pre> | ||
| + | Live migrating VE | ||
| + | Suspending VE | ||
| + | Setting up checkpoint... | ||
| + | suspend... | ||
| + | Can not suspend VE: Device or resource busy | ||
| + | file on unsupported FS: magic 0bad1dea | ||
| + | Checkpointing failed | ||
| + | Error: Failed to suspend VE | ||
| + | </pre> | ||
| + | |||
| + | === Reason === | ||
| + | The VE which you wish to migrate uses inotify mechanism (magic 0bad1dea), that is not | ||
| + | supported by <tt>028stab031</tt> and older kernels. | ||
| + | |||
| + | === Workaround === | ||
| + | Update till <tt>028stab035</tt> or newer kernel. | ||
| + | |||
| + | === Links === | ||
| + | |||
| + | * http://bugzilla.openvz.org/show_bug.cgi?id=552 | ||
| + | * http://forum.openvz.org/index.php?t=tree&goto=14780&#msg_14780 | ||
[[Category:Troubleshooting]] | [[Category:Troubleshooting]] | ||
Revision as of 07:53, 11 July 2007
This article contents known reasons of migration failures.
Contents
Reason #1
Symptomps
After giving vzmigrate -v --online <ip address> <veid> the following message appears:
Error: undump failed: Invalid argumentStopping VE ... Restoring failed: iptables-restore exited with 1 rst_restore_net: -22
Reason
The VE which you wish to migrate uses some iptables modules, that are not loaded on destination node. Consequently iptables-restore fails.
Workaround
Load all iptables kernel modules that are used by VE on destination node.
Links
- http://bugzilla.openvz.org/show_bug.cgi?id=631
- http://forum.openvz.org/index.php?t=tree&th=2756&mid=14198&&rev=&reveal=
Reason #2
Symptomps
The system runs 028stab031 or older kernels and after giving vzmigrate -v --online <ip address> <veid> the following message appears:
Live migrating VE
Suspending VE
Setting up checkpoint...
suspend...
Can not suspend VE: Device or resource busy
file on unsupported FS: magic 0bad1dea
Checkpointing failed
Error: Failed to suspend VE
Reason
The VE which you wish to migrate uses inotify mechanism (magic 0bad1dea), that is not supported by 028stab031 and older kernels.
Workaround
Update till 028stab035 or newer kernel.
