[00:01] <rbasak> Looks like you have third party apt sources enabled.
[00:01] <rbasak> Look in /etc/apt/sources.list and /etc/apt/sources.list.d/
[00:01] <rbasak> If you add third party sources, you allow problems in those third party sources to break your system.
[00:02] <rbasak> I don't know for sure what's causing your breakage here, or if it's caused by a third party source.
[00:03] <rbasak> But it's the first thing to eliminate, and the bump of openssl by that third party source makes it look more likely than not in this case, IMHO.
[00:03] <rbasak> (given the symptom you're reporting)
[00:03] <TheHonorableKitt> thanks man, I'm gonna take a look at that, thanks very much
[06:26] <patz0r> hello, does anyone know how I can create a mirror of my OS drive to a second disk (OS already installed)
[06:26] <patz0r> I experienced some kind of issue and could not do it during installation
[06:37] <cpaelzer> patz0r: no guarantee for your data as that is just a page I found, nothing I own - but https://www.considerednormal.com/2016/10/configuring-software-raid1-after-installation-of-ubuntu-16/ looks good I'd think
[06:38] <patz0r> thanks i'll check it out, worst case i can re-install but i'd have to do it over IPMI which i'd like to avoid
[06:38] <patz0r> it wouldn't allow me to create a mirror during install though, i could select both disks but not proceed through the md creation
[06:48] <cpaelzer> rbasak: no further action needed, I updated the bug
[07:41] <patz0r> cpaelzer, i'm going through that article you linked now, do you know whether I need to manually copy my 'efi filesystem' partition or if I can just do my linux filesystem?
[07:51] <cpaelzer> patz0r: sorry I don't know, I'd think you better keep the efi out of the raid to be sure
[07:51] <cpaelzer> just raid the other partition
[07:51] <cpaelzer> and keep the efi out of it
[08:09] <patz0r> cpaelzer, thank you, I will try that
[11:04] <ahasenack> good morning
[11:05] <ahasenack> smoser: rbasak: retrying apt-get update for a few times is one of the first things that was added to charmhelpers a long time ago, to give you an idea of apt-get update's reliability :)
[11:06] <ahasenack> rbasak: in this specific case, I think it was because the container was shutdown while some apt job was running, and that left a lock file in place
[11:06] <ahasenack> to generate a disco base image, I had to deploy cosmic, release-upgrade, and generate an image from that, since we don't have disco images yet (or didn't, haven't checked today)
[12:02] <kstenerud> Does anyone know why rmadison prints multiple unstable releases for a package? For example rmadison -u debian nspr
[12:02] <kstenerud> or dovecot
[12:10] <xnox> kstenerud, why not? it's not illegal to publish multiple versions of a thing in a suite.
[12:10] <xnox> plus this is results from dak's postgres database
[12:11] <xnox> kstenerud, this $ rmadison -u debian -S nspr -s unstable
[12:11] <xnox> might explain it better
[12:11] <xnox> 4.12-2 built on hurd-i386, 4.19 built on kfreebsd, 4.20 on linux-any
[13:21] <ahasenack> kstenerud: could you please also upload a disco package to ppa:kstenerud/cosmic-fetchmail-gmailssl-1798786 ?
[13:21] <ahasenack> kstenerud: in the future you can drop the ${distro} prefix from ppas, as they can hold multiple releases
[14:04] <ahasenack> kstenerud: can you please squash the two changelog commits? https://code.launchpad.net/~kstenerud/ubuntu/+source/fetchmail/+git/fetchmail/+merge/358699
[14:04] <ahasenack> kstenerud: then I'm ready to sponsor
[14:04] <ahasenack> if you want
[14:16] <smoser> ahasenack: yes. there is no reason to retry apt-get update
[14:17] <ahasenack> remember hash-mismatch errors? I still get those every now and then
[14:17] <xnox> ahasenack, on which repos and which releases?
[14:17] <smoser> that is only possible on < xenial.
[14:17] <ahasenack> so I was told
[14:17] <xnox> i only get it against debugsysms repo
[14:17] <ahasenack> but I get it even in bionic
[14:17] <xnox> cause that repo doesn't have by-hash publication.
[14:17] <ahasenack> the cause might be different: might be a mirror being updated in a bad way
[14:18] <xnox> ahasenack, but which archieves of bionic?
[14:18] <ahasenack> a mirror
[14:18] <xnox> ahasenack, which mirror =)
[14:18] <ahasenack> br.archive.ubuntu.com
[14:18] <smoser> yeah... its 2 separate things.
[14:18] <xnox> and how it's done, and does it publish by-hashes?
[14:18] <ahasenack> I don't know, I don't maintain it. Just saying that retrying apt-get update still has its use cases
[14:18] <ahasenack> granted, in the case of a bad mirror, retrying for just a few minutes will probably not help
[14:18] <xnox> ahasenack, we need to see your apt-get update log when it happens
[14:18] <smoser> on < xenial, its known problem. but in my experience retrying is unlikely to fix the issue. especially retrying within seconds... what change would you expect in that case to make it work?
[14:19] <xnox> ahasenack, please pastebinit next time it happens.
[14:19] <smoser> on xenial+, it really should not happen.
[14:19] <ahasenack> will do
[14:19] <smoser> and we should not just program in retries to ignore it.
[14:19] <xnox> but to me it looks like it is updated badly.
[14:20] <xnox> actually, no, looks fine
[14:21] <rbasak> A by-hash mirror still needs to sync in the correct order
[14:22] <rbasak> (new by-hash first, then InRelease update, then delete expired by-hash entries)
[14:22] <xnox> country mirrors should be using 2stage sync, which does that.
[14:22] <rbasak> I don't think you can check it's doing that correctly as an external observer.
[14:22] <xnox> well, i'm trying to spot if their by-hashes are out of date ;-)
[14:23] <rbasak> You're a human being trying to spot a subsecond race? OK :)
[14:23] <xnox> rbasak, i believe ahasenack is a human too ;-) and is catching it
[14:23] <smoser> xnox is not mere human
[14:23] <rbasak> I said he gets them now and then.
[14:24] <rbasak> Which is rather different from looking on just one moment :)
[14:27] <xnox> smoser, i wonder if you gonna come to the curtin + s390x call =)
[14:27] <xnox> unless it's an rharper only thing.....
[14:27] <smoser> xnox: you can add me. i have a conflict at the first half hour there.
[14:28] <smoser> but itmight end early
[14:29] <zetheroo> I am having trouble trying to monitor the new time/date service on Ubuntu 18.04 with Zabbix. Prior to Ubuntu 18.04 we were able to monitor using the Zabbix key 'net.udp.service[ntp]' but now with timedatectl/timesyncd this is no longer working.
[14:29] <xnox> smoser, you have mail
[14:29] <ahasenack> zetheroo: via snmp?
[14:29] <ahasenack> just curious
[14:29] <zetheroo> The guys in the Zabbix channel don't seem sure what to do about this so I am asking here ..
[14:30] <zetheroo>  ahasenack: no, using the Zabbix Agent
[14:30] <zetheroo> the question is more how things changed in Ubuntu from 16.04 ?
[14:30] <ahasenack> zetheroo: what exactly was that monitoring before, a process? An open port?
[14:30] <teward> because in 16.04 it didn't use timesyncd, IIRC it used ntp/ntpd
[14:30] <teward> with a local only listener
[14:31] <zetheroo> https://help.ubuntu.com/lts/serverguide/NTP.html.en
[14:31] <zetheroo> 'Since Ubuntu 16.04 timedatectl / timesyncd (which are part of systemd) replace most of ntpdate / ntp.'
[14:31] <teward> as i said - that's what's changed.
[14:31] <smoser> ahasenack: wrt retrying... i dropped the apt retry because what it was really doing was waiting fo the system to boot.
[14:31] <teward> oop i'm tired disregard.
[14:32] <zetheroo> But, yes, it didn't seem to be an issue with 16.04, only really noticed it in 18.04
[14:32] <smoser> i replaced that with better logic to determine when the system was booted.
[14:32] <ahasenack> smoser: ok, got it
[14:32] <teward> zetheroo: if the key is net.udp.service[ntp] then it's likely it was testing ithe NTP UDP socket locally
[14:32] <smoser> i'm not entirely opposed to retry-ing on apt-get update... but i'd  lke it to be more intentional
[14:32] <smoser> ahasenack: does it ever actually fix the problem for you?
[14:33] <zetheroo> teward: right
[14:33] <zetheroo> and we were also using this key to look if the process was running: system.run[ntpstat > /dev/null 2>&1; echo $?]
[14:33] <ahasenack> smoser: not really, it would have to retry for a long time, or I would have to be lucky and the situation (mirror, or flaky network) to resolve itself by coincidence
[14:33] <smoser> in either xenial or <xenial, you're effecitvely just hoping that the mirror will fix itself during your wait.
[14:33] <smoser> right.
[14:33] <xnox> ahasenack, and you are not behind an apt-caching proxy or like a local squid-apt-proxy deployed, anything like that?
[14:33] <ahasenack> smoser: given the failure, I just noted that the retry was removed, and decided t oask
[14:34] <ahasenack> xnox: I am, but when that happened I removed the proxy to test, and it still failed
[14:34] <smoser> so... i dont' see the point in retrying if its not going to do anything in the majority of cases.
[14:34] <ahasenack> xnox: of course, after a while (30min?), it worked again
[14:34] <xnox> ahasenack, but did you clear local apt state too?
[14:34] <zetheroo> since 18.04 neither of these checks work anymore ... so I am wondering what would we be looking for / monitoring with the new time sync service?
[14:34] <xnox> ahasenack, cause little does it know...... if it already saw inconsistent stuff.
[14:34] <ahasenack> xnox: apt-get clean, I don't remember if I rm-f'ed the files
[14:34] <ahasenack> the list files, that is
[14:34] <ahasenack> whatever remains in /var
[14:35] <ahasenack> zetheroo: you could be looking for the process, or for the actual clock/time
[14:36] <zetheroo> ahasenack: I've been trying to find out what the process is that keep the system time sync'ed
[14:36] <ahasenack> zetheroo:  2627 ?        Ssl    0:00 /lib/systemd/systemd-timesyncd
[14:36] <teward> zetheroo: just for kicks, install chrony, and add a 'listen' directive to the end of it, then restart the service and see if Zabbix gets a reply?  It might just be querying the local TCP port directly.
[14:37] <teward> if Zabbix gets a data set then it's probably querying the local ntp service directly with NTP requests
[14:37] <ahasenack> zetheroo: you can also use timedatectl to query its status
[14:37] <ahasenack> try "timedatectl status"
[14:37] <ahasenack> maybe you can change your monitoring to call that and parse its output
[14:38] <teward> ^ this also
[14:39] <zetheroo> teward: According to the Zabbix docs the net.udp.service key 'Checks if service is running and responding to UDP requests.'
[14:39] <teward> zetheroo: which means it's querying NTP over udp/123 by default
[14:39] <zetheroo> there is a separate key for TCP 'net.tcp.service'
[14:39] <teward> zetheroo: same difference except tcp/123
[14:40] <teward> but as i stated, there's nothing responding to NTP requests locally on that port
[14:40] <zetheroo> before 18.04 all we had to do was install ntpstat and the checks were working
[14:42] <ahasenack> afaik you can still use ntp
[14:42] <ahasenack> it's just not the default
[14:42] <teward> ^ this
[14:43] <zetheroo> I already tried that
[14:43] <teward> ahasenack: though, ntpstat relies on ntpq it seems under the hood
[14:43] <zetheroo> installed ntpstat and still nothing
[14:43] <teward> ahasenack: so if NTPd isn't running ntpq might not reply.
[14:43] <teward> therefore ntpstat may fail
[14:43] <ahasenack> well, I mean, switch back to everything ntp-based
[14:43] <zetheroo> apparently you have to actually switch
[14:43] <ahasenack> apt install ntp
[14:43] <ahasenack> that will remove chrony
[14:43] <teward> yep
[14:43] <ahasenack> and disable timesyncd iirc
[14:44] <rbasak> Wait, what are you trying to achieve?
[14:44] <zetheroo> I would really rather use the default services
[14:44] <rbasak> timesyncd is just a client. Looks like you were checking that a server was working before
[14:45] <rbasak> Do you actually want/need a server?
[14:45] <ahasenack> it seems easer for him to get back to ntp rather than switch the monitoring tool to timesyncd
[14:45] <ahasenack> rbasak: I think in the ntp days, even on a client, there was always an open udp port used by it
[14:45] <rbasak> Yes
[14:45] <rbasak> But what is the actual check for?
[14:45] <rbasak> To check that the service is up?
[14:45] <ahasenack> compliance? :)
[14:45] <rbasak> Regular systemd service monitoring will check that.
[14:45] <rbasak> To check that the time is believed to be in sync?
[14:46] <zetheroo> I mean, I thought maybe others were monitoring the time/date info on their servers which were using timedatectl/timesyncd
[14:46] <rbasak> That wasn't being checked before.
[14:47] <zetheroo> It would be a start to be able to monitor that the time/date sync service is running
[14:47] <rbasak> zetheroo: it doesn't make sense, now that we're running a more pure client, to expect what you were doing before to work exactly. You're going to have to define what you actually want checked.
[14:47] <rbasak> OK, so use systemctl status systemd-timesyncd.service for that
[14:47] <smoser> ahasenack: https://bazaar.launchpad.net/~smoser/+junk/check-archive/files
[14:47] <zetheroo> ok
[14:47] <rbasak> Hopefully your monitoring system has a way to integrate better with systemd to check service statuses though.
[14:47] <smoser> that is 'check-archive'. run like:
[14:48] <smoser>   check-archive -v http://br.archive.ubuntu.com/ubuntu trusty-updates
[14:48] <smoser> it will checksum all files comparing against the indexes
[14:48] <smoser> and stores headers and such.
[14:48] <smoser> of responses.
[14:49] <smoser> it reports happy right now on trusty-updates
[14:50] <zetheroo>  rbasak: I was just thinking that ...
[14:50] <smoser> http://paste.ubuntu.com/p/YKhQMqzvBN/
[15:25] <tomreyn> I'm tracking some high / medium 'importance' bugs, where progress feels slow. Some of them are in 'triaged' state (and have been for a while), others confirmed. and there are yet others which have been 'new' for months.
[15:29] <tomreyn> i'm sure everybody is working on more important things and i most likely just don't understand how priorities are internally set (i'm entirely serious here), but with my admittedly very limited insight, it feels the priorities may be wrong, and stable server-live installers which are more suitable for an LTS release should be provided soon.

[15:30] <rbasak> tomreyn: could you provide your best example of a mistriaged bug please?
[15:35] <tomreyn> this is hard to tell, i'll post a couple.
[15:35] <tomreyn> bug 1783413 has been handled, but only in curtin, so nothing has changed from a user perspectiver from what i understand.
[15:35] <tomreyn> bug 1784124 remains 'new' since end of july
[15:36] <rbasak> Thanks
[15:37] <tomreyn> bug 1785354 - if i understand it correctly, means that any system installed with the released server-live installer doesn't get regular file system checks. i would have assigned higher piro then.
[15:38] <tomreyn> bug 1783129 is high prio, but continues to affect anyone using the released (not daily snapshot) installer
[15:38] <tomreyn> i'll stop here. thanks for having a look, rbasak
[15:41] <tomreyn> to anyone seeking commercial consultance, in the current state, i can only recommend to not use the server-live LTS installer, and this is seven months post release.
[15:41] <ahasenack> kstenerud: can I upload https://code.launchpad.net/~kstenerud/ubuntu/+source/fetchmail/+git/fetchmail/+merge/358699 ?
[15:41] <tomreyn> (which is not what i want to do.)
[15:44] <openfire> I still use the "alternate" installer, frankly.
[15:48] <ahasenack> kstenerud: around?
[15:57] <ahasenack> cpaelzer: will you finish this review, or should I grab a slot? https://code.launchpad.net/~kstenerud/ubuntu/+source/openssh/+git/openssh/+merge/358491
[16:03] <rharper> tomreyn: thanks for the feedback; and thanks for filing those bugs and testing
[17:15] <ikla> I'm trying to install 18.04 server on a machine and it boots up and the screen starts flickering and the installation menu does not come up.
[17:15] <ikla> any ideas?
[17:15] <ikla> standard onboard graphics
[17:27] <xnox> ikla, is it serial console or graphical?
[17:27] <xnox> ikla, can you change to a different tty?
[17:27] <xnox> ikla, you can try the alternative server cd too (linked in a separate link from the download pages)
[17:42] <xnox> smoser, do spill the beans =)
[19:17] <mdeslaur> cpaelzer: hi! Mind if I release postgresql 10.6 as a security update?
[19:55] <tomreyn> rharper: i didn't file all of them, just some. thanks to you and all dev's for your continuous work. IMO 18.04 server is really a great improvement over 16.04, netplan is nice (except for some edges where it doesn't work so well, yet), and subiquity / curtin will surely be nice (and much nicer) once they cover the features d-i provides. keep up the good work! :)
[23:55] <sleepee> Has anybody tried to create an Ubuntu VM with virt-install?
[23:56] <sleepee> and used the --extra-args option?
[23:56] <sarnold> five or six years ago
[23:56] <rbasak> virt-install is mostly deprecated by cloud images.
[23:57] <rbasak> Try multipass - https://github.com/CanonicalLtd/multipass - it's much easier
[23:57] <rbasak> And way quicker because there's no need to run an installer.
[23:58] <sleepee> i'm just trying to create a vm on a local kvm host.