| Too many errors on container start [message #53775] |
Mon, 14 March 2022 06:51  |
mangust
Messages: 39
Registered: April 2008
Location: USA
|
Member |
|
|
It was lot of messages about usleep in OVZ8.
Now it is even more errors in startup scripts in OVZ9
I can only think about using > /dev/null 2>&1 as a remedy.
[root@node01 ~]# vzctl start 1301
Starting Container ...
Mount image: /vz/private/1301/root.hdd
Container is mounted
Setting permissions for image=/vz/private/1301/root.hdd
tune monotonic -786 285110074
tune boottime -786 285018640
Os release: 4.18.0
Setting permissions for image=/vz/private/1301/root.hdd
Cannot detect partition for /dev/dm-9700
Adding ip address(es): 10.1.3.1 fc00:0:1:3::1
awk: cmd. line:1: warning: regexp escape sequence `\ ' is not a known regexp operator
awk: cmd. line:1: warning: regexp escape sequence `\ ' is not a known regexp operator
awk: cmd. line:1: warning: regexp escape sequence `\ ' is not a known regexp operator
awk: cmd. line:1: warning: regexp escape sequence `\ ' is not a known regexp operator
awk: cmd. line:1: warning: regexp escape sequence `\ ' is not a known regexp operator
warning: usleep is deprecated, and will be removed in near future!
warning: use "sleep 1" instead...
warning: usleep is deprecated, and will be removed in near future!
warning: use "sleep 1" instead...
warning: usleep is deprecated, and will be removed in near future!
warning: use "sleep 0.1" instead...
warning: usleep is deprecated, and will be removed in near future!
warning: use "sleep 0.1" instead...
warning: usleep is deprecated, and will be removed in near future!
warning: use "sleep 0.1" instead...
warning: usleep is deprecated, and will be removed in near future!
warning: use "sleep 0.1" instead...
warning: usleep is deprecated, and will be removed in near future!
warning: use "sleep 0.1" instead...
warning: usleep is deprecated, and will be removed in near future!
warning: use "sleep 0.1" instead...
warning: usleep is deprecated, and will be removed in near future!
warning: use "sleep 0.1" instead...
warning: usleep is deprecated, and will be removed in near future!
warning: use "sleep 0.1" instead...
warning: usleep is deprecated, and will be removed in near future!
warning: use "sleep 0.1" instead...
warning: usleep is deprecated, and will be removed in near future!
warning: use "sleep 0.1" instead...
warning: usleep is deprecated, and will be removed in near future!
warning: use "sleep 0.1" instead...
sendto function returned error: Cannot assign requested address
sendto function returned error: Network is unreachable
sendto function returned error: Network is unreachable
warning: usleep is deprecated, and will be removed in near future!
warning: use "sleep 0.1" instead...
vz-net_add WARNING: /usr/sbin/ndsend fc00:0:1:3::1 virbr1 FAILED
vz-net_add WARNING: /usr/sbin/ndsend fc00:0:1:3::1 virbr0 FAILED
vz-net_add WARNING: /usr/sbin/ndsend fc00:0:1:3::1 br0 FAILED
Set hostname: pxy01.dxamedia.com
File resolv.conf was modified
Container start in progress...
Also after system bootup not all container are in the running state. About half of them are stopped after startup. Each time random.
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
