I just updated my Yunohost to 12.0. It seemed to work fine at first, I could access the new portal and the different services. Then I rebooted and now my system wonât boot. I donât have access to the portal, nor even access to a terminal through SSH.
Iâve connected a screen and the boot is stuck with this error:
firmware: failed to load iwlwifi-cc-a0-72.ucode (-2)
The error is repeated multiple times with seemingly other versions of iwlwifi (71, 70, 69).
I canât access a tty (Ctrl+Alt+Fx) so I have no possibility to fix anything directly. I suppose I need to chroot my system if I want to fix it, but Iâm not sure what I should do next.
(I donât even use the wifi so itâs even more upsetting)
Can it finally integrate with other directory services?? Or at least other Yunohost servers so thereâs redundancy? (directory service redundancy)
Iâve been waiting for this for so long so I could use Yunohost. I hope itâs finally here, and the are big hopes too since itâs all about auth. <3
Thanks for the reply.
I installed the firmware through chroot, it removed the error messages but didnât solve the problem. In the end I think (since I tried quite a few things) it was the UUID of the swap partition that changed during the upgrade and wasnât correctly updated in the fstab.
Anyway, itâs working now. Thanks for your help, and for the amazing work on Yunohost.
needed to install by hand php7.4-mysql to solve a connection problem to mysql, from a hosted CMS (b2evolution installed âby handâ) apt install php7.4-mysql and now itâs ok, database found
Hi,
I have an error with the prostgresql migration on one server.
The migration to yunohost 12 is complete and all the applications are working fine. But the migration of postgresql from version 13 to version 15 is failing :
Eeeh Iâm confused, you donât need to add a subdomain for domain1 or domain2
If you want every application to show up in domain3âs portal, you can enable the âShow other domainâs appâ in the webadmin > Domains > domain3 > Portal customization
2024-11-05 19:17:12,329: DEBUG - Setting up linux-headers-6.1.0-26-arm64 (6.1.112-1) ...
2024-11-05 19:17:12,333: INFO - [###################.] > 96.0% Installing linux-headers-6.1.0-26-arm64
2024-11-05 19:17:12,385: DEBUG - /etc/kernel/header_postinst.d/dkms:
2024-11-05 19:17:12,386: DEBUG - dkms: running auto installation service for kernel 6.1.0-26-arm64.
2024-11-05 19:17:12,597: DEBUG - Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file
2024-11-05 19:17:12,598: DEBUG - Signing key: /var/lib/dkms/mok.key
2024-11-05 19:17:12,598: DEBUG - Public certificate (MOK): /var/lib/dkms/mok.pub
2024-11-05 19:17:12,601: DEBUG - Certificate or key are missing, generating self signed certificate for MOK...
2024-11-05 19:17:13,464: DEBUG - Error! The /var/lib/dkms/wireguard/1.0.20210219/6.1.0-26-arm64/aarch64/dkms.conf for module wireguard includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch/config.
2024-11-05 19:17:13,464: DEBUG - This indicates that it should not be built.
2024-11-05 19:17:13,468: DEBUG - Error! One or more modules failed to install during autoinstall.
2024-11-05 19:17:13,469: DEBUG - Refer to previous errors for more information.
2024-11-05 19:17:13,474: DEBUG - dkms: autoinstall for kernel: 6.1.0-26-arm64 failed!
2024-11-05 19:17:13,474: DEBUG - run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
2024-11-05 19:17:13,477: DEBUG - Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.1.0-26-arm64.postinst line 11.
2024-11-05 19:17:13,478: DEBUG - dpkg: error processing package linux-headers-6.1.0-26-arm64 (--configure):
2024-11-05 19:17:13,478: DEBUG - installed linux-headers-6.1.0-26-arm64 package post-installation script subprocess returned error exit status 1
hmmmff that one seems tricky and related to wireguard / dkms stuff, i donât know enough about these to understand whatâs the issue exactly
Assuming youâre able to, yes, but dpkg/apt might complain that linux-headers-stuff still canât be installed and it might derp about it
Yes that might be a side-effect of being in an intermediate state, should be fixed once itâs fully upgraded, or maybe using yunohost tools regen-conf nsswitch --force
Checking for presence of required libraries fatal
Your installation references loadable libraries that are missing
from the new installation. You can add these libraries to the
new installation, or remove the functions using them from the
old installation. A list of problem libraries is in the file:
/var/lib/postgresql/15/main/pg_upgrade_output.d/20241106T102820.262/loadable_libraries.txt
uuuugh wokay, never seen anything like this but can you share the content of /var/lib/postgresql/15/main/pg_upgrade_output.d/20241106T102820.262/loadable_libraries.txt ?
Thanks a lot everyone for the great job on the upgrade and answering many questions!
I did the upgrade today and currently i have 5 issues:
My Fail2ban is down, my Yunohost-Portal-api also down, I canât update any apps (Maybe due to the portal-api component?), canât accessanything using SSO without getting the 500 or 502errors and also noticed that navigating in the menu became very slow. Maybe all these are related to the yunohost-portal-api?
As for logs:
Fail2ban (Services are loading indefinitely, so I got the error from the terminal).
journalctl:
- Nov 06 14:50:36 systemd[1]: fail2ban.service: Main process exited, code=exited, status=255/EXCEPTION
- Nov 06 14:50:36 systemd[1]: fail2ban.service: Failed with result 'exit-code'.
- Nov 06 14:50:38 systemd[1]: Started fail2ban.service - Fail2Ban Service.
- Nov 06 14:50:38 fail2ban-server[1555]: 2024-11-06 14:50:38,394 fail2ban.configreader [1555]: WARNING 'allowipv6' not defined in 'Definition'. Using default one: 'auto'
- Nov 06 14:50:38 fail2ban-server[1555]: 2024-11-06 14:50:38,432 fail2ban [1555]: ERROR Failed during configuration: Have not found any log file for recidive jail
- Nov 06 14:50:38 fail2ban-server[1555]: 2024-11-06 14:50:38,438 fail2ban [1555]: ERROR Async configuration of server failed
- Nov 06 14:50:38 systemd[1]: fail2ban.service: Main process exited, code=exited, status=255/EXCEPTION
- Nov 06 14:50:38 systemd[1]: fail2ban.service: Failed with result 'exit-code'.
Yunohost-Portal-API here. : TLDR: saying it does nothaveaccess to yunohost-portal-api.log strangely.
Hmmm so both yunohost-portal-api.log and fail2ban.log would have disappeared from /var/log/ � Did you perform anything specific regarding log files such as savagely deleting everything in /var/log/ or something ?
Hi @Aleks I plead Guilty. I had huge files in this folder and it was taking more than 300 GB, I thought I was smart but not really lol
Solved the Yunohost-portal-api error which seems to have solved many of the issues i had including sso and slowness. I had to recreate the log file and give it the right permissions.
Now, Iâd need your kind assistance to know the name of the file for fail2ban if the error shared is related to some missing log file, thanks