-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Update 1.7.3 to 1.8 seems to be broken - [E] InitIssuesIndexer: create index, mkdir /usr/local/bin/data: permission denied #6398
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Same here on a raspberry. For gitea I use a seperate user with home folder (user: gitea, Home folder: /home/gitea). I store all gitea files in the home folder of gitea. Until version 1.7.3 all was working fine but with the new update (version 1.8.0) I get the same error like above. PS: Instead of MySQL I use sqlite3. |
Probably related to #6367 |
@lunny could this be related to your indexer refactoring? |
@lunny Thanks for that information. I pasted the last lines of my Maybe this ticket can be closed as it seems to be a duplicate of #6367. I was looking for existing issues but didn't found any. I guess i was searching with the wrong keywords. |
duplicated with #6367 |
[x]
):Description
I did an update from version 1.7.3 to 1.8. As the documentation says i have just to download the new file, name it "gitea" and restart my service. I am using Gitea on my raspberry
I have done this before to update the last 2 times. It works like a charm.
Previous updates were just fine. Everything works as before. As i updated from 1.7.3 to 1.8 i was unable to start the server by hand.
Unfortunately the log is not filled when i use
systemctl start gitea.service
. There i am only getting the status that the service is not running anymore.I am not using /usr/local/bin.. to store my data. I changed no paths of my configuration.
When i replace the new gitea executable with the old version (1.7.3) i have no issues and can start the service by hand or service without modifying anything.
Could it be related to #5482 or #4672?
The text was updated successfully, but these errors were encountered: