Я выполняю 18.04.4 LTS с HWE.
После перезагрузки я должен вручную работать "sudo netplan, применяются" для установки статического IP, описанного в 50 облаках init.yaml:
network:
ethernets:
renderer: networkd
enp0s25:
dhcp4: no
optional: false
addresses: [172.28.1.99/24]
gateway4: 172.28.1.1
nameservers:
addresses: [172.28.1.99, 172.28.1.1]
version: 2
Я вижу много сообщений, говорящих о пропуске ожидания сети для становления доступным, но ничто о том, как осуществить ожидание сети.
Так, сразу после того, как я вхожу в систему, я могу netplan применяться и несколько секунд спустя, статический IP применяется, и карта возросла.
При рассмотрении journalctl - без пейджеров - лютеций systemd-networkd, существует только "Разрешение, отклоненное" ошибки во время начальной загрузки...
-- Reboot --
Feb 04 20:10:52 lei systemd[1]: Starting Network Service...
Feb 04 20:10:52 lei systemd-networkd[935]: Failed to connect to bus: Permission denied
Feb 04 20:10:52 lei systemd-networkd[935]: Could not connect to bus: Permission denied
Feb 04 20:10:52 lei systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=1/FAILURE
Feb 04 20:10:52 lei systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
Feb 04 20:10:52 lei systemd[1]: Failed to start Network Service.
Feb 04 20:10:52 lei systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart.
Feb 04 20:10:52 lei systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 1.
Feb 04 20:10:52 lei systemd[1]: Stopped Network Service.
Feb 04 20:10:52 lei systemd[1]: Starting Network Service...
Feb 04 20:10:52 lei systemd-networkd[936]: Failed to connect to bus: Permission denied
Feb 04 20:10:52 lei systemd-networkd[936]: Could not connect to bus: Permission denied
Feb 04 20:10:52 lei systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=1/FAILURE
Feb 04 20:10:52 lei systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
Feb 04 20:10:52 lei systemd[1]: Failed to start Network Service.
Feb 04 20:10:52 lei systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart.
Feb 04 20:10:52 lei systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 2.
Feb 04 20:10:52 lei systemd[1]: Stopped Network Service.
Feb 04 20:10:52 lei systemd[1]: Starting Network Service...
Feb 04 20:10:52 lei systemd-networkd[938]: Failed to connect to bus: Permission denied
Feb 04 20:10:52 lei systemd-networkd[938]: Could not connect to bus: Permission denied
Feb 04 20:10:52 lei systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=1/FAILURE
Feb 04 20:10:52 lei systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
Feb 04 20:10:52 lei systemd[1]: Failed to start Network Service.
Feb 04 20:10:52 lei systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart.
Feb 04 20:10:52 lei systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 3.
Feb 04 20:10:52 lei systemd[1]: Stopped Network Service.
Feb 04 20:10:52 lei systemd[1]: Starting Network Service...
Feb 04 20:10:52 lei systemd-networkd[939]: Failed to connect to bus: Permission denied
Feb 04 20:10:52 lei systemd-networkd[939]: Could not connect to bus: Permission denied
Feb 04 20:10:52 lei systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=1/FAILURE
Feb 04 20:10:52 lei systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
Feb 04 20:10:52 lei systemd[1]: Failed to start Network Service.
Feb 04 20:10:52 lei systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart.
Feb 04 20:10:52 lei systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 4.
Feb 04 20:10:52 lei systemd[1]: Stopped Network Service.
Feb 04 20:10:52 lei systemd[1]: Starting Network Service...
Feb 04 20:10:52 lei systemd-networkd[940]: Failed to connect to bus: Permission denied
Feb 04 20:10:52 lei systemd-networkd[940]: Could not connect to bus: Permission denied
Feb 04 20:10:52 lei systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=1/FAILURE
Feb 04 20:10:52 lei systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
Feb 04 20:10:52 lei systemd[1]: Failed to start Network Service.
Feb 04 20:10:52 lei systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart.
Feb 04 20:10:52 lei systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 5.
Feb 04 20:10:52 lei systemd[1]: Stopped Network Service.
Feb 04 20:10:52 lei systemd[1]: systemd-networkd.service: Start request repeated too quickly.
Feb 04 20:10:52 lei systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
Feb 04 20:10:52 lei systemd[1]: Failed to start Network Service.
Затем записи от того, когда я сделал netplan, применяются...
Feb 04 20:11:49 lei systemd[1]: Starting Network Service...
Feb 04 20:11:49 lei systemd-networkd[2856]: Enumeration completed
Feb 04 20:11:49 lei systemd[1]: Started Network Service.
Feb 04 20:11:49 lei systemd-networkd[2856]: lo: Link is not managed by us
Feb 04 20:11:53 lei systemd-networkd[2856]: enp0s25: Gained carrier
Feb 04 20:11:54 lei systemd-networkd[2856]: enp0s25: Gained IPv6LL
Feb 04 20:11:54 lei systemd-networkd[2856]: enp0s25: Configured
Я реализовал более трудную конфигурацию .yaml, как рекомендуется heynnema, и все еще имейте те же результаты. netplan - отладка генерирует, возвратился:
root@l:/etc/netplan# netplan --debug generate
DEBUG:command generate: running ['/lib/netplan/generate']
** (generate:22264): DEBUG: 21:54:44.867: Processing input file /etc/netplan/50-cloud-init.yaml..
** (generate:22264): DEBUG: 21:54:44.867: starting new processing pass
** (generate:22264): DEBUG: 21:54:44.868: enp0s25: setting default backend to 1
** (generate:22264): DEBUG: 21:54:44.868: Configuration is valid
** (generate:22264): DEBUG: 21:54:44.868: Generating output files..
** (generate:22264): DEBUG: 21:54:44.868: NetworkManager: definition enp0s25 is not for us (backend 1)
На перезагрузке у меня все еще нет статического IP, пока я вручную не выполняюсь, netplan применяются...
dparks@l:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp0s25: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether d0:50:99:67:5e:2b brd ff:ff:ff:ff:ff:ff
dparks@l:~$
dparks@l:~$ sudo netplan apply
[sudo] password for dparks:
dparks@l:~$
dparks@l:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether d0:50:99:67:5e:2b brd ff:ff:ff:ff:ff:ff
inet 172.28.1.99/24 brd 172.28.1.255 scope global enp0s25
valid_lft forever preferred_lft forever
inet6 fe80::d250:99ff:fe67:5e2b/64 scope link
valid_lft forever preferred_lft forever
/etc/systemd/network пусто:
dparks@l:~$ ls -al /etc/systemd/network
total 8
drwxr-xr-x 2 root root 4096 Apr 20 2018 .
drwxr-xr-x 5 root root 4096 Feb 6 06:18 ..
Эта проблема была полна решимости быть проблемой полномочий о корневой папке:
dr-xr-x--x 26 root root 4096 Feb 4 20:09 /
Исправление к 0755 решило вопрос, и netplan применяется правильно при начальной загрузке.
drwxr-xr-x 26 root root 4096 Feb 4 20:09 /
Файлы .yaml являются очень суетливыми о добавлении отступа, интервале и никаких вкладках.
Предположение, что Вы используете Сервер Ubuntu...
Используйте этот .yaml файл...
network:
renderer: networkd
version: 2
ethernets:
enp0s25:
addresses: [172.28.1.99/24]
gateway4: 172.28.1.1
nameservers:
addresses: [172.28.1.99, 172.28.1.1]
Затем:
sudo netplan --debug generate
# генерируйте файлы конфигурации
sudo netplan apply
# примените новую конфигурацию
reboot
# из-за статического адреса