[01:38] <theborger> anyone know a reason that BCM5709 would not work when doing an install?
[03:11] <mTeK> I'm trying to test a zfs pool write speed and dd keeps telling me that "dd: failed to open" the path to the zpool
[03:12] <mTeK> I can touch a file in the directory so why wouldn't dd be able to write there?
[03:15] <mTeK> "oflag=direct" removing that fixes the issue.
[03:16] <mTeK> Must be a zfs thing according to google.
[04:05] <jge> if I have a bond0 interface with lacp on, would I see those lacp messages being sent out with tcpdump?
[13:55] <M^tt> Good day, I've just started playing with uvtool and cloud images. I'm wondering where the hostname is set? as it seems to reset on each boot
[14:10] <M^tt> ok so its the datasource disk, i can see it has been pulled out into /run/cloud-init/instance-data.json, just not sure what format that disk is in ? best way to adjust it ?
[14:18] <M^tt> nevermind i guess im just mixing up hostname vs fqdn, it strips out the domain
[14:23] <M^tt> really should be able to set that fqdn though i think
[16:51] <hallyn> omg the 'new' ubuntu server install is annoying (over a slow remote console)
[17:08] <lotuspsychje> hallyn: new as in wich version?
[17:16] <hallyn> it's bionic
[17:16] <hallyn> was trying to do 'manual' disk setup
[17:17] <hallyn> near as i can tell, every time i go down a field, after 1s it times out and goes back to the top, and there are no shortcuts for 'back' (to reread bc i set it up in a shell) or 'done'
[19:47] <pennTeller> Hi guys, can I get your input on how to find the latest network outage on my ubuntu server?
[19:54] <TJ-> pennTeller: what kind of outage?
[19:55] <pennTeller> TJ- my website was down for a few minutes a couple of days ago and I woud like to find out why
[19:55] <pennTeller> TJ- so at the moment it was either my ubunt server failed somehow or my router was blocking visitors
[19:56] <pennTeller> so I am tying to find from the logs if the network was marked as having gone down
[19:56] <TJ-> pennTeller: well, start with the web-server logs, it may be the web server restarted. If not, then look at the kernel log, or various logs via journalctl
[19:56] <TJ-> pennTeller: for a hard loss of ethernet link, check the kernel log ("journalctl -b 0 -k")
[19:57] <pennTeller> TJ- thanks, I agree. I just don't know what I should be "grepping" for
[19:57] <pennTeller> thanks for that suggestion
[19:57] <TJ-> pennTeller: if you know the approx time it happened try using a timestamp to narrow it down
[19:58] <pennTeller> thank you, do you know any particular "greppable" termns?
[19:58] <TJ-> pennTeller: you can do things like "journalctl -b 0 --since 2 days ago' --until '1 day ago' "
[19:59] <TJ-> pennTeller: you can use exact dates/times in those expressions
[19:59] <pennTeller> thanks I will give that a show
[19:59] <TJ-> pennTeller: is systemd-networkd used to manage the network? if so "journalctl -b 0 -u systemd-networkd" may help
[20:00] <SuperLag> I understand it's considered good practice to not leave SSH Host keys on servers you intend for use with cloning. So you delete them.
[20:01] <SuperLag> However, I mistakenly assumed that Ubuntu Server would *automatically* generate new host keys when SSHD starts on boot. It does not. You're left with a machine you cannot log into remotely. Is this intended behavior?
[20:02] <SuperLag> RHEL and CentOS generate the new host keys, automatically, the next time sshd gets restarted
[20:04] <SuperLag> I logged in from the hypervisor console and ran "dpkg-reconfigure openssh-server" and this was the resolution. However, that seems like it shouldn't be necessary. Am I mistaken?
[20:05] <TJ-> SuperLag: that's the way it's done, from openssh-server.postinst script. I'm not aware of any boot-time detection/tooling to do that
[20:09] <SuperLag> TJ-: So if you're prepping a VM for cloning...what is your recourse?
[20:09] <SuperLag> the idea being you don't have a bunch of VMs with the same host key..
[20:10] <TJ-> SuperLag: cloud-init
[20:11] <TJ-> SuperLag: see e.g. https://github.com/canonical/cloud-init/blob/master/doc/examples/cloud-config-ssh-keys.txt