[02:01] <volkswagner> gretings
[02:02] <volkswagner> I upgraded 16.04 running Samba4 AD DC to 18.04 but samba internal DNS is not working
[02:02] <volkswagner> I saw info "unmask samba-ad-dc" but that didn't help
[02:03] <sarnold> check the logs / journal, maybe there's something in there?
[02:04] <volkswagner> Here's some info from log and samba config (I'm running Samba Version 4.7.6-Ubuntu) https://pastebin.ubuntu.com/p/Q4dcdqt5dG/
[02:05] <volkswagner> also from nmbd.log server role = 'active directory domain controller' not compatible with running nmbd standalone. You should start 'samba' instead, and it will control starting the internal nbt server
[02:06] <volkswagner> is samba service replaced by samba-ad-dc in /etc/init.d?
[02:06] <sarnold> volkswagner: those logs are from four years ago, do you have newer? :)
[02:06] <sarnold> they might be logged to the journal, I'm not sure
[02:07] <volkswagner> that's weird
[02:07] <sarnold> volkswagner: it looks like there's a systemd service file for it /lib/systemd/system/samba-ad-dc.service
[02:08] <volkswagner> this is from log.samba  Failed to listen on 0.0.0.0:53 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED
[02:09] <volkswagner> when running ps -aux what should samba internal look like? I have output in pastebin from today :)
[02:11] <volkswagner> do I need to remove/uninstall systemd-relsove?
[02:11] <sarnold> I'm not sure there, I've not run samba myself in ~20 years
[02:12] <sarnold> don't touch systemd-resolved, I think that'd lead to pain
[02:12] <sarnold> hmm
[02:12] <sarnold> how *are* you supposed to get this thing to work though.. maybe you can get samba to bind to specific interfaces?
[02:16] <volkswagner> If I stop systemd-resolve then restart samba my dns works
[02:17] <volkswagner> I found a thread that adds a line to /etc/systemd/resolved.conf with "DNSStubListener=no"
[02:17] <sarnold> woot
[02:17] <sarnold> that sounds reasonable
[02:20] <volkswagner> @sarnold thanks for pointing out my ancient log entries. I need to slow down!
[02:21] <sarnold> hehe :)
[02:21] <sarnold> I didn't spot them right away..
[02:23] <volkswagner> I think that worked a treat
[02:23] <volkswagner> doing more testing now
[02:23] <sarnold> sweet sweet :)
=== Roy_Mustang is now known as A_D
[06:24] <lordievader> Good morning
=== m1dnight_ is now known as ssdflkjshflkjhsf
=== ssdflkjshflkjhsf is now known as m1dnight_
=== m1dnight_ is now known as ssdflkjshflkjhsf
=== ssdflkjshflkjhsf is now known as m1dnight_
=== m1dnight_ is now known as m1dnight__
=== m1dnight__ is now known as m1dnight_
=== m1dnight_ is now known as m1dnight__
[17:08] <arooni> so upgrading an ancient 16.04 server to 18.04; saw that these aren't supported; https://gist.github.com/arooni/ab974fa96c481541964072d6a3a5c42f ;; what do you suggest i do once the upgrade is complete
[17:12] <teward> arooni: to start with a lot of those go and get replaced by other libraries.  If you *absolutely require* Python 3.4 then you're probably going to need to compile and install it yourself as a separate Python instance on system.  `libssl` gets upgraded to `libssl 1.1.0` and such.  Most of these are just tied to obsolete versions that get upgraded anyways to *newer* software dependency versions from what I can tell
[17:13] <teward> libssl, libvpx, etc. unless they are removed would just get replaced with the versions that *are* in the system
[17:13] <teward> (and mysql-server 5.5 isn't what's shipped anymore anyways)
[17:27] <leftyfb> arooni: simplified, do you require libssl or do you require libssl1.0.2? Will libssl1.1 work?
[17:32] <arooni> i believe the libssl is really just needed for nginx's web server
[17:32] <arooni> or perhaps some part of the ruby app i'm running
[17:32] <arooni> thanks for the quick and useful feedback everyone
[17:33] <arooni> would you folks recommend while i'm doing this to jump to 20.04 ?
[17:33] <arooni> also i happen to be running 20.04 on my dev laptop so that would be convenient
[17:34] <Ussat> I would not reccomend a upgrade like that at all, build new in parallel andmigrate
[17:35] <Ussat> Thats what I generally do anyway
[17:35] <TJ-> I've adopted a process for that of creating the new release in a container, duplicating everything from the host, then switching the root file-systems over
[17:35] <arooni> its because there are too many things that go wrong with the upgrade process?
[17:36] <Ussat> I just use ansible
[17:36] <Ussat> arooni, its because you are going from 16
[17:36] <Ussat> Just my opinion
[17:36] <Ussat> 'I also do this with ALL ypgrades
[17:36] <Ussat> again, just my process what I do
[17:37] <Ussat> I also use ansible which makes this process almost automated
[17:42] <leftyfb> also my opinion.... though they left so it doesn't matter :/
[17:43] <leftyfb> Ussat: what do you do about upgrading the host OS? My goal is to have 2x servers and move containers between them during the upgrade of the host OS
[18:05] <Ussat> leftyfb, I build new in parallel then migrate apps/data
[18:05] <Ussat> I have a lot of this automated w/ansible
[18:06] <leftyfb> Ussat: you rebuild every container onto a new host?
[18:06] <Ussat> I dont use containers
[18:06] <Ussat> well, thats not totally true, I have a couple.......maby, 4 or 5 ?
[18:07] <Ussat> but almost everything I have is a VM also
=== JanC is now known as Guest66672
=== JanC_ is now known as JanC