При перезапуске сетевых интерфейсов отказываeт dhcp

[oermolaev]

Про перезапуск сетевых интерфейсов тем прочитано не мало, однако вынужден начать свою.
Итак, при перезапуске сетевых интерфейсов любым способом, в том числе и

Код: [Выделить]

ifdown -a ; ifup -a отказывают службы ntpd и isc-dhcp-server. Возможно и другие, но на виду пока только эти.
На самом сервере обе службы по запросу статуса в состоянии "is running."
И, если с isc-dhcp-server помогает force-reload, то с ntp - только полная перезагрузка.
Поправка: во всех случаях помогает только полная перезагрузка.
Ещё одна поправка: force-reload всё-таки помогает

Полагаю, это не нормально? Какие будут идеи?

[PyMbIH]

отказывают службы ntpd и isc-dhcp-server. Возможно и другие, но на виду пока только эти.
На самом сервере обе службы по запросу статуса в состоянии "is running."

Сразу говорю, что я новичок.
Но я три раза перечитал ваше сообщение. Так и не понял в каком моменте службы "отказывают", если они в состоянии "is running"?
Вы бы хотели, чтобы при выключении сетевых интерфейсов эти службы становились "inactive (dead)"?

[danilsl]

Было подобное с dnsmasq. Думаю это убунтовская фишка и перезапуск нужно настраивать в upstart. Ну иначе нафига нужно было ломать нормальных демонов?
В моём случае проблема решилась сносом репозиторного dnsmasq и сборкой из исходников версии с родного сайта

[oermolaev]

PyMbIH,

не понял в каком моменте службы "отказывают", если они в состоянии "is running"?

Службы отказывают клиенту.
Вот как это выглядит когда сервер обслуживает клиента:

(Нажмите, чтобы показать/скрыть)

Код: [Выделить]

Feb 15 14:37:21 x2gosrv dhclient: Internet Systems Consortium DHCP Client 4.2.4
Feb 15 14:37:21 x2gosrv dhclient: Copyright 2004-2012 Internet Systems Consortium.
Feb 15 14:37:21 x2gosrv dhclient: All rights reserved.
Feb 15 14:37:21 x2gosrv dhclient: For info, please visit https://www.isc.org/software/dhcp/
Feb 15 14:37:21 x2gosrv dhclient:
Feb 15 14:37:21 x2gosrv dhclient: Listening on LPF/eth0/a2:55:bd:8f:28:6b
Feb 15 14:37:21 x2gosrv dhclient: Sending on   LPF/eth0/a2:55:bd:8f:28:6b
Feb 15 14:37:21 x2gosrv dhclient: Sending on   Socket/fallback
Feb 15 14:37:21 x2gosrv dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 (xid=0x5f2b214c)
Feb 15 14:37:21 x2gosrv dhclient: DHCPREQUEST of 192.168.36.180 on eth0 to 255.255.255.255 port 67 (xid=0x5f2b214c)
Feb 15 14:37:21 x2gosrv dhclient: DHCPOFFER of 192.168.36.180 from 192.168.36.1
Feb 15 14:37:21 x2gosrv dhclient: DHCPACK of 192.168.36.180 from 192.168.36.1
Feb 15 14:37:21 x2gosrv dhclient: bound to 192.168.36.180 -- renewal in 1745 seconds.

И вот как выглядит когда отказывает:

(Нажмите, чтобы показать/скрыть)

Код: [Выделить]

Feb 15 14:01:04 x2gosrv dhclient: Internet Systems Consortium DHCP Client 4.2.4
Feb 15 14:01:04 x2gosrv dhclient: Copyright 2004-2012 Internet Systems Consortium.
Feb 15 14:01:04 x2gosrv dhclient: All rights reserved.
Feb 15 14:01:04 x2gosrv dhclient: For info, please visit https://www.isc.org/software/dhcp/
Feb 15 14:01:04 x2gosrv dhclient:
Feb 15 14:01:04 x2gosrv dhclient: Listening on LPF/eth0/a2:55:bd:8f:28:6b
Feb 15 14:01:04 x2gosrv dhclient: Sending on   LPF/eth0/a2:55:bd:8f:28:6b
Feb 15 14:01:04 x2gosrv dhclient: Sending on   Socket/fallback
Feb 15 14:01:04 x2gosrv dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 (xid=0xa135546)
Feb 15 14:01:07 x2gosrv dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6 (xid=0xa135546)
Feb 15 14:01:13 x2gosrv dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15 (xid=0xa135546)
Feb 15 14:01:28 x2gosrv dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 20 (xid=0xa135546)
Feb 15 14:01:48 x2gosrv dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 21 (xid=0xa135546)
Feb 15 14:02:09 x2gosrv dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17 (xid=0xa135546)
Feb 15 14:02:26 x2gosrv dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14 (xid=0xa135546)
Feb 15 14:02:40 x2gosrv dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15 (xid=0xa135546)
Feb 15 14:02:55 x2gosrv dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 (xid=0xa135546)
Feb 15 14:03:03 x2gosrv dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11 (xid=0xa135546)
Feb 15 14:03:14 x2gosrv dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18 (xid=0xa135546)

[AnrDaemon]

А что на сервере то в это время?

[oermolaev]

На сервере

(Нажмите, чтобы показать/скрыть)

Код: [Выделить]

~# tail -f /var/log/syslog
Feb 16 00:28:42 proxdeb dhcpd: DHCPREQUEST for 192.168.36.182 from 1e:a9:98:63:9a:fe via vmbr1
Feb 16 00:28:42 proxdeb dhcpd: DHCPACK on 192.168.36.182 to 1e:a9:98:63:9a:fe via vmbr1
Feb 16 00:31:01 proxdeb dhcpd: uid lease 192.168.36.131 for client 78:e4:00:68:58:65 is duplicate on 192.168.36.0/24
Feb 16 00:31:01 proxdeb dhcpd: DHCPREQUEST for 192.168.36.12 from 78:e4:00:68:58:65 via vmbr1
Feb 16 00:31:01 proxdeb dhcpd: DHCPACK on 192.168.36.12 to 78:e4:00:68:58:65 via vmbr1
Feb 16 00:31:37 proxdeb named[68669]: client 192.168.36.21#54643: update '36.168.192.in-addr.arpa/IN' denied
Feb 16 00:31:52 proxdeb dhcpd: DHCPINFORM from 192.168.36.12 via vmbr1
Feb 16 00:31:52 proxdeb dhcpd: DHCPACK to 192.168.36.12 (78:e4:00:68:58:65) via vmbr1
Feb 16 00:33:07 proxdeb dhcpd: DHCPINFORM from 192.168.36.12 via vmbr1
Feb 16 00:33:07 proxdeb dhcpd: DHCPACK to 192.168.36.12 (78:e4:00:68:58:65) via vmbr1
Feb 16 00:35:08 proxdeb dhcpd: DHCPREQUEST for 192.168.36.143 from 50:e5:49:40:10:bb (computer) via vmbr1
Feb 16 00:35:08 proxdeb dhcpd: DHCPACK on 192.168.36.143 to 50:e5:49:40:10:bb (computer) via vmbr1
Feb 16 00:35:12 proxdeb dhcpd: DHCPREQUEST for 192.168.36.143 from 50:e5:49:40:10:bb (computer) via vmbr1
Feb 16 00:35:12 proxdeb dhcpd: DHCPACK on 192.168.36.143 to 50:e5:49:40:10:bb (computer) via vmbr1
Feb 16 00:35:16 proxdeb dhcpd: DHCPINFORM from 192.168.36.143 via vmbr1
Feb 16 00:35:16 proxdeb dhcpd: DHCPACK to 192.168.36.143 (50:e5:49:40:10:bb) via vmbr1
Feb 16 00:35:35 proxdeb dhcpd: DHCPINFORM from 192.168.36.12 via vmbr1
Feb 16 00:35:35 proxdeb dhcpd: DHCPACK to 192.168.36.12 (78:e4:00:68:58:65) via vmbr1
Feb 16 00:36:04 proxdeb pvedaemon[72017]: worker exit
Feb 16 00:36:04 proxdeb pvedaemon[2596]: worker 72017 finished
Feb 16 00:36:04 proxdeb pvedaemon[2596]: starting 1 worker(s)
Feb 16 00:36:04 proxdeb pvedaemon[2596]: worker 89014 started
Feb 16 00:37:02 proxdeb named[68669]: received control channel command 'reconfig'
Feb 16 00:37:02 proxdeb named[68669]: loading configuration from '/etc/bind/named.conf'
Feb 16 00:37:02 proxdeb named[68669]: reading built-in trusted keys from file '/etc/bind/bind.keys'
Feb 16 00:37:02 proxdeb named[68669]: using default UDP/IPv4 port range: [1024, 65535]
Feb 16 00:37:02 proxdeb named[68669]: using default UDP/IPv6 port range: [1024, 65535]
Feb 16 00:37:02 proxdeb named[68669]: sizing zone task pool based on 7 zones
Feb 16 00:37:02 proxdeb named[68669]: Warning: 'empty-zones-enable/disable-empty-zone' not set: disabling RFC 1918 empty zones
Feb 16 00:37:02 proxdeb named[68669]: reloading configuration succeeded
Feb 16 00:37:02 proxdeb named[68669]: any newly configured zones are now loaded
Feb 16 00:37:02 proxdeb kernel: vmbr1: port 7(veth182.0) entering disabled state
Feb 16 00:37:02 proxdeb kernel: vmbr1: port 6(veth180.0) entering disabled state
Feb 16 00:37:02 proxdeb kernel: vmbr1: port 5(veth159.0) entering disabled state
Feb 16 00:37:02 proxdeb kernel: vmbr1: port 4(veth155.0) entering disabled state
Feb 16 00:37:02 proxdeb kernel: vmbr1: port 3(veth151.0) entering disabled state
Feb 16 00:37:02 proxdeb kernel: vmbr1: port 2(veth100.0) entering disabled state
Feb 16 00:37:02 proxdeb kernel: vmbr1: port 1(eth1) entering disabled state
Feb 16 00:37:02 proxdeb dhcpd: receive_packet failed on vmbr1: Network is down
Feb 16 00:37:02 proxdeb kernel: device eth1 left promiscuous mode
Feb 16 00:37:02 proxdeb kernel: vmbr1: port 1(eth1) entering disabled state
Feb 16 00:37:02 proxdeb kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready
Feb 16 00:37:02 proxdeb kernel: device veth182.0 left promiscuous mode
Feb 16 00:37:02 proxdeb kernel: vmbr1: port 7(veth182.0) entering disabled state
Feb 16 00:37:02 proxdeb kernel: device veth180.0 left promiscuous mode
Feb 16 00:37:02 proxdeb kernel: vmbr1: port 6(veth180.0) entering disabled state
Feb 16 00:37:02 proxdeb kernel: device veth159.0 left promiscuous mode
Feb 16 00:37:02 proxdeb kernel: vmbr1: port 5(veth159.0) entering disabled state
Feb 16 00:37:02 proxdeb kernel: device veth155.0 left promiscuous mode
Feb 16 00:37:02 proxdeb kernel: vmbr1: port 4(veth155.0) entering disabled state
Feb 16 00:37:02 proxdeb kernel: device veth151.0 left promiscuous mode
Feb 16 00:37:02 proxdeb kernel: vmbr1: port 3(veth151.0) entering disabled state
Feb 16 00:37:02 proxdeb kernel: device veth100.0 left promiscuous mode
Feb 16 00:37:02 proxdeb kernel: vmbr1: port 2(veth100.0) entering disabled state
Feb 16 00:37:03 proxdeb kernel: device eth1 entered promiscuous mode
Feb 16 00:37:03 proxdeb kernel: ATL1E 0000:01:00.0: irq 27 for MSI/MSI-X
Feb 16 00:37:03 proxdeb kernel: ATL1E 0000:01:00.0: ATL1E: eth1 NIC Link is Up<100 Mbps Full Duplex>
Feb 16 00:37:03 proxdeb kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready
Feb 16 00:37:03 proxdeb kernel: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Feb 16 00:37:03 proxdeb kernel: vmbr1: port 1(eth1) entering forwarding state
Feb 16 00:37:03 proxdeb named[68669]: received control channel command 'reconfig'
Feb 16 00:37:03 proxdeb named[68669]: loading configuration from '/etc/bind/named.conf'
Feb 16 00:37:03 proxdeb named[68669]: reading built-in trusted keys from file '/etc/bind/bind.keys'
Feb 16 00:37:03 proxdeb named[68669]: using default UDP/IPv4 port range: [1024, 65535]
Feb 16 00:37:03 proxdeb named[68669]: using default UDP/IPv6 port range: [1024, 65535]
Feb 16 00:37:03 proxdeb named[68669]: sizing zone task pool based on 7 zones
Feb 16 00:37:03 proxdeb named[68669]: Warning: 'empty-zones-enable/disable-empty-zone' not set: disabling RFC 1918 empty zones
Feb 16 00:37:03 proxdeb named[68669]: reloading configuration succeeded
Feb 16 00:37:03 proxdeb named[68669]: any newly configured zones are now loaded
Feb 16 00:37:04 proxdeb ntpd[2290]: Deleting interface #6 vmbr1, fe80::224:8cff:fe6f:df80#123, interface stats: received=0, sent=0, dropped=0, active_time=8343 secs
Feb 16 00:37:04 proxdeb ntpd[2290]: peers refreshed
Feb 16 00:37:06 proxdeb ntpd[2290]: Listen normally on 15 vmbr1 fe80::224:8cff:fe6f:df80 UDP 123
Feb 16 00:37:06 proxdeb ntpd[2290]: peers refreshed
Feb 16 00:37:13 proxdeb kernel: vmbr1: no IPv6 routers present
Feb 16 00:37:41 proxdeb pveproxy[81587]: worker exit
Feb 16 00:37:41 proxdeb pveproxy[2624]: worker 81587 finished
Feb 16 00:37:41 proxdeb pveproxy[2624]: starting 1 worker(s)
Feb 16 00:37:41 proxdeb pveproxy[2624]: worker 90089 started
Feb 16 00:39:09 proxdeb kernel: eth0: no IPv6 routers present
Feb 16 00:40:04 proxdeb pvedaemon[74522]: worker exit
Feb 16 00:40:04 proxdeb pvedaemon[2596]: worker 74522 finished
Feb 16 00:40:04 proxdeb pvedaemon[2596]: starting 1 worker(s)
Feb 16 00:40:04 proxdeb pvedaemon[2596]: worker 91591 started
Feb 16 00:41:12 proxdeb pvedaemon[91591]: <root@pam> successful auth for user 'root@pam'
Feb 16 00:41:56 proxdeb pvedaemon[76114]: worker exit
Feb 16 00:41:56 proxdeb pvedaemon[2596]: worker 76114 finished
Feb 16 00:41:56 proxdeb pvedaemon[2596]: starting 1 worker(s)
Feb 16 00:41:56 proxdeb pvedaemon[2596]: worker 92659 started


