github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

CreateIssuesIndexer: mkdir indexers: permission denied #570

New Issue
Closed
opened 2025-11-02 03:28:29 -06:00 by GiteaMirror · 19 comments
GiteaMirror commented 2025-11-02 03:28:29 -06:00
Owner
Copy Link

Originally created by @NuLL3rr0r on GitHub (Mar 23, 2017).

  • 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.

Originally created by @NuLL3rr0r on GitHub (Mar 23, 2017). - 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.
GiteaMirror added the type/question label 2025-11-02 03:28:29 -06:00
GiteaMirror commented 2025-11-02 03:28:30 -06:00
Author
Owner
Copy Link

@cez81 commented on GitHub (Mar 23, 2017):

Have you got an indexers directory in the same directory as gitea? If yes, what permissions? If no, try creating it.

@cez81 commented on GitHub (Mar 23, 2017): Have you got an `indexers` directory in the same directory as gitea? If yes, what permissions? If no, try creating it.
GiteaMirror commented 2025-11-02 03:28:30 -06:00
Author
Owner
Copy Link

@psolyca commented on GitHub (Mar 24, 2017):

I have the same issue and I have to delete them each time I update Gitea even of they have the right permissions.

I am using mysql and a compiled version (ae9b02b0).

@psolyca commented on GitHub (Mar 24, 2017): I have the same issue and I have to delete them each time I update Gitea even of they have the right permissions. I am using mysql and a compiled version (ae9b02b0).
GiteaMirror commented 2025-11-02 03:28:30 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Mar 25, 2017):

@psolyca maybe the Gitea direcotry is not owned by user git.

@lunny commented on GitHub (Mar 25, 2017): @psolyca maybe the Gitea direcotry is not owned by user `git`.
GiteaMirror commented 2025-11-02 03:28:30 -06:00
Author
Owner
Copy Link

@psolyca commented on GitHub (Mar 25, 2017):

I am using Arch Linux version
https://aur.archlinux.org/packages/gitea-git/
Which is installed, ran with gitea user and group. Everything is homogeneous with gitea user.
I will try with git user.

@NuLL3rr0r do you use git user or an other one ?

@psolyca commented on GitHub (Mar 25, 2017): I am using Arch Linux version https://aur.archlinux.org/packages/gitea-git/ Which is installed, ran with gitea user and group. Everything is homogeneous with gitea user. I will try with git user. @NuLL3rr0r do you use git user or an other one ?
GiteaMirror commented 2025-11-02 03:28:31 -06:00
Author
Owner
Copy Link

@NuLL3rr0r commented on GitHub (Mar 26, 2017):

@cez81 thank you for the suggestion. I do not have access to the server at the moment but I'll check and report back.

@psolyca if I recall correctly it was git user. I'll check on that too and report back.

@NuLL3rr0r commented on GitHub (Mar 26, 2017): @cez81 thank you for the suggestion. I do not have access to the server at the moment but I'll check and report back. @psolyca if I recall correctly it was git user. I'll check on that too and report back.
GiteaMirror commented 2025-11-02 03:28:31 -06:00
Author
Owner
Copy Link

@NuLL3rr0r commented on GitHub (Mar 26, 2017):

@cez81 I have /var/db/gitea/data as APP_DATA_PATH and there is no indexers directory inside /var/db/gitea.

@psolyca The user and the group are git.

@NuLL3rr0r commented on GitHub (Mar 26, 2017): @cez81 I have /var/db/gitea/data as APP_DATA_PATH and there is no indexers directory inside /var/db/gitea. @psolyca The user and the group are git.
GiteaMirror commented 2025-11-02 03:28:31 -06:00
Author
Owner
Copy Link

@cez81 commented on GitHub (Mar 26, 2017):

@NuLL3rr0r I don't think indexers uses APP_DATA_PATH. Try setting something like this instead in your app.ini

[indexer]
ISSUE_INDEXER_PATH = /var/db/gitea/data/indexers/issues.bleve
@cez81 commented on GitHub (Mar 26, 2017): @NuLL3rr0r I don't think indexers uses APP_DATA_PATH. Try setting something like this instead in your app.ini ``` [indexer] ISSUE_INDEXER_PATH = /var/db/gitea/data/indexers/issues.bleve ```
GiteaMirror commented 2025-11-02 03:28:31 -06:00
Author
Owner
Copy Link

@psolyca commented on GitHub (Mar 26, 2017):

I reinstall the same recompiled version with git user and group (without removing old version).
So everything has changed to git user and I do not have the issue anymore.
I tried with reinstalling the same version with gitea user and group and I have also no issue.

Does the indexers files and folder follow a version of gitea ? I will try with an other version to see if the issue come back.

@psolyca commented on GitHub (Mar 26, 2017): I reinstall the same recompiled version with git user and group (without removing old version). So everything has changed to git user and I do not have the issue anymore. I tried with reinstalling the same version with gitea user and group and I have also no issue. Does the indexers files and folder follow a version of gitea ? I will try with an other version to see if the issue come back.
GiteaMirror commented 2025-11-02 03:28:31 -06:00
Author
Owner
Copy Link

@NuLL3rr0r commented on GitHub (Apr 2, 2017):

