Closed
Description
- Gitea version (or commit ref): 1.11.2
- Git version: 2.17.1
- Operating system: Ubuntu 18.04.4
- 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:
# This is from the upgrade
$ ./update-gitea.sh 1.11.2
Updating gitea to version: '1.11.2'
+ wget -O gitea http://dl.gitea.io/gitea/1.11.2/gitea-1.11.2-linux-amd64
--2020-03-06 14:49:11-- http://dl.gitea.io/gitea/1.11.2/gitea-1.11.2-linux-amd64
Resolving dl.gitea.io (dl.gitea.io)... 104.27.143.155, 104.27.142.155, 2606:4700:3033::681b:8f9b, ...
Connecting to dl.gitea.io (dl.gitea.io)|104.27.143.155|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://dl.gitea.io:443/gitea/1.11.2/gitea-1.11.2-linux-amd64 [following]
--2020-03-06 14:49:11-- https://dl.gitea.io/gitea/1.11.2/gitea-1.11.2-linux-amd64
Connecting to dl.gitea.io (dl.gitea.io)|104.27.143.155|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 81229448 (77M) [application/octet-stream]
Saving to: ‘gitea’
gitea 100%[=====================================================================================================================>] 77.47M 3.82MB/s in 35s
2020-03-06 14:49:47 (2.20 MB/s) - ‘gitea’ saved [81229448/81229448]
+ chmod +x gitea
+ sudo chown gitea:gitea gitea
+ sudo mv gitea /srv/gitea/gitea-v1.11.2
+ sudo systemctl stop gitea
+ cd /srv/gitea
+ sudo ln -sf gitea-v1.11.2 gitea
+ sudo systemctl start gitea
+ sudo systemctl status gitea
● gitea.service - Gitea
Loaded: loaded (/etc/systemd/system/gitea.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2020-03-06 14:49:48 EST; 22ms ago
Main PID: 66761 (gitea)
Tasks: 6 (limit: 11059)
Memory: 5.6M
CPU: 15ms
CGroup: /system.slice/gitea.service
└─66761 /srv/gitea/gitea web
Mar 06 14:49:48 srv-1 systemd[1]: Started Gitea.
# This is where I notice the issue. Systemctl says it's running, and the Git logs looks fine:
$ sudo journalctl -u gitea
Mar 06 14:35:06 srv-1 gitea[4263]: [Macaron] 2020-03-06 14:35:06: Completed GET /serviceworker.js 200 OK in 1.96247ms
Mar 06 14:49:47 srv-1 systemd[1]: Stopping Gitea...
Mar 06 14:49:48 srv-1 systemd[1]: Stopped Gitea.
Mar 06 14:49:48 srv-1 systemd[1]: gitea.service: Consumed 3h 43min 1.604s CPU time
Mar 06 14:49:48 srv-1 systemd[1]: Started Gitea.
# Ok, but the website isn't responding. I then look at the following:
$ sudo netstat -nltp | grep git
$
# It's not listening on the correct port (9090 as defined in my config) which was working before this in 1.11.1
Description
I try to keep updated on the latest point releases. Typically this is smooth, but today it 1.11.2 didn't come up on the correct port (or apparently any port). The process was running and the logs don't show any errors. Not sure what is going on.
Metadata
Metadata
Assignees
Labels
No labels