Can't update any existing User after upgrading from 9.10.2-u3 to 11
I upgraded my mini from 9.10.2-u3 to FreeNAS 11 Stable
I had two users already set up, with home directories that worked
I updated one user with an extra long password (26 characters a thru z)
I clicked save and it gave me a traceback error but the screenshot didn't save
I rebooted it in the 9.10.2-u3 environment and they work
I updated again and it didn't work again. I got screenshots of the error messages this time
Let me know if I can provide any other insight.
If it helps my mini's ip is 10.20.1.95
#5 Updated by William Grzybowski over 3 years ago
- Status changed from Unscreened to Screened
Bonnie Follweiler wrote:
Sean, the issue only affects upgrades to FreeNAS 11. My "clean" install of FreeNAS 11 allows the long password.
I'll be using your mini in a few to try to reproduce and fix the issue. Please let it alone for a while, is that possible? Thanks
#7 Updated by William Grzybowski over 3 years ago
- Status changed from Screened to Unscreened
- Assignee changed from William Grzybowski to John Hixson
- Priority changed from No priority to Critical
- Target version set to 11.0
When AD is enabled making user operations take a lot of timeGenerating smb4.conf is one of them:
- time /usr/local/libexec/nas/generate_smb4_conf.py
1.017u 0.153s 0:23.76 4.8% 360+554k 2+0io 0pf+0w
John said he will look into it.
#10 Updated by John Hixson over 3 years ago
- Status changed from Screened to 15
So I've added the ability to tune this. Also, you shouldn't get a stack trace anymore. It would be nice if you could verify ;-) If when you update a user, you still see in /var/log/debug.log "ERROR: call timeout", then this is still taking too long and there may be a bigger problem. The default for this is 30 seconds, but you can adjust it by adding a sysctl with freenas.account.user.timeout.reload=xxx where xxx is value in seconds.