AD users not being updated on snap

[blue68f100]

Actually he has 8 fingers and 2 thumbs.

[Hallis]

Originally Posted by blue68f100

Actually he has 8 fingers and 2 thumbs.

That we know of.

[madeinoz]

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

[Phoenix32]

Glad you found it, and thank you for providing info for future use...

[CuznMark]

Ok I hate to beat a dead horse. I am in a bind and this looks like the place to help me.. I am havign the same problem with teh AD users not showing up.. I have a Snap 2000. I am trying to find an answer to fix it. but I am not having any luck. snapos 4.0.860.

thanx for any help.. I did find something with the debug commands. It showed me that the large domain list was disabled.. I dunno how to enable it. there is no help command for it.

Mark

[blue68f100]

If you are on OS 4.0.860 it's can be found under Network Settings -> Microsoft, just change over to Domain then advanced options. That's all I know.

[CuznMark]

that was all set.. well I finally figured it out.. Our DC was corrupt and they have been working on it.. Hopefully it will be working in the morning

thanx again.
mark

[pulsarxss]

Originally Posted by madeinoz

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

How can I access /var/lock/samba/ directory on a SnapServer 520 with GuardianOS 4.4.049sp3?

Thankx,
Pulsar

[blue68f100]

You can use the debug page. You have to use full path cmd's since you can not migrate down to a directory. You may want to see and stop process before you start deleting things. cp works, just need to locate you directory and copy files to it, so you can look at them. Putty no long works as it did with older versions. You can no longer get admin rights, the reason you have to use the debug page.

ls /var/lock/samba/


the cd does not work

[pulsarxss]

Originally Posted by blue68f100

You can use the debug page. You have to use full path cmd's since you can not migrate down to a directory. You may want to see and stop process before you start deleting things. cp works, just need to locate you directory and copy files to it, so you can look at them. Putty no long works as it did with older versions. You can no longer get admin rights, the reason you have to use the debug page.

ls /var/lock/samba/


the cd does not work

Thank's blue68f100.

Access to this page is from ipaddress/config/debug (SnapOS) also for GuardianOS?

I'll give a try in next hour and I post results.

Hold on for a further help

TIA,
Pulsar

[pulsarxss]

According to blue68f100 I used debug page from:

http://<snap_name>/admin/debug.cgi

and then simply run this command

rm /var/lock/samba/winbindd_idmap.tdb

After this I restart the Snap and all went well!

Hope this help someone else.

Pulsar(xss)

[anklee]

I joined this forum to let you know that this post helped me resolve this issue after trying to correct this problem for 2 days. I had searched and tried so many suggestions that I was about to just give up. Finally I found your post. I have a newer OS so I had to go into debug using: http://<snap_name>/sadmin/debug.cgi. Thanks again so much.