My YunoHost server
Hardware: Old laptop
YunoHost version: 11.0.9.14
I have access to my server : Through SSH | through the webadmin | direct access via keyboard / screen
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : After running the migration from Buster to Bullseye I had to do some tweaking with nginx (I couldn’t access through webadmin) and “disabled” temporarily the yunohost diagnostic to update yunohost-admin (after the migration, yunohost-admin was still at version 4.x.x and the automatic diagnostic couldn’t finish, probably because of the problem described below).
Description of my issue
Some services don’t start:
sudo systemctl --failed
fail2ban.service loaded failed failed Fail2Ban Service
funkwhale-beat.service loaded failed failed funkwhale celery beat process
funkwhale-worker.service loaded failed failed funkwhale celery worker
unattended-upgrades.service loaded failed failed Unattended Upgrades Shutdown
yunomdns.service loaded failed failed YunoHost mDNS service
All of them terminates with signal=ILL
sudo systemctl status fail2ban.service as an example:
sudo systemctl status fail2ban.service
fail2ban.service - Fail2Ban Service
Loaded: loaded (/lib/systemd/system/fail2ban.service; enabled; vendor preset: enabled)
Active: failed (Result: signal) since Fri 2022-09-16 15:28:03 CEST; 36min ago
Docs: man:fail2ban(1)
Process: 1257 ExecStartPre=/bin/mkdir -p /run/fail2ban (code=exited, status=0/SUCCESS)
Process: 1258 ExecStart=/usr/bin/fail2ban-server -xf start (code=killed, signal=ILL)
Main PID: 1258 (code=killed, signal=ILL)systemd[1]: fail2ban.service: Main process exited, code=killed, status=4/ILL
systemd[1]: fail2ban.service: Failed with result ‘signal’.
systemd[1]: fail2ban.service: Scheduled restart job, restart counter is at 6.
systemd[1]: Stopped Fail2Ban Service.
systemd[1]: fail2ban.service: Start request repeated too quickly.
systemd[1]: fail2ban.service: Failed with result ‘signal’.
systemd[1]: Failed to start Fail2Ban Service.
systemd[1]: fail2ban.service: Unit cannot be reloaded because it is inactive.
After running dmesg I found some errors about libffi:
traps: fail2ban-server[683] trap invalid opcode ip:7f335149263c sp:7ffd61d14758 error:0 in libffi.so.7.1.0[7f3351492000+6000]
traps: yunomdns[676] trap invalid opcode ip:7fa8f3fb063c sp:7ffed2540b88 error:0 in libffi.so.7.1.0[7fa8f3fb0000+6000]
traps: python3[2123] trap invalid opcode ip:7fcd470fa63c sp:7ffcc7f18678 error:0 in libffi.so.7.1.0[7fcd470fa000+6000]
traps: celery[1349] trap invalid opcode ip:7f0e7948863c sp:7ffe65348f58 error:0 in libffi.so.7.1.0[7f0e79488000+6000]
traps: yunohost[4887] trap invalid opcode ip:7f433efa163c sp:7fff26235f38 error:0 in libffi.so.7.1.0[7f433efa1000+6000]
traps: unattended-upgr[7601] trap invalid opcode ip:7f8fc2e8763c sp:7ffcfcd2bf08 error:0 in libffi.so.7.1.0[7f8fc2e87000+6000]
Also if I try to run yunohost diagnostic from the webadmin page, yunohost-api crashes with the same error:
traps: yunohost-api[581] trap invalid opcode ip:7f171a81e63c sp:7ffec0367a48 error:0 in libffi.so.7.1.0[7f171a81e000+6000]