Bug #3822
closed2.2 boot hangs at "Synchronizing user settings"
0%
Description
I mentioned this issue on IRC roughly 2 weeks ago and someone said it was a known issue being worked on (don't recall the exact details), but it's still happening as of the most recent 2.2 snapshot at the time of this writing. Didn't see a ticket, so opening this.
Under some, but not all circumstances on 2.2, the boot will hang forever at "Synchronizing user settings..."
also mentioned here:
https://forum.pfsense.org/index.php?topic=80247.0
I haven't been able to fully quantify the circumstances under which this happens. I do have a pretty basic config that'll replicate, I'll add that to the projects repo.
Updated by Chris Buechler about 10 years ago
config file is redmine-3822.xml under projects/ticket-configs/
Updated by Chris Buechler about 10 years ago
should be easy to replicate with that config file. Appears to happen at every boot. I end up having to ctrl-c out of the boot, manually add a default route (interfaces already configured but not routing at that point), SSH in and comment out local_sync_accounts in /etc/rc.bootup for it to boot.
Updated by Renato Botelho about 10 years ago
- Status changed from New to Rejected
I restored that config file twice in different snapshots, could not reproduce. It happened in the past when, due to a already fixed issue, config ended up with an empty entry (<user/> or <group/>) to hang at this exact point during boot, but it's not the case with this config file.
Updated by Jim Pingle about 10 years ago
- Status changed from Rejected to New
- Assignee changed from Chris Buechler to Jim Pingle
There is apparently still a problem here (See https://forum.pfsense.org/index.php?topic=80247.msg444042#msg444042 ), but it's not quite so easy to reproduce.
I have a config sample from a user that I'm trying to test with now to get some more info. Will update/reassign with the results.
Updated by Jim Pingle about 10 years ago
I still can't reproduce it here but in the config that user sent me, they do have an odd group tag.
<group> <member>2000</member> <member>2001</member> <member>2003</member> </group>
Updated by Jim Pingle about 10 years ago
- Status changed from New to Feedback
- Assignee deleted (
Jim Pingle)
I still can't reproduce this no matter how I try to break it. Setting to feedback for now. I posted a message on the forum thread linked above asking for people to retest as well.
Updated by Chris Buechler about 10 years ago
- Status changed from Feedback to Resolved
Edit: scratch that, still an issue in some particular edge case I haven't quantified yet.
Updated by Chris Buechler about 10 years ago
- Status changed from Resolved to New
- Assignee set to Chris Buechler
still an issue in some particular edge case I haven't quantified yet.
Updated by Chris Buechler about 10 years ago
- Assignee changed from Chris Buechler to Renato Botelho
I updated the above mentioned redmine-3822.xml config file. I can reliably reproduce this hang by just restoring this config to a clean install of the latest 2.2 (full amd64, though I doubt that matters). On the first reboot after the config restore, it's fine. After the first boot of the restored config completes, reboot, and it'll hang on the next and every subsequent boot.
Updated by Chris Palmer about 10 years ago
I have two machines on the latest 2.2 that hang every first boot but come alive after a re-boot. I can provide configs for both if needed.
Updated by Chris Palmer about 10 years ago
If I halt the system then they will hang at "Synch user settings" ?? But if I pull the plug they seem to finish the boot. Probably a better description.
Updated by Chris Buechler about 10 years ago
- Status changed from New to Feedback
this seems to have been fixed within the last day or two, at least the systems I had where it was replicable no longer have the issue, and a couple others on the forum have reported the same.
Updated by Chris Buechler about 10 years ago
- Status changed from Feedback to Resolved
Several upgrades later on systems that used to have this issue, and we're still good. Others on forum have also confirmed.