Gitea service keeps attempting to start

Hi!

I have followed the installation from binary guide from here:
https://docs.gitea.io/en-us/install-from-binary/

And I have set up the Linux service accordingly:
https://docs.gitea.io/en-us/linux-service/

My problem is that the service keeps trying to start Gitea on port 3000 even though Gitea is running fine already, so because of this the /home/git/gitea/log/gitea.log file keeps getting inflated with the following message every 2 seconds (the service is set to check if Gitea is running every 2 seconds):

[…io/gitea/cmd/web.go:178 runWeb()] [E] Failed to start server: listen tcp 0.0.0.0:3000: bind: address already in use

My question is why does the service not see that Gitea is already running? What is the method that it uses to check for the Gitea process?

I’m running Gitea with Apache2 reverse proxy on a subfolder in my domain (like https://example.com/gitea), with https redirection. I don’t know if this has anything to do with it…

My gitea app.ini looks like this:

APP_NAME = Gitea
RUN_USER = git
RUN_MODE = prod

[security]
INTERNAL_TOKEN = [EDITED]
INSTALL_LOCK   = true
SECRET_KEY     = [EDITED]

[database]
DB_TYPE  = mysql
HOST     = 127.0.0.1:3306
NAME     = gitea
USER     = gitea
PASSWD   = [EDITED]
SSL_MODE = disable
PATH     = data/gitea.db

[repository]
ROOT = [EDITED]

[server]
PROTOCOL         = https
SSH_DOMAIN       = example.com
DOMAIN           = example.com
HTTP_PORT        = 3000
ROOT_URL         = https:example.com/gitea/
DISABLE_SSH      = false
SSH_PORT         = 22
LFS_START_SERVER = true
LFS_CONTENT_PATH = [EDITED]
LFS_JWT_SECRET   = [EDITED]
OFFLINE_MODE     = false
CERT_FILE        = [EDITED]
KEY_FILE         = [EDITED]
ENABLE_REVERSE_PROXY_AUTHENTICATION = false
ENABLE_REVERSE_PROXY_AUTO_REGISTRATION = false

[mailer]
ENABLED = true
HOST    = smtp.gmail.com:587
FROM    = [EDITED]
USER    = [EDITED]
PASSWD  = [EDITED]

[service]
REGISTER_EMAIL_CONFIRM            = true
ENABLE_NOTIFY_MAIL                = true
DISABLE_REGISTRATION              = true
ALLOW_ONLY_EXTERNAL_REGISTRATION  = false
ENABLE_CAPTCHA                    = false
REQUIRE_SIGNIN_VIEW               = false
DEFAULT_KEEP_EMAIL_PRIVATE        = false
DEFAULT_ALLOW_CREATE_ORGANIZATION = true
DEFAULT_ENABLE_TIMETRACKING       = true
NO_REPLY_ADDRESS                  = noreply.hidden.org

[picture]
DISABLE_GRAVATAR        = false
ENABLE_FEDERATED_AVATAR = true

[openid]
ENABLE_OPENID_SIGNIN = true
ENABLE_OPENID_SIGNUP = false

[session]
PROVIDER = file
[log]
MODE      = file
LEVEL     = Error
ROOT_PATH = /home/git/gitea/log

What’s your uname -a?

Linux ODROID-XU4-01 4.14.78-150 #1 SMP PREEMPT Tue Oct 23 10:43:36 -03 2018 armv7l armv7l armv7l GNU/Linux

Ubuntu 18.04 running on ODROID XU4.

Somehow the situation fixed itself in the meantime, I don’t know how…

1 Like

Glad to hear your problem fixed itself. If you see a regression talk to this guy he’s an embedded linux god https://github.com/arpitjindal97

Thank you for your help! I appreciate it!

I’m having the same problem with Gitea v1.9.3. Gitea used to run fine on my Odroid XU4 (which is ARM v7) up until version 1.7.5. And then the ARM v7 support was ruined. There is not even a pre-build binary for ARM v7 available. So I tried to use the ARM v6 binary instead, as suggested by the Gitea downloads page (as a workaround). And the service keeps restarting and Gitea is not available in the browser. I do hope the ARM v7 support will be fixed soon!

The ARM v7 support has not been fixed to this day (almost 2 years). Despite what is recommended, to use the ARMv6 binaries, that does not work on Odroid boards. It may work on the Raspberry Pis, but I guess if you’ve started using Gitea on Odroid Xu4, like me, then you’re just out of luck, it does not look like the Gitea team intends to ever fix the ARMv7 support. I’m still stuck at Gitea v1.7.5 :cry: