[systemd-devel] How can I view DHCP-PD information?

[沙包妖梦]

I can see "ppp0: DHCP: received delegated prefix xx" from
systemd-networkd log output, can I get the prefix by using networkctl or
something else?

[systemd-devel] Failed to restart xxxx.service: "Unit tmp.mount is masked"

[沙包妖梦]

Hello, and help, I ran into an issue for several times. I don't know when
and why it happen.

When I want to restart some service, it sais: "Failed to start
xx.service: Unit .mount is masked".
.mount has "RequiresMountsFor" or "PrivateTmp".
When this happens, I will see ALL mountpoint units is masked by "systemctl
status *.mount". (except something like sys-kernel-config.mount)

For example, this time I found my *qbittorrent *is crashed and not auto
restart, so I run "systemctl restart qbittorrent":

> Failed to restart qbittorrent.service: Unit tmp.mount is masked.
>

`systemctl status tmp.mount` shows:

> ● tmp.mount - /tmp
>Loaded: masked (Reason: Unit tmp.mount is masked.)
>Active: active (mounted) since Mon 2019-09-23 00:05:27 CST; 6 days ago
> Where: /tmp
>  What: tmpfs
> Tasks: 0 (limit: 4915)
>Memory: 116.0K
>CGroup: /system.slice/tmp.mount
>

 Then I found every mount unit "is masked", eg:

> ● data-AppData.mount - /data/AppData
>Loaded: masked (Reason: Unit data-AppData.mount is masked.)
>Active: active (mounted) since Mon 2019-09-23 00:05:37 CST; 6 days ago
> Where: /data/AppData
>  What: /dev/mapper/virtual-storage
> Tasks: 0 (limit: 4915)
>Memory: 332.0K
>CGroup: /system.slice/data-AppData.mount
>

I can unmount, remount, r/w. everything seems ok.
I can't restart any service depends on "/data/AppData", like my custom
*homedns-machine.service*, because it has "RequiresMountsFor=/data/AppData"
The service run without problem, but after I stopped it, systemctl refuse
to start.
I can start the service if I comment out "RequiresMountsFor" and reload it.

"systemctl unmask tmp.mount" return 0 with no output. But "systemctl
status" output not change. It still "masked".
Everytime I can only restart my server.

*Anyone know how to fix this?*

systemctl --version

> systemd 241 (v241-12.git1e19bcd.fc30)
> +PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP
> +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN
> +PCRE2 default-hierarchy=hybrid

cat /etc/system-release

> Fedora release 30 (Thirty)

 uname -a

> Linux server.home.gongt.me 5.2.15-200.fc30.x86_64 #1 SMP Mon Sep 16
> 15:17:36 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] Q: Can I use nspawn & networkd with existing bridge network?

[沙包妖梦]

I already have a bridge network bridge0 on my host. It includes a physical
interface connected to a router.
Then I start my container with --network-bridge=bridge0
My container will get a ip address from the router, but it seems never
renew.

For debug, I change my router's DHCP Leasetime to 2 minutes. Then start
container.
machinectl show my container IP is 192.168.1.*.
After few minuets, run machinectl again, it change to 169.254.xxx.xxx. I
can not ping this address.

Do I need some extra configure to use an existing bridge?
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel