[07:09] <ltorvalds024> I tried reinstalling php by remove all the packages and systemd service, but now if I install it again, systemd service cannot be found
[07:09] <ltorvalds024> can someone please tell me how can I install it from scratch again?
[13:57] <teward> sdeziel: rbasak: one of the ways we can 'debug' these local conf problems in nginx like we're seeing is extend the apport hook to include the complete set of configurations - `nginx -T` - that's in place in an install, the only *hazards* of this is that it may have identifiable information in the configuration (IPs, hostnames, etc.) in them.  But a full config dump does help to ID issues like the latest bug that was filed.  Thoughts?
[13:58] <sdeziel> teward: I find the existing apport collected stuff to be enough to quickly ID a problem.  That is mostly because the nginx.service has a "nginx -t" call which provides useful logging
[13:59] <teward> true
[13:59] <teward> but usually when debugging these in #nginx I end up having to ask the user to provide their whole config
[13:59] <sdeziel> teward: I personally have no problem with the existing method and would have concerns to collect people's configs automatically
[13:59] <teward> yeah that's one of the concerns I have too
[13:59] <sdeziel> teward: true, I don't deal with as many as you do
[13:59] <teward> just thinking ;)
[14:00] <teward> wow 30s between the message here and it pinging my phone, geez.  I think irccloud is having a Bad Day xD
[14:00] <sdeziel> yeah, the idea is nice but the automatic part of it might causes privacy issues
[14:01] <teward> true.  we can always just ask users to attach the output of `nginx -T` if we really need it, then let them sanitize it
[14:01] <teward> ... someone send me coffee, its cold and hot hot coffee would be appreciated today
[14:01] <sdeziel> hehe, I didn't knew there was a "-T" variant, thx!
[14:04] <sdeziel> in this bug report case, since it was on Groovy, I ended up starting a lxd container to make sure it was not a new issue but even with that extra step, I only spent 2-3 minutes so I'm satisfied with the overall bug triage experience we already have. Thanks for thinking about ways to improve it anyway
[14:14] <teward> well they upgraded focal -> groovy
=== jelly-home is now known as jelly
[14:14] <teward> which unless you did THAT in a container too, might be a factor
[14:14] <teward> shouldn't be but could be
[14:16] <sdeziel> IIRC, they started at 18.10
[14:16] <sdeziel> no way I'm going to do that ;)
[14:16] <teward> lol
[14:17] <teward> > Occurred when upgrading from Focal to Groovy
[14:17] <teward> but you're right they started at 18.10
=== cpaelzer__ is now known as cpaelzer
[16:31] <arch-nemesis> Hello, all. Are there boot options on the ubuntu 20.04.1 iso image other than "autoinstall"? I have a configuration in which servers are booted from pxe and installed with subiquiti "autoinstall" and cloud-config. This works well. But I want to add an additional menu to just boot into a live environment for troubleshooting purposes. Without any boot options, subiquit is launched
[16:31] <arch-nemesis> automatically. I know I can just hit ctrl-z to get out of it, but other people might not be informed of this when they need to troubleshoot.
[16:32] <arch-nemesis> I can't seem to find a list of boot parameters aside from the guide for setting up auto-installation. Poking around in the casper directory has been pretty fruitless also, and I am just not sure where to look.
[16:43] <rbasak> arch-nemesis: I'm not sure but I don't think there's any supported boot option to give you a shell instead of subquity. You might be able to hack something together, but I don't know how.
[16:44] <rbasak> You could file a feature request against subquity to add that.
[16:48] <arch-nemesis> okay, thanks, rbasak!
[16:55] <rbasak> arch-nemesis: also see https://discourse.ubuntu.com/t/server-installer-plans-for-20-04-lts/13631 - you might want to add a post there
=== Pici` is now known as Pici
=== ijohnson is now known as ijohnson|lunch
[19:10] <sdeziel> powersj: big thanks for https://ubuntu.com/server/docs/service-ldap really valuable doc!
[19:12] <powersj> sdeziel, thanks, glad the server guide is getting used :) although I think ahasenack deserves the praise for the most recent updates
[19:13] <sdeziel> ahasenack: thanks!
[19:14] <sdeziel> I've never really touched LDAP but I need to do an OpenLDAP migration. Let's say the detailed explanations in the docs are going to make my life so much easier
=== ijohnson|lunch is now known as ijohnson
=== halvors1 is now known as halvors
=== halvors1 is now known as halvors