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

gitea.service not starting on boot #7508

New Issue
Closed
opened 2025-11-02 07:27:59 -06:00 by GiteaMirror · 8 comments
GiteaMirror commented 2025-11-02 07:27:59 -06:00
Owner
Copy Link

Originally created by @RolfNoot on GitHub (Jun 25, 2021).

  • Gitea version (or commit ref): 1.14.3
  • Git version: 2.17.1
  • Operating system: Ubuntu 18.04.4 LTS
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Log gist:

Description

The gitea service doesn't start on boot, it fails with "Found ordering cycle" on boot (see log below). When I start manually after boot, the service starts well.

LOG

systemd[1]: sockets.target: Found ordering cycle on gitea.service/start
systemd[1]: sockets.target: Job gitea.service/start deleted to break ordering cycle starting with sockets.target/start

Originally created by @RolfNoot on GitHub (Jun 25, 2021). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Make sure it's not mentioned in the FAQ (https://docs.gitea.io/en-us/faq) 5. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.14.3 - Git version: 2.17.1 - Operating system: Ubuntu 18.04.4 LTS <!-- Please include information on whether you built gitea yourself, used one of our downloads or are using some other package --> <!-- Please also tell us how you are running gitea, e.g. if it is being run from docker, a command-line, systemd etc. ---> <!-- If you are using a package or systemd tell us what distribution you are using --> - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Log gist: <!-- It really is important to provide pertinent logs --> <!-- Please read https://docs.gitea.io/en-us/logging-configuration/#debugging-problems --> <!-- In addition, if your problem relates to git commands set `RUN_MODE=dev` at the top of app.ini --> ## Description <!-- If using a proxy or a CDN (e.g. CloudFlare) in front of gitea, please disable the proxy/CDN fully and connect to gitea directly to confirm the issue still persists without those services. --> The gitea service doesn't start on boot, it fails with "Found ordering cycle" on boot (see log below). When I start manually after boot, the service starts well. ## LOG systemd[1]: sockets.target: Found ordering cycle on gitea.service/start systemd[1]: sockets.target: Job gitea.service/start deleted to break ordering cycle starting with sockets.target/start
GiteaMirror added the type/questionissue/needs-feedback labels 2025-11-02 07:27:59 -06:00
GiteaMirror commented 2025-11-02 07:28:02 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Jun 25, 2021):

We would need to see your service file.

@zeripath commented on GitHub (Jun 25, 2021): We would need to see your service file.
GiteaMirror commented 2025-11-02 07:28:02 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Jun 25, 2021):

It's worth noting that this isn't a bug with gitea but a problem with your systemd configuration.

@zeripath commented on GitHub (Jun 25, 2021): It's worth noting that this isn't a bug with gitea but a problem with your systemd configuration.
GiteaMirror commented 2025-11-02 07:28:02 -06:00
Author
Owner
Copy Link

@RolfNoot commented on GitHub (Jun 25, 2021):

Yes, I get that it's a configuration problem. I took the gitea.service as provided by the documentation and changed it accordingly. I can see that systemd tried to start the service and that it failed.
gitea.service

@RolfNoot commented on GitHub (Jun 25, 2021): Yes, I get that it's a configuration problem. I took the gitea.service as provided by the documentation and changed it accordingly. I can see that systemd tried to start the service and that it failed. [gitea.service](https://github.com/go-gitea/gitea/files/6718272/gitea.service.txt)
GiteaMirror commented 2025-11-02 07:28:02 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Jun 25, 2021):

Have you changed other systemd configuration?

Do you have a mysql.service?

Have you created a socket activation?

@zeripath commented on GitHub (Jun 25, 2021): Have you changed other systemd configuration? Do you have a mysql.service? Have you created a socket activation?
GiteaMirror commented 2025-11-02 07:28:03 -06:00
Author
Owner
Copy Link

@RolfNoot commented on GitHub (Jun 25, 2021):

  1. It runs on a system which runs other services as well. Some other services have been installed before.
  2. There's no mysql service.
  3. Maybe another service uses socket activation, I don't know the details of what's installed previously.

Let me note that when starting the service after boot, it succeeds.

