<br><br><div class="gmail_quote">On 24 July 2013 00:49, Benjamin Henrion <span dir="ltr"><<a href="mailto:bh@udev.org" target="_blank">bh@udev.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5">On Tue, Jul 16, 2013 at 3:17 AM, Kir Kolyshkin <<a href="mailto:kir@openvz.org">kir@openvz.org</a>> wrote:<br>
> On 15 July 2013 05:29, Benjamin Henrion <<a href="mailto:bh@udev.org">bh@udev.org</a>> wrote:<br>
>><br>
>> Hi,<br>
>><br>
>> Any idea how to ignore "Dump file /vz/dump/Dump.3030 exists, trying to<br>
>> restore from it"?<br>
><br>
><br>
> Well, it is ignored. As you can see below, vzctl start found the dump file<br>
> and tried restoring<br>
> from it (instead of starting from scratch). Since restoring failed, vzctl<br>
> started the container<br>
> in a usual manner.<br>
><br>
>><br>
>><br>
>> If I do not set the avlue DUMPDIR in /etc/vz/vz.conf, does it ignores<br>
>> this dump file?<br>
><br>
><br>
> No, in this case a built-in dumpdir value is used as far as I remember.<br>
> Check the sources to find out for sure.<br>
><br>
>><br>
>><br>
>> I had to remove the file by hand to rescue my vz.<br>
><br>
><br>
> What do you mean? As I explained above (and as you can see below) container<br>
> is still started, with vzctl start ignoring the unsuccessful restore<br>
> attempt.<br>
><br>
>><br>
>><br>
>> * 14:22 root@hn /vz/dump# vzctl restart 3030<br>
>> Restarting container<br>
>> Stopping container ...<br>
>> Container was stopped<br>
>> Container is unmounted<br>
>> Dump file /vz/dump/Dump.3030 exists, trying to restore from it<br>
>> Restoring container ...<br>
>> Container is mounted<br>
>> undump...<br>
>> Setting CPU units: 1000<br>
>> Setting CPUs: 16<br>
>> Configure veth devices: veth303.1 veth303.0 veth303.2<br>
>> Adding interface veth303.1 to bridge vzbr0 on CT0 for CT3030<br>
>> Adding interface veth303.0 to bridge vzbr0 on CT0 for CT3030<br>
>> Adding interface veth303.2 to bridge vzbr0 on CT0 for CT3030<br>
>> Error: undump failed: No such file or directory<br>
>> Restoring failed:<br>
>> Error: rst_open_file: failed to lookup path '/var/nagios/nagios.lock': -2<br>
>> Error: can't open file /var/nagios/nagios.lock<br>
>> Error: rst_file: -2 753032<br>
>> Error: rst_files: -2<br>
>> Error: make_baby: -2<br>
>> Error: rst_clone_children<br>
>> Error: make_baby: -2<br>
>> Error: rst_clone_children<br>
>> Container restore failed<br>
>> Starting container...<br>
>> Setting CPU units: 1000<br>
>> Setting CPUs: 16<br>
>> Configure veth devices: veth303.1 veth303.0 veth303.2<br>
>> Adding interface veth303.1 to bridge vzbr0 on CT0 for CT3030<br>
>> Adding interface veth303.0 to bridge vzbr0 on CT0 for CT3030<br>
>> Adding interface veth303.2 to bridge vzbr0 on CT0 for CT3030<br>
>> Container start in progress...<br>
>><br>
>> * 14:23 root@hn /vz/dump# rm /vz/dump/Dump.3030<br>
>><br>
>> * 14:24 root@hn /vz/dump# vzctl restart 3030<br>
>> Restarting container<br>
>> Stopping container ...<br>
>> Container was stopped<br>
>> Container is unmounted<br>
>> Starting container...<br>
>> Container is mounted<br>
>> Setting CPU units: 1000<br>
>> Setting CPUs: 16<br>
>> Configure veth devices: veth303.1 veth303.0 veth303.2<br>
>> Adding interface veth303.1 to bridge vzbr0 on CT0 for CT3030<br>
>> Adding interface veth303.0 to bridge vzbr0 on CT0 for CT3030<br>
>> Adding interface veth303.2 to bridge vzbr0 on CT0 for CT3030<br>
>> Container start in progress...<br>
>><br>
>> * 14:24 root@hn-a231 /vz/dump#<br>
><br>
><br>
><br>
> Which vzctl version is that? (Yes, please, whenever you are talking about<br>
> vzctl, specify its version)<br>
><br>
> I remember that some recent version deletes a dump file on start in any<br>
> case, because:<br>
> - if a container is restored from that file, it is no longer needed;<br>
> - if a container can't be restored from that file, it is a bad file.<br>
><br>
> This functionality appears in vzctl 4.3, as noted in its changelog:<br>
><br>
>> vzctl start: remove dumpfile on successful start<br>
><br>
> For the reference, the git commit in question is this one:<br>
> <a href="http://git.openvz.org/?p=vzctl;a=commitdiff;h=eca2ff0" target="_blank">http://git.openvz.org/?p=vzctl;a=commitdiff;h=eca2ff0</a><br>
<br>
</div></div>Just setting:<br>
<br>
VE_STOP_MODE="stop" in /etc/vz/vz.conf<br>
<br>
seems to be enough to get rid of Suspend mode.</blockquote><div><br></div><div><br></div><div>That is right, but it was not what you were asking about.</div><div><br></div><div>Also, I have answered all your questions, could you please answer mine?</div>
</div>