Snap on Raspberry Pi (Raspbian), 500 error page, related to `libarmmem-${PLATFORM}.so` and `/etc/ld.so.preload`

[Flagelmann]

Gitea Version

All snap Gitea on Raspbian

Description

After installation, Gitea seems working, however, when git clone/push or view from web, Gitea reports 500 error.

The error in logs is:

ERROR: ld.so: object '/usr/lib/arm-linux-gnueabihf/libarmmem-${PLATFORM}.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored

---

There is a workaround in comments.

[techknowlogick]

Hi, there is a form that requests data that you seemed to have bypassed. We need baseline information about your installation (version, and much more). As well we need logs, many things can cause 500 errors, but the logs will narrow things down.

[Flagelmann]

Hello techknowlogick,

Updated with some info in the original post.

The default directory set for logs (snap version) /var/snap/gitea/common/log is totally empty.

No logs are generated at all, it seems, even if I keep pushing the repo link as a maniac.

Kind regards

[zeripath]

You need to figure out where your logs are going.

To do that you need to tell us how you are starting Gitea. That is:

1. Are you starting gitea on the command line? - then setting the logs to console would be easiest
2. Are you using docker? - if you set the logs to console then docker logs $containerid would show the console logs - otherwise they will be in files on your docker
3. Are you using systemd? - Systemd will send console output to its journal - journalctl will help there.

You need to have read https://docs.gitea.io/en-us/logging-configuration/#debugging-problems

You need to find out where your app.ini is and give us a suitably sanitised copy of that too.

[Flagelmann]

Hello,

I've used Canonical Snap option: https://docs.gitea.io/en-us/install-from-package/#canonical-snap

So, snapd is actually running gitea (gitea.web), as a service.

MySQL has been installed, obviously, outside the snap package (as it is not included in it).

By default, the gitea snap package configure the log directory to /var/snap/gitea/common/log. But it is void.

I've tried searching a bit on the system, but it seems it is not writing anywhere on the system.....

Any suggestion (a part systemd logs)?

[wxiaoguang]

1. can you check where does snap store or display the stdout log? I am not familiar with snap system.
   • it's said that snap logs can be viewd by journalctl
2. you may set log configs in app.ini of Gitea to make the log to be saved into a file.
   • https://docs.gitea.io/en-us/config-cheat-sheet/#log-log

   • gitea/custom/conf/app.example.ini

     Line 434 in 54243ee

     [log]

[Flagelmann]

Ok, done.

It seems the official snap package is not fully compatible with Raspberry Pi 3+....(or it has a bug).....

ERROR: ld.so: object '/usr/lib/arm-linux-gnueabihf/libarmmem-${PLATFORM}.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored

The ${PLATFORM} variable seems not correclty populated......

NOTE: this message is displayed everytime when creating a void repo or migrating/cloning a public Github repo (I presume it will not work also with other similar services).

ADDITIONAL NOTE: I will try to modify the dynamic linker (ld.so.preload) to use directly the proper .so and I will update.

[wxiaoguang]

Well, it's not the first time to see this bug.

• Error 500 on opening a repository #17369

Exactly the same .....

I do not have a Raspberry Pi. To continue investigate this problem, either some of the maintainers have similar devices, or some users with system skills can help to debug.

"The ${PLATFORM} variable seems not correctly populated......" Good catch, waiting for your test results.

[Flagelmann]

Ok, fixed.

It seems Gitea does not need (for the tests I have done) that libarmmem-${PLATFORM}.so module.

First I have tried using the /usr/lib/arm-linux-gnueabihf/libarmmem-v7l.so, in the /etc/ld.so.preload conf file (related to the arch of this Raspberry Pi), then restarted Gitea and no progress.

So, just as a try, I just commented that single line in /etc/ld.so.preload: now the migration/cloning/creation repo processes works as expected (and blazing fast). Checked these processes on gitea.log in tail -f mode and no errors as output during the execution.

For me, for now, this issues can be closed (and informing other users on this approach, if they want to try it).

Many thanks for the log related suggestion (I did not change console to file in the app.ini).

In any case I will monitor the situation on Gitea to see if other functions will not work.

Kind regards.

[wxiaoguang]

Do you know how to make things work correctly without these manual editing steps?

If we can find a correct way, we should improve the snap build of Gitea.

ps: please keep this issue open, until we can find a good solution.

[Flagelmann]

Well, I do not know so much yet about snap, the most simple thing that I could think is including a simple .sh script in the snap package, called to each start/restart of the gitea package, to check and "comment" that line if found in /etc/ld.so.preload file....

But that's only a simple approach that I would use....