DietPi-Software | Gitea: Fails on RPi2/3/4 with segmentation fault

Created on 1 Dec 2019  ·  21Comments  ·  Source: MichaIng/DietPi

ADMIN EDIT

Solution:

apt update
apt upgrade
systemctl restart gitea

Creating a bug report/issue

Required Information

  • DietPi version |
    G_DIETPI_VERSION_CORE=6 G_DIETPI_VERSION_SUB=26 G_DIETPI_VERSION_RC=3 G_GITBRANCH='master' G_GITOWNER='MichaIng'
  • Distro version | 10.2
  • Kernel version | Linux DietPi 4.19.75-v7+ #1270 SMP Tue Sep 24 18:45:11 BST 2019 armv7l GNU/Linux
  • SBC device | RPi3
  • Power supply used | 5V 1A
  • SDcard used | SanDisk ultra

Additional Information (if applicable)

  • Software title | gitea
  • Was the software title installed freshly or updated/migrated?
    Fresh Install

  • Can this issue be replicated on a fresh installation of DietPi?
    Fresh Install

  • Bug report ID | 0db9287d-176f-4c67-b39f-ca13a08ff016

Steps to reproduce

  1. Use dietpi-software to install gitea

Expected behaviour

  • gitea should be running and accessible on port 3000

Actual behaviour

service file fails
code=killed, signal=SEGV

Extra details

running the same command outside of service files produces the same results
root@DietPi:/home/dietpi# /mnt/dietpi_userdata/gitea/gitea web
Segmentation fault

ARMv7 External Bug RPi Solution available
Source
picture Cabur

All 21 comments

Many thanks for your report.

Hmm a SEGV sounds like a wrong or corrupted binary, especially since Gitea comes without any additional files or needs. Could you try the most recent one:

wget https://dl.gitea.io/gitea/1.9.6/gitea-1.9.6-linux-arm-6 -O /mnt/dietpi_userdata/gitea/gitea
MichaIng picture MichaIng on 1 Dec 2019

Tied and got the same results:

root@DietPi:/mnt/dietpi_userdata/gitea# wget https://dl.gitea.io/gitea/1.9.6/gitea-1.9.6-linux-arm-6 -O /mnt/dietpi_userdata/gitea/gitea
    --2019-12-01 18:34:01--  https://dl.gitea.io/gitea/1.9.6/gitea-1.9.6-linux-arm-6
Resolving dl.gitea.io (dl.gitea.io)... 104.27.143.155, 104.27.142.155, 2606:4700:30::681b:8e9b, ...
Connecting to dl.gitea.io (dl.gitea.io)|104.27.143.155|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 86613588 (83M) [application/octet-stream]
Saving to: ‘/mnt/dietpi_userdata/gitea/gitea’

/mnt/dietpi_userdata/gitea/gitea        100%[============================================================================>]  82.60M  3.22MB/s    in 43s

2019-12-01 18:34:45 (1.92 MB/s) - ‘/mnt/dietpi_userdata/gitea/gitea’ saved [86613588/86613588]

root@DietPi:/mnt/dietpi_userdata/gitea# systemctl start gitea
root@DietPi:/mnt/dietpi_userdata/gitea# ^start^status
systemctl status gitea
● gitea.service - Gitea (DietPi)
   Loaded: loaded (/etc/systemd/system/gitea.service; disabled; vendor preset: enabled)
   Active: failed (Result: signal) since Sun 2019-12-01 18:34:55 GMT; 6s ago
  Process: 2046 ExecStart=/mnt/dietpi_userdata/gitea/gitea web (code=killed, signal=SEGV)
 Main PID: 2046 (code=killed, signal=SEGV)

Dec 01 18:34:55 DietPi systemd[1]: Started Gitea (DietPi).
Dec 01 18:34:55 DietPi systemd[1]: gitea.service: Main process exited, code=killed, status=11/SEGV
Dec 01 18:34:55 DietPi systemd[1]: gitea.service: Failed with result 'signal'.
root@DietPi:/mnt/dietpi_userdata/gitea# ./gitea web
Segmentation fault
Cabur picture Cabur on 1 Dec 2019

@Cabur
Ah I forget about a permissions issue that was just solved with v6.27. Please try:

chown -R dietpi:dietpi /mnt/dietpi_userdata/gitea
systemctl restart gitea

Although this should not lead to a segmentation fault 🤔.

Side note: https://github.com/MichaIng/DietPi/pull/3250

  • Latest version will now be grabbed from GitHub release page automatically. It's v1.10.0 already, however all listed versions should work.
