[Samba] Upgrading from Samba 4.0.1 to 4.1.6

[Jason Waters]

I added a realms section to my krb5.conf file and now I can at least run
the kinit command.  But the samba-tool dns query fspa tte.local @ ALL
command returns a bunch of entries now.  But takes forever.  Something is
up with the DNS being very very slow.  Any thoughts of where to look?




On Mon, Mar 17, 2014 at 8:35 AM, Jason Waters <jwaters at h2os.com> wrote:

> When I put the right information, this is the error I get
>
> ERROR(runtime): uncaught exception - (-1073741643, 'NT_STATUS_IO_TIMEOUT')
>   File
> "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/__init__.py",
> line 175, in _run
>     return self.run(*args, **kwargs)
>   File "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/dns.py",
> line 984, in run
>     dns_conn = dns_connect(server, self.lp, self.creds)
>   File "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/dns.py",
> line 37, in dns_connect
>     dns_conn = dnsserver.dnsserver(binding_str, lp, creds)
>
>
>
> On Mon, Mar 17, 2014 at 8:25 AM, Jason Waters <jwaters at h2os.com> wrote:
>
>> I see why I got that error.  I needed to put the server and the domain.
>>  my bad!  Still acting slow though.
>>
>>
>> On Mon, Mar 17, 2014 at 8:14 AM, Jason Waters <jwaters at h2os.com> wrote:
>>
>>> root at fspa:~# kinit administrator
>>> kinit: Cannot contact any KDC for realm 'ABC.LOCAL' while getting
>>> initial credentials
>>> root at fspa:~# samba-tool dns query SERVER DOMAIN @ ALL
>>> ERROR(runtime): uncaught exception - (-1073741772,
>>> 'NT_STATUS_OBJECT_NAME_NOT_FOUND')
>>>   File
>>> "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/__init__.py",
>>> line 175, in _run
>>>     return self.run(*args, **kwargs)
>>>   File
>>> "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/dns.py", line
>>> 984, in run
>>>     dns_conn = dns_connect(server, self.lp, self.creds)
>>>   File
>>> "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/dns.py", line
>>> 37, in dns_connect
>>>     dns_conn = dnsserver.dnsserver(binding_str, lp, creds)
>>>
>>>
>>>
>>> On Mon, Mar 17, 2014 at 8:12 AM, Jason Waters <jwaters at h2os.com> wrote:
>>>
>>>> I seem to be having a DNS issue.  The DNS server is really really slow
>>>> when I use samba.  Any ideas?
>>>>
>>>> Jason
>>>>
>>>> root at fspa:~# ping google.com
>>>> PING google.com (204.186.215.54) 56(84) bytes of data.
>>>> 64 bytes from 204.186.215.54: icmp_req=1 ttl=61 time=13.7 ms
>>>> 64 bytes from 204.186.215.54: icmp_req=2 ttl=61 time=11.1 ms
>>>> 64 bytes from 204.186.215.54: icmp_req=3 ttl=61 time=10.9 ms
>>>> 64 bytes from 204.186.215.54: icmp_req=4 ttl=61 time=13.8 ms
>>>> ^C64 bytes from 204.186.215.54: icmp_req=5 ttl=61 time=13.1 ms
>>>>
>>>> --- google.com ping statistics ---
>>>> 5 packets transmitted, 5 received, 0% packet loss, time 20179ms
>>>> rtt min/avg/max/mdev = 10.907/12.562/13.896/1.284 ms
>>>>
>>>>
>>>> See the 20179ms???
>>>>
>>>>
>>>> On Sun, Mar 16, 2014 at 11:30 AM, Jason Waters <jwaters at h2os.com>wrote:
>>>>
>>>>> Marc,
>>>>>   Sorry about just grepping the error.  Didn't know if that would flag
>>>>> anything that you "knew" already.  Like the .pem issue before.  I figured
>>>>> out the problem.  In smb.conf I had [print$] defined with a directory that
>>>>> didn't exist.  As soon as I created it samba would start and stay running!
>>>>>  Thank you for the help.  Also sorry about my calling it PDC/BDC.  I will
>>>>> refer to them as domain controllers from now on! :)
>>>>>
>>>>> Jason
>>>>>
>>>>>
>>>>> On Sat, Mar 15, 2014 at 9:44 PM, Marc Muehlfeld <
>>>>> samba at marc-muehlfeld.de> wrote:
>>>>>
>>>>>> Am 16.03.2014 02:32, schrieb Jason Waters:
>>>>>>
>>>>>>  Got a little further.  I removed the pem files and then the one(PDC)
>>>>>>> started and stayed working.  The BDC did not.  I got this when I
>>>>>>> grep the
>>>>>>> log file.
>>>>>>>
>>>>>>> root at fsZZ:/usr/local/samba-4.1.6/var# grep error log.samba
>>>>>>>
>>>>>>
>>>>>> Please empty your logs, start samba and then have a look at _all_ the
>>>>>> messages are shown. Only with the lines containing the word "error" in
>>>>>> lower cases it would be very hard to help.
>>>>>>
>>>>>>
>>>>>> What do you mean with "one(PDC) started and stayed working. The BDC
>>>>>> did not." What is not working? Are all processes running? If not, which is
>>>>>> missing? It Samba listening on all ports it should? If not, which ports are
>>>>>> not listening? ....
>>>>>>
>>>>>>
>>>>>> Btw: You said you have a Samba AD, then you don't have PDC/BDCs. You
>>>>>> have Domain Controllers. Please use this term, as PDC/BDC indicate that
>>>>>> you're running a NT4-style domain. This confuses, as for a Samba4 NT4-style
>>>>>> domain you have to do different steps than for an AD DC.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Regards,
>>>>>> Marc
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>