[Solved] L'API YunoHost ne répond pas - "502" Bad Gateway

Support
,
1

Heu… Je ne sais pas que faire
Quand je me connecte à l’admin, j’ai comme message d’erreur

L’API YunoHost ne répond pas

Vraiment désolé de cela.

Vous devez chercher de l’aide sur le forum ou le chat pour corriger la situation, ou signaler le bug sur le bugtracker.
Les informations suivantes peuvent être utiles à la personne qui vous aide :

Erreur: "502" Bad Gateway

Action: "GET" /yunohost/api/installed?locale=fr

Message d’erreur :

L’API YunoHost ne répond pas. Peut-être que ‘yunohost-api’ est en panne ou a été redémarré
?

J’ai fait (tel quel)

"GET" /yunohost/api/installed?locale=fr

Mais c’est sans effet. J’ai aussi fait

yunohost service restart yunohost-api

Egalement sans effet.
Que dois-je faire?
D’avance merci

2

Du coup regardons systemctl status yunohost-api et journalctl -u yunohost-api -n 40 --no-hostname --no-pager

3

Merci @Aleks , cela donne

systemctl status yunohost-api
● yunohost-api.service - YunoHost API Server
     Loaded: loaded (/etc/systemd/system/yunohost-api.service; enabled; vendor >
     Active: activating (auto-restart) (Result: signal) since Fri 2023-05-05 07>
    Process: 209020 ExecStart=/usr/bin/yunohost-api (code=killed, signal=SEGV)
   Main PID: 209020 (code=killed, signal=SEGV)
        CPU: 168ms
lines 1-6/6 (END)

ET

sudo journalctl -u yunohost-api -n 40 --no-hostname --no-pager
[sudo] password for admin: 
-- Journal begins at Wed 2023-03-22 01:26:08 CET, ends at Fri 2023-05-05 07:45:48 CEST. --
May 05 07:45:10 systemd[1]: yunohost-api.service: Scheduled restart job, restart counter is at 7110.
May 05 07:45:10 systemd[1]: Stopped YunoHost API Server.
May 05 07:45:10 systemd[1]: Started YunoHost API Server.
May 05 07:45:10 systemd[1]: yunohost-api.service: Main process exited, code=killed, status=11/SEGV
May 05 07:45:10 systemd[1]: yunohost-api.service: Failed with result 'signal'.
May 05 07:45:15 systemd[1]: yunohost-api.service: Scheduled restart job, restart counter is at 7111.
May 05 07:45:15 systemd[1]: Stopped YunoHost API Server.
May 05 07:45:15 systemd[1]: Started YunoHost API Server.
May 05 07:45:16 systemd[1]: yunohost-api.service: Main process exited, code=killed, status=11/SEGV
May 05 07:45:16 systemd[1]: yunohost-api.service: Failed with result 'signal'.
May 05 07:45:21 systemd[1]: yunohost-api.service: Scheduled restart job, restart counter is at 7112.
May 05 07:45:21 systemd[1]: Stopped YunoHost API Server.
May 05 07:45:21 systemd[1]: Started YunoHost API Server.
May 05 07:45:21 systemd[1]: yunohost-api.service: Main process exited, code=killed, status=11/SEGV
May 05 07:45:21 systemd[1]: yunohost-api.service: Failed with result 'signal'.
May 05 07:45:26 systemd[1]: yunohost-api.service: Scheduled restart job, restart counter is at 7113.
May 05 07:45:26 systemd[1]: Stopped YunoHost API Server.
May 05 07:45:26 systemd[1]: Started YunoHost API Server.
May 05 07:45:26 systemd[1]: yunohost-api.service: Main process exited, code=killed, status=11/SEGV
May 05 07:45:26 systemd[1]: yunohost-api.service: Failed with result 'signal'.
May 05 07:45:31 systemd[1]: yunohost-api.service: Scheduled restart job, restart counter is at 7114.
May 05 07:45:31 systemd[1]: Stopped YunoHost API Server.
May 05 07:45:31 systemd[1]: Started YunoHost API Server.
May 05 07:45:31 systemd[1]: yunohost-api.service: Main process exited, code=killed, status=11/SEGV
May 05 07:45:31 systemd[1]: yunohost-api.service: Failed with result 'signal'.
May 05 07:45:36 systemd[1]: yunohost-api.service: Scheduled restart job, restart counter is at 7115.
May 05 07:45:36 systemd[1]: Stopped YunoHost API Server.
May 05 07:45:36 systemd[1]: Started YunoHost API Server.
May 05 07:45:37 systemd[1]: yunohost-api.service: Main process exited, code=killed, status=11/SEGV
May 05 07:45:37 systemd[1]: yunohost-api.service: Failed with result 'signal'.
May 05 07:45:42 systemd[1]: yunohost-api.service: Scheduled restart job, restart counter is at 7116.
May 05 07:45:42 systemd[1]: Stopped YunoHost API Server.
May 05 07:45:42 systemd[1]: Started YunoHost API Server.
May 05 07:45:42 systemd[1]: yunohost-api.service: Main process exited, code=killed, status=11/SEGV
May 05 07:45:42 systemd[1]: yunohost-api.service: Failed with result 'signal'.
May 05 07:45:47 systemd[1]: yunohost-api.service: Scheduled restart job, restart counter is at 7117.
May 05 07:45:47 systemd[1]: Stopped YunoHost API Server.
May 05 07:45:47 systemd[1]: Started YunoHost API Server.
May 05 07:45:47 systemd[1]: yunohost-api.service: Main process exited, code=killed, status=11/SEGV
May 05 07:45:47 systemd[1]: yunohost-api.service: Failed with result 'signal'.
admin@wikizen:~$
4

Hmoké alors le process se fait sans cesse tuer à cause d’une segfault …

Est-ce que tu saurais expliquer si ça marchait avant et si tu as fait un truc qui fait que ça marche plus …?

On peut aussi tenter de regarder ce que yunohost-api --debug raconte

5

Non, je n’ai rien changé précédement. Je n’ai juste pas tenu compte des avertissements m’indiquant que emailpoubelle n’était plus suivi
yunohost-api --debug
donne

yunohost-api --debug
Traceback (most recent call last):
  File "/usr/lib/python3.9/logging/config.py", line 564, in configure
    handler = self.configure_handler(handlers[name])
  File "/usr/lib/python3.9/logging/config.py", line 745, in configure_handler
    result = factory(**kwargs)
  File "/usr/lib/python3.9/logging/handlers.py", line 445, in __init__
    logging.FileHandler.__init__(self, filename, mode=mode,
  File "/usr/lib/python3.9/logging/__init__.py", line 1142, in __init__
    StreamHandler.__init__(self, self._open())
  File "/usr/lib/python3.9/logging/__init__.py", line 1171, in _open
    return open(self.baseFilename, self.mode, encoding=self.encoding,
PermissionError: [Errno 13] Permission denied: '/var/log/yunohost/yunohost-api.log'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/bin/yunohost-api", line 52, in <module>
    yunohost.api(debug=opts.debug, host=opts.host, port=opts.port)
  File "/usr/lib/python3/dist-packages/yunohost/__init__.py", line 53, in api
    init_logging(interface="api", debug=debug)
  File "/usr/lib/python3/dist-packages/yunohost/__init__.py", line 183, in init_logging
    configure_logging(logging_configuration)
  File "/usr/lib/python3/dist-packages/moulinette/utils/log.py", line 67, in configure_logging
    dictConfig(logging_config)
  File "/usr/lib/python3.9/logging/config.py", line 809, in dictConfig
    dictConfigClass(config).configure()
  File "/usr/lib/python3.9/logging/config.py", line 571, in configure
    raise ValueError('Unable to configure handler '
ValueError: Unable to configure handler 'file'
6

Il faudrait lancer yunohost-api --debug, mais en tant que root

7

Ca n’a pas l’air de marcher

udo yunohost-api --debug
[sudo] password for admin: 
117  DEBUG initializing base actions map parser for api
118  DEBUG loading actions map
119  DEBUG building parser...
155  DEBUG building parser took 0.035s
Segmentation fault

Et par ailleurs, je reçois des mails d’erreur qui indiquent

/bin/bash: line 1: 427364 Segmentation fault      yunohost diagnosis run --email > /dev/null 2> /dev/null
Running the automatic diagnosis failed miserably
8

Une erreur de segmentation de l’api, je n’ai pas encore vu alors que j’ai déjà installé pas mal de Yunohost depuis la version 2.x.

Est-ce que la ram de ta machine est encore en bon état ? C’est quoi d’ailleurs comme machine ? Un vps, un pc, une brique internet ?

9

C’est un VPS. je ne sais pas comment le vérifier

10

Bon… sur une machine virtuelle, il me semble que c’est peu probable que ce soit la ram.

Je suppose que tu as déjà essayer de redémarrer ta vm ?

1 Like
11

Désolé et merci de cette manière gentille de présenter les choses “je suppose que…”. Je n’avais pas osé faire cela. Et de fait après ce redémarrage, c’est réglé.
Encore merci @Aleks

1 Like
12

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