Failed to initialize issue indexer: mkdir data: permission denied in several situations #3339

@lunny commented on GitHub (May 17, 2019):

Merge pull request should be a known issue.

@lunny commented on GitHub (May 17, 2019): Merge pull request should be a known issue.

GiteaMirror commented

@Frickeldave commented on GitHub (May 19, 2019):

But as described before, it's not only an issue with pull requests, also with editing in web and with version 1.8.0 during startup...

@Frickeldave commented on GitHub (May 19, 2019): But as described before, it's not only an issue with pull requests, also with editing in web and with version 1.8.0 during startup...

GiteaMirror commented

@lunny commented on GitHub (May 20, 2019):

@Frickeldave I think you should check your filesystem permission since the log said permission denied.

@lunny commented on GitHub (May 20, 2019): @Frickeldave I think you should check your filesystem permission since the log said `permission denied`.

GiteaMirror commented

@Frickeldave commented on GitHub (May 20, 2019):

Hi,

that was the first thing i have done. But i think the permissions are not the problem. The path /home/appuser/app and /home/appuser/data is fully writable for the user.

drwxr-sr-x 1 appuser appuser 26 May 17 06:58 .
drwxr-xr-x 1 root root 21 Feb 22 07:57 ..
-rw------- 1 appuser appuser 90 May 20 07:44 .ash_history
-rw-r--r-- 1 appuser appuser 150 May 15 15:29 .bashrc
drwxr-sr-x 1 appuser appuser 16 May 15 15:28 app
drwxr-sr-x 11 appuser appuser 269 May 17 06:49 data

Is it possile, that gitea tries to write to another path?

Regards

Dave

@Frickeldave commented on GitHub (May 20, 2019): Hi, that was the first thing i have done. But i think the permissions are not the problem. The path /home/appuser/app and /home/appuser/data is fully writable for the user. _drwxr-sr-x 1 appuser appuser 26 May 17 06:58 . drwxr-xr-x 1 root root 21 Feb 22 07:57 .. -rw------- 1 appuser appuser 90 May 20 07:44 .ash_history -rw-r--r-- 1 appuser appuser 150 May 15 15:29 .bashrc drwxr-sr-x 1 appuser appuser 16 May 15 15:28 app drwxr-sr-x 11 appuser appuser 269 May 17 06:49 data_ Is it possile, that gitea tries to write to another path? Regards Dave

GiteaMirror commented

@Frickeldave commented on GitHub (May 22, 2019):

Hi,

any ideas regarding that issue? Any more feedback needed?

Regards

Dave

@Frickeldave commented on GitHub (May 22, 2019): Hi, any ideas regarding that issue? Any more feedback needed? Regards Dave

GiteaMirror commented

6eb53ac570/modules/setting/indexer.go (L45)

@zeripath commented on GitHub (May 22, 2019):

The issue indexer path is determined here:

AppDataPath is determined here:

6eb53ac570/modules/setting/setting.go (L615)

And AppWorkPath is either:

DIRECTORY_OF_GITEA_BINARY
$GITEA_WORK_DIR

In 1.9 you will be able to set this using the --work-dir option.

Looking at the information you've provided it looks like you need to set GITEA_WORK_DIR=/home/appuser/data

I suggest you shadow Gitea with a script that sets these for you.

@zeripath commented on GitHub (May 22, 2019): The issue indexer path is determined here: https://github.com/go-gitea/gitea/blob/6eb53ac570ab9af51fc9cbd79f1db782edce57e0/modules/setting/indexer.go#L45 AppDataPath is determined here: https://github.com/go-gitea/gitea/blob/6eb53ac570ab9af51fc9cbd79f1db782edce57e0/modules/setting/setting.go#L615 And AppWorkPath is either: * DIRECTORY_OF_GITEA_BINARY * $GITEA_WORK_DIR In 1.9 you will be able to set this using the --work-dir option. Looking at the information you've provided it looks like you need to set GITEA_WORK_DIR=/home/appuser/data I suggest you shadow Gitea with a script that sets these for you.

GiteaMirror commented

@Frickeldave commented on GitHub (May 22, 2019):

Hi,

thank you very much. I already have a wrapper script. In my inital post this is already described:

