=== genii is now known as genii-meeting === JanC is now known as Guest7251 === JanC_ is now known as JanC === genii-meeting is now known as genii-core === not_phunyguy is now known as phunyguy [06:03] good morning [06:43] heya [06:58] o/ [06:59] hi bryyce and utkarsh2102 [06:59] already found the first glibc 2.35 victim :-) [06:59] open-vm-tools [06:59] a few other likely suspects are still rebuilding, so I'll wait to have my set of tasks for next week I guess :-) [07:01] ooh! [08:01] good morning [09:01] uh, why am I listed as a community member? :) [09:01] for eg: https://code.launchpad.net/~bryce/ubuntu/+source/apache2/+git/apache2/+merge/415047 [09:01] interesting! [13:07] utkarsh2102: everyone is because they don't officially own the branch nor are a reviewer for it [13:08] oh, alright, that explains it, I guess. :) [13:09] hi, can someone help me? i use nextcloud on my server, and this is error i have in error log (Image size of 6000x8000 would exceed allowed memory limit of 128) but memory limit i have set to 1G, any idea? :/ [13:30] peto: is that a php setting, the memory limit? [13:37] likely the latter 128 is the default [13:37] https://www.php.net/manual/en/ini.core.php#ini.sect.resource-limits [13:37] well the limit is a setting - so "both" [13:37] :-) [13:39] @ahasenackyes should be php setting [13:42] i have changed php.ini in apache2,cli, fpm , but still the error [13:44] peto: i think phpinfo() would report active limits, so you could verify what is actually applied. [13:47] I can't seem to get any hits for a web search for the error message you reported, using "Image size of" AND "would exceed allowed memory limit of" - can you double check this is the exact message you're getting? [13:48] the default php message for the memory_limit setting would be Fatal error: Allowed memory size of XXX bytes exhausted (tried to allocate YYY bytes) [13:50] @tomreyn phpinfo show 1G memory limit. also serverinfo on nextcloud show 1G [13:50] if your message really differs, this might hint at some other memory limit being hit, such as for a php graphics module (gd or imagemagick) [13:51] but when i Upload a image cca 9 MB, no thumbnail or preview is showing, and the error is shown [13:52] and the message is exactly as you wrote? [13:55] there seems to be an "Allocation would exceed memory limit" message, maybe it's that? [14:02] @tomreyn the error is with the memory limit i wrote, and also ""message":"OC_Image::fixOrientation(): No image loaded"" [14:06] peto: can you show the full line that gets logged? [14:06] if multiple lines, use a pastebin [14:06] chances are this is anextcloud generated error message then [14:08] peto: generally, with software that's not packaged in ubuntu, such as nextcloud, your best option for support is to use the support options its developers provide (if any) [14:10] here the error https://pastebin.com/Qqb38M01 [14:10] yes, i think i will create a bug on GH [14:11] i imagine there may be an irc channel on nextcloud here on libera.chat - you could ask alis about it: [14:11] !alis [14:11] Alis is an IRC service to help you find channels. For help on using it, see «/msg Alis help list» or ask in #libera - Example usage: «/msg Alis list http» [14:14] on #nextcloud we cant find the problem, so i tried here [14:40] I rebuilt the container stack packages against the new glibc and ran the tests, it seems we have no issue this time \o/ [14:58] kanashiro: that's great news [15:27] indeed [17:45] what's snapd and why was it using all the CPU [17:46] what snaps do, needed for some things, wish it wasn't isntalled by default on server [17:52] how do you figure out what snaps are installed? [17:53] snap list [17:56] core18, core20, lxd, snapd... what are core18 and core20? [17:56] ubuntu 18.04 and ubuntu 20.04 [17:57] would removing snapd break anything? [17:58] in your case, only if you use lxc containers [17:59] goodbye snapd may you never eat 100% CPU again :D [18:04] sdeziel: how did you manage to create https://termbin.com/a06m? Did you use typescript or something to direct all outputs to a file, and then sent it to termbin.com using `nc`? [18:06] typescript might be using a wrong term ...I think it was script or something back in the day when I was taking a few c courses, which required the output of make and etc in the text file. [18:07] it was `script`... (please ignore my question - got it sorted out) [18:07] k8yun: I have "alias tb='nc termbin.com 9999'" in my ~/.bashrc [18:08] I see.. I saw that at the website... yeah, I should do the same [18:08] k8yun: so I when I type "tb", I can then freely enter/copy-n-paste text, then when I Ctrl-D, it is sent to termbin.com [18:08] thank you sir [18:08] good point - thank you sir! [18:08] and I get back the URL in return [18:08] you are welcome [18:08] yeah, I used the termbin a bit and I quite like it [18:09] eol [18:09] eof [18:15] speaking of tb, I wish there is a plug in in HexChat that you can just run "curl https://termbin.com/zhw4 [18:15] " to display the output on the same channel window (for myself only, not for others). [19:44] Anyone know of a script or other solution to get the user home directory from the Active Directory user object and map their home drive automatically? [19:45] removing snapd broke systemd: units apparmor.service and snap.lxd.activate.service are failing [19:46] snap.lxd.activate.service can go away but apparmor seems more concerning [19:47] what even created this snap.lxd.activate.service and this /etc/usr.lib.snapd.snap-confine.real and why didn't they go away when uninstalling snapd? [19:53] how did you remove it? You have to first remove all snaps, and then finally remove the snapd deb itself [19:53] and when removing snaps with `snap remove`, the core ones have to be last [19:56] The `snapd` package doesn't prevent removal if there are still snaps installed? [19:57] (pretends_to_be_shocked.jpg, etc.) [19:58] I wouldn't be shocked [19:58] ymmv [19:58] sometimes I don't go out looking for bugs :) [19:59] I have an Ansible playbook that does it in the right order, so I wouldn't have hit it. [19:59] smart [19:59] btw, do you use ansible from debian/ubuntu? I just found out this week that what we carry is very old [20:00] in terms of versioning, at least (which is also confusing, looks like there were some strong version bumps done by upstream) [20:01] I use this PPA for my personal stuff: https://launchpad.net/~ansible/+archive/ubuntu/ansible [20:01] I know athos is a big ansible fan [20:02] not sure which version he uses though [20:02] And we pip install it at $dayjob. [20:07] Alslinet: that sounds a bit like something sssd ought to do [20:12] It doesnt it seems [20:13] :( sorry [20:20] ahasenack: meh. so just rm /etc/apparmor.d/usr.lib.[...] ? [20:20] depends what the error is, you just said "broke my system" [20:21] note that removing the file from disk doesn't remove it from the kernel (the apparmor profile, that is) [20:21] it just says the apparmor unit failed because of this file [20:22] check /var/log/syslog, and/or journalctl -u apparmor, see if it has more info [20:22] Feb 04 19:35:38 lavabit apparmor.systemd[312]: AppArmor parser error for /etc/apparmor.d in /etc/apparmor.d/usr.lib.snapd.snap-confine.real at line 11: Could not open '/var/lib/snapd/apparmor/snap-confine' [20:22] Feb 04 19:35:38 lavabit apparmor.systemd[356]: AppArmor parser error for /etc/apparmor.d/usr.lib.snapd.snap-confine.real in /etc/apparmor.d/usr.lib.snapd.snap-confine.real at line 11: Could not open '/var/lib/snapd/apparmor/snap-confine' [20:23] ok, so that looks like profiles that were including other profile files, which are now gone [20:24] I don't have a one-size-fits-all solution, if you have leftover snaps running, after you removed snapd [20:24] this was after a reboot [20:24] you could try reinstalling snapd (the deb), then see if with "snap list" you get to see the snaps, and then remove them one by one with snap [20:24] meh *rm -rf /etc/apparmor.d/the_offending_file* [20:24] or maybe apt purging snapd (the deb) does remove the snaps, but then you wouldn't ahve this error [20:24] or just delete those files, if you don't have the programs they confine installed any more [20:25] yeah, look carefully, make sure they are about apps/paths you don't have anymore [20:25] or else you could be removing the apparmor profiles for existing apps [20:25] this *should* be fine [20:26] not rebooting again to find out tho [20:30] in jammy I just did an "apt purge snapd" with many snaps installed, and it removed them all during the deb purge [20:30] and restart apparmor after that was also fine [20:30] so that's good [20:31] apparmor is also fine (green) after a reboot [20:33] hmm yeah in hindsight apt purge seems like a better idea [20:35] that should be snapd fully gone tho ^^ [20:38] orndorffgrant: yeah so today I releaned about systemd.paths :) thanks for the discussion https://github.com/canonical/cloud-init/pull/1244#issuecomment-1030243537. testing locally with a shell script that dumped a message to a file I validated that compound [Unit] ConditionPathExists and [Path] PatchExists/PathChanged directives seem to work and noop in the right places [20:38] Pull 1244 in canonical/cloud-init "WIP: cloud-id: publish /run/cloud-init/cloud-id- files" [Open] [20:41] *PathExists/PathChanged* rather [20:41] blackboxsw: very cool! I'm not sure if we actually _need_ the .path (just a check on startup should be sufficient for what ua needs) but that would be nice to have systemd handle starting/stopping automatically on those state changes, I'll play around with it [20:42] the thing I wonder w/ systemd.path is the race we'll have at systemd compilation time. /run/cloud-init/cloud-id-X won't exist until later in the boot process after systemd alreafdy comiled boot goals and ruled out your service [20:43] so I wonder without using systemd.path to camp on inotify whether you'd never trigger your service in practice [20:43] Right, I was hoping something like `After: cloud-config.target` could be sufficient to make sure that file would be in place, but would need to test to confirm [20:45] orndorffgrant: +1. I think/thought I validated that the service remains inert based on anything in /run which wasn't present at system boot. But, yes will involve testing to confirm that's the case. [20:47] Got it, yeah I'll test it for sure and the .path will probably be useful anyway so we'll probably use that too [20:51] I think the After just implies ordering of execution, not whether the systemd unit is included in the boot target goals [21:28] is there a simple way to allow everything in/on the docker-created interfaces dynamically with ufw? [21:29] ie: I want my docker containers to be able to connect to the mysql instance running on host, but I don't want to have to manually whitelist interfaces === genii-core is now known as genii === genii is now known as genii-core