[07:02] <lordievader> Good morning.
[11:50] <blackflow> Hello. I'm running Bind9 as resolver in our ipv4 only network. I'd like to force it to use ipv4 only, there's a flag "-4" for "named" executable. I've added it to OPTIONS in /etc/default/bind9, restarted named, but "-4" is not showing in ps output, and it keeps trying ipv6
[11:50] <blackflow> I tried copying /lib/systemd/system/bind9.service  to /etc/systemd/system/  and changed the ExecStart to include -4   , but still the same
[11:51] <blackflow> How do I force the -4 option to the named executable of Bind9?
[11:51] <blackflow> (Ubuntu 16.10)
[17:25] <r33d_> hi
[19:24] <fishcooker> lordievader: hello
[20:06] <JMichaelX> sarnold: i upgraded from 14.04 to 16.04 from command line, using do-release-upgrade, and have since done multiple apt upgrades and apt dist-upgrades.
[20:06] <JMichaelX> however, it is still using 3.13.0-110-generic
[20:06] <teward> JMichaelX: is this a VPS?
[20:06] <teward> oh wait home server nevermind
[20:06] <genii> Maybe you have something pinned
[20:10] <JMichaelX> have not pinned anything
[20:10] <genii> It could also be that you have a package installed with specific kernel name, instead of just linux-image-generic
[20:10] <JMichaelX> i can just try to install the most recent kernel, but just found it odd that the kernel did not upgrade
[20:11] <JMichaelX> yes, possible. will check that
[20:14] <genii> !info linux-image-3.13.0-110-generic
[20:14] <genii> !info linux-image-3.13.0-110-generic trusty
[20:14] <genii> !info linux-image-3.13.0-110-generic xenial
[20:15] <genii> Hm
[20:15] <OerHeks> is this vagrant?
[20:17] <JMichaelX> ok, it does appear that linux-image-generic was not installed. i seriously doubt i ever removed it, however
[20:17] <JMichaelX> after installing linux-image-generic, i did get errors like: initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
[20:25] <JMichaelX> are these types of errors something a person should not be seeing in 16.04?
[20:28] <genii> Are these messages persisting after a boot into the newer kernel?
[20:29] <JMichaelX> am preparing to check that. will brb
[20:35] <JMichaelX> so far so good. 4.4.0-66-generic now in use, and i'm seeing no errors. many thanks for the help
[20:35] <genii> Excellent.
[20:37] <genii> JMichaelX: The upstart error can also happen when there are old startup scripts in /etc/init/ ( upstarts scripts) but also startup script in /etc/init.d/ ( systemd)
[20:37] <genii> ( for the same service)