[05:52] <lordievader> Good morning
[11:18] <Hamidreza> Hi guys, I get blkid on my server and saw:
[11:18] <Hamidreza> UUID_SUB="5ff58eb8-9879e85a-e512-5cb9019340f4" TYPE="VMFS_volume_member"
[11:18] <Hamidreza> but it should be UUID ......
[11:18] <Hamidreza> and type of my disk should be xfs
[11:18] <Hamidreza> Now I enter mkfs.xfs /dev/sdb but it doesn't do anything/
[11:18] <Hamidreza> How can I fix my problem?
[16:23] <leftyfb> Does systemd-resolved in xenial not have a stub resolver? How does it work if we can't point to it (127.0.0.53)?
[16:23] <leftyfb> I'm trying to get local caching working on Ubuntu 16.04 using systemd-resolved
[16:25] <leftyfb> I have the service enabled and running and /etc/resolv.conf linked to /run/systemd/resolved/resolv.conf and a DNS= and DOAMINS= entry in /etc/systemd/resolved.conf since that info doesn't seem to get pulled from DHCP at all
[16:25] <leftyfb> what am I missing?
[16:31] <leftyfb> I notice resolved is listening on port 5355
[16:37] <leftyfb> it's not listening on port 53
[16:51] <ddstreet> leftyfb you should probably symlink to /run/systemd/resolved/stub-resolv.conf instead
[16:52] <ddstreet> sorry /run/systemd/resolve/stub-resolv.conf
[16:52] <leftyfb> ddstreet: there is no stub listener on 16.04
[16:52] <leftyfb> that file never gets created and the service is not listening on 53
[16:53] <ddstreet> you enabled systemd-resolved service?
[16:54] <ddstreet> ah yeah, in xenial the stub resolv.conf isn't created
[16:54] <ddstreet> you'll need to manually edit your resolv.conf then
[16:55] <ddstreet> it might not even work in xenial...
[16:57] <ddstreet> yeah it's missing a few things that would get it working, you could theoretically get it to work with some manual stuff but i'd recommend against it
[16:57] <ddstreet> i mean i wouldn't recommend using xenial at this point since it's going ESM this month... ;-)
[16:57] <leftyfb> well aware. We have updated to bionic and soon focal, but we still have some customers on xenial that we can't move off for some time
[16:58] <ddstreet> honestly if you need a local caching dns server on xenial, probably something else would be better, maybe dnsmasq
[17:01] <ddstreet> if you do want to manually get resovled working, you'd need to remove resolvconf, make dhclient not replace/update the resolv.conf file, change systemd-resolved to listen on :53 instead of :5355, tell systemd-resolved what the right upstream nameservers are (or get dhclient to notify it)
[17:02] <ddstreet> would not suggest it...too many things that might break