[00:24] <hdon__> hi all :) is ubuntu server configured to synchronize clock via ntp by default?
[00:26] <sarnold> hdon__: I believe it is, at least the seeded-in-ubuntu tool reports that it's in the ubuntu-server dailies, and in ubuntu
[00:28] <hdon__> thanks sarnold :)
[00:31] <hdon__> can i set up a chroot and install trusty on it from a xenial system?
[00:32] <sarnold> hdon__: debootstrap can probably help
[00:32] <sarnold> hdon__: why do you want a trusty chroot?
[00:32] <sarnold> there may be better ways to do whatever it is you're doing, I get skeptical whenever anyone uses a chroot for anything :)
[00:33] <hdon__> sarnold: need to work on a legacy app
[01:02] <mwhahaha> jamespage, coreycb: just a heads up but neutron tempest tests seem to be in a bad spot for pike (i think we're still on pike) http://logs.openstack.org/23/498723/27/check/puppet-openstack-integration-4-scenario001-tempest-ubuntu-xenial/856db37/job-output.txt.gz#_2017-12-19_20_54_29_276144
[04:06] <RoboApe> hi all
[06:16] <cpaelzer> good morning
[06:39] <cpaelzer> rbasak: was there any hickup on the slof SRU-MPs?
[06:39] <cpaelzer> rbasak: you mentioned to look at them already yesterday, but I see no update
[06:39] <cpaelzer> rbasak: if there is anything I shall resolve please let me know - or did you again hit things on the review process itself?
[07:06] <lordievader> Good morning
[09:06] <adac> any idea what this problem might be about? https://i.imgur.com/s2T7xra.png hapening to me on 16.04 with proxmox
[09:28] <TJ-> adac: ATA SFF is the legacy ATA IDE interface, and it looks like the device is erroring in a way the kernel cannot handle
[09:37] <adac> TJ-, thank you! Is there a way I can find out what exactly it is causing it?
[09:37] <adac> I now upgraded the kernel everywhere
[09:41] <TJ-> adac: Clues, if any, should be in the kern.log
[09:47] <adac> TJ-, Had a look at it, but it doesn't seem be written out actually
[09:47] <TJ-> adac: is the BUG happening during early boot time?
[09:48] <adac> TJ-, actually the host was running for quite some time. Then at some point it was not responsive anymore
[09:48] <adac> and then I had a lookk at proxmox vpn view
[09:48] <adac> where I got this error
[09:48] <TJ-> adac: so there should be kernel logging then
[09:49] <TJ-> the only time logging won't be available is at early boot before the file-system containing /var/log/ is mounted read-write, or at shutdown
[09:49] <adac> TJ-, this is booting up log or? https://gist.github.com/anonymous/705067de0b94127485abcaa1d26fff31
[09:50] <TJ-> adac: yes, usually /var/log/kern.log
[09:51] <adac> TJ-, yes and before this booting up log entries I tried to search for an error but there seems to be none
[09:51] <adac> is there a good way to search for errors?
[09:51] <adac> in the log file
[09:51] <TJ-> adac: reading is the only way :)
[09:51] <adac> hehe ok
[09:52] <adac> I mean I'd expect the error right before the reboot, or?
[09:52] <TJ-> adac: basic procedure is locate the boot-up entries after the system restarted and work backwards. You'd expect any clues to be just before the new-boot messages
[09:52] <adac> *reboot entries
[09:52] <adac> exactly
[09:52] <adac> but there is noe
[09:52] <adac> none
[09:53] <TJ-> adac: but sometimes they could have happened some time ago, rather than being Bang! Snap! Drat! Oh! BUG!
[09:53] <adac> hehe ok I will scroll up again a bit then :)
[09:53] <adac> brb
[09:54] <TJ-> adac: I'd focus on the ATA devices attached, check their SMART status (smartctl), and so on
[10:03] <adac> TJ-, ok! One more question: can this also come from external mounts like with davfs?
[10:04] <TJ-> adac: anything on an ATA interface I'd think
[10:06] <adac> TJ-, what really seems to make problems is this davs mount
[10:06] <adac> it is completely unreliable
[10:06] <adac> it is mounted on all my servers
[10:06] <adac> and yesterday I was copying over something there from another server
[10:07] <adac> and I think nearly at the same time this incident happend
[10:09] <TJ-> adac: I can't imagine how a webDAV network mount is going to be using ATA!
[10:10] <adac> me neither actually
[10:10] <adac> :)
[15:03] <coreycb> jamespage: this is ready for a review when you get a chance: https://code.launchpad.net/~ubuntu-server-dev/ubuntu/+source/percona-xtradb-cluster-5.7/+git/percona-xtradb-cluster-5.7/+ref/master
[15:09] <coreycb> jamespage: and the xtrabackup updates are here for now. once approved i think they can be pushed to the existing xtrabackup repo: https://code.launchpad.net/~ubuntu-server-dev/ubuntu/+source/percona-xtrabackup-2.4.9/+git/percona-xtrabackup-2.4.9