I have a startscript (start.sh) as entrypoint defined. In this startscript i set all needed variables:

_
export USER=$(whoami)
export USERNAME=$(whoami)
export GITEA_CUSTOM=/home/appuser/data/custom
export GITEA_WORK_DIR=/home/appuser/data
_

I start gitea with /home/appuser/app/gitea -c /home/appuser/data/gitea.ini within the start.sh script.

Regards

Dave

@Frickeldave commented on GitHub (May 22, 2019): Hi, thank you very much. I already have a wrapper script. In my inital post this is already described: I have a startscript (start.sh) as entrypoint defined. In this startscript i set all needed variables: _ export USER=$(whoami) export USERNAME=$(whoami) export GITEA_CUSTOM=/home/appuser/data/custom export GITEA_WORK_DIR=/home/appuser/data _ I start gitea with /home/appuser/app/gitea -c /home/appuser/data/gitea.ini within the start.sh script. Regards Dave

GiteaMirror commented

@zeripath commented on GitHub (May 22, 2019):

I don't think your Gitea work dir export is working properly 2019/05/15 14:03:35 [T] AppWorkPath: /home/appuser/app

@zeripath commented on GitHub (May 22, 2019): I don't think your Gitea work dir export is working properly `2019/05/15 14:03:35 [T] AppWorkPath: /home/appuser/app`

GiteaMirror commented

@zeripath commented on GitHub (May 22, 2019):

There's another place things get written to (!) $HOME/gitea-repositories but I can't remember off the top of my head which config that corresponds to.

@zeripath commented on GitHub (May 22, 2019): There's another place things get written to (!) $HOME/gitea-repositories but I can't remember off the top of my head which config that corresponds to.

GiteaMirror commented

@Frickeldave commented on GitHub (May 22, 2019):

Possibly. Here is a print from my console output:

_
/ $ echo "" > /home/appuser/data/log/gitea.log
/ $ cat /home/appuser/data/log/gitea.log

/ $ echo $GITEA_WORK_DIR
/home/appuser/data
/ $ /home/appuser/app/gitea web -c /home/appuser/data/gitea.ini
2019/05/22 12:23:36 [T] AppPath: /home/appuser/app/gitea
2019/05/22 12:23:36 [T] AppWorkPath: /home/appuser/data
2019/05/22 12:23:36 [T] Custom path: /home/appuser/data/custom
2019/05/22 12:23:36 [T] Log path: /home/appuser/data/log
/ $ cat /home/appuser/data/log/gitea.log

2019/05/22 12:23:36 [I] Log Mode: File(Info)
2019/05/22 12:23:36 [I] XORM Log Mode: File(Info)
2019/05/22 12:23:36 [I] Cache Service Enabled
2019/05/22 12:23:36 [I] Session Service Enabled
2019/05/22 12:23:36 [I] Beginning ORM engine initialization.
2019/05/22 12:23:36 [I] ORM engine initialization attempt #1/10...
2019/05/22 12:23:36 [I] ORM engine initialization successful!
2019/05/22 12:23:36 [I] Git Version: 2.20.1
2019/05/22 12:23:36 [...itea/routers/init.go:95 GlobalInit()] [E] Failed to initialize issue indexer: mkdir indexers: permission denied
_

As you can see, in the current console session, GITEA_WORK_DIR is set properly. Any other thing i can check?

Attached you will find my gitea.ini file.

Regards

Dave

gitea.ini.zip

