[00:17] <Glorfindel> any likelyhood of issue if I close all user-initiated programs and then upgrade on ubuntu server 16.04?
[00:17] <Glorfindel> it should just come back up and I'd be able to ssh back in, right?
[00:23] <sarnold> it's always nice to have a way to a console if the machine's a few thousand miles away...
[00:25] <leftyfb> If it's a server, it usually has some sort of OOB access (ipmi,idrac,ilo,AMT)
[00:25] <Glorfindel> I guess worst case I reinstall it from scratch and import my backups
[00:25] <Glorfindel> leftyfb: I'm not familiar with that, what does it do?
[00:26] <leftyfb> Glorfindel: what type/model of server?
[00:26] <Glorfindel> 1and1 vps
[00:26] <Glorfindel> the non dedicated one
[00:26] <leftyfb> ok, contact them for support then
[00:27] <sarnold> hmm... lots of possibilities there
[00:27] <sarnold> it might be an openvz container on a system
[00:27] <sarnold> it might be a vm
[00:27] <sarnold> you may or may not have an eas yway to get t oa console through a web interface or something similar
[00:31] <Glorfindel> they have a kvm console
[00:31] <snowgoggles> Glorfindel: something doesn't smell right if you don't have low level management of your vps and you are attempting to upgrade the vps. is this a PaaS?
[00:31] <sarnold> eh, even amazon doesn't have consoles on ec2
[00:32] <sarnold> I'm not saying that's great, but it's not necessarily horrible
[00:32] <Glorfindel> snowgoggles: I can also upgrade to 18.04 via their install disk, but that means copying everything back again afterwards
[00:33] <Glorfindel> I was hoping to just upgrade and keep all my files and programs
[00:33] <snowgoggles> Glorfindel: what service is this?
[00:34] <sarnold> Glorfindel: should be fine. it usually is..
[00:34] <Glorfindel> 1and1
[00:34] <sarnold> juts be sure to have a plan in case things don't go to plan
[00:34] <Glorfindel> 1and1.com rather
[00:34] <sarnold> heh
[00:35] <Glorfindel> I believe it's IaaS
[00:38] <snowgoggles> Glorfindel: site says all vps have console access so i don't see an issue unless it's false advertising
[00:43] <Glorfindel> ok, I'll give it a shot sometime here then
[00:43] <Glorfindel> I think I'll try getting a backup first
[00:48] <sarnold> always a good idea :)
[05:54] <cpaelzer> good morning
[05:59] <lotuspsychje> good morning cpaelzer
[07:35] <lordievader> Good morning
[08:38] <Klendazu> Hello everyone, i have ubuntu 10.04 lucid version, i want to upgrade the php version to 5.6 but in the ondrej ppa repository there is no lucid version, can anyone can help me to upgrade the php version ??
[08:48] <Klendazu> No one can help me ? or tell me where i can find information to install or upgrade php 5.6 into lucid 10.04 version ??
[08:49] <lordievader> Klendazu: 10.04 is EOL for a couple of years.
[08:49] <Klendazu> i know, but i have an iscp version on it
[08:49] <lordievader> Upgrading to a more recent Ubuntu version will give you a newer PHP version automatically.
[08:49] <Klendazu> to upgrade this server is so complicate
[08:49] <Klendazu> the only thing to do is upgrade to 5.6 the php
[08:50] <lordievader> Running EOL software is a security risk.
[08:50] <Klendazu> I know
[11:03] <ahasenack> good morning
[11:34] <lordievader> <freenode_aha "good morning"> Hey ahasenack
[13:02] <ahasenack> hi there lordcirth
[13:02] <ahasenack> er
[13:02] <ahasenack> lordievader:
[13:02] <ahasenack> that one :)
[13:02] <lordievader> 👋
[13:02] <lordievader> How are you doing?
[13:23] <ahasenack> lordievader: good, thanks, and you?
[13:35] <rbasak> ahasenack, kstenerud: I marked bug 1810827 as Triaged/High and added to our backlog. Any reason I shouldn't have done that?
[13:35] <rbasak> Given that we have steps to reproduce etc.
[13:35] <rbasak> I should have asked before making changes, sorry.
[13:36] <ahasenack> that's fine, but there is no patch yet
[13:36] <rbasak> I see
[13:37] <rbasak> I added a bug watch for the upstream project.
[13:37] <rbasak> I think that means it'll hit our triage queue again when the upstream bug gets resolved.
[13:37] <ahasenack> good
[13:37] <rbasak> Thank you for finding the upstream bug etc!
[13:39] <rbasak> ahasenack: triage process question on bug 570944. I think it can be marked Fix Released again. Were you expecting that to be done by the next triager?
[13:40] <rbasak> I ask because it was marked '+' in the triage tool (as expected)
[13:40] <ahasenack> rbasak: oh, I thought mathieu had done it
[13:40] <rbasak> np
[13:40] <rbasak> Not a process question then, thanks :)
[13:40] <ahasenack> rbasak: yep, +1 for fix released again
[13:40] <rbasak> Done
[16:11] <rbasak> cpaelzer_: I had grabbed https://code.launchpad.net/~kstenerud/ubuntu/+source/logwatch/+git/logwatch/+merge/361551 to review
[16:11] <rbasak> Have we collided?
[16:15] <cpaelzer_> rbasak: you grabbed yesterday
[16:15] <cpaelzer_> I added mine as I had a few spare minutes
[16:59] <Slashman> hello, I'm trying to install ubutun 18.04 on a new server, this server has UEFI, doing the manual filesystem setup, I cannot create a partition for EUFI boot... is there a way to get back the old installer somehow to do that?
[17:01] <Slashman> or is there a way to create the uefi partition with the new installer?
[17:01] <ahasenack> Slashman: the installer should take care of creating that partition
[17:01] <ahasenack> I think it calls it "ESP" iirc, just don't worry about it and it should work
[17:01] <ahasenack> that being said, the old installer is still available if you want
[17:02] <Slashman> ahasenack: ok, I'll try to set it up without configuring the ESP, how can I start the old installer?
[17:02] <ahasenack> Slashman: the old installer is another image, let me fetch the link
[17:04] <Slashman> ahasenack: the /boot/efi partition is created after you create a first partition
[17:04] <ahasenack> Slashman: I think it's this one: http://cdimage.ubuntu.com/releases/18.04.1/release/ubuntu-18.04.1-server-amd64.iso
[17:04] <ahasenack> it doesn't have the "live" word in it
[17:06] <Slashman> "/boot must be on a partition on a local disk" when trying to create it on a lv, sad...
[17:11] <TJ-> Slashman: did the installer start in UEFI mode, and is the disk label GPT ?
[17:11] <Slashman> TJ-: yeah, everything worked fine, except the installer doesn't allow /boot on a lv, so I'm starting the old installer image
[17:12] <TJ-> Slashman: that'll be subiquity I presume?
[17:12] <Slashman> is subiquity the name of the new installer,
[17:12] <Slashman> ?
[17:12] <TJ-> Slashman: Yes
[17:13] <Slashman> TJ-: yes then
[17:13] <TJ-> Slashman: I think it stands for 'server' ubiquity (the latter is the name of the desktop installer)
[17:14] <Slashman> ahasenack: thank you for the link, that's the correct image indeed
[17:14] <TJ-> Slashman: I don't use the installers so not touched that, but I do hear a lot of issues since it doesn't have feature-parity with the original debian-installer approach
[17:16] <Slashman> TJ-: well, I found at least one missing feature here ^^
[17:18] <TJ-> Slashman: I prefer using my own scripts and debootstrap
[17:20] <Slashman> TJ-: I would love to, it's just a question of time
[17:21] <TJ-> Slashman: I know :) I'm typicall deploying LUKS + RAID + LVM so it is worth it
[17:23] <Slashman> I may just clone the system disk (which is on hardware raid) when I'll have to install a lot of systems
[17:28] <siwica> I am trying to setup a bridge br0 with an ip address using netplan. Can anybody give me a hint why ifconfig does not show an ip for bro with the following config? https://pastebin.com/SWfZEJJ8
[17:33] <lordcirth> siwica, I gave up on getting netplan to work properly with bridges. I write configs in /etc/systemd/network instead. It's not even harder.
[17:34] <TJ-> siwica: firstly check if a systemd network definition has been generated for the bridge in /run/systemd/network/
[17:35] <TJ-> siwica: if so, then usr journalctl to check for problems with it
[17:37] <siwica> TJ-: The systemd network definition looks ok
[17:37] <siwica> Also I can see the bridge interface running ifconfig. Just its IP is missing.
[17:39] <siwica> The content is the following: https://pastebin.com/gipdEC69
[17:39] <siwica> Nothing to see with journalctl it seems
[17:40] <siwica> lordcirth: If nothing else works, I will revert to doing this. Just thought I should probably adhere to the new way of doing things.
[17:41] <Slashman> I agree with lordcirth, I'm not a fan of adding an other layer on top of systemd-networkd
[17:41] <Slashman> siwica: new ubuntu way, I'm not sure if any other distribution are using netplan.io by default
[17:41] <lordcirth> netplan is from Debian
[17:42] <Slashman> lordcirth: oh, I though it was from canonical, is this planed to be in debian 10?
[17:42] <cyphermox> it is from Canonical
[17:43] <Slashman> I still don't like this additional layer anyway
[17:43] <cyphermox> it's recently been added to Debian
[17:43] <cyphermox> siwica: you'll need to look at what networkctl says. sometimes the issue has to do with how the network interfaces are identified
[17:44] <lordcirth> cyphermox, oh, thanks
[17:44] <TJ-> siwica: if there's a systemd.network config for the bridge then the issue isn't netplan, unless it is generating an incorrect config. Is the physical interface slaved to the bridge up and active?
[17:45] <siwica> TJ-: The physical interface is up but not running. No network cable plugged in there as of now.
[17:45] <TJ-> siwica: Thought so. That's expected of systemd. We've seen a few people caught out by this. Address not assigned until at least one slave interface is active
[17:46] <siwica> So if I plugin a cable the address should be shown?
[17:46] <siwica> I'll try this out after dinner :)
[17:47] <TJ-> siwica: Yes; you're not the first to be stumped by this !
[17:47] <siwica> TJ-: Ok, thanks a lot. This cost me a couple hours unfortunately.
[17:49] <TJ-> siwica: yeah, despite it not being netplan.io's fault it ought to be documented behaviour
[17:49] <cyphermox> siwica: what version of netplan?
[17:50] <siwica> cyphermox: 1.10.1-5build1
[17:51] <siwica> (Not sure if this is the version of the Debian package of the upstream version number)
[17:51] <siwica> *or
[17:51] <siwica> TJ-: Yeah, this would help.
[17:53] <siwica> In any case I don't really understand the trend of encoding everything in YAML files nowadas at any cost.
[17:54] <lordcirth> I have no problem with YAML - I use Saltstack all day. Netplan just doesn't *do* anything
[17:54] <lordcirth> It takes your input, introduces subtle problems, then exports exactly the same data to networkd
[17:54] <siwica> But lets you write YAML :D
[17:55] <siwica> Maybe that's enough of an advantage to some people
[17:55] <lordcirth> I write my networkd files with Salt, which is YAML! :P
[17:55] <lordcirth> I can generate bridges and vlan ifaces from a list of vlan ids.  It's great.
[17:56] <siwica> I might check it out at some later point when I am not having time pressure
[17:59] <TJ-> siwica: the drive, I think, was to have a single config work for multiple network management tools, hence the 'renderers' in netplan.
[18:38] <cyphermox> siwica: that's very very bad as a version number
[18:39] <cyphermox> siwica: you may have installed "netplan" instead of "netplan.io"; there's a calendar package with a similar name, so it's a relatively common issue
[18:40] <cyphermox> should be something like 0.36.2 or bigger, but still starting with 0.something.