[02:29] <mybalzitch> why are virtio network drivers under 4.10.0-37 seemingly so unstable
[02:32] <mybalzitch> I run into issues with heavy nfs/tcp traffic and the interface seems to hang/become unusable
[05:42] <cpaelzer> good morning
[06:14] <Thumpxr> morning. as far as i know, 17.10 should be online now, but why cant i seem to get the update ?
[06:15] <andol> Thumpxr: Why would you expect it to be fully online now? I haven't seen any announcements.
[06:16] <lordievader> Good morning
[06:18] <Thumpxr> andol oh lol, i somehow went to 16.10 dir and didnt realized it ._.
[06:22] <andol> Ah :)
=== jelly-home is now known as jelly
[09:04] <Jenshae> o7
=== jelly-home is now known as jelly
[12:21] <dduvnjak> Used this to fix a long boot time on Ubuntu Xenial (on AWS): https://askubuntu.com/a/897432
[12:22] <dduvnjak> It worked for a few days, but now apt-daily.service started getting executed at boot again. Here's the `systemd-analyze blame` output: https://pastebin.com/zLBQZSm9
[12:23] <dduvnjak> Not sure how that's possible with `OnBootSec=15min` in the timer config. Could it be that a dependent service is kicking it off?
[13:05] <TJ-> dduvnjak: what does the critical-chain report show ?
[13:11] <dduvnjak> TJ-: https://pastebin.com/wGqv8Bjj
[13:13] <kirkland> jbicha: hi, I'm just seeing your message about f6 killing byobu/irc
[13:14] <TJ-> dduvnjak: from that the apt.daily isn't holding things up, so it'll be running in parallel as I thought. It shows cloud-init-local.service taking 7.8 secs
[13:16] <dduvnjak> TJ-: It's not slowing anything up, but it's causing issues with provisioning scripts which run at boot since it's locking /var/lib/dpkg/lock (which is another issue). It should be running 15 mins after boot, but somehow it's not. Is it possible that apt-daily-upgrade.service is launching it?
[13:16] <TJ-> dduvnjak: oh, I see! sorry, from you showing timings I thought that was your issue
[13:17] <TJ-> dduvnjak: there's away to check what causes a service to start... now what the heck is it!?!
[13:17] <dduvnjak> there were two issues actually :) boot time and dpkg lock
[13:19] <dduvnjak> Is that a trick question? :D
[13:19] <TJ-> I was hoping someone would tell us and save me hurting my brain trying to find it!
[13:25] <dduvnjak> `journalctl -u apt-daily-upgrade.service` doesn't say anything useful
[13:26] <TJ-> indeed. I've seen something like the critical-chain output but showing what caused a service to start.
[13:27] <dduvnjak> I'll try to analyze the SVG plot output
[13:31] <dduvnjak> Looks like it was launched by cloud-init: https://www.dropbox.com/s/bifyio036ia208t/Screenshot%202017-10-19%2015.30.55.png?dl=0
[13:38] <joelio> cloud-init will do an apt-get update which will lock dpkg?
[13:38] <joelio> I've had to add sleeps before for that
[13:39] <kirkland> jbicha: I can't reproduce;  I just used F6 to detach, and reattach, 30x times, no problem
[13:41] <TJ-> dduvnjak: does "systemctl list-dependencies [--before | --after ] apt-daily.service" help (try both options)
[13:42] <jbicha> kirkland: thanks. If I get annoyed enough, I'll try to reproduce with a more pristine environment
[13:42] <joelio> boottime might be that update process (could also be waiting for entropy for keys, but pollinate usually speeds that up)
[14:18] <dduvnjak> TJ-: Thanks. It looks like it might be a dependency of apt-daily-upgrade.service: https://pastebin.com/RQ2veAR9 Will try to set a timer on that one also to see what happens.
[14:19] <TJ-> dduvnjak: according to the systemd folks there isn't a way to identify what actually triggered the tart of the specific instance, only to show the dependencies as written in the unit/target/wants
[14:20] <dduvnjak> ah ok
[14:21] <dduvnjak> Thanks for your help. I have a feeling cloud-init kicked it off, even though user-data is specifically set to disable running upgrades on boot. I must have missed something.
[14:22] <TJ-> it does get mind-boggling doesn't it?
[14:26] <dduvnjak> to say the least :D
[14:28] <joelio> there's some default stuff in /var/lib/cloud... iirc
[15:37] <maxagaz> what is the dpkg-reconfigure command to reconfigure my messy network ?
[15:38] <maxagaz> I thought it was dpkg-reconfigure network-manager but it's not installed
[15:38] <maxagaz> dpkg-reconfigure --all doesn't work either anymore
[15:39] <Jenshae> apt-offline supported by Ubuntu-server?
[15:40] <Jenshae> One trick I had with network problems was to boot a live USB, download the packages I needed on the same machine then move those packages to the local drive, boot the drive and install them there.
[15:45] <nacc> Jenshae: not sure why server matters to apt-offline?
[15:45] <nacc> Jenshae: it's available inn ubuntu
[15:47] <Jenshae> nacc: Thinking that if maxagaz has lost net with broken network-manager that he can use apt-offline to pull across the packages that he needs from another machine to fix it.
[15:48] <nacc> maxagaz: "messy network"?
[15:48] <maxagaz> my server is in a vbox
[15:57] <Jenshae> Laters o7
[17:08] <Aison> hello, what is the root password of the mysql server after installation?!? There is no prompt on apt-get install mysql-server
[17:12] <nacc> Aison: what version of ubuntu?
[17:14] <Aison> nacc, zesty
[17:21] <nacc> Aison: just tested it and it definitely prompted me
[17:21] <nacc> Aison: do you perhaps have some settings that are making it noninteractive?
[17:22] <Aison> I don't think so. eg. phpmyadmin installation is interactive
[17:24] <Aison> I completely remove now and try again...
[17:25] <nacc> Aison: dunno, perhaps you already had it insntalled?
[17:25] <Aison> now it works, really strange, hmmm
[17:27] <Aison> I guess there was already a database installed
[17:28] <Aison> not mysql itself, but the databases (maybe because of a previous unclean removal)
[17:29] <nacc> could be
[22:56]  * Olanzapin is away -( bbl )- at 12:56a -( P:On / L:On )-