[Solved] Empty diagnosis, missing apps

My YunoHost server

Hardware: Raspberry Pi 4 at home
YunoHost version: 11.2.10
I have access to my server : Through SSH | through the webadmin
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no

Description of my issue

Most of my apps are suddenly unresponsive: the nextcloud client tells me that I’ve been logged out, logging in throught the portal I get either nothing or I’m asked to log in through the portal again.
For example:

  • miniflux: store: unable to create app session: dial tcp [::1]:5432: connect: connection refused
  • wallabag: some binary I guess: ����������������������������������������
  • nextcloud: nothing happens, I’m back to the portal.

As an admin, if I run a diagnosis, I end up with either nothing (most of the time), or just one line telling me all is well, or a long list with everything green but postgres.

If I got to ‘Applications’, the interface only shows ’ There are no installed apps.’
I’ve ssh’d in and the apps are still there.

I noticed that:

root@ynh:~# df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/root        29G   28G  236M 100% /
devtmpfs        1.7G     0  1.7G   0% /dev
tmpfs           1.9G   56K  1.9G   1% /dev/shm
tmpfs           759M 1012K  758M   1% /run
tmpfs           5.0M  4.0K  5.0M   1% /run/lock 
/dev/mmcblk0p1  255M   31M  225M  13% /boot
/dev/sda1       458G  275G  160G  64% /mnt/seagate500
tmpfs           380M     0  380M   0% /run/user/0 

/dev/root is full, could it be that?

Thank you!

You don’t have swap?
What gives free -h? Probably out of ram. But you have to free up root partition

This is what I get:

root@ynh:~# free -h
total        used        free      shared  buff/cache   available
Mem:           3.7Gi       791Mi       339Mi       178Mi       2.6Gi       2.7Gi
Swap:           99Mi        88Mi        11Mi

Not sure how to interpret this, to be honest.

sudo yunohost tools basic-space-cleanup te permet de faire un peu de ménage dans le disque. Un reboot est parfois nécessaire pour les fichiers système

2 Likes

ok merci! La commande ne m’a pas permis de récupérer de l’espace mais un reboot l’a fait:

root@ynh:~# df -h   
Filesystem      Size  Used Avail Use% Mounted on 
/dev/root        29G   16G   13G  56% /     
devtmpfs        1.7G     0  1.7G   0% /dev    
tmpfs           1.9G   16K  1.9G   1% /dev/shm
tmpfs           759M  1.2M  758M   1% /run  
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
/dev/mmcblk0p1  255M   31M  225M  13% /boot
/dev/sda1       458G  275G  160G  64% /mnt/seagate500
tmpfs           380M     0  380M   0% /run/user/0

Tout est rentré dans l’ordre!

2 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.