На другой машине в это же время:

(Нажмите, чтобы показать/скрыть)

Код: [Выделить]

/# ifdown eth0; ifup eth0
Internet Systems Consortium DHCP Client 4.2.4
Copyright 2004-2012 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/a2:55:bd:8f:28:6b
Sending on   LPF/eth0/a2:55:bd:8f:28:6b
Sending on   Socket/fallback
DHCPRELEASE on eth0 to 192.168.36.1 port 67 (xid=0x8e013a2)
reload: Unknown instance:
invoke-rc.d: initscript smbd, action "reload" failed.
Internet Systems Consortium DHCP Client 4.2.4
Copyright 2004-2012 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/a2:55:bd:8f:28:6b
Sending on   LPF/eth0/a2:55:bd:8f:28:6b
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 (xid=0x2356db91)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 (xid=0x2356db91)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 (xid=0x2356db91)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 (xid=0x2356db91)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 (xid=0x2356db91)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15 (xid=0x2356db91)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 (xid=0x2356db91)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 (xid=0x2356db91)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 (xid=0x2356db91)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 21 (xid=0x2356db91)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 (xid=0x2356db91)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12 (xid=0x2356db91)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18 (xid=0x2356db91)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 (xid=0x2356db91)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14 (xid=0x2356db91)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12 (xid=0x2356db91)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13 (xid=0x2356db91)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16 (xid=0x2356db91)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12 (xid=0x2356db91)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 (xid=0x2356db91)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16 (xid=0x2356db91)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16 (xid=0x2356db91)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15 (xid=0x2356db91)

[AnrDaemon]

Мне кажется, или у вас слишком много всего наворочено?…

[oermolaev]

Ещё одна поправка: force-reload всё-таки помогает...

(Нажмите, чтобы показать/скрыть)

Мне кажется, или у вас слишком много всего наворочено?…

ничего особенного, на "коробочный" дистрибутив proxmox навешены настройки bind9, isc-dhcp-server, ntpd, iptables..

При ручном перезапуске интерфейсов всё "раскорячивается", но я нашел варианты как всё восстановить без перезагрузки. Как я понимаю, проблема в очередности поднятия служб.. или маршрутов..
Возможно проблема только в dhcp.