After a mail mentionning that i cannot run the sambaundoguidindex, here the
error i'm getting :
root at samba:~/samba-4.8.2/source4/scripting/bin# killall samba
root at samba:~/samba-4.8.2/source4/scripting/bin# ./sambaundoguididx
Traceback (most recent call last):
File "./sambaundoguididx", line 54, in <module>
samdb.modify(modmsg)
_ldb.LdbError: (32, 'ldb_wait from (null) with LDB_WAIT_ALL: No such object
(32)')
A transaction is still active in ldb context [0x581b2778] on
tdb:///var/lib/samba/private/sam.ldb
Don't really know how to deal with this and google leave me with no clue.
Renaud
On 6/7/2018 11:33 AM, Renaud via samba wrote:> After a mail mentionning that i cannot run the sambaundoguidindex, here the > error i'm getting : > > root at samba:~/samba-4.8.2/source4/scripting/bin# killall samba > root at samba:~/samba-4.8.2/source4/scripting/bin# ./sambaundoguididx > Traceback (most recent call last): > File "./sambaundoguididx", line 54, in <module> > samdb.modify(modmsg) > _ldb.LdbError: (32, 'ldb_wait from (null) with LDB_WAIT_ALL: No such object > (32)') > A transaction is still active in ldb context [0x581b2778] on > tdb:///var/lib/samba/private/sam.ldb > > Don't really know how to deal with this and google leave me with no clue. > > Renaud > > >Renaud, You should only need to run this script if doing a in place upgrade from 4.7.x to 4.8.0 or 4.8.1 fails. I see you are using 4.8.2. This should have been fixed. Did you upgrade from 4.7.x to 4.8.2 and have issues? Most likely you will need to restore from backup or create a new DC if you can't run the script. -- -JAMES
On Fri, 2018-06-08 at 12:14 -0400, lingpanda101 via samba wrote:> On 6/7/2018 11:33 AM, Renaud via samba wrote: > > After a mail mentionning that i cannot run the sambaundoguidindex, here the > > error i'm getting : > > > > root at samba:~/samba-4.8.2/source4/scripting/bin# killall samba > > root at samba:~/samba-4.8.2/source4/scripting/bin# ./sambaundoguididx > > Traceback (most recent call last): > > File "./sambaundoguididx", line 54, in <module> > > samdb.modify(modmsg) > > _ldb.LdbError: (32, 'ldb_wait from (null) with LDB_WAIT_ALL: No such object > > (32)') > > A transaction is still active in ldb context [0x581b2778] on > > tdb:///var/lib/samba/private/sam.ldb > > > > Don't really know how to deal with this and google leave me with no clue. > > > > Renaud > > > > > > > > Renaud, > > You should only need to run this script if doing a in place upgrade > from 4.7.x to 4.8.0 or 4.8.1 fails. I see you are using 4.8.2. This > should have been fixed. Did you upgrade from 4.7.x to 4.8.2 and have issues? > > Most likely you will need to restore from backup or create a new DC if > you can't run the script.If that isn't an option for some reason, then a dump of the database backend files using ldbdump, and then a re-create of the files with ldbadd might be possible, but I haven't got an automated script for that yet (probably something we will need to do in aid of the LMDB port however). You would still need to do the other steps that script does, and then finish with a samba-tool dbcheck --reindex In short, hopefully a backup was made. Sorry, Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Catalyst IT http://catalyst.net.nz/services/samba
On Mon, 2018-06-11 at 09:34 +0200, renaud.rolles at giraudbtp.com wrote:> > > You should only need to run this script if doing a in place > > > upgrade from 4.7.x to 4.8.0 or 4.8.1 fails. I see you are using 4.8.2. > > > This should have been fixed. Did you upgrade from 4.7.x to 4.8.2 and have > > > > issues? > > > > > > Most likely you will need to restore from backup or create a new DC if > > > you can't run the script. > > > > If that isn't an option for some reason, then a dump of the database backend > > files using ldbdump, and then a re-create of the files with ldbadd might be > > possible, but I haven't got an automated script for that yet (probably > > something we will need to do in aid of the LMDB port however). > > > > You would still need to do the other steps that script does, and then finish > > with a samba-tool dbcheck --reindex > > > > In short, hopefully a backup was made. > > I did an upgrade from 4.7.6 to 4.8.0, I't broke perms, didn't notice it right away, just some app wouldn't start due to perm issue. > I allready tried the undoguidindex with no luck so I waited until 4.8.2 and trie dit instead (didn't worked) > > As backup stands, there was a lack of config of my part..... > Is the following step the good way to try to restore ? > > Stop samba 4.8.2 > LDBDump database into a file > Drop the old database file > LDBadd file into a new database. > Run sambaundoguidindex > Start samba 4.8.2 > Run samba-tool dbcheck --reindexThat might work. I've not tried it myself and I would have to suggest getting professional help, but it seems OK.> > Sorry, > > Don't be, thank you for develloping this tool.Thanks, Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Catalyst IT http://catalyst.net.nz/services/samba
> > > > Stop samba 4.8.2 > > LDBDump database into a file > > Drop the old database file > > LDBadd file into a new database. > > Run sambaundoguidindex > > Start samba 4.8.2 > > Run samba-tool dbcheck --reindex > > That might work. I've not tried it myself and I would have to suggest getting > professional help, but it seems OK. >To be sure, databases files are : sam.ldb privilege.ldb secrets.ldb share.ldb sam.ldb.d/*.ldb ? You metion professional help, you mean this : https://www.sernet.de/en/services/support/ ? (this is the closest one) Thank.