gitea: Crashes after Gitea is configured - "Unable to initialize Bleve Issue Indexer"

  • Gitea version (or commit ref): latest and 1.0
  • Git version: What ever is in the Docker image
  • Operating system: Debian Buster with Docker (version 19.03.8, build afacb8b7f0)
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant

Description

Using the instructions found on the website I’ve make a Mysql server in Docker and setup using the database preparation instructions. I could guarantee that the Docker Mysql server works because I could connect and control the server using Mysql Workbench. I could also attest that the creditial and permissions for the

I’ve tried many times with different settings. Also dumped the entire Database and persistant files of Gitea between test runs. I would repeat the same problematic result everytime.

I suspect it might have to do with the fact I am using Portainer (not sure what’s the difference). Not sure…

Before, I’ve tried using Docker Compose I ran into another problem that is why I didn’t use that.

To replicate my problem:

  • Make a Mysql DB, pretty much default. connect to same network

  • Gitea using settings below, go to gitea’s webpage, go to login

  • Enter DB info and save

  • Saves the info, reloads and crashes. Crashes everytime afterwards as well.

Screenshots

Gitea Docker

Docker Settings image

Docker logs, shows Gitea terminating for no reason… repeatedly. image

Mysql Docker

image

image

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 18 (7 by maintainers)

Most upvoted comments

Ok it looks like for some reason bleve doesn’t like that filesystem. I guess there’s something odd about it - @lunny might know more. What’s your host system?

In any case the workaround is to use the db issue indexer.

In app.ini:

[indexer]
ISSUE_INDEXER_TYPE = db

Changed the title so it is easier for others to find it.

This should really go in the Installation with Docker page as I had the exact same problem. It seems like the default setup of gitea doesn’t work well with the fairly common use of MergerFS.

Linuxserver.io The Perfect Media Server - 2019 Edition Serverbuilds.net Setting up media server using Ubuntu and SnapRaid

Symptoms

Using the exact Installation with Docker steps, the docker instance crashes without details at the end of setup yeilding Received signal 15; terminating.

Steps to diagnose and resolve

  1. Edit /gitea-data/gitea/conf/app.ini as follow
 [log]
 ROOT_PATH = /data/gitea/log
 MODE      = console
 LEVEL     = debug
 XORM     = console
  1. Find that the real error is [F] Unable to initialize Bleve Issue Indexer at path: /data/gitea/indexers/issues.bleve Error: no such device
  2. Search and find this issue
  3. Edit /gitea-data/gitea/conf/app.ini as follow
 [indexer]
 ISSUE_INDEXER_PATH = /data/gitea/indexers/issues.bleve
 ISSUE_INDEXER_TYPE = db

Okay, what a success! This one-liner fixed everything! It doesn’t crash now. Awesome.

Btw, adding onto my last message, the server (running Docker) runs on Debian Buster.

Thanks @zeripath and all the others for all your help all along.