gitea.service: Failed with result 'start-limit-hit'.

[snelweg]

• Gitea version (or commit ref): 1.8 (gitea-1.8-linux-amd64
  ) upgrading from gitea-1.7-linux-amd64
  Debian Linux xxxxx 2.6.32-042stab134.8 Rename import paths: "github.com/gogits/gogs" -> "github.com/go-gitea/gitea" #1 SMP Fri Dec 7 17:16:09 MSK 2018 x86_64 GNU/Linux
  gogs@xxxx:~/gitea$ cat /etc/debian_version
  8.11

Wanted to upgrade from 1.7 to 1.8. But gitea 1.8 will not start on my machine:

`root@xxxxxx:~# systemctl status gitea
● gitea.service - Gitea (Git with a cup of tea)
Loaded: loaded (/etc/systemd/system/gitea.service; enabled; vendor preset: enabled)
Active: failed (Result: start-limit-hit) since Mon 2019-04-08 11:20:42 CEST; 4min 16s ago
Process: 659 ExecStart=/home/gogs/gitea/gitea web (code=killed, signal=ABRT)
Main PID: 659 (code=killed, signal=ABRT)

Apr 08 11:20:42 nas2.microkloon.nl systemd[1]: gitea.service: Unit entered failed state.
Apr 08 11:20:42 nas2.microkloon.nl systemd[1]: gitea.service: Failed with result 'signal'.
Apr 08 11:20:42 nas2.microkloon.nl systemd[1]: gitea.service: Service hold-off time over, scheduling restart.
Apr 08 11:20:42 nas2.microkloon.nl systemd[1]: Stopped Gitea (Git with a cup of tea).
Apr 08 11:20:42 nas2.microkloon.nl systemd[1]: gitea.service: Start request repeated too quickly.
Apr 08 11:20:42 nas2.microkloon.nl systemd[1]: Failed to start Gitea (Git with a cup of tea).
Apr 08 11:20:42 nas2.microkloon.nl systemd[1]: gitea.service: Unit entered failed state.
Apr 08 11:20:42 nas2.microkloon.nl systemd[1]: gitea.service: Failed with result 'start-limit-hit'.
`
When I switch back to 1.7 everything works again. What am I doing wrong?
(I once a long time ago used gogs, still using that username on my machine, but everything is Gitea now)

[lafriks]

Check gitea.log for errors

[snelweg]

Check gitea.log for errors

gitea.log is not updated when using 1.8. So no messages about the error in the log file.

`
root@nas2:/home/gogs/gitea/log# ls -la
total 1336
drwxr-xr-x 3 gogs gogs 4096 Apr 8 00:03 .
drwxr-xr-x 5 gogs gogs 4096 Apr 8 11:58 ..
-rw-r----- 1 gogs gogs 647 Apr 8 11:26 gitea.log
-rw-r----- 1 gogs gogs 188 Mar 26 21:50 gitea.log.2019-04-02.001
drwxr-xr-x 2 gogs gogs 4096 Aug 14 2018 hooks
-rw-r----- 1 gogs gogs 0 Aug 6 2018 http.log
-rw-r----- 1 gogs gogs 8201 Apr 6 15:30 serv.log
-rw-r----- 1 gogs gogs 72387 Apr 8 11:56 xorm.log
-rw-r----- 1 gogs gogs 391326 Apr 1 23:53 xorm.log.2019-04-02.001
-rw-r----- 1 gogs gogs 339346 Apr 2 23:53 xorm.log.2019-04-03.001
-rw-r----- 1 gogs gogs 56310 Apr 3 23:53 xorm.log.2019-04-04.001
-rw-r----- 1 gogs gogs 37362 Apr 4 23:53 xorm.log.2019-04-05.001
-rw-r----- 1 gogs gogs 85418 Apr 5 23:53 xorm.log.2019-04-06.001
-rw-r----- 1 gogs gogs 118515 Apr 6 23:53 xorm.log.2019-04-07.001
-rw-r----- 1 gogs gogs 190882 Apr 7 23:53 xorm.log.2019-04-08.001

`

[snelweg]

Looks like I found the problem:

gogs@nas2:~/gitea$ ./gitea FATAL: kernel too old Aborted

So no upgrading anymore for me then. Thanks.

[lafriks]

you can compile manually with older golang version (1.9). Check docs on how to do that.