[00:06] <nacc> cpaelzer: postgresql-10 is now blocked by the freeze, feel free to pick it up from here (pg-repack has already migrated)
[01:05] <paul__> Can anyone recommend a web app I Can install on my home server to allow basic file management to a specific server location (upload, download, delete) through the browser?
[01:06] <paul__> remaining space on partition would be nice too
[01:08] <sarnold> owncloud or nextcloud seemed popular
[01:23] <CodeMouse92__> (Nextcloud is awesome)
[01:25] <CodeMouse92__> paul__: I would definitely look into Nextcloud for that. Nice, clean web interface, good controls, sync clients, etc. You can also set quotas on users.
[06:05] <lordievader> Good morning
[06:29] <cpaelzer> nacc: I see pg-10 is now just waiting for freeze as you said
[06:30] <cpaelzer> nacc: there is not much more to do, I pinged the release team, but we are good if that migrates next week as well
[06:30] <cpaelzer> nacc: IIRC after the beta spins are complete it should migrate prior to release
[06:30] <cpaelzer> or do you think without pings it will automatically become a post release SRU?
[12:44] <Gargravarr> tyhicks: think i figured out why the Precision (on the 4.4 kernel) still broke despite removing intel-microcode - i updated the BIOS, which as i proved with the XPS, also updated the microcode
[12:44] <Gargravarr> trying your 4.4 kernel now
[13:07] <Gargravarr> hallelujah, 4.4.0-119 working with SSSD
[13:11] <Gargravarr> tyhicks: many thanks for your hard work fixing this
[13:46] <tyhicks> Gargravarr: thanks for the testing!
[14:15] <ahasenack> rbasak: hi, since you know debian
[14:15] <ahasenack> rbasak: https://anonscm.debian.org/gitweb/?p=collab-maint/logwatch.git I'm trying to see the commit for "dovecot: Ignore "Logged out" and "Debug" lines. closes...", at the very end of the "short log" section
[14:15] <ahasenack> but I get "bad object id"
[14:15] <ahasenack> is anonscm.debian.org broken?
[14:19] <rbasak> ahasenack: https://anonscm.debian.org/cgit/collab-maint/logwatch.git/commit/?id=f431e2e386af0da575d58fe80748199849d705ef
[14:19] <rbasak> ahasenack: maybe a bug? I went via the log page.
[14:20] <rbasak> ahasenack: also given the move over to salsa I wonder if somebody broke something doing something by hand to the repo.
[14:20] <ahasenack> thanks
[14:39] <ahasenack> ddstreet: hi,
[14:40] <ahasenack> ddstreet: I'm doing some bug triaging, and this old-ish bug came up: https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1701023
[14:41] <ahasenack> does that ring a bell? The bug fixed since 10.1 (which is the last working package for the reporter) is https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1573272
[14:41] <ahasenack> 3 attempts even
[15:02] <nacc> cpaelzer: ack
[15:07] <OliPicard> Hey Everyone, I was wondering how do I download an older version of SQLite? I'm looking for SQLite 3.10.1 but I'm not able to find a download link on SQLite.org to the older version. I was wondering if theres a method I could use directly in APT to request an older version of the application?
[15:07] <rbasak> OliPicard: https://launchpad.net/ubuntu/+source/sqlite3 -> View full publishing history
[15:08] <Gargravarr> tyhicks: so which combination of intel_microcode and kernel is it that causes SSSd to go down in flames?
[15:08] <rbasak> OliPicard: click on the version string you want, then see the Downloads section
[15:08] <OliPicard> rbasak: Thank you Robie :)
[15:08] <Gargravarr> i'm looking at machines in Landscape and trying to figure out which ones are safe to upgrade
[15:09] <tyhicks> Gargravarr: intel-microcode with 3.20180312.0 in the version string with any of the recent 4.4 and 4.13 kernels (since January)
[15:10] <Gargravarr> okay. i've got a machine with that version microcode and kernel 4.13.0-26
[15:10] <Gargravarr> i assume upping the kernel (before the current patch is released) would be Bad :)
[15:11] <Gargravarr> are previous versions of the microcode affected?
[15:18] <tyhicks> Gargravarr: you could downgrade the microcode if you wanted to run the latest kernels
[15:18] <tyhicks> Gargravarr: you could also uninstall the intel-microcode package until the new kernels are available
[15:34] <Gargravarr> i might do that, thanks for clarifying
[17:26] <bladernr> Hey, is the live ISO (Subiquity) going to completely replace d-i for 18.04, or will both options be available?
[17:28] <dpb1> both will be available
[17:28] <dpb1> and supported
[17:31] <bladernr> dpb1, thanks!
[17:32] <bladernr> I was just playing with the live one to answer some questions and it's come along nicely.
[17:32] <dpb1> thoughts so far?
[17:32] <dpb1> I mean, it's pretty much final at this point of course
[17:32] <dpb1> but we have things in store for 18.04.1.
[17:54] <jbicha> hi, when you get a chance, it would be great for you to update https://wiki.ubuntu.com/BionicBeaver/ReleaseNotes
[17:55] <jbicha> Beta release is scheduled for today-ish and the Server section is incomplete (I filled out the Desktop section but didn't know what y'all wanted to highlight)
[18:27] <ProCycle> I'm trying to figure out what the apache varible HTTP_REFERER could contain but there seems to be no documentation. Anyone know if it gives the full url or just the domain?
[18:28] <ProCycle> Or how I might expose the contents of that varible so I can find out?
[18:34] <dpb1> https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html
[18:35] <sdeziel> ProCycle: the referer is included in the default logging of Apache
[18:36] <ProCycle> So it sounds like it's the full url
[18:36] <sdeziel> grep -w combined /etc/apache2/apache2.conf
[18:36] <sdeziel> ProCycle: it is whatever the browser/UA decided to put in
[18:36] <ProCycle> Trying to redirect people coming from scam coupon sites to a disclaimer page
[18:50] <tomreyn> ProCycle: the best way to have a webserver print the value of a variable is probably a http response header (make up your own X-header (e.g. X-VAR-REFERER) and have the webserver return it and the value of the variable.
[18:51] <tomreyn> you can then view this with curl, wget or the web development utilities integrated into firefox or chromium
[18:51] <ProCycle> Interesting approach, thanks
[19:12] <ProCycle> Well shoot I get a redirect loop because the redirect doesn't strip the referer header which triggers the rewrite again
[19:13] <ProCycle> Putting [L] at the end doesn't stop it, and putting [END] breaks my server
[19:36] <ProCycle> Huh I don't get why it just loops. The only thing I can think of it's because the host uses a nginx reverse proxy for apache
[19:37] <ProCycle> Guess it's time to move to a better host
[20:24] <arooni> trying to connect to a mysql server from another machine... ri
[20:25] <arooni> lets reprhrase that
[20:25] <arooni> if i cant telnet to that ip / port number; theres going to be no hope to connecting via mysql right
[20:26] <sdeziel> arooni: indeed, if you you cannot telnet to $IP:3306, then the mysql client won't be able either
[20:27] <arooni> whats weird is that i have allowed access via ufw from this ip address and port number; and restarted ufw
[20:27] <arooni> am i missing something ?
[20:27] <lordcirth_work> arooni, are you sure that mysql is listening on that ip instead of only on localhost?
[20:27] <arooni> well i did telnet locally to 3306 and it did work
[20:28] <arooni> i.e. telnet localhost 3306
[20:28] <arooni> (from the machine running mysql server)
[20:28] <arooni> and ufw reports 3306                       ALLOW       192.168.1.100
[20:33] <arooni> fixed it; apparently a bind-address of localhost in mysql conf disallows it to thikn about listening to any remote connections
[20:34] <nacc> arooni: yes, that seems correct.
[20:34] <JanC> obviously
[20:35] <arooni> i credit my amazing insomnia for making me stupider today
[20:35] <JanC> it's a good thing that it only listens locally by default too  :)
[20:35] <arooni> agree
[20:35] <arooni> do i have to do something when i make ufw changes or are they live immediately
[20:40] <jdstrand> arooni: if you use the ufw command (eg, ufw allow to any port 3306 from 192.168.1.100), it is leve immediately
[20:40] <jdstrand> live*
[22:26] <nacc> teward: ping -- you've got some noise in your last nginx merge (i'm fixing it up) -- will probably need you to sanity check what i end up dropping (e.g., you've got undocuemnted chagnes to debian/gbp.conf and d/p/0003....patch
[23:35] <ProCycle> Huh what would cause the root account to write files as -rw-r----- but directories as drwx------
[23:36] <ProCycle> so group can read files but can't read directories...
[23:37] <sarnold> the modes are computed by what the application requested for the operation along with the umask in place at the time
[23:40] <ProCycle> so when I run sudo is it using the root account umask or the user running sudo?
[23:43] <sarnold> ProCycle: like everything else with sudo, it's complicated :) see umask_override and umask in sudoers(5) for the details ..
[23:51] <ProCycle> Hmm so, it's complicated. Best just set file permissions afterwards
[23:52] <ProCycle> Writing a backup service file so need to make sure files it makes have the right permissions so the backup server can grab them
[23:53] <sarnold> systemd.exec(5) has a UMask= setting you may find helpful
[23:56] <ProCycle> Ah cool that looks useful