MichaIng picture MichaIng on 1 Dec 2019

Still no luck. Also looked at the side note, Pulled the latest from their git V1.10 and same results. going to go back and try some more tomorrow.

Cabur picture Cabur on 2 Dec 2019

@Cabur
I'll try it on my RPi as well, on the VMs it works just fine on all distros (just tested).

MichaIng picture MichaIng on 2 Dec 2019

@MichaIng
So interesting, when running inside gdb, it comes right up, outside still seg faults (still running V1.10 from their github)
dietpi@DietPi:~$ gdb /mnt/dietpi_userdata/gitea/gitea web

Cabur picture Cabur on 2 Dec 2019
👍1

@Cabur
Very strange indeed, I make some test on my RPi as well, since on VM it works very well.

MichaIng picture MichaIng on 4 Dec 2019

🈹 Bug confirmed: This binary fails with segmentation fault on my RPi2 as well: https://dl.gitea.io/gitea/1.9.6/gitea-1.9.6-linux-arm-6
Same with: https://dl.gitea.io/gitea/1.10.0/gitea-1.10.0-linux-arm-6
I tested the newest v1.10.1 as well and all binaries down to v1.9.0, all the same.

Very strange as I'm pretty sure that worked before... Probably some recent firmware/kernel upgrade broke things?

