[01:43] <SpaceBass> Hey yall, I've got a problem with a brand new 22.04 install and SSSD. Ive joined the box to an AD domain which has no GPOs. We just use it for user auth. In sssd.conf I have: ad_gpo_access_control = permissive BUT no users can log in. I get an error about not being able to apply GPOs for the machine
[01:44] <SpaceBass> That's a known bug in an older version of sssd but this is a very current machine with a newer version than the fixed version of sssd 
[08:55] <andypandy> I am using ZFS on my home server, running ubuntu 20.04 currently. I was wondering if I get any benefits from a 22.04.1 upgrade. Since ZFS is part of the kernel (I believe?) is there any differences between 20.04 and 22.04 as far as ZFS is concerned? The kernel are updated on 20.04 anyways?
[08:56] <andypandy> I am trying to find out what the changes are but are only finding articles talking about GNOME versions etc for desktop use. Is there anything major changing for servers?
[08:57] <rbasak> The package versions of most things get updated.
[08:57] <rbasak> Do you know about the release notes? https://discourse.ubuntu.com/t/jammy-jellyfish-release-notes/24668
[08:57] <rbasak> The package version updates described there are just highlights though.
[08:57] <andypandy> I will make sure to read those, not sure if I have before.
[08:58] <andypandy> Im mostly using the server for Docker and ZFS as NAS. I am flipping back and forth between "New stuff is fun" and "Dont mess with things that work fin"
[08:58] <andypandy> :D
[12:20] <ahasenack> the irony: "test-fastsuite       FAIL timed out
[12:20] <ahasenack> "
[14:51] <sdeziel> I have a file (/proc/1311748/maps) that when read with `cat` or `grep` causes the reading process to segfault. Anyone has an idea what's going on here? What it looks like https://termbin.com/ekdc
[14:55] <ahasenack> anything in dmesg when that happens? Like an apparmor deny perhaps?
[14:55] <ahasenack> is it only cat? Have you tried others? If it's cat mishandling an error condition, maybe others cope with it better
[14:56] <sdeziel> ahasenack: it's not just cat, grep too but dmesg shows the kernel is having a bad day, will report after a reboot, thanks!
[14:59] <JanC> could be hardware issues with memory too
[17:42] <sarnold> andypandy: l2arc persistence, perhaps?
[19:08] <SpaceBass> Having a lot of issues with sssd and AD on 22.04 
[19:08] <SpaceBass> Looks like I'm still getting some of the bugs that were reported to be fixed and closed a while ago :/ 
[19:08] <SpaceBass> Anyone having success with SSSD and AD? 
[20:52] <av2156> hello, is systemd-networkd == networkd? are both same ?
[20:59] <sergiodj> SpaceBass: I'm busy with something else right now, but if you could file a bug against the package and provide as much information as possible, I'd appreciate
[20:59] <sergiodj> steps to reproduce the problem are also very much welcome
[21:40] <SpaceBass> Ill try
[21:41] <SpaceBass> Basically, the hack to use permissive around GPOs isn't working in 22.04 
[21:52] <sarnold> av2156: probably systemd-networkd == networkd; I know I've been lazy and saved myself all that typing in the past :)
[21:53] <av2156> okay
[21:53] <av2156> noice
[22:28] <av2156> Hi, I want to fix my ethernet connection on u ubuntu server
[22:28] <av2156> been trying with netplan
[22:28] <av2156> buy netplan apply always throws the same error
[22:30] <av2156> "subprocess.CallProcessError: Command '['systemctl', 'start', 'netplan-wpa-wlp3s0.service']' returned non-zero exit status 1."
[22:30] <sarnold> run that command yourself and see if it emits any more detailed errors?
[22:31] <av2156> also everywhere i read, i saw just one yaml file on ubuntu server, mime has two 00-installer-config-wifi.yaml & 00-installer-config.yaml
[22:31] <av2156> @sarnold ok
[22:32] <av2156> sarnold: but the service mentioned has incorrect wifi name, mine is wlan0 and it has wlp3s0
[22:32] <sarnold> av2156: is the name wrong in your yamls?
[22:33] <av2156> yes
[22:33] <av2156> is that the issue ?
[22:36] <av2156> edited the yaml
[22:36] <av2156> applied the yaml
[22:37] <av2156> now rebooting
[22:37] <sarnold> it might be one of several issues; you could either write your netplan config to use set-name to set the name to something https://netplan.io/reference#common-properties-for-all-device-types or match the name that it's actually got
[22:40] <av2156> alright
[22:41] <av2156> also
[22:41] <av2156> I am a little bit confused about the static ip
[22:42] <av2156> what would be my gateway ip ? and what ip should i assign if i want to?
[22:42] <sarnold> the gateway IP depends upon your local network configuration -- your network administrator should be able to tell you what gateway to use, if any
[22:42] <av2156> i saw in router settings allowed range starts from 192.168.1.33
[22:42] <av2156> funnily i am my net admin
[22:43] <av2156> 🫡
[22:43] <sarnold> aha :) then in that case it's almost always the IP address of whatever you'd consider to the "the router" or "the firewall" sort of thing
[22:43] <sarnold> usually it's a .1 number in an address, but that's just a convention
[22:43] <av2156> so i ll have to assign something starting after 33 ?
[22:44] <av2156> or from after 192.168.1.1 ?
[22:44] <sarnold> I'm not sure what your router's "allowed range" actually means -- you're probably right, but that leaves only around 30 addresses for dhcp use, which feels pretty low for the average home
[22:45] <av2156> ip lease i meant
[22:45] <av2156> ranges from 33 to 253
[22:45] <av2156> i ll have to assign between these to set a static ip?
[22:47] <sarnold> that sounds very plausible, yes
[22:47] <av2156> ok
[22:50] <av2156> rebooted wifi still couldnt get an ip