@cez81 Thank you so much!

That solved the issue for me.

@NuLL3rr0r commented on GitHub (Apr 2, 2017): @cez81 Thank you so much! That solved the issue for me.
GiteaMirror commented 2025-11-02 03:28:32 -06:00
Author
Owner
Copy Link

@fbettag commented on GitHub (Apr 8, 2017):

worked here too! thanks

@fbettag commented on GitHub (Apr 8, 2017): worked here too! thanks
GiteaMirror commented 2025-11-02 03:28:32 -06:00
Author
Owner
Copy Link

@bkcsoft commented on GitHub (Apr 18, 2017):

@NuLL3rr0r So, is this issue resolved? Do we need better documentation on this? Better defaults? :)

@bkcsoft commented on GitHub (Apr 18, 2017): @NuLL3rr0r So, is this issue resolved? Do we need better documentation on this? Better defaults? :)
GiteaMirror commented 2025-11-02 03:28:32 -06:00
Author
Owner
Copy Link

@cez81 commented on GitHub (Apr 18, 2017):

Maybe move indexers into the data directory? Or is there a reason why it isn't in there?

@cez81 commented on GitHub (Apr 18, 2017): Maybe move indexers into the data directory? Or is there a reason why it isn't in there?
GiteaMirror commented 2025-11-02 03:28:32 -06:00
Author
Owner
Copy Link

@NuLL3rr0r commented on GitHub (Apr 19, 2017):

@bkcsoft

Well, it solved the issue for me and it seems for others, too. But, I believe @cez81 is right; why it isn't there by default?
In addition to the documentation, it would be a good idea to add that option to the sample config file.

Thanks!

@NuLL3rr0r commented on GitHub (Apr 19, 2017): @bkcsoft Well, it solved the issue for me and it seems for others, too. But, I believe @cez81 is right; why it isn't there by default? In addition to the documentation, it would be a good idea to add that option to the sample config file. Thanks!
GiteaMirror commented 2025-11-02 03:28:33 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Apr 19, 2017):

Maybe @ethantkoenig could give us his consideration when he sent that PR.

@lunny commented on GitHub (Apr 19, 2017): Maybe @ethantkoenig could give us his consideration when he sent that PR.
GiteaMirror commented 2025-11-02 03:28:33 -06:00
Author
Owner
Copy Link

@ethantkoenig commented on GitHub (Apr 21, 2017):

I admittedly didn't put a lot of thought into the default ISSUE_INDEXER_PATH value. If anyone thinks it would make sense to change it, I'm open to suggestions.

@ethantkoenig commented on GitHub (Apr 21, 2017): I admittedly didn't put a lot of thought into the default `ISSUE_INDEXER_PATH` value. If anyone thinks it would make sense to change it, I'm open to suggestions.
GiteaMirror commented 2025-11-02 03:28:33 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Apr 21, 2017):

Maybe ISSUE_INDEXER_PATH = /var/db/gitea/data/indexers/issues.bleve should be added to config cheetsheet and change the default value to gitea/data.

@lunny commented on GitHub (Apr 21, 2017): Maybe `ISSUE_INDEXER_PATH = /var/db/gitea/data/indexers/issues.bleve` should be added to config cheetsheet and change the default value to `gitea/data`.
GiteaMirror commented 2025-11-02 03:28:33 -06:00
Author
Owner
Copy Link

@jerrykan commented on GitHub (Oct 19, 2017):

I just got hit by this issue trying to migrate from gogs v0.9.141 to gitea v1.2.0

If the default value is ISSUE_INDEXER_PATH = indexers/issues.bleve what is the indexers/issues.bleve path relative to? the data directory? the current working directory?

Does the app.ini config support variable interpolation like ISSUE_INDEXER_PATH = %{APP_DATA_PATH}/indexers/issues.bleve? or is it worth adding support so that these relative paths can be a bit more explicit?

@jerrykan commented on GitHub (Oct 19, 2017): I just got hit by this issue trying to migrate from gogs v0.9.141 to gitea v1.2.0 If the default value is `ISSUE_INDEXER_PATH = indexers/issues.bleve` what is the `indexers/issues.bleve` path relative to? the data directory? the current working directory? Does the `app.ini` config support variable interpolation like `ISSUE_INDEXER_PATH = %{APP_DATA_PATH}/indexers/issues.bleve`? or is it worth adding support so that these relative paths can be a bit more explicit?
GiteaMirror commented 2025-11-02 03:28:33 -06:00
Author
Owner
Copy Link

@cez81 commented on GitHub (Oct 19, 2017):

Relative to the binary.

It does.

https://github.com/go-gitea/gitea/pull/2192 should move indexers directory to APP_DATA_PATH.

@cez81 commented on GitHub (Oct 19, 2017): Relative to the binary. It does. https://github.com/go-gitea/gitea/pull/2192 should move indexers directory to APP_DATA_PATH.
GiteaMirror commented 2025-11-02 03:28:34 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Nov 3, 2017):

Path is no relative to data directory. Fixed by #2192

@lafriks commented on GitHub (Nov 3, 2017): Path is no relative to data directory. Fixed by #2192
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/question
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#570
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?