samba - Jul 2013 - Accessing sysvol results in fatal PANIC: internal error

Hello,

I am currently testing two Samba 4.0.6 AD DCs. I've noticed that permissions
in the sysvol directory do not seem to be consistent. Some GPs are owned by
root, while others are owned by DOMAIN\Domain Admins. Attempting to fix the
permissions with "samba-tool ntacl sysvolreset" while samba is running
results in a "PANIC: internal error". In fact, even trying to "ls
-l" the directories inside of the sysvol directory causes a PANIC. The
domain is then unusable until I restart samba. Here is a verbose log with
"log level = 3": http://pastebin.com/F1tSZVNf

What is the correct/safe way to fix permissions on the sysvol directory (and why
do they get changed like this) and what is a safe way to sync the sysvol
directory between DCs (rsync causes this same PANIC)?

Thanks,

Andrew Martin

----- Original Message -----
> From: "Andrew Martin" <amartin at xes-inc.com>
> To: samba at lists.samba.org
> Sent: Friday, July 12, 2013 9:48:41 PM
> Subject: [Samba] Accessing sysvol results in fatal PANIC: internal error
> 
> Hello,
> 
> I am currently testing two Samba 4.0.6 AD DCs. I've noticed that
> permissions in the sysvol directory do not seem to be consistent.
> Some GPs are owned by root, while others are owned by DOMAIN\Domain
> Admins. Attempting to fix the permissions with "samba-tool ntacl
> sysvolreset" while samba is running results in a "PANIC: internal
> error". In fact, even trying to "ls -l" the directories
inside of
> the sysvol directory causes a PANIC. The domain is then unusable
> until I restart samba. Here is a verbose log with "log level =
3":
> http://pastebin.com/F1tSZVNf
> 
> What is the correct/safe way to fix permissions on the sysvol
> directory (and why do they get changed like this) and what is a safe
> way to sync the sysvol directory between DCs (rsync causes this same
> PANIC)?
> 
> Thanks,
> 
> Andrew Martin
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
> 
It seems that this might be bug #9820:
https://bugzilla.samba.org/show_bug.cgi?id=9820
I haven't noticed it in winbind specifically, just in that samba
becomes unresponsive.

If so, the attached patch (#9043) is the current solution to this
problem? Can it be applied to 4.0.6?

Thanks,

Andrew