@Frickeldave commented on GitHub (May 22, 2019): Possibly. Here is a print from my console output: _ / $ echo "" > /home/appuser/data/log/gitea.log / $ cat /home/appuser/data/log/gitea.log / $ echo $GITEA_WORK_DIR /home/appuser/data / $ /home/appuser/app/gitea web -c /home/appuser/data/gitea.ini 2019/05/22 12:23:36 [T] AppPath: /home/appuser/app/gitea 2019/05/22 12:23:36 [T] AppWorkPath: /home/appuser/data 2019/05/22 12:23:36 [T] Custom path: /home/appuser/data/custom 2019/05/22 12:23:36 [T] Log path: /home/appuser/data/log / $ cat /home/appuser/data/log/gitea.log 2019/05/22 12:23:36 [I] Log Mode: File(Info) 2019/05/22 12:23:36 [I] XORM Log Mode: File(Info) 2019/05/22 12:23:36 [I] Cache Service Enabled 2019/05/22 12:23:36 [I] Session Service Enabled 2019/05/22 12:23:36 [I] Beginning ORM engine initialization. 2019/05/22 12:23:36 [I] ORM engine initialization attempt #1/10... 2019/05/22 12:23:36 [I] ORM engine initialization successful! 2019/05/22 12:23:36 [I] Git Version: 2.20.1 2019/05/22 12:23:36 [...itea/routers/init.go:95 GlobalInit()] [E] Failed to initialize issue indexer: mkdir indexers: permission denied _ As you can see, in the current console session, GITEA_WORK_DIR is set properly. Any other thing i can check? Attached you will find my gitea.ini file. Regards Dave [gitea.ini.zip](https://github.com/go-gitea/gitea/files/3207322/gitea.ini.zip)

GiteaMirror commented

@zeripath commented on GitHub (May 22, 2019):

It looks like you've just copied the whole of app.ini.sample as your app.ini... That's unnecessary and a very good way of ending up over-configuring things and perhaps even breaking things.

You should only copy what you need. For example, the log section is not meant to copied over exactly the way you have done - did you read it? I'm also concerned that you say you're using 1.7.2 (or maybe 1.8.0) but that app.ini.sample is the 1.9 sample. (You're definitely not running 1.9 I can tell from the logging.) I would seriously recommend paring down your app.ini so that it represents what you need to configure and only what you need to configure.

Further are you telling me that you're ending up with different configuration between starting gitea on the console and starting it through your start.sh script? If so the problem lies in your start.sh script. Is it possible that your options are being overridden somewhere else? On the admin pages of gitea you should be able to check where it thinks it is looking for things. In particular it will say if GITEA_WORK_DIR is set and/or GITEA_CUSTOM.

You really should also upgrade your Gitea to at least 1.8.1.

@zeripath commented on GitHub (May 22, 2019): It looks like you've just copied the whole of app.ini.sample as your app.ini... That's unnecessary and a very good way of ending up over-configuring things and perhaps even breaking things. You should only copy what you need. For example, the log section is not meant to copied over exactly the way you have done - did you read it? I'm also concerned that you say you're using 1.7.2 (or maybe 1.8.0) but that app.ini.sample is the 1.9 sample. (You're definitely not running 1.9 I can tell from the logging.) I would seriously recommend paring down your app.ini so that it represents what you need to configure and only what you need to configure. Further are you telling me that you're ending up with different configuration between starting gitea on the console and starting it through your start.sh script? If so the problem lies in your start.sh script. Is it possible that your options are being overridden somewhere else? On the admin pages of gitea you should be able to check where it thinks it is looking for things. In particular it will say if GITEA_WORK_DIR is set and/or GITEA_CUSTOM. You really should also upgrade your Gitea to at least 1.8.1.

GiteaMirror commented

@Frickeldave commented on GitHub (May 22, 2019):

Thank you very much for the time you invest.
Currently in 1.8.0 i have the situtation, that gitea isn't starting, therefore i cannot look into the admin page. It just write out the 4 lines at the console i have posted before. In the version 1.7.2 gitea is starting with the same configuration file (1.7.2 is our prod system, 1.8.0 my dev system).
Currently i ran gitea from an interactive console just for testing (and to exclude every issue that should come from the start.sh script). I execute the 4 export command and then run gitea as shown before.
Regarding the app.ini version: I will compare with the 1.8.0 version, and let you know the results here.

@Frickeldave commented on GitHub (May 22, 2019): Thank you very much for the time you invest. Currently in 1.8.0 i have the situtation, that gitea isn't starting, therefore i cannot look into the admin page. It just write out the 4 lines at the console i have posted before. In the version 1.7.2 gitea is starting with the same configuration file (1.7.2 is our prod system, 1.8.0 my dev system). Currently i ran gitea from an interactive console just for testing (and to exclude every issue that should come from the start.sh script). I execute the 4 export command and then run gitea as shown before. Regarding the app.ini version: I will compare with the 1.8.0 version, and let you know the results here.

GiteaMirror commented