Even stranger, as well the last ARMv7 build (https://dl.gitea.io/gitea/1.7.6/gitea-1.7.6-linux-arm-7) fails... I skipped Git (and MariaDB) install, retrying with, although that should not cause a SEGV.

Okay same thing, I also tried within systemd-nspawn container, same result: All gitea fail with SEGV, even those which definitely worked before. So I'm pretty sure that it has something to do with some recent firmware update... I'm not keen to downgrade my production RPi to verify....

This seems to be the most fitting issue reported on Gitea repo: https://github.com/go-gitea/gitea/issues/8909
Didn't get much interest, interestingly 🤔.

We could try to compile own binaries, however I don't have the time to redo this after every Gitea release currently.

MichaIng picture MichaIng on 9 Dec 2019

Okay indeed seems to be an RPi kernel bug, which has been resolved upstream but has not yet been released: https://github.com/raspberrypi/linux/issues/3271#issuecomment-541227379

Note that rpi-update is not installed by default on DietPi, G_AGI rpi-update will do, however as a general recommendation I would wait for the official package release, as long as one can wait.

MichaIng picture MichaIng on 9 Dec 2019

New firmware packages have been released, tested it and works fine now. I mark this as closed.

Solution:

apt update
apt upgrade
systemctl restart gitea
MichaIng picture MichaIng on 23 Jan 2020

Running DietPi on an x86_64, after installing gitea, /mnt/dietpi_userdata/gitea/ was still owned by root. After a bit of puzzling (well before I saw this issue), a chown -R dietpi:dietpi /mnt/dietpi_userdata/gitea/ got it all working. This is with prep-script on Debian buster, kernel 4.19.0, and latest DietPi v6.32.2 release.

jcw picture jcw on 4 Oct 2020

Hi,

was this a fresh installations of Gitea? Because permission should have been changed on installation
https://github.com/MichaIng/DietPi/blob/208ab64c88ce168d2b3af4205544ea66edeacaf4/dietpi/dietpi-software#L12052

I did a quick test installation on my VM and permissions got adjusted as expected

root@DietPiVM1:~# ls -la /mnt/dietpi_userdata | grep gitea
drwxr-xr-x 6 dietpi dietpi 4096 Oct  4 01:08 gitea
root@DietPiVM1:~#
Joulinar picture Joulinar on 4 Oct 2020
👍1

Strange, that step is included in the installer, I was just verifying and the directory is owned as expected by dietpi:dietpi 🤔: https://github.com/MichaIng/DietPi/blob/master/dietpi/dietpi-software#L12052

.... lol while I was writing, thanks @Joulinar 😄.

MichaIng picture MichaIng on 4 Oct 2020

2nd time today 🤣

Joulinar picture Joulinar on 4 Oct 2020

Odd. This on a fresh DietPi install from yesterday, and a fresh gitea install today. Only other install I did before that was Nextcloud, which went fine (incl lighttpd & mariadb). Running on a 2009 Mac Mini, which I'm setting up as server, but that should not be relevant, as the Debian 10.6 installer proceeded without any issues.

Anyway, it works. Water under the bridge, I don't think there's a way to get to the bottom of this without doing it all over again.

jcw picture jcw on 4 Oct 2020

Just did a fresh gitea install on a fresh rpi3 (along with nextcloud and nginx) - same issue. Solved with chown -R dietpi:dietpi /mnt/dietpi_userdata/gitea/ + reboot, then gitea shows up on port 3000. It's not tied into nginx out of the box, but that's no big deal, and well-documented here.

jcw picture jcw on 11 Oct 2020

Here's an example setup which brings gitea to http://192.168.188.92/git/ in my case:

# cat /etc/nginx/sites-dietpi/dietpi-gitea.conf
    location /git/ { # Note: Trailing slash
        proxy_pass http://localhost:3000/; # Note: Trailing slash
    }

This location also needs to be specified on first connect to gitea, where it asks for the URL to use:

# grep ROOT_URL /mnt/dietpi_userdata/gitea/custom/conf/app.ini
ROOT_URL         = http://192.168.188.92/git/
jcw picture jcw on 11 Oct 2020

Well but setting up a reverse proxy has nothing to do with the initial issue. I will test setting up Gitea and missing permission later on once I'm back home.

Joulinar picture Joulinar on 11 Oct 2020

My apologies, I should have created a separate issue for this.

jcw picture jcw on 11 Oct 2020

I verified it again, using same setup as you. RPi3B+, installing Nginx, Nextcloud as well as Gitea

That's how it looks like during installation

root@DietPi3:/mnt/dietpi_userdata# ls -la
total 44
drwxrwxr-x 11 dietpi   dietpi   4096 Oct 11 19:20 .
drwxr-xr-x  6 root     root     4096 Oct  8 12:58 ..
drwxrwxr-x  2 dietpi   dietpi   4096 Sep 22 13:54 Music
drwxrwxr-x  2 dietpi   dietpi   4096 Sep 22 13:54 Pictures
drwxrwxr-x  2 dietpi   dietpi   4096 Sep 22 13:54 Video
drwxrwxr-x  2 dietpi   dietpi   4096 Sep 22 13:54 downloads
drwxr-xr-x  3 root     root     4096 Oct 11 19:20 gitea
drwxr-xr-x  5 mysql    mysql    4096 Oct 11 19:20 mysql
drwxr-xr-x  2 www-data www-data 4096 Oct 11 19:20 nextcloud_data
drwx------  3 dietpi   dietpi   4096 Oct  8 21:58 syncthing
drwxr-xr-x  3 dietpi   dietpi   4096 Oct  8 11:45 syncthing_data
root@DietPi3:/mnt/dietpi_userdata#

But as soon as configurations steps completed

[ SUB1 ] DietPi-Software > Configuring Gitea: Git with a cup of tea
[ INFO ] DietPi-Create_MySQL_DB | Creating MariaDB database gitea for user gitea
[  OK  ] Creating MariaDB database gitea for user gitea | Completed

permission changed as expected

root@DietPi3:/mnt/dietpi_userdata# ls -la
total 44
drwxrwxr-x 11 dietpi   dietpi   4096 Oct 11 19:20 .
drwxr-xr-x  6 root     root     4096 Oct  8 12:58 ..
drwxrwxr-x  2 dietpi   dietpi   4096 Sep 22 13:54 Music
drwxrwxr-x  2 dietpi   dietpi   4096 Sep 22 13:54 Pictures
drwxrwxr-x  2 dietpi   dietpi   4096 Sep 22 13:54 Video
drwxrwxr-x  2 dietpi   dietpi   4096 Sep 22 13:54 downloads
drwxr-xr-x  3 dietpi   dietpi   4096 Oct 11 19:20 gitea
drwxr-xr-x  6 mysql    mysql    4096 Oct 11 19:24 mysql
drwxrwx---  4 www-data www-data 4096 Oct 11 19:24 nextcloud_data
drwx------  3 dietpi   dietpi   4096 Oct  8 21:58 syncthing
drwxr-xr-x  3 dietpi   dietpi   4096 Oct  8 11:45 syncthing_data
root@DietPi3:/mnt/dietpi_userdata#

I'm still not able to replicate your behaviour.

Joulinar picture Joulinar on 11 Oct 2020

Curiouser and curiouser. Thanks for checking. I'll redo my test later. I checked well after the gitea install was over. Puzzling!

jcw picture jcw on 11 Oct 2020
Was this page helpful?
0 / 5 - 0 ratings

Related issues

bhaveshgohel picture bhaveshgohel  ·  3Comments
Fourdee picture Fourdee  ·  3Comments
pfeerick picture pfeerick  ·  3Comments
MichaIng picture MichaIng  ·  3Comments
mok-liee picture mok-liee  ·  3Comments