ALT Linux sysadmins discussion
 help / color / mirror / Atom feed
* [Sysadmins] OpenVZ VE dont start
@ 2018-06-09  7:35 Alexander Volkov
  2018-06-13  9:45 ` Alexander Volkov
  0 siblings, 1 reply; 4+ messages in thread
From: Alexander Volkov @ 2018-06-09  7:35 UTC (permalink / raw)
  To: ALT Linux sysadmins' discussion

Приветствую.
С марта не перезагружал ноду, P8, ядро alt162 из сизифа.
Сегодня при двух перезагрузках не стартуют контейнеры, точнее, стартуют и сразу стопаются:

Jun  9 04:06:55 vladregion vz: Bringing up interface venet0: succeeded
Jun  9 04:06:55 vladregion vz: Assigning IPv4 address to interface venet0: succeeded
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Jun  9 04:06:55 vladregion vz: Configuring interface venet0: succeeded
Jun  9 04:06:55 vladregion vzctl: Setting CPU units: 1000
Jun  9 04:06:55 vladregion vzctl: WARNING: Settings were not saved to config and will be lost after CT restart (use --save flag)
Jun  9 04:06:55 vladregion vz: Configuring cpuunits limit for VE0 to 1000: succeeded
Jun  9 04:06:55 vladregion vzctl: Starting container...
Jun  9 04:06:55 vladregion vzctl: WARNING: /var/lib/vz is mounted with data=writeback not recommended for ploop; please use data=ordered instead
Jun  9 04:06:55 vladregion vzctl: Opening delta /var/lib/vz/private/953/root.hdd/root.hdd
Jun  9 04:06:55 vladregion vzctl: Error in ploop_check (check.c:574): Dirty flag is set
Jun  9 04:06:55 vladregion vzctl: Adding delta dev=/dev/ploop46680 img=/var/lib/vz/private/953/root.hdd/root.hdd (rw)
Jun  9 04:06:55 vladregion kernel: [   55.277240]  ploop46680: p1
Jun  9 04:06:55 vladregion kernel: [   55.280389]  ploop46680: p1
Jun  9 04:06:55 vladregion kernel: [   55.282401] EXT4-fs (ploop46680p1): INFO: recovery required on readonly filesystem
Jun  9 04:06:55 vladregion kernel: [   55.282408] EXT4-fs (ploop46680p1): write access will be enabled during recovery
Jun  9 04:06:55 vladregion kernel: [   55.330853] EXT4-fs (ploop46680p1): recovery complete
Jun  9 04:06:55 vladregion kernel: [   55.331130] EXT4-fs (ploop46680p1): mounted filesystem with ordered data mode. Opts:
Jun  9 04:06:55 vladregion vzctl: Mounting /dev/ploop46680p1 at /var/lib/vz/root/953 fstype=ext4 data='balloon_ino=12,'
Jun  9 04:06:55 vladregion vzctl: Container is mounted
Jun  9 04:06:55 vladregion kernel: [   55.331460] EXT4-fs (ploop46680p1): loaded balloon from 12 (4947976 blocks)
Jun  9 04:06:55 vladregion kernel: [   55.383226] CT: 953: started
Jun  9 04:06:55 vladregion vzctl: Adding IP address(es): 192.168.100.253
Jun  9 04:06:55 vladregion vzctl: vps-net_add ERROR: Unable to get source ip [venet0]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Jun  9 04:06:55 vladregion vzctl: Killing container ...
Jun  9 04:06:55 vladregion vzctl: Container start failed (try to check kernel messages, e.g. "dmesg | tail")

я не знаю, что он там назначил при инициализации, но адреса нет. Назначаю руками, стартую VE - нормально запускаются.

Никто не ловил такое?


-- 
Regards, Alex



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Sysadmins] OpenVZ VE dont start
  2018-06-09  7:35 [Sysadmins] OpenVZ VE dont start Alexander Volkov
@ 2018-06-13  9:45 ` Alexander Volkov
  2018-06-14 12:12   ` Michael Shigorin
  0 siblings, 1 reply; 4+ messages in thread
From: Alexander Volkov @ 2018-06-13  9:45 UTC (permalink / raw)
  To: ALT Linux sysadmins' discussion



09.06.2018, 10:36, "Alexander Volkov" <alt@vladregion.ru>:
> Приветствую.
> С марта не перезагружал ноду, P8, ядро alt162 из сизифа.
> Сегодня при двух перезагрузках не стартуют контейнеры, точнее, стартуют и сразу стопаются:
>
> Jun 9 04:06:55 vladregion vz: Bringing up interface venet0: succeeded
> Jun 9 04:06:55 vladregion vz: Assigning IPv4 address to interface venet0: succeeded
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Jun 9 04:06:55 vladregion vz: Configuring interface venet0: succeeded
> Jun 9 04:06:55 vladregion vzctl: Setting CPU units: 1000
> Jun 9 04:06:55 vladregion vzctl: WARNING: Settings were not saved to config and will be lost after CT restart (use --save flag)
> Jun 9 04:06:55 vladregion vz: Configuring cpuunits limit for VE0 to 1000: succeeded
> Jun 9 04:06:55 vladregion vzctl: Starting container...
> Jun 9 04:06:55 vladregion vzctl: WARNING: /var/lib/vz is mounted with data=writeback not recommended for ploop; please use data=ordered instead
> Jun 9 04:06:55 vladregion vzctl: Opening delta /var/lib/vz/private/953/root.hdd/root.hdd
> Jun 9 04:06:55 vladregion vzctl: Error in ploop_check (check.c:574): Dirty flag is set
> Jun 9 04:06:55 vladregion vzctl: Adding delta dev=/dev/ploop46680 img=/var/lib/vz/private/953/root.hdd/root.hdd (rw)
> Jun 9 04:06:55 vladregion kernel: [ 55.277240] ploop46680: p1
> Jun 9 04:06:55 vladregion kernel: [ 55.280389] ploop46680: p1
> Jun 9 04:06:55 vladregion kernel: [ 55.282401] EXT4-fs (ploop46680p1): INFO: recovery required on readonly filesystem
> Jun 9 04:06:55 vladregion kernel: [ 55.282408] EXT4-fs (ploop46680p1): write access will be enabled during recovery
> Jun 9 04:06:55 vladregion kernel: [ 55.330853] EXT4-fs (ploop46680p1): recovery complete
> Jun 9 04:06:55 vladregion kernel: [ 55.331130] EXT4-fs (ploop46680p1): mounted filesystem with ordered data mode. Opts:
> Jun 9 04:06:55 vladregion vzctl: Mounting /dev/ploop46680p1 at /var/lib/vz/root/953 fstype=ext4 data='balloon_ino=12,'
> Jun 9 04:06:55 vladregion vzctl: Container is mounted
> Jun 9 04:06:55 vladregion kernel: [ 55.331460] EXT4-fs (ploop46680p1): loaded balloon from 12 (4947976 blocks)
> Jun 9 04:06:55 vladregion kernel: [ 55.383226] CT: 953: started
> Jun 9 04:06:55 vladregion vzctl: Adding IP address(es): 192.168.100.253
> Jun 9 04:06:55 vladregion vzctl: vps-net_add ERROR: Unable to get source ip [venet0]
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Jun 9 04:06:55 vladregion vzctl: Killing container ...
> Jun 9 04:06:55 vladregion vzctl: Container start failed (try to check kernel messages, e.g. "dmesg | tail")
>
> я не знаю, что он там назначил при инициализации, но адреса нет. Назначаю руками, стартую VE - нормально запускаются.
>
> Никто не ловил такое?
>

В общем, это раскомментированная запись
VE_ROUTE_SRC_DEV="venet0"
в /etc/vz/vz.conf

В момент поднятия службы на нём нет адреса.

-- 
Regards, Alex



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Sysadmins] OpenVZ VE dont start
  2018-06-13  9:45 ` Alexander Volkov
