[00:00] <TJ-> teward: It might need to be templated to allow stunnel4@XXXX.service for per-connection control
[00:02] <teward> TJ-: actually fine with it being one entire service controlled by one master
[00:02] <teward> like uwsgi is
[00:02] <teward> at least for MY use case
[00:03] <teward> but whichever, if you want to take a stab at it feel free
[00:03] <teward> i'll even build and live-test it :)
[00:03] <TJ-> teward: being ablr to bring up each tunnel separately would be better; rather like how I have the pppd@ service
[00:03] <teward> true
[00:03] <teward> TJ-: well, if you want to )
[00:03] <teward> TJ-: well, if you want to :)
[00:03] <TJ-> teward: I'll see if that is feasible since it also implies multiple processes
[00:04] <teward> right
[00:04] <teward> TJ-: hate putting more projects on you though xD
[00:04] <teward> but i'd like it to be SystemDified instead of old xD
[00:05] <TJ-> Curtman: the targetcli-fb package doesn't include any service files; the man-page is indicating that /some/ distro maintainers *may* add such service control files, but Debian/Ubuntu haven't so far as I can see in 18.04 at least
[00:05] <TJ-> teward: It's fine; It's light entertainment for me
[00:06] <sarnold> hah, on my unpacked archive sources, the only target.service file I have ... came from a centos srpm that I unpacked.
[00:06] <teward> lol "light entertainment"
[00:06]  * teward conscripts TJ- to do all the work*
[00:06]  * TJ- is 4 hours past bed-time and running away fast :p
[00:07] <sarnold> ha :)
[00:10] <teward> heh
[00:30] <Curtman> I wonder what use targetcli could possibly be without a service to actually make the thing available once you configure it.  :/
[00:47] <Curtman> Oh well.. tgtd seems like the way to go anyway.  Seems strange though.
[04:14] <cyberfingers> I am using a php app SEO Panel, which I want to connect to an external MySQL Server. What do I need to install so this will work? Thanks
[06:30] <lordievader> Good morning
 good morning.
[07:50] <lordievader> Morning
[07:51] <jc__> Two days back we were discussing about 2 NIC on ubuntu 16 and 18.
[08:08] <jc__> Anyone with insight in "systemd-resolve --status", I have configured two NIC on the ubuntu server 18. But I am noticing only one NIC details in the logs
[08:09] <blackflow> !details
 and <ubottu> I have posted logs here. https://paste.ubuntu.com/p/QdVZyz84bP/
[08:25] <jc__> if you look at my configuration of netplan. I have configured the two interfaces , but "systemd-resolve --status" show only one of the configuration in the status. I am not able to use second NIC to ssh or ping from other servers
[08:27] <jc__> similar issue , I am facing on ubuntu 16 also. I could not figure out the reason.
[08:28] <jc__> these interfaces are connected to two vlans on the switch.
[08:28] <blackflow> jc__: not sure I understand your problem. what does systemd-resolved have to do here?
[08:29] <blackflow> looks like resolved is using eth0 to send out DNS requests. or more precisely, it's using the default gateway route for the configured lookup IPs. systemd-resolved is just a stub resolver, it requires an upstream recursive (caching) resolver
[08:29] <jc__> My main issue is, I am not able to use second NIC. I am not sure, what is actual issue.
[08:29] <blackflow> which one is "second".... eth1?
[08:29] <jc__> eth1 is second NIC
[08:30] <blackflow> can you ping 10.2.14.1 ?
[08:30] <sahid> jamespage: cinder is needing ddt => 1.2.1 and we ship 1.1.1 with eoan
[08:30] <jc__> yes, I can from the server
[08:30] <jc__> root@h019:~# ping -c2  10.2.14.1
[08:30] <jc__> PING 10.2.14.1 (10.2.14.1) 56(84) bytes of data.
[08:30] <jc__> 64 bytes from 10.2.14.1: icmp_seq=1 ttl=255 time=6.47 ms
[08:31] <blackflow> jc__: is that a "yes"?
[08:31] <jc__> sorry. Yes. I can ping
[08:31] <blackflow> jc__: right. can you ping any other IP in the 10.2.0.0/16 subnet?
[08:32] <jc__> yes, I can ping all the ips which are configured in 10.2.0.0/16 subnet.
[08:32] <blackflow> jc__: so what's the problem then?
[08:33] <jc__> I am not able to connect to server IP: 10.2.14.119 using ssh or I can not ping the server
[08:34] <jc__> I am able to connect to the server using  10.1.14.119 (eth0) first NIC
[08:35] <blackflow> which means the server is configured for 10.1.14.119 and not 10.2.14.119?
[08:35] <blackflow> are you connecting by hostname or by ip?
[08:35] <jc__> I have connected using the IP, not using hostnamr
[08:36] <jc__> So, I configure the server with more than 1 IP
[08:36] <jc__> How can ***
[08:37] <blackflow> Which one? The one you can connect to over 10.1.14.119 but not over 10.2.14.119 ?
[08:38] <jc__> Yes, I can connect to server using  10.1.14.119 but not over 10.2.14.119. I want to use both, is it possible to configure the server.
[08:41] <blackflow> jc__: so you have two cables going to that server? one for eth0 and one for eth1?
[08:42] <jc__> Yes, I have connected two cables to eth0 and eth1. They are basically connected to same switch in different vlan.
[08:44] <blackflow> and did you configure this other servers, for required IPs on specific NICs?
[08:44] <blackflow> *server
[08:47] <jc__> I did not configure other servers. Servers which I configured are not able to use more than 1 NIC.     On this server, I have configured the specific ips, during the installation of ubuntu 18.
[08:47] <blackflow> jc__: oh also, some massive confusion here you caused, the pastebin you posted, is that THE server you can't access at 10.2.14.119 from some other machine in the network?
 : sorry for the confusion. All the logs , I have provided are from the same server, to which I am trying to connect.    I am able to connect to the server using  10.1.14.119 (eth0), but I am not able to connect to the server using ( 10.2.14.119).
