Gitea unable to start

[drsect0r]

• Gitea version: Docker 907f7f0a49e0
• Git version:
• Operating system: Debian 8
• Database (use [x]):
  • PostgreSQL
  • MySQL
  • MSSQL
  • SQLite
• Can you reproduce the bug at https://try.gitea.io:
  • Yes (provide example URL)
  • No
  • Not relevant
• Log gist:

Description

Gitea appears to be stuck in a loop and is unable to start, displaying the messages below. Only thing related I could find is commit cb87f29.

WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping
2018/04/30 09:57:31 [T] AppPath: /app/gitea/gitea
2018/04/30 09:57:31 [T] AppWorkPath: /app/gitea
2018/04/30 09:57:31 [T] Custom path: /data/gitea
2018/04/30 09:57:31 [T] Log path: /data/gitea/log
WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping
2018/04/30 09:57:32 [T] AppPath: /app/gitea/gitea
2018/04/30 09:57:32 [T] AppWorkPath: /app/gitea
2018/04/30 09:57:32 [T] Custom path: /data/gitea
2018/04/30 09:57:32 [T] Log path: /data/gitea/log
WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping
2018/04/30 09:57:33 [T] AppPath: /app/gitea/gitea
2018/04/30 09:57:33 [T] AppWorkPath: /app/gitea
2018/04/30 09:57:33 [T] Custom path: /data/gitea
2018/04/30 09:57:33 [T] Log path: /data/gitea/log
WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping
2018/04/30 09:57:34 [T] AppPath: /app/gitea/gitea
2018/04/30 09:57:34 [T] AppWorkPath: /app/gitea
2018/04/30 09:57:34 [T] Custom path: /data/gitea
2018/04/30 09:57:34 [T] Log path: /data/gitea/log

[daviian]

There's already a discussion about that warning: gliderlabs/docker-alpine#30

Guess we should implemented the workaround mentioned here gliderlabs/docker-alpine#30 (comment)

[drsect0r]

I also don't think this is the cause of Gitea not starting. (just found out about #3859)

[pojntfx]

I have the same problem using the latest gitea docker image. Any workarounds? Tried gliderlabs/docker-alpine#30 (entered the commands into the running container from the OpenShift web console; should I do this differently?) but that did not work, still the same error. I'm using postgresql as my database.

[NoMoreNicksLeft]

I have this same problem. The linked alpine issue fix does not work for me. This loops forever.

[ivarlovlie]

probably unrelated, but this loop/error only occurs when i set START_SSH_SERVER to true

[lafriks]

That's because gitea can not bind on 22 port probably

[UtechtDustin]

@lafriks
I also get the same output (without the warning)

2018/06/20 19:06:35 [T] AppPath: /opt/gitea/gitea
2018/06/20 19:06:35 [T] AppWorkPath: /opt/gitea
2018/06/20 19:06:35 [T] Custom path: /opt/gitea/custom
2018/06/20 19:06:35 [T] Log path: /opt/log

Gittea dont start and i got also no errors (also not in the log file).

[ptrcnull]

Still happens for me on the latest Docker image.

• Gitea version: Docker fa6ca546d614
• Database: SQLite

EDIT: nvm, fixed it. for anyone reading: check your disk space

[daknuett]

I have the same problem. I am on version 60505c2ef496475a7f90f0ea577a8cf1f3d2b53dfa7d0c9aca342e7b620d309a with SQLite database.

Gitea seems to ignore my gitea/conf/app.ini:

Dec 19 13:26:15 syslogd started: BusyBox v1.28.4
Dec 19 13:26:15 sshd[15]: Server listening on :: port 22.
Dec 19 13:26:15 sshd[15]: Server listening on 0.0.0.0 port 22.
2018/12/19 13:26:15 [T] AppPath: /app/gitea/gitea
2018/12/19 13:26:15 [T] AppWorkPath: /app/gitea
2018/12/19 13:26:15 [T] Custom path: /data/gitea
2018/12/19 13:26:15 [T] Log path: /data/gitea/log
2018/12/19 13:26:16 [T] AppPath: /app/gitea/gitea
2018/12/19 13:26:16 [T] AppWorkPath: /app/gitea
2018/12/19 13:26:16 [T] Custom path: /data/gitea
2018/12/19 13:26:16 [T] Log path: /data/gitea/log
2018/12/19 13:26:16 [I] Gitea vb65e37e built with: bindata, sqlite, sqlite_unlock_notify
2018/12/19 13:26:17 [T] AppPath: /app/gitea/gitea
2018/12/19 13:26:17 [T] AppWorkPath: /app/gitea
2018/12/19 13:26:17 [T] Custom path: /data/gitea
2018/12/19 13:26:17 [T] Log path: /data/gitea/log
2018/12/19 13:26:18 [T] AppPath: /app/gitea/gitea
2018/12/19 13:26:18 [T] AppWorkPath: /app/gitea
2018/12/19 13:26:18 [T] Custom path: /data/gitea
2018/12/19 13:26:18 [T] Log path: /data/gitea/log
2018/12/19 13:26:19 [T] AppPath: /app/gitea/gitea
2018/12/19 13:26:19 [T] AppWorkPath: /app/gitea
2018/12/19 13:26:19 [T] Custom path: /data/gitea
2018/12/19 13:26:19 [T] Log path: /data/gitea/log
2018/12/19 13:26:20 [T] AppPath: /app/gitea/gitea
2018/12/19 13:26:20 [T] AppWorkPath: /app/gitea
2018/12/19 13:26:20 [T] Custom path: /data/gitea
2018/12/19 13:26:20 [T] Log path: /data/gitea/log
[repeats]

Although I have in my app.ini:

DISABLE_SSH      = false
SSH_PORT         = 10022

All was working fine unti it recently just stopped working.

[danst0]

Same here. Latest Docker image. app.ini is ignored.

[Marco77577]

And also here. Is there no solution?

[daknuett]

Well the last time I had to wait for the next image and it started working again.

A possible workaround is to explicitly tag the version that works, instead of using latest.

[zeripath]

Hmm they should always work! If they're not working you need to open an issue.

[techknowlogick]

I will lock this conversation so that any new issue can be resolved in open tickets.