[04:18] <foo> I often have issues with log files: https://bpa.st/UWPA -> anyone see anything wrong with that? the live.log file doesn't get written sometimes I have to delete it
[04:20] <foo> I'm seeing OOM killing off a process, think I'm going to go from 2GB to 4GB swap. 
[04:21] <foo> Is 4GB swap a "no no" ? 
[04:26] <genii> The usual rule of thumb is same swap size as ram
[04:27] <genii> ( or double)
[05:16] <foo> genii: thanks, it's currently double - then. 
[05:16] <foo> genii: no harm in setting it to 4GB though, eh?
[05:17] <foo> Also, part of the issue here - OOM was killing off a critical process and I didn't know about it. What's the best way to track with this? I suspect systemd restarted the process when it got killed off... which kept happening and I didn't see that
[05:59] <cpaelzer> good morning
[07:19] <mirespace> good morning 
[10:07] <athos> good morning!
[12:14] <MJCD> athos: what's good about it
[14:33] <sergiodj> athos: hey
[14:33] <sergiodj> thinking about the postgresql MRE's, I think it may be worth pinging the SRU team for the B/F uploads
[14:33] <sergiodj> the impish one has already migrated
[14:35] <athos> sergiodj: +1 will do :)
[14:35] <athos> thx!
[14:35] <sergiodj> np!
[14:36] <sergiodj> (the bug came up during my triage ;-)
[14:46] <sergiodj> lvoytek: hey
[14:48] <sergiodj> this one came up during my triage: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1964910 .  would you like to take a look to see if it fits one of the known cases?  I can also triage it for now if you'd prefer
[14:51] <lvoytek> I'll take a look, thanks
[14:51] <sergiodj> ACK, thanks
[14:56] <lvoytek> It's not a duplicate of the main two, but it is one i've seen before. I'll try to find the one similar to this and compare them. It seems like they uninstalled and reinstalled mysql a lot of times which often obscures the actual error a bit
[14:57] <sergiodj> yeah, I had the same impression from a first glance
[14:58] <sergiodj> couldn't fit it into the two categories you had determined before
[17:23] <lvoytek> sergiodj: found a duplicate of the bug here: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1960971 I'll respond to the user and mark it as a duplicate. Seeing both of the reports makes me more certain that purging mysql and reinstalling in a short amount of time causes this error
[17:24] <sergiodj> lvoytek: +1, thanks for looking into it
[19:46] <bryceh> I think we may want to think about having the mysql apport hook parse the apt log to detect cases like that one, where they've reinstalled more than a couple times, and bail out of filing a bug.  I agree that situation gets more to being a support case than an actionable bug report.
[19:57] <bryceh> $ grep dpkg /usr/share/apport/package-hooks/xserver-xorg-core.py
[19:57] <bryceh>             # Perhaps parse dpkg.log for update dates
[19:57] <bryceh>     attach_file_if_exists(report, "/var/log/dpkg.log", "DpkgLog")
[19:57] <bryceh> heh, seems I had that same idea once long ago
[19:57] <sarnold> heh
[19:57] <sarnold> it's certianly not new :(
[19:59] <bryceh> I wrote an Xorg.*.log parser, but seems I didn't get to the apt logs.  Format looks pretty straightforward though.
[20:01] <bryceh> ah well, another line in the ol todo list
[20:06] <bryceh> aha: https://bazaar.launchpad.net/~ubuntu-x-swat/xdiagnose/trunk/view/head:/bin/dpkg-log-summary