[03:09] <keithzg[m]> Sven_vB: Yeah, I was vaguely thinking about doing such wrapper-script filtering. Instead decided to just install https://packages.debian.org/sid/all/s3cmd which seems to be new enough to avoid the problem (and, with S3 always subtly shifting, it's nice to be on the latest version anyways)
[03:10] <Sven_vB> :) good that you found it
[03:11] <keithzg[m]> Normally I'd be a bit more wary about crossing releases/distros like that, but it's just to-be-interpreted Python text anyways, so I figure it's probably fine :)
[03:12] <keithzg[m]> (So confident I didn't even bother grabbing the deb from the Groovy repos, heh)
[07:26] <lordievader> Good morning
[16:13] <xibalba> my home ubuntu box has ~800 processes right now, and so many of them appear to be related to ZFS even though i'm not using any ZFS on this system. processes like z_iput (129 processes), z_fr_iss_* (97), arc_prune (129). not sure what's going on here, just started looking into it
[16:25] <foo> Trying to get pihole running. Something else is listening on port 53. I had it running before but apparently something changed. I thought netstat -nap |grep :53 would show me what's running, but I'm not able to clearly see it. bind and named not running.
[16:26] <foo> This is the error: ERROR: for pihole  Cannot start service pihole: driver failed programming external connectivity on endpoint pihole (b045e64594c66786472712e8689802c00e4e69d1042ccf05765e10c52db7a299): Error starting userland proxy: listen tcp 0.0.0.0:53: bind: address already in use
[16:28] <foo> ah, got it service dbus-org.freedesktop.resolve1 stop
[17:03]  * foo works to turn off dbus-org.freedesktop.resolve1 at boot time
[17:14] <foo> How do I disable a service in systemd?
[17:14] <foo> Having some internet issues and googling is making this difficult
[17:16] <oerheks> systemctrl enable/disable/mask/unmask <service>
[17:21] <foo> oerheks: thanks, something else is going on here it would seem
[17:22] <foo> Error starting userland proxy: listen tcp 0.0.0.0:53: bind: address already in use
[17:22] <foo> Getting that but nothing is running on :53
[17:23] <foo> netstat -nap |grep :53 shows nothing
[17:23] <foo> It's almost like since I removed dbus-org.freedesktop.resolve1 something else is doing DNS... or maybe at runtime when I try docker-compose up, something *is* running on :53?
[17:24] <oerheks> i did read somewhere that pihole install needs to disable resolv.. not sure what guide that was
[17:25] <foo> ah, it's systemd-resolved.service
[17:30] <foo> Finally, gah.
[17:35] <foo> sigh, spoke too soon.
[17:35] <foo> # cat /etc/resolv.conf
[17:35] <foo> cat: /etc/resolv.conf: No such file or directory
[17:35] <foo> that doesn't look good.
[17:38] <foo> I've spent close to 3 hours this morning trying to get pihole working on startup. It was working fine for months, then realized it wasn't set up to start on startup. Now it runs on startup, but it seems there's a ubuntu-level issue with /etc/resolv.conf disappearing. If anyone has any troubleshooting steps please let me know, I'm going to bypass it with another DNS server so I can actually do work...
[17:38] <foo> I'm stumped at why I'm having so many issues.
[17:39] <foo> ah, might be dns cache issues
[18:00] <foo> No, there is still quite a bit of lag to resolve and some devices aren't resolving. Gah
[18:05] <foo> I'm beginning to think there's an IPv6 in my /etc/resolve.conf ... and I can't ping it
[18:06] <foo> I don't know where this is coming from
[18:08] <RoyK> foo: can you ping something like 2001:4860:4860::8888 ?
[18:09] <foo> RoyK: I realize you said "something like" - ping: cannot resolve 2001:4860:4860::8888: Unknown host -
[18:12] <RoyK> pipng6?
[18:13] <RoyK> *ping6*
[18:13] <foo> RoyK: yes, that worked
[18:13] <RoyK> some older versjons of ping are separated between the two stacks - newer ones take both
[18:13] <foo> I just did dig google.com @ ... and I tried it against both IPs in resolv.conf, the one for pihole, and this other IPv6. IPv6 definitely hangs
[18:31] <RoyK> foo: if you can ping an ipv6 host on the other side of the planet, then it works. that the resolver doesn't work is another thing
[18:31] <RoyK> can you dig aaaa @yourresolver google.com ?
[18:42] <foo> RoyK: thakns, I got it. I had to reboot the airport time capsule. Looks like some quirk that likekly cost me a few hours, meh
[18:43] <RoyK> so it works?
[18:43] <foo> RoyK: yes
[18:43] <RoyK> whee
[18:44] <foo> RoyK: thanks for "being there" :)
[18:46] <RoyK> foo: np :)