@ 2018-06-14 12:12   ` Michael Shigorin
  2018-06-14 12:53     ` Alexander Volkov
  0 siblings, 1 reply; 4+ messages in thread
From: Michael Shigorin @ 2018-06-14 12:12 UTC (permalink / raw)
  To: sysadmins

On Wed, Jun 13, 2018 at 12:45:32PM +0300, Alexander Volkov wrote:
> В общем, это раскомментированная запись
> VE_ROUTE_SRC_DEV="venet0"
> в /etc/vz/vz.conf
> 
> В момент поднятия службы на нём нет адреса.

Может, на http://altlinux.org/OpenVZ отметить?

-- 
 ---- WBR, Michael Shigorin / http://altlinux.org
  ------ http://opennet.ru / http://anna-news.info


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Sysadmins] OpenVZ VE dont start
  2018-06-14 12:12   ` Michael Shigorin
@ 2018-06-14 12:53     ` Alexander Volkov
  0 siblings, 0 replies; 4+ messages in thread
From: Alexander Volkov @ 2018-06-14 12:53 UTC (permalink / raw)
  To: ALT Linux sysadmins' discussion



14.06.2018, 15:12, "Michael Shigorin" <mike@altlinux.org>:
> On Wed, Jun 13, 2018 at 12:45:32PM +0300, Alexander Volkov wrote:
>>  В общем, это раскомментированная запись
>>  VE_ROUTE_SRC_DEV="venet0"
>>  в /etc/vz/vz.conf
>>
>>  В момент поднятия службы на нём нет адреса.
>
> Может, на http://altlinux.org/OpenVZ отметить?
>
Добавил абзац в замечания по использованию.

-- 
Regards, Alex



^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2018-06-14 12:53 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-06-09  7:35 [Sysadmins] OpenVZ VE dont start Alexander Volkov
2018-06-13  9:45 ` Alexander Volkov
2018-06-14 12:12   ` Michael Shigorin
2018-06-14 12:53     ` Alexander Volkov

ALT Linux sysadmins discussion

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/sysadmins/0 sysadmins/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 sysadmins sysadmins/ http://lore.altlinux.org/sysadmins \
		sysadmins@lists.altlinux.org sysadmins@lists.altlinux.ru sysadmins@lists.altlinux.com
	public-inbox-index sysadmins

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.sysadmins


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git