similar to: Internal Error Signal 11 (Samba 3.2.3)

Dear samba list, For some time we've had servers connecting to a w2k3 r2 server via ADS setup. Wins was working fine and users were able to authenticate. Recently we've added a GFS like system. This required getting the UID/GID's unified. Suggestions were made on the samba IRC channel to install SFU on the PDC. I'm receiving some very strange output. Usernames/pwd have

Hello list users, I have been struggling with this combination in the subject field couple of days now, so I decided to ask for some advice here. Hopefully someone can point me to a right direction. The ultimate goal for me is to authenticate users using AD, so that the UID/GID values configured for users with SFU would also be in use in all our Linux machines. My understanding is that using

Quoting Adam Tauno Williams <awilliam at whitemice.org>: >>>> It should work, it sounds like a mis-configuration somewhere, can you >>>> post the smb.conf, /etc/nsswitch.conf, /etc/resolv.conf and >>>> /etc/krb5.conf from the member server. >>> "wbinfo -u" lists 415 lines >>> "getent passwd" returns 93 lines

I'm trying to load the apple attributes and classes to samba4 using ldbmodify. I can get it to load, sort of. I keep getting errors and having to modify the file. Command I'm using: sudo ldbmodify -v -H ldap://lda.server.local -UAdministrator /home/user/apple-mcx.ldif here is the ldif that I'm loading

On 03/07/2019 15:50, Sven Schwedas via samba wrote: > It's amazing how long Samba just keeps running even when apparently > everything's broken. > > In preparation of finally upgrading our DCs to 41.0, I ran dbcheck on > all of them, resulting in: > > graz-dc-sem: >> Checking 3861 objects >> Error: governsID

Well, colleagues, I'm stuck a bit. I tried many different ways to setup system with vinum root (the only reference I found yet besides old "bootstrapping vinum" article is Joerg's commit message: http://freebsd.rambler.ru/bsdmail/cvs-all_2003/msg01225.html I failed. I have 4-stable system set up at ad0, and tried to set up pair of drives for new system at ad2 and ad3 (actually,

It's amazing how long Samba just keeps running even when apparently everything's broken. In preparation of finally upgrading our DCs to 41.0, I ran dbcheck on all of them, resulting in: graz-dc-sem: > Checking 3861 objects > Error: governsID CN=ucsUser,CN=Schema,CN=Configuration,DC=ad,DC=tao,DC=at on 1.3.6.1.4.1.19414.3.2.2 already exists as an attributeId or governsId > Error:

I expected that someone had the same problem before. DBchecker module does not provide fix for this. The implication is that the main Samba DC is working fine but does not allow replication with other DCs. They report WERR_DS_DRA_INTERNAL_ERROR in samba-tool dsr showrepl for two two sections: Configuration and the main one that contains the users. Other sections replicate fine. Promoting new DC

On 04/07/2019 14:45, Sven Schwedas via samba wrote: > On 03.07.19 18:04, Rowland penny via samba wrote: >>>>> How do I get rid of these bogus Schema entries, and how do I fix the >>>>> user account? >>>> I do not think you can remove anything from the schema, but I believe >>>> you can deactivate schema objects, try reading this:

On 04.07.19 15:54, Rowland penny via samba wrote:>> Still left are the three governsId collisions, which are now identical >> across all DCs: >> >>> Checking 3861 objects >>> Error: governsID >>> CN=ucsUser,CN=Schema,CN=Configuration,DC=ad,DC=tao,DC=at on >>> 1.3.6.1.4.1.19414.3.2.2 already exists as an attributeId or governsId >>>

On 03.07.19 18:04, Rowland penny via samba wrote: >>>> How do I get rid of these bogus Schema entries, and how do I fix the >>>> user account? >>> I do not think you can remove anything from the schema, but I believe >>> you can deactivate schema objects, try reading this: >>> >>>

Is this a problem? Does this mean no replication links exist? michael at sles-bree:~> samba-tool drs showrepl -k yes Bree\SLES-BREE DSA Options: 0x00000025 DSA object GUID: 7ea641b0-d418-4c74-a4fa-c15b852467b8 DSA invocationId: 1017ff29-756c-4777-b395-b481f4b5387c ==== INBOUND NEIGHBORS ==== ==== OUTBOUND NEIGHBORS ==== ==== KCC CONNECTION OBJECTS ==== Connection -- Connection name:

> > We found that replPropertyMetaData is uniquie for each user, setting > > it empty "fix the error' but breaks the user object. > > Correct, if you delete replPropertyMetaData in any way, you totally > break replication. > dbcheck should wipe that part of replPropertyMetaData with --fix but it is not implemented. If that attribute does non replicate, there

Using ldap as my sam backend and Samba 3.0.0-2, I'm showing that samba stops parsing a RID when it encounters a letter. For example, I have an accounting group with gid 2771 and therefore rid ad3. When I list the groups in the samba domain, however, I get this listing: Domain Admins (DOMAINSID-512) -> Domain Admins Domain Users (DOMAINSID-513) -> Domain Users Domain Guests

On Sat, 2017-05-27 at 03:16 +0200, Karan Blas via samba wrote: > > > We found that replPropertyMetaData is uniquie for each user, setting > > > it empty "fix the error' but breaks the user object. > > > > Correct, if you delete replPropertyMetaData in any way, you totally > > break replication. > > > > dbcheck should wipe that part of

Dear colleagues, experimenting with vinum stripes and mirrors, I'd stuck myself with the following: panic: throw_rude_remark: called without config lock (from vinumconfig.c:throw_rude_remark:103) The system before this panic has two 160G drives with two vinum partitions on each (one for mirrored root and one for the rest with swap between); these were ad0 and ad2. For the experiments,

hi bringing this thread back to life i waited to ugprade to 4.5.0 and after installing it i get a lot the same errors for users and computers objects when runnung samba-tool dbcheck --cross-ncs Checked 4744 objects (4909 errors) ERROR: unsorted attributeID values in replPropertyMetaData on CN=50LPT01,OU=Computers,OU=50,OU=MAINOU,DC=DOMAIN,DC=MY Not fixing replPropertyMetaData on

Thank you Andrew, really appreciated. I have now run 'samba-tool dbcheck --cross-ncs --fix' and it has successfully fixed some errors; there were 110 previously, however there are still 69 remaining after a second pass of dbcheck --fix. The remaining errors seem to be mainly of this form: ERROR: duplicate attributeID values for myattrib in replPropertyMetaData on

Hi ..., I am trying to upgrade from Samba 4.4.4 to Samba 4.7.7 and I am facing an error similar to the one mentioned here - https://bugzilla.samba.org/show_bug.cgi?id=12297 https://bugzilla.samba.org/show_bug.cgi?id=12385 I get the following error message *every time* I run - samba-tool dbcheck --cross-ncs --fix --yes

Hi, I just did this a view days agon. These where the ldifs I used. laps_1.ldif dn: CN=ms-MCS-AdmPwd,CN=Schema,cn=configuration,DC=X changetype: add objectClass: attributeSchema ldapDisplayName: ms-MCS-AdmPwd adminDisplayName: ms-MCS-AdmPwd adminDescription: Stores password of local Administrator account on workstation attributeId: