[07:29] <lordievader> Good morning
[11:30] <lotuspsychje> DemomanCA: explain the details of your issue here please
[11:31] <lotuspsychje> DemomanCA: also idle & patient a bit, as volunteers might still wakeup at this time
[11:32] <DemomanCA> Thanks lotuspsychje, so I have a fresh 18.04 install, 2 network interfaces together in an LACP bond. Interface works fine on boot, grabs IPv4 and IPv6 address from my DHCP server, all good. However, any time systemd-networkd restarts, the network stops working. Main causes are systemd updates or if I change a config and run sudo netplan apply. No idea where to start troubleshooting
[11:32] <DemomanCA> this....
[17:21] <muhaha> Anyone is using OpenID,SAML for login to Ubuntu ?
[19:03] <Delvien> Changed /etc/hostname, and entries in /etc/hosts and still cant get ubuntu server to change its hostname. what am I missing?
[19:04] <tomreyn> dhcp
[19:05] <Delvien> its statically set
[19:05] <tomreyn> which ubuntu release is it?
[19:05] <Delvien> 18.04.1
[19:05] <tomreyn> does "hostnamectl status" report what you expect it to report?
[19:06] <Delvien> Static hostname is correct, transient hostname shows old one?
[19:07] <Delvien> did a hostnamectl set-hostname, gonna reboot see if it sticks this time
[19:07] <tomreyn> i would quote the man page but it's a bit long
[19:08] <Delvien> and it reverted again
[19:10] <tomreyn> hmm, how did you install?
[19:10] <teward> did you edit /etc/cloud/cloud.cfg and make sure yo uset preserve_hostname from 'false' to 'true'?
[19:12] <teward> if you used the live installer it might do evil things like this if you reboot and revert the hostnames after you make changes
[19:13] <Delvien> i did live installer, but preserve_hostname is set to false
[19:14] <teward> set it to true
[19:14] <teward> it should now stick
[19:14] <Delvien> OHhh i see
[19:14] <Delvien> man things have changed for ubuntu server since the last time i used it
[19:15] <teward> cloud-init is an annoying piece of [CENSORED REDACTED CENSORED] and if that file is present in the install it can cause headaches
[19:15] <teward> nah it's a subiquity / live installer ISO headache
[19:15] <teward> if you use the alternate installer it still works as normal
[19:15] <Delvien> yeah had to fix the damn sources too
[19:15] <teward> though you still need to hostnamectl and such
[19:16] <Delvien> Ahhh that did it
[19:16] <Delvien> thank god, i was about to switch back to fedora server lol
[19:18] <powersj> teward, have you filed a bug against subiquity for this behavior?
[19:18] <teward> powersj: IIRC this is known cloud-init behavior
[19:18] <teward> not subiquity
[19:19] <powersj> that doesn't mean subiquity is doing the right thing
[19:19] <teward> true, but i haven't filed a bug yet, no.
[19:19] <teward> E:TOOBUSY
[19:20] <teward> powersj: also, since I use a modified 18.04.1 template to deploy all my servers, or I'm doing per-system manual installs, or installs that're LXD container based... I don't have the issue anymore
[19:20] <teward> so i've never gotten around to it :P
[19:28] <teward> powersj: assuming I don't forget, should I file a bug against cloud-init or subiquity in this case?
[19:28] <teward> because it sounds like subiquity needs to adjust the cloud config but doesn't.
[19:28] <teward> and I haven't tested the 18.10 or 19.04 dailies yet to see if they exhibit the same behavior
[19:30] <powersj> teward, I'd say start with subiquity
[19:30] <teward> ack
[19:30] <teward> powersj: would i have to do that from a live session or would filing from my 18.04 install suffice?
[19:30] <teward> at least for the `ubuntu-bug` stuff
[19:30] <powersj> your install is fine
[19:32] <teward> oh... that's unusual
[19:32] <teward> $ ubuntu-bug subiquity
[19:32] <teward> dpkg-query: no packages found matching subiquity
[19:32] <teward> :|
[19:33] <teward> guess i'll do it manually then
[19:37] <teward> powersj: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1809155 <--
[19:38] <powersj> teward, thanks!
[19:39] <NyanCat> ... Anyone know where I can find auth.log or like, anything else?
[19:39] <NyanCat> my /var/log is uncomfortably empty
[19:41] <sarnold> did you happen to mount other filesystems over it?
[19:41] <sarnold> or are you currently 'in' a namespace without populated directory?
[19:41] <NyanCat> No, it's a brand new system
[19:41] <NyanCat> There are files *in* /var/log, just not auth.log, syslog or kern.log
[19:42] <teward> powersj: five monopoly bucks says it's a cloudinit headache problem :P
[19:43] <NyanCat> Should probably mention that this is OVH's 16.04 ARM template
[19:43] <NyanCat> Which is already stupid annoying to begin with as it's missing some very basic packages
[19:43] <NyanCat> but I can't imagine why they'd have taken out logging
[19:47] <tomreyn> hdn't ovh signed this agreement not to modify ubuntu images?
[19:47] <NyanCat> I'm missing quite a few things by the looks of it, TBH
[19:48] <NyanCat> I was able to read the sshd logs with journalctl but that's not really a replacement (IMO) for auth.log
[19:48] <NyanCat> I'm gonna send in a ticket asking them 'the hell they're doing
[19:49] <tomreyn> there used to be this https://www.reddit.com/r/linux/comments/4ov74y/ovh_founder_on_twitter_canonical_is_attempting_to/
[19:49] <teward> tomreyn: did they?  Was that enforced with Canonical Legal?
[19:49] <teward> if it was we can go bash OVH with a hammer... :P
[19:49] <tomreyn> i don't remember the final outcome, but have a hunch they agreed to the terms in the end.
[19:50] <NyanCat> https://www.irccloud.com/pastebin/TUpJsg4e/
[19:50] <NyanCat> for anyone curious though there's the directory structure in /var/log
[19:50] <tomreyn> is this a VM or dedicated?
[19:50] <NyanCat> It's a dedicated server
[19:51] <NyanCat> One of their ARM servers though
[19:51] <tomreyn> and which version does lsb_release -ds report exactly?
[19:51] <NyanCat> well that's just it
[19:51] <NyanCat> lsb_release doesn't work
[19:51] <NyanCat> /etc/os-release $VERSION is set to 16.04 though
[19:52] <teward> lsb_release doesn't work how?
[19:52] <teward> doesn't say anything?  isn't installed?
[19:53] <teward> E:NotEnoughInfo
[19:53] <tomreyn> also: cat /etc/issue
[19:53] <NyanCat> Looks like just lsb-release isn't installed
[19:53] <NyanCat> stand by
[19:54] <tomreyn> if you could pastebin /etc/os-release that's be nice, too
[19:54] <NyanCat> Ubuntu 16.04 LTS
[19:55] <tomreyn> so it's 16.04.0 apparently
[19:55] <NyanCat> https://www.irccloud.com/pastebin/1IWduBTP/
[19:55] <tomreyn> it is :-(
[19:55] <tomreyn> i suspect there may be no syslogging daemon installed, thus no /var/log/syslog
[20:32] <NyanCat> tomreyn: that's exactly it
[20:32] <NyanCat> rsyslog is not installed
[20:33] <NyanCat> It just seems, if OVH was going for a minimal image to use on these servers, that's probably the one thing I wouldn't have left out of the image, you know
[20:37] <NyanCat> so ¯\_(ツ)_/¯
[20:37] <NyanCat> issue fixed
[20:47] <tomreyn> NyanCat: you might want to install updates, though, since you must be lacking a lot.
[20:47] <NyanCat> that's the other screwy thing
[20:47] <NyanCat> there's nothing available
[20:47] <tomreyn> it'd be nice to see your apt-cache policy (after apt-get update)
[20:48] <NyanCat> https://www.irccloud.com/pastebin/T4mM5IDb/
[20:51] <tomreyn> no security patches for you
[20:51] <tomreyn> nor any updates
[20:52] <NyanCat> well, it's not like i needed security, it's not paramount or anything, right???
[20:52] <NyanCat> ....*nervous laugh*
[20:52] <tomreyn> NyanCat: i'm sure your host can provide a qualified statement on this.
[20:53] <NyanCat> lol
[20:53] <NyanCat> OVH and qualified in the same sentence
[20:54] <NyanCat> Worth a shot, but sending a trouble ticket to OVH is like giving a kid $5 to go get bread and expecting them to come back with bread
[20:54] <tomreyn> in the past it's been common for hosters (i've seen several do so) running arm systems to fix the kernel image to the image they shipped, for whihc no sources were available.
[20:54] <tomreyn> that's because upgrading them is not neccessarily flawless, and if they break repairing cantake more time.
[20:55] <tomreyn> and if you decide to stick to a certain kernel image you may want to keep the user space the same, too, i guess. so maybe this is what you'Re seeing.
[20:56] <tomreyn> is it a good idea to do this, and connect this to the internet? definitely no.
[20:56] <NyanCat> I'm running "vanilla" according to them
[20:56] <NyanCat> When you image the server one of the advanced configuration options is to use the distribution or vanilla kernel
[20:56] <tomreyn> cat /proc/version should tell
[20:57] <NyanCat> ..... no way
[20:57] <NyanCat> I'll send you a message for this one, it does reveal IPs
[21:00] <tomreyn> NyanCat: the FQDN in the kernel string just reveals the hostname of the system this kernel was built on.
[21:04] <NyanCat> So it's purely coincidental that the FQDN happens to resolve to an IP in the same subnet as my server
[21:04] <NyanCat> I suppose, if that particular block was reserved for their ARM servers
[21:06] <tomreyn> i don't know how they do IPAM, there is #ovh, maybe someone knows there, but i doubt they'll disclose it.
[21:43] <mwhudson> teward: thanks for filing that bug
[23:48] <maddawg2> hmm so i installed ubuntu server 18.04LTS and it seems (correct me if I'm wrong) that 3rd party repositories are disabled?
[23:48] <maddawg2> if so how do i enable them
[23:49] <sarnold> add files to /etc/apt/sources.list.d/ as you decide you want them
[23:50] <mwhudson> maddawg2: you expected some third party repos to be enabled by default?
[23:51] <maddawg2> umm no i added them but for whatever reason apt-get is providing me errors now that were not existing in 16.04
[23:51] <maddawg2> i think maybe i found the reason
[23:51] <maddawg2> universe repository is disabled i think by default
[23:51] <mwhudson> ah that
[23:51] <maddawg2> it was unable to grab dependencies
[23:51] <mwhudson> that's fixed in the latest iso btw
[23:51] <maddawg2> ah
[23:52] <maddawg2> good to know.. i downloaded this one maybe 6 months ago but never got around to upgrading my server
[23:52] <mwhudson> http://releases.ubuntu.com/18.04.1.0/
[23:53] <maddawg2> hm the ISO i have is labeled: ubuntu-18.04.1-live-server-amd64.iso
[23:54] <maddawg2> that not the same as 18.04.1.0?
[23:54] <tomreyn> file names will be the same
[23:54] <tomreyn> checksums will differ
[23:54] <tomreyn> actually i'm wrong, sorry
[23:55] <tomreyn> the updated ISOs seem to be named ubuntu-18.04.1.0-live-server-amd64.iso (extra ".0")
[23:57] <maddawg2> i wonder why it wasnt there to begin with tbh
[23:58] <maddawg2> seems like a big oversight... makes me wonder wehat else is borked :-P
[23:58] <sarnold> an apt update && apt upgrade will show you the rest :)
[23:59] <tomreyn> maddawg2: if you would like a similar result to what the old (debian) installers provided, then use the 'alternative' (non-'live') server installer