OpenVZ Forum


Home » General » Support » OpenVZ 7, option "bootorder" seems to have no effect when starting/stopping CT
Re: OpenVZ 7, option "bootorder" seems to have no effect when starting/stopping CT [message #53749 is a reply to message #53745] Thu, 27 May 2021 00:47 Go to previous message
devnull is currently offline  devnull
Messages: 20
Registered: May 2012
Junior Member
Hello!

Many thanks for your answer and sorry for the delay.

I have created a custom Bash script to start containers in the correct order.

But, because I cannot reboot the host just to test it, I will wait until it is really needed.

There are two steps to check:

1) iptables is locked while service firewalld (and/or iptables) are starting

=> I have disabled firewalled and removed saved rules for iptables service

2) vzlist -a and/or prlctl list -a can be "unstable" for a while (while booting)

=> it seems that IP adresses of containers are not available immediately (not atomic)

So, the "home-made" firewall script waits until all IP addresses (venet) are available and it launchs the custom script that starts containers.

If everything goes fine, I will post the code.

Have a great day!
 
Read Message
Read Message
Read Message
Previous Topic: logrotate duplicates for vz-event
Next Topic: pcompact errors during nightly cron
Goto Forum:
  


Current Time: Tue Aug 12 17:59:21 GMT 2025

Total time taken to generate the page: 0.84108 seconds