-
-
Notifications
You must be signed in to change notification settings - Fork 5.9k
Closed
Labels
type/questionIssue needs no code to be fixed, only a description on how to fix it yourself.Issue needs no code to be fixed, only a description on how to fix it yourself.
Description
- Gitea version (or commit ref): 1.1.0
- Git version: 2.11.1
- Operating system: FreeBSD 11.0-RELEASE-p8 (or) FreeBSD 10.3-RELEASE-p17
- Database (use
[x]
):- [X ] PostgreSQL
- MySQL
- MSSQL
- SQLite
- Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- [X ] Not relevant
- Log gist:
2017/03/23 14:47:42 [I] Log Mode: File(Info)
2017/03/23 14:47:42 [I] XORM Log Mode: File(Info)
2017/03/23 14:47:42 [I] Cache Service Enabled
2017/03/23 14:47:42 [I] Session Service Enabled
2017/03/23 14:47:42 [I] Mail Service Enabled
2017/03/23 14:47:42 [I] Notify Mail Service Enabled
2017/03/23 14:47:43 [I] Git Version: 2.11.1
2017/03/23 14:47:43 [...els/issue_indexer.go:77 InitIssueIndexer()] [E] CreateIssuesIndexer: mkdir indexers: permission denied
Description
I updated two of my productions Gitea servers from v1.0.1 to v1.1.0 through FreeBSD ports and now Gitea service refuses to start with the following line in the logs:
2017/03/23 14:47:43 [...els/issue_indexer.go:77 InitIssueIndexer()] [E] CreateIssuesIndexer: mkdir indexers: permission denied
The error is very ambiguous and hard to understand. So, now both servers are simply out of production due to this error or whatever caused it.
Metadata
Metadata
Assignees
Labels
type/questionIssue needs no code to be fixed, only a description on how to fix it yourself.Issue needs no code to be fixed, only a description on how to fix it yourself.