Stuck on Synchronizing user settings
-
I upgraded to the 28th snapshot and it still does this. If you would like I can pm you my cell # and I can provide you with IP kvm access to the box so you can check it out. Of course it would have to be any time after 7 pm est as this is a production box.
-
We shouldn't need direct access. If it still happens on a current (September) snapshot, get the users and groups from your config, blank out the passwords, and post that portion of the config here or PM it.
-
I'll update it tonight and try a few reboots. I do know I disabled the admin login and created my own login name
-
jimp, I have sent you a pm. Updated to Sept 03 and still having the same issue.
-
The part in the PM was what I was after. Though I can't seem to reproduce the hang with your settings, I did notice one odd part. You have a <group>tag with some members defined but no name or other info.
If you edit that out of the config does it still hang for you?
<group><member>2000</member> <member>2001</member> <member>2003</member></group> ```</group> -
The part in the PM was what I was after. Though I can't seem to reproduce the hang with your settings, I did notice one odd part. You have a <group>tag with some members defined but no name or other info.
If you edit that out of the config does it still hang for you?
<group><member>2000</member> <member>2001</member> <member>2003</member></group> ```</group>No clue how that got there. I never mess with groups. However how do I edit that out?
-
The simplest way would be to download a fresh config backup, find that block, edit it out, save the file, then restore it.
-
Can you still reproduce this on current snapshots? I still can't replicate it here. One of my VMs used to do this every other reboot if not a few in a row but on recent snapshots it has been fine.
-
as of 10/09 and possibly as early as 10/07 I can no longer replicate this on my two 2.2 boxes.
One is a nano 4g install and the other is a hard drive.
They come up fine every time now.
-
as of 10/09 and possibly as early as 10/07 I can no longer replicate this on my two 2.2 boxes.
One is a nano 4g install and the other is a hard drive.
They come up fine every time now.
I will try an update tonight and give it a try.
-
Seems to be fixed :)
-
-
How did you resolve this? i have the same issue :-\
It was fixed fixed in newer 2.2 snapshots than the time when this thread started, just upgrading to the latest snapshot fixed it for everyone here.
If you're still seeing this, it's probably a problem with your configuration (though those seemed to be ignored when I last tested that circumstance). Open your config backup in a text editor (other than Windows Notepad) and look for a stray <group>or <user>tag. The <group>tag seemed to be at the time the issue, if you have a line in your config that only shows <group>, delete that line.</group></group></user></group>
