|
From: | Bob Proulx |
Subject: | [savannah-help-public] [sr #109616] insufficient permission for pushing a git commit |
Date: | Sat, 5 Jan 2019 02:24:59 -0500 (EST) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.80 Safari/537.36 |
Update of sr #109616 (project administration): Status: None => Done Open/Closed: Open => Closed _______________________________________________________ Follow-up Comment #3: Thank you for reporting the problem. It is appreciated. Initially I thought it was just git shallow clones (--depth 1) that were failing and I had pushed this back in the queue of broken things to fix that were less urgent after other things due to the IP subnet migration to the new network. That was a mistake as this was preventing write access and should have been very urgent. Sorry. It's been a long two days. The migration is mostly complete now. The root cause was that the nfs mountd on the backend was not connecting to the database server for account data via libnss. It was the libnss-mysql part that was failing. Confusing because it was working when testing it but apparently not working at the instant that the nfs mountd was initially started and this was a sticky state. Therefore ids were not getting mapped. Therefore write access was not being allowed. Restarting the nfs mountd got this working again. Unmounting the NFS mount on the client and remounting it finished it. Please try it again. It should be working for you now. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/support/?109616> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |