Pi-Hole Installation fails at PiHole-FTL

My YunoHost server

Hardware: Raspberry Pi 3 B+
YunoHost version: 11.1.15
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
If your request is related to an app, specify its name and version: Pi-Hole 5.14.2~ynh1

Description of my issue

Hi folks :wave:
My installation of Pi-Hole fails.
For later use of Yunohost on my RPi4, I wanted to try some apps on my old RPi3 B+ first. Among them also Pi-Hole.

I tried to install Pi-Hole via SSH and found that when installing PiHole-FTL, it fails at 38%. I noticed that the RAM is almost completely used up at this step (38%), but the CPU is not. The Pi can then hardly be operated via SSH. It was not until I aborted the installation that the Pi was usable again.

Hope someone can help me further. Thanks.

2023-04-02 22:50:10,871: DEBUG - [ 36%] Building C object src/database/CMakeFiles/database.dir/sqlite3-ext.c.o
2023-04-02 22:50:11,568: DEBUG - [ 37%] Building C object src/database/CMakeFiles/database.dir/aliasclients.c.o
2023-04-02 22:50:12,667: DEBUG - [ 37%] Built target database
2023-04-02 22:50:12,988: DEBUG - Scanning dependencies of target sqlite3
2023-04-02 22:50:13,051: DEBUG - [ 37%] Building C object src/database/CMakeFiles/sqlite3.dir/shell.c.o
2023-04-02 22:50:13,886: DEBUG - /tmp/tmp.vGmw8xeufZ/src/database/shell.c: In function ‘recoverTransferSettings’:
2023-04-02 22:50:13,893: DEBUG - /tmp/tmp.vGmw8xeufZ/src/database/shell.c:13530:17: warning: comparison of integer expressions of different signedness: ‘int’ and ‘long unsigned int’ [-Wsign-compare]
2023-04-02 22:50:13,894: DEBUG - 13530 |     for(ii=0; ii<sizeof(aPragma)/sizeof(aPragma[0]); ii++){
2023-04-02 22:50:13,895: DEBUG -       |                 ^
2023-04-02 22:50:13,896: DEBUG - /tmp/tmp.vGmw8xeufZ/src/database/shell.c: In function ‘recoverOpenOutput’:
2023-04-02 22:50:13,902: DEBUG - /tmp/tmp.vGmw8xeufZ/src/database/shell.c:13608:40: warning: comparison of integer expressions of different signedness: ‘int’ and ‘long unsigned int’ [-Wsign-compare]
2023-04-02 22:50:13,903: DEBUG - 13608 |   for(ii=0; p->errCode==SQLITE_OK && ii<sizeof(aFunc)/sizeof(aFunc[0]); ii++){
2023-04-02 22:50:13,904: DEBUG -       |                                        ^
2023-04-02 22:50:14,015: DEBUG - /tmp/tmp.vGmw8xeufZ/src/database/shell.c: In function ‘recoverVfsRead’:
2023-04-02 22:50:14,025: DEBUG - /tmp/tmp.vGmw8xeufZ/src/database/shell.c:15002:21: warning: comparison of integer expressions of different signedness: ‘int’ and ‘long unsigned int’ [-Wsign-compare]
2023-04-02 22:50:14,026: DEBUG - 15002 |         for(ii=0; ii<sizeof(aPreserve)/sizeof(aPreserve[0]); ii++){
2023-04-02 22:50:14,026: DEBUG -       |                     ^
2023-04-02 22:51:04,250: DEBUG - [ 38%] Building C object src/database/CMakeFiles/sqlite3.dir/sqlite3.c.o

Here is the full log: https://paste.yunohost.org/raw/usudonubem


:fr: Modèle de message (français)

Mon serveur YunoHost

Matériel: Raspberry Pi 3 B+
Version de YunoHost: 11.1.15
J’ai accès à mon serveur : En SSH | Par la webadmin
Êtes-vous dans un contexte particulier ou avez-vous effectué des modificiations particulières sur votre instance ? : non
Si votre requête est liée à une applicatio, précisez son nom et sa version: Pi-Hole 5.14.2~ynh1

Description du problème

Bonjour à tous :wave:
L’installation de Pi-Hole échoue.
Pour une utilisation ultérieure de Yunohost sur mon RPi4, je voulais d’abord essayer quelques applications sur mon vieux RPi3 B+. Parmi elles, Pi-Hole.

J’ai essayé d’installer Pi-Hole via SSH et j’ai constaté que l’installation de PiHole-FTL n’avançait pas à 38%. J’ai remarqué qu’à cette étape (38%), la mémoire vive est presque entièrement consommée, mais pas le CPU. Il est alors presque impossible d’utiliser le Pi via SSH. Ce n’est qu’après avoir interrompu l’installation que le Pi est à nouveau utilisable.

J’espère que quelqu’un pourra m’aider. Merci.

2023-04-02 22:50:10,871: DEBUG - [ 36%] Building C object src/database/CMakeFiles/database.dir/sqlite3-ext.c.o
2023-04-02 22:50:11,568: DEBUG - [ 37%] Building C object src/database/CMakeFiles/database.dir/aliasclients.c.o
2023-04-02 22:50:12,667: DEBUG - [ 37%] Built target database
2023-04-02 22:50:12,988: DEBUG - Scanning dependencies of target sqlite3
2023-04-02 22:50:13,051: DEBUG - [ 37%] Building C object src/database/CMakeFiles/sqlite3.dir/shell.c.o
2023-04-02 22:50:13,886: DEBUG - /tmp/tmp.vGmw8xeufZ/src/database/shell.c: In function ‘recoverTransferSettings’:
2023-04-02 22:50:13,893: DEBUG - /tmp/tmp.vGmw8xeufZ/src/database/shell.c:13530:17: warning: comparison of integer expressions of different signedness: ‘int’ and ‘long unsigned int’ [-Wsign-compare]
2023-04-02 22:50:13,894: DEBUG - 13530 |     for(ii=0; ii<sizeof(aPragma)/sizeof(aPragma[0]); ii++){
2023-04-02 22:50:13,895: DEBUG -       |                 ^
2023-04-02 22:50:13,896: DEBUG - /tmp/tmp.vGmw8xeufZ/src/database/shell.c: In function ‘recoverOpenOutput’:
2023-04-02 22:50:13,902: DEBUG - /tmp/tmp.vGmw8xeufZ/src/database/shell.c:13608:40: warning: comparison of integer expressions of different signedness: ‘int’ and ‘long unsigned int’ [-Wsign-compare]
2023-04-02 22:50:13,903: DEBUG - 13608 |   for(ii=0; p->errCode==SQLITE_OK && ii<sizeof(aFunc)/sizeof(aFunc[0]); ii++){
2023-04-02 22:50:13,904: DEBUG -       |                                        ^
2023-04-02 22:50:14,015: DEBUG - /tmp/tmp.vGmw8xeufZ/src/database/shell.c: In function ‘recoverVfsRead’:
2023-04-02 22:50:14,025: DEBUG - /tmp/tmp.vGmw8xeufZ/src/database/shell.c:15002:21: warning: comparison of integer expressions of different signedness: ‘int’ and ‘long unsigned int’ [-Wsign-compare]
2023-04-02 22:50:14,026: DEBUG - 15002 |         for(ii=0; ii<sizeof(aPreserve)/sizeof(aPreserve[0]); ii++){
2023-04-02 22:50:14,026: DEBUG -       |                     ^
2023-04-02 22:51:04,250: DEBUG - [ 38%] Building C object src/database/CMakeFiles/sqlite3.dir/sqlite3.c.o

Voici le journal complet : https://paste.yunohost.org/raw/usudonubem

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