Quote:
|
Originally Posted by madeinoz
I had a number of short powerfailures today after power being off most of the night after my UPS depleted, so my 4500 snap got to cycle a couple of times before batteries got to recharge  Snap rebooted no problems.
However now I have an issue where Active directory users/ groups are not being propagated to the snap server, i.e. I add a new user on active directory and it the user does not does not show up in the snapserver. I have removed the snap from the active directory and re-added still no go.
All my users except one can access the snapserver as per normal, thats fine for the time being (except for that one user hehe), however it will become an issue if I need to change groups add/remove users etc.
I'm running 4500 1TB OS 4.2.054 |
Ok seem to have found the problem.
for anyone else that has the problem.
I initiall tried recovering via the DRImage, but this kept on failing, So I started poking around in the logfiles via the shell.
In the /var/log/samba/log.winbindd I was getting alot of "tdb(/var/lock/samba/winbindd_idmap.tdb): rec_read bad magic 0x42424242 at offset=32280" errors.
So looks like the winbind database got corrupt! I ended up deleting all the files under /var/lock/samba and restarted samba on the snapserver, this re-creates all those files. Snapserver is now talking to the Active directory again
WARNING doing this stuffs up all userID mappings on the AD on the snapserver, so I went back to factory default ACLs on volume and then had to reset all directory user permisisions for all relevenant Active directory groups/ users etc..
All is working now
