[08:17] <lordievader> Good morning
[13:44] <coreycb> sahid: designate is pushed/uploaded. thanks.
[13:46] <sahid> thanks coreycb
[13:53] <coreycb> cool, thanks
[13:56] <coreycb> sahid: aodh pushed and uploaded
[13:56] <coreycb> sahid: i just backported a new python-diskimage-builder so hoping that fixes up the ussuri backports
[14:00] <sahid> ack, i think we need to bump the ersion of python3-sqlalchemy-utils to >= 0.33.10
[14:43] <coreycb> sahid: ok I pushed a branch to lp:~ubuntu-server-dev/ubuntu/+source/python-sqlalchemy-utils. I see upper-constraints at 0.36.0.
[16:56] <coreycb> sahid: networking-* uploaded
[17:09] <sahid> coreycb: ack thanks
[21:40] <okdana> hello, could someone help me understand how i'm meant to use pg_upgradecluster (tool for upgrading postgres databases) when the ubuntu repos don't maintain the older postgres packages it needs to work?
[21:40] <okdana> e.g. cosmic/disco/eoan only have postgresql-11
[21:42] <sdeziel> okdana: I've only used this tool when upgrading from LTS to LTS but it shouldn't matter. According to my notes, the new version will be able to upgrade the old cluster
[21:42] <sdeziel> okdana: when I upgrade from Xenial to Bionic, I do: pg_dropcluster --stop 10 main && pg_upgradecluster 9.5 main && pg_dropcluster 9.5 main
[21:43] <okdana> that's what i'm planning to do, experimenting with upgrading from bionic to focal (which does have 11 and 12, but obv i'm on 10)
[21:43] <okdana> but pg_upgradecluster returns: pg_controldata not found, please install postgresql-10
[21:43] <okdana> and it was my past experience that it needs the binaries from the current/old version
[21:44] <sdeziel> okdana: IIRC, the old PG version is letf installed after an upgrade, no?
[21:45] <okdana> for an in-place upgrade, probably, yeah
[21:45] <okdana> you reckon that's the intended use case?
[21:45] <sdeziel> okdana: right, I've only used that tool when doing in-place upgrades and thought it was your case
[21:46] <sdeziel> okdana: if you need the old version on a freshly installed machine you can probably resort to using apt.postgresql.org
[21:46] <okdana> unfortunately not, it will be a sort of 'a/b' situation, where focal is installed from scratch onto another partition and then we switch over there
[21:47] <okdana> yeah, might have to
[21:47] <okdana> i think we might have done that last time actually, but we were already using their repo anyway
[21:49] <okdana> unfortunately the postgres repo doesn't have any focal packages yet
[22:00] <Ussat> anyone have a min to look at something. My syslog-ng conf file has directives for both UDP and TCP, but I am not getting any logs via tcp, netstat shows I AM listening.  https://pastebin.com/K5HV6amj
[22:00] <Ussat> anyone have any ideas, this is latest Ubuntu 18.X
[22:00] <Ussat> UDP works fine
[22:48] <Fieldy> hello, how do i restart the network on ubuntu server 18.04.3 LTS? I would rather not reboot just to do this
[22:53] <mybalzitch> have you tried "sudo service networking restart"
[22:53] <Fieldy> ahh, i was doing sysctl not service. i'll give that a shot
[22:59] <Fieldy> er systemctl. tired.
[23:07] <mybalzitch> :)
[23:07] <mybalzitch> I'm not sure it works with netplan, might only be a ifupdown thing
[23:08] <mybalzitch> but I purged that trash from my install
[23:08] <mybalzitch> sudo service netplan restart might do something
[23:20] <Fieldy> thanks!
[23:37] <tomreyn> on 18.04, the "service" command should really be a wrapper around systemctl, like it was a wrapper around upstart and Sys V init in the past.