@RolfNoot commented on GitHub (Jun 25, 2021): 1. It runs on a system which runs other services as well. Some other services have been installed before. 2. There's no mysql service. 3. Maybe another service uses socket activation, I don't know the details of what's installed previously. Let me note that when starting the service after boot, it succeeds.
GiteaMirror commented 2025-11-02 07:28:03 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Jun 25, 2021):

2 .There's no mysql service.

Well that's your problem:

[Unit]
Description=Gitea (Git with a cup of tea)
After=syslog.target
After=network.target
###
# Don't forget to add the database service dependencies
###
#
Wants=mysql.service
After=mysql.service
...

You explicitly depend on the mysql.service here. Comment these two lines out.

@zeripath commented on GitHub (Jun 25, 2021): > 2 .There's no mysql service. Well that's your problem: ```systemd [Unit] Description=Gitea (Git with a cup of tea) After=syslog.target After=network.target ### # Don't forget to add the database service dependencies ### # Wants=mysql.service After=mysql.service ... ``` You explicitly depend on the mysql.service here. Comment these two lines out.
GiteaMirror commented 2025-11-02 07:28:04 -06:00
Author
Owner
Copy Link

@RolfNoot commented on GitHub (Jun 25, 2021):

Sorry, I didn't see the service listed at /etc/systemd/system/ However if I do service --status-all, this is my output:

 [ - ]  acpid
 [ + ]  apparmor
 [ + ]  apport
 [ + ]  atd
 [ - ]  console-setup.sh
 [ + ]  cron
 [ - ]  cryptdisks
 [ - ]  cryptdisks-early
 [ + ]  dbus
 [ + ]  ebtables
 [ + ]  grub-common
 [ - ]  hwclock.sh
 [ - ]  irqbalance
 [ + ]  iscsid
 [ - ]  keyboard-setup.sh
 [ + ]  kmod
 [ - ]  lvm2
 [ + ]  lvm2-lvmetad
 [ + ]  lvm2-lvmpolld
 [ + ]  lxcfs
 [ - ]  lxd
 [ - ]  mdadm
 [ - ]  mdadm-waitidle
 [ + ]  mosquitto
 [ + ]  mysql
 [ + ]  netfilter-persistent
 [ + ]  nginx
 [ - ]  open-iscsi
 [ - ]  open-vm-tools
 [ - ]  plymouth
 [ - ]  plymouth-log
 [ + ]  postgresql
 [ + ]  procps
 [ + ]  redis-server
 [ - ]  rsync
 [ + ]  rsyslog
 [ - ]  screen-cleanup
 [ + ]  ssh
 [ + ]  sysstat
 [ + ]  udev
 [ + ]  ufw
 [ + ]  unattended-upgrades
 [ - ]  uuidd
@RolfNoot commented on GitHub (Jun 25, 2021): Sorry, I didn't see the service listed at `/etc/systemd/system/` However if I do `service --status-all`, this is my output: ``` [ - ] acpid [ + ] apparmor [ + ] apport [ + ] atd [ - ] console-setup.sh [ + ] cron [ - ] cryptdisks [ - ] cryptdisks-early [ + ] dbus [ + ] ebtables [ + ] grub-common [ - ] hwclock.sh [ - ] irqbalance [ + ] iscsid [ - ] keyboard-setup.sh [ + ] kmod [ - ] lvm2 [ + ] lvm2-lvmetad [ + ] lvm2-lvmpolld [ + ] lxcfs [ - ] lxd [ - ] mdadm [ - ] mdadm-waitidle [ + ] mosquitto [ + ] mysql [ + ] netfilter-persistent [ + ] nginx [ - ] open-iscsi [ - ] open-vm-tools [ - ] plymouth [ - ] plymouth-log [ + ] postgresql [ + ] procps [ + ] redis-server [ - ] rsync [ + ] rsyslog [ - ] screen-cleanup [ + ] ssh [ + ] sysstat [ + ] udev [ + ] ufw [ + ] unattended-upgrades [ - ] uuidd ```
GiteaMirror commented 2025-11-02 07:28:04 -06:00
Author
Owner
Copy Link

@RolfNoot commented on GitHub (Jun 25, 2021):

Sorry for bothering, I finally find out that after a systemctl daemon-reload everything works well!

Thanks!

@RolfNoot commented on GitHub (Jun 25, 2021): Sorry for bothering, I finally find out that after a `systemctl daemon-reload` everything works well! Thanks!
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 issue/needs-feedback 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#7508
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?