[08:51] <blackflow> jc__: can you pastebin the output of `ip a` ?
[08:52] <jc__> From other servers, I can ping  10.1.14.119, 10.2.14.119. But I am not able to ping the configured server from firewall using  10.2.14.119 or ssh using  10.2.14.119.     From my firewall I can ssh and ping using  10.1.14.119
[08:53] <jc__> `ip a`  -->  https://paste.ubuntu.com/p/SnQQzKFspX/
[08:53] <blackflow> if you can ping 10.2.14.119 from other servers, then everything is fine on this server. you apparently have a problem elsewhere in your 10.2.0.0/16 network
[08:54] <blackflow> unless that 10.2.14.119 is not _this_ 10.2.14.119 but some other machine in the network has it....
[08:57] <jc__> No other machine in the network has this IP. But I will find out more about the network settings for 10.2.0.0/16. I didn't set it up. I am not completely sure, where to look for this configuration. By chance these details will be on the switch?
[08:59] <blackflow> jc__: I have no idea how your network is laid out and what with.  Point is, if you can ping _this_ machine via 10.2.14.119 from another, then as far as _this_ machine config is considered, it's okay.
[09:12] <jc__> what about the routes. something might be wrong with the routing?
[09:12] <jc__> blackflow:
[09:21] <blackflow> jc__: not if you can ping _this_ machine from any other and/or any other machine from _this_, in the 10.2.0.0/16 subnet
[09:23] <jc__> blackflow: okey Thanks. I will more on other networking issues
[10:11] <geodb27> People : hi ! What would be the best way to setup a floating ip on ubuntu 18.04 LTS server editions machines. I've got three of them and from what I've reat, the network config is handled by netplan now.
[10:13] <blackflow> geodb27: what do you mean exactly by floating IP.
[10:15] <geodb27> Hi blackflow and thanks for your concern. I've three servers. Each has a static IP and I don't want to change anything about that. Aside, I'd like to have an IP that would enable me to reach my cluster formed of these three machines. I know that it can be done under some other systems (like redhat) with pacemaker for example.
[10:16] <geodb27> With such, a static ip address, the IP is assigned to one only of these servers and is automatically assigned to one of the alive servers of the cluster if the one that handles it goes down.
[10:16] <blackflow> well the simplest solution is to setup this secondary IP as additional static IP, then the router is reponsible for proper routing
[10:18] <blackflow> now if you don't have such a router with such capabilities (eg. by a hosting company offering floating IPs), you'd have to implement it yourself. pacemaker+corosync is one way, yes.
[10:21] <geodb27> One "current" setup for this is when you want an apache server to never be down. The floating ip is assigned a dns name. An a service on the cluster is responsible to have the ip and the service (here apache) to be hosted on only one machine at a time.
[10:21] <geodb27> So, well, if I read you, I'd have to go with pacemaker and corosync for this, right ?
[10:21] <geodb27> Will it not conflict with netplan ?
[10:23] <blackflow> wouldn't know, I'm not using neplan. but in this particular case you set up the floating IP as a static IP and then make it "floating" on the router side.
[10:23] <geodb27> I can't do that on the router side.
[10:26] <blackflow> so then you need the complex way, with a HA cluster setup like corosync+pacemaker
[10:39] <geodb27> Thanks for your kind help blackflow. I'll head for this, then :-)
[12:13] <ahasenack> good morning
[14:13] <supaman> when ubuntu-server 18.04 starts up and iptables is activated (not ufw), from where does iptables get its rules?
[14:16] <ahasenack> maybe you have iptables-restore being called from somewhere?
[14:16] <ahasenack> but the package doesn't provide an initscript, or systemd service, for that
[14:17] <sdeziel> supaman: I know that iptables-persistent does just that
[14:17] <sdeziel> iptables-persitent stores rules under /etc/iptables/rules.v*
[14:17] <supaman> hmm ... I do have a systemctl status iptables ...
[14:19] <supaman> there is is this app, iredapd that is set up on this server which seems to be doing something with iptables
[15:37] <jamespage> sahid: OK uploaded everything apart from barbican - see notes in tracking sheet
[15:49] <sahid> jamespage: ACK, thanks a lot for your reviews
[15:49] <jamespage> np
[18:06] <nitzicuile> Hi ppl. I was here yesterday. I was having problems with do-release-upgrade (18.10 -> 19.04). I was using Dspace with Tomcat8. I already installed Tomcat9 and Dspace is working. The problem is SOLR, it seems that something is not right. The connection with postgresql is ok, but Dspace can't show data due to SOLR fail. ¿Any idea? https://pastebin.com/pjTk9W4P
[18:07] <nitzicuile> I am pretty sure that config files are ok. It works before the upgrade and Tomcat9 installation.
[18:09] <lordcirth> nitzicuile, you might want to find a channel about that software.
[18:09] <lordcirth> !alis | nitzicuile
[19:16] <ahasenack> ddstreet: around?
[20:03] <slashd> ahasenack, ddstreet is on vacation
[20:05] <ahasenack> ok