samba - Sep 2016 - turned on log level = 10 . . . no logs

I have created a second DC and joined it to my first DC. Seemed to go
well, then not. Now experiencing dns issues. My syslog on first DC shows
"Failed to connect host 192.168.xx.49 (22******c8._msdcs.dtshrm.dt) on
port 135 - NT_STATUS_CONNECTION_REFUSED." (Which is referencing the
second DC connection failed.) 

Now, _please set the dns issue aside for the moment_ as I went to my
second DC and set log level to "10" to see what is going on and the
second DC is not generating log files. It did not create
/var/log/samba/* anything. This after a couple of restarts. I checked
the "smbd -b" output of DC2 and Samba is set to "LOGFILEBASE:
/var/log/samba." 

The second DC is a Ubuntu 16.04.1LTS running Samba 4.3.9 (from repo) and
bind9.10.3-P4-Ubuntu. 

Does anyone know how can I get the logs to generate? Is there something
else I "need to turn on"?

-- 
_______________________________

Bob Wooden of Donelson Trophy

615.885.2846
www.donelsontrophy.com [1]

"Everyone deserves an award!!"
 

Links:
------
[1] http://www.donelsontrophy.com

On Fri, 30 Sep 2016 07:01:05 -0500
Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote:
> I have created a second DC and joined it to my first DC. Seemed to go
> well, then not. Now experiencing dns issues. My syslog on first DC
> shows "Failed to connect host 192.168.xx.49
> (22******c8._msdcs.dtshrm.dt) on port 135 -
> NT_STATUS_CONNECTION_REFUSED." (Which is referencing the second DC
> connection failed.) 
> 
> Now, _please set the dns issue aside for the moment_ as I went to my
> second DC and set log level to "10" to see what is going on and
the
> second DC is not generating log files. It did not create
> /var/log/samba/* anything. This after a couple of restarts. I checked
> the "smbd -b" output of DC2 and Samba is set to
"LOGFILEBASE:
> /var/log/samba." 
> 
> The second DC is a Ubuntu 16.04.1LTS running Samba 4.3.9 (from repo)
> and bind9.10.3-P4-Ubuntu. 
> 
> Does anyone know how can I get the logs to generate? Is there
> something else I "need to turn on"?
> 
Lets start with the dns entries, go and read this:

https://wiki.samba.org/index.php/Verifying_and_Creating_a_DC_DNS_Record

Rowland

On 2016-09-30 07:27, Rowland Penny via samba wrote:
> On Fri, 30 Sep 2016 07:01:05 -0500
> Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote:
> 
>> I have created a second DC and joined it to my first DC. Seemed to go
>> well, then not. Now experiencing dns issues. My syslog on first DC
>> shows "Failed to connect host 192.168.xx.49
>> (22******c8._msdcs.dtshrm.dt) on port 135 -
>> NT_STATUS_CONNECTION_REFUSED." (Which is referencing the second DC
>> connection failed.) 
>> 
>> Now, _please set the dns issue aside for the moment_ as I went to my
>> second DC and set log level to "10" to see what is going on
and the
>> second DC is not generating log files. It did not create
>> /var/log/samba/* anything. This after a couple of restarts. I checked
>> the "smbd -b" output of DC2 and Samba is set to
"LOGFILEBASE:
>> /var/log/samba." 
>> 
>> The second DC is a Ubuntu 16.04.1LTS running Samba 4.3.9 (from repo)
>> and bind9.10.3-P4-Ubuntu. 
>> 
>> Does anyone know how can I get the logs to generate? Is there
>> something else I "need to turn on"?
> 
> Lets start with the dns entries, go and read this:
> 
> https://wiki.samba.org/index.php/Verifying_and_Creating_a_DC_DNS_Record
> 
> Rowland
I had been through that but something changed. 

When I get to  "ldbsearch-H /var/lib/samba/private/sam.ldb
'(invcationId=*)' --cross-ncs objectguid" now returns "Search
failed -
Unsupported critical extension 1.2.840.113226.1.4.1340" 

So . . . thoughts?

-- 
_______________________________

Bob Wooden of Donelson Trophy