-rw-r----- 1 root root 13884 May 4 2020 fail2ban.log.1.gz-2020050713.backup
-rw-r----- 1 root root 1468974 Nov 14 2021 mail.info.1.gz-2021111400.backup
-rw-r----- 1 root root 1014391 Jun 26 00:00 mail.info.1.gz-2022062600.backup
dans /home mais pour tout ce que je fais, j’ai ce problème No space left on device même pour installer ncdu :
…et toutes les 10mn, je reçois un message d’injures de la part d’un petit diable Cron : YunoHost DynDNS update; sleep $((RANDOM%60)); ! ping -q -W5 -c1 ip.yunohost.org >/dev/null 2>&1 || test -e /var/run/moulinette_yunohost.lock || yunohost dyndns update >> /dev/null :
Je suis parvenu à trouver ce qui encombrait /var/log.
J’ai un sous-répertoire /avr/log/journal avec un nom composé de chiffres et de lettres illisibles, dans lequel j’ai des fichiers dépendant créés par systemd.
Le plus gros : -rw-r----- 1 root root 16777216 Aug 12 11:07 system@119965c3ab0b4454ac16003480225294-0000000000000001-0005e60942738168.journal
J’en ai 6 le même jour à la même heure :
-rw-r----- 1 root root 634880 Aug 11 15:33 system@3c6e9fba1ce549f9835ac7b83f6353f0-000000000000020a-0005e5ed3e718354.journal
Il a donc été généré quand j’ai fait le backup ou quand j’ai fait la migration.
J’ai viré les 6 journeaux du 11/08 le les 2 du 12.
Tout semble maintenant fonctionnel. J’accède aux apllis par le web, sauf que le hotspot bien qu’en activité sans erreurs au diagnostic, n’apparaît pas dans les réseaux disponibles.
@Sty_X : comme expliqué dans le disclaimer (et un peu dans la release note), ffsync n’est plus supporté et bloque la migration. Il faut désinstaller l’app.
Le soucis ne peut pas être résolu, ffsync n’est plus du tout maintenu (ce n’est pas de notre ressort, c’est Mozilla qui a abandonné le projet) et est bloqué en Python 2 qui est déprécié depuis un gros moment maintenant et n’est plus du tout disponible sur Bullseye …
Suite à la désinstallation de ffsync, la migration bloque toujours. Il semblerait qu’il reste des éléments liés à ffsync, mais je ne sais pas comment les “nettoyer” manuellement et surtout proprement…
The issue with migrating postgresql 11 to 13 is not solved after the last yunohost update. This is as expected. I am referring to the error connected to locales, eg. initdb: could not find suitable text search configuration for locale "nn_NO.UTF-8". I am of course willing to try suitable commands and share log output to get the issue solved, and I am grateful for any suggestions. Do tell me if I should create a bug report to tidy up the forum thread a little
Wasn’t aware of this but I would highly NOT recommend it as it justs uses some custom tools to install Python 2 on the machine and this sounds pretty dangerous. Technically that may work, sure. But that’s a very bad idea.
But Python 2 has reached end of life for more than 2 years now (and it’s been deprecated since at least 5 years) and won’t receive security fixes.
So bottom line : don’t use unmaintained software that is built on top of unmaintained technology - period. Yes it’s a shame that Firefox abandoned the project and we could have long discussions about the sustainability / ethic / governance / usability of FOSS but ¯\_(ツ)_/¯
root@ynh:~# apt-mark showhold
root@ynh:~# apt-mark unhold gcc-8-base
gcc-8-base was already not hold.
root@ynh:~# apt upgrade gcc-8-base
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libgcc1 : Depends: gcc-8-base (= 8.3.0-6+rpi1) but 8.4.0-7+rpi1 is to be installed
E: Broken packages
most important apps in my server work fine (I’ve just to repair Calibreweb) so so far it is not a big issue.
In fact I found that just had to --skip this migration after running the rest of the migrations, and a couple of manual tweaks (two missing packages related to php7.4, a locale issue in the migration from postgresql 9 to 11), things are working for me (all apps and web admin are back up – except for ihatemoney but I should be able to fix it later).
I am very curious to know what you did to fix the postgresql migration, because that’s the current showstopper for me. Would you mind sharing what you did to overcome or bypass the problem? Many thanks!
So in the logs I found out that there was an issue with something related to the locale. For some reason it expected en_GB.UTF-8 while I only had en_US.UTF-8 (and fr_FR.UTF-8 and a few others). Then I ran sudo dpkg-reconfigure locales, ticked en_GB.UTF-8, and then sudo yunohost tools migrations run. And it worked for me.
