s3 to join s4

[Collen]

Hi, after some investigation i came to the following.

i can join the s4 domain, but dns is not registered/updated
but manual adding the domain name to zone file fix the problem.

but i get a panic action if i do the following:

after starting winbind (s3) i do getent group
and the backtrace occur,

if i first do getent passwd, and then getent group
no problems occur.

after the first succes, no problem will occur anny more
until the winbind cache time expires (300) or winbind is restarted

after that the story starts from scratch again (first getent group fails)

also the domain users group seems to be empty with getent group
but users are assigned to it. i can see it in ad usernmanager


------------------
[2011/12/16 09:55:18.517414,  5] 
rpc_client/cli_pipe.c:738(rpc_api_pipe_send)
   rpc_api_pipe: host green.jordanet.hermanjordan.nl
[2011/12/16 09:55:18.517452,  5] rpc_client/cli_pipe.c:177(rpc_write_send)
   rpc_write_send: data_to_write: 1472
[2011/12/16 09:55:18.549282,  5] rpc_client/cli_pipe.c:97(rpc_read_send)
   rpc_read_send: data_to_read: 2112
[2011/12/16 09:55:18.549540,  0] ../lib/util/debug.c:413(talloc_log_fn)
   Bad talloc magic value - unknown value
[2011/12/16 09:55:18.549596,  0] lib/util.c:1117(smb_panic)
   PANIC (pid 11563): Bad talloc magic value - unknown value
[2011/12/16 09:55:18.551954,  0] lib/util.c:1221(log_stack_trace)
   BACKTRACE: 22 stack frames:
    #0 winbindd(log_stack_trace+0x29) [0x752c52]
    #1 winbindd(smb_panic+0x76) [0x752d78]
    #2 /usr/lib/libtalloc.so.2(-0xbd468687) [0x372979]
    #3 /usr/lib/libtalloc.so.2(talloc_strdup+0x27a) [0x37650a]
    #4 winbindd(+0x539d72) [0xb1ad72]
    #5 winbindd(dcerpc_lsa_lookup_sids3+0x5a) [0xb1b486]
    #6 winbindd(winbindd_lookup_sids+0x13c) [0x68a89b]
    #7 winbindd(+0xae4e4) [0x68f4e4]
    #8 winbindd(+0x96752) [0x677752]
    #9 winbindd(_wbint_LookupGroupMembers+0x7f) [0x699916]
    #10 winbindd(+0xc42f8) [0x6a52f8]
    #11 winbindd(winbindd_dual_ndrcmd+0x145) [0x698c69]
    #12 winbindd(+0xb6fe7) [0x697fe7]
    #13 winbindd(+0xb7273) [0x698273]
    #14 winbindd(+0x185921) [0x766921]
    #15 winbindd(tevent_common_loop_immediate+0x11c) [0x765643]
    #16 winbindd(run_events_poll+0x3f) [0x763602]
    #17 winbindd(+0x182a70) [0x763a70]
    #18 winbindd(_tevent_loop_once+0x9e) [0x764710]
    #19 winbindd(main+0xcee) [0x66d884]
    #20 /lib/libc.so.6(__libc_start_main+0xf3) [0xff16b3]
    #21 winbindd(+0x89741) [0x66a741]
[2011/12/16 09:55:18.552154,  0] lib/fault.c:372(dump_core)
   dumping core in /usr/local/samba/var/cores/winbindd
-------------------------

On 8-12-2011 12:41, Collen wrote:
> Ok, no sorry.
>
> I've tested it today and still have the problems..
>
> i can join the s4 domain, but still get the dns invalid error
> the s3 shows up in the computer list on the AD, but not in the DNS
>
> i can browse to S3 with windows, resolving usernames and group names fails.
>
> on the S3 net ads group/user/info all works nice (i can see the users
> and groups)
>
> wbinfo fails in allways
>
> getent makes the winbind coredump ?! (on s3)
> something with talloc magic value unkown.
>
> s3 version 3.6.1 - s4 git pull from yesterday
>
> so it's not really working for me.
>
> greetz, Collen
>
> On 5-12-2011 17:38, Matthieu Patou wrote:
>> On 05/12/2011 16:40, Collen wrote:
>>> Hi, just a quick question,
>>>
>>> what s3 version is better to use to join s4 ?
>>> 3.5 or 3.6 ? (both on different machines)
>>>
>> Both should work.
>>> i did try 3.6 but get a dns_update error after the net ads join.
>>> (dns_invallid_message)
>> That's a long lasting bug, it should have been fixed lately and should
>> be in the 4.0 (or 3.7 depending on which came first).
>>>
>>> the join was successful, but is not working (?)
>>>
>> What make you think so ?
>>
>> Matthieu.
>>
>>
>

-- 
---
Collen Blijenberg - systeem/netwerk beheerder