OpenVZ Forum


Home » International » Russian » venet0... failed (Determining IP information for venet0... failed)
venet0... failed [message #52836] Tue, 16 May 2017 07:41 Go to next message
needle is currently offline  needle
Messages: 2
Registered: May 2017
Junior Member
From: *sovintel.net
ifup venet0

Determining IP information for venet0... failed.
Linux ******* 2.6.32-042stab123.1 #1 SMP Wed Mar 22 15:21:30 MSK 2017 x86_64 x86_64 x86_64 GNU/Linux

service network restart
Shutting down interface vmbr0:                             [  OK  ]
Shutting down interface bond0.221:                         [  OK  ]
Shutting down interface bond0:                             [  OK  ]
Shutting down interface venet0:  Shutting down interface venet0: 
                                                           [  OK  ]
Shutting down loopback interface:                          [  OK  ]
Bringing up loopback interface:                            [  OK  ]
Bringing up interface bond0:  Determining if ip address *.*.*.* is already in use for device bond0...
RTNETLINK answers: Network is unreachable
RTNETLINK answers: Network is down
ifup-local ERROR: Unable to add route ip route add *.*.*.* dev venet0 
                                                           [  OK  ]
Bringing up interface venet0:  Bringing up interface venet0: 
Configuring interface venet0: 
net.ipv4.conf.venet0.send_redirects = 0
Configuring ipv6 venet0: 
RTNETLINK answers: Network is unreachable
                                                           [  OK  ]
Bringing up interface bond0.221:                           [  OK  ]
Bringing up interface vmbr0:  Determining if ip address *.*.*.* is already in use for device vmbr0...

в общем не работает venet0.
подскажите что можно посмотреть и в какую сторону лучше двигаться.
если понадобиться информация по "настройкам" пишите предоставлю.
Re: venet0... failed [message #52841 is a reply to message #52836] Wed, 17 May 2017 13:07 Go to previous message
needle is currently offline  needle
Messages: 2
Registered: May 2017
Junior Member
From: *sovintel.net
разобрался в чем была причина, можно закрывать(удалять)
Previous Topic: После перезагрузки сервера один контейнер завис
Next Topic: OpenVZ API получение дисковой квоты: выделено, занято, свободно.
Goto Forum:
  


Current Time: Mon Sep 25 08:14:23 GMT 2017