Closed vbombaerts closed 1 year ago
Pour les erreurs de type "pas de réponse"; il semble y avoir des problème avec le proxy ajp.
21/02 [Mon Feb 21 14:24:51.599254 2022] [proxy_ajp:error] [pid 49366] (70007)The timeout specified has expired: AH01030: ajp_ilink_receive() can't receive header [Mon Feb 21 14:24:53.858415 2022] [proxy_ajp:error] [pid 58035] (70007)The timeout specified has expired: AH01030: ajp_ilink_receive() can't receive header [Mon Feb 21 14:27:32.052094 2022] [proxy_ajp:error] [pid 54208] (70007)The timeout specified has expired: AH01030: ajp_ilink_receive() can't receive header [Mon Feb 21 14:32:24.331417 2022] [proxy_ajp:error] [pid 50334] (70007)The timeout specified has expired: AH01030: ajp_ilink_receive() can't receive header [Mon Feb 21 14:36:20.749262 2022] [proxy_ajp:error] [pid 60787] (70007)The timeout specified has expired: AH01030: ...
25/02 ... [Fri Feb 25 17:23:18.096201 2022] [proxy_ajp:error] [pid 54208] (70007)The timeout specified has expired: AH01030: ajp_ilink_receive() can't receive header [Fri Feb 25 17:25:52.808285 2022] [proxy_ajp:error] [pid 57848] (70007)The timeout specified has expired: AH01030: ajp_ilink_receive() can't receive header [Fri Feb 25 17:32:57.956669 2022] [proxy_ajp:error] [pid 60787] (70007)The timeout specified has expired: AH01030: ajp_ilink_receive() can't receive header ...
Courant avril 2022, de nombreux coupures - elles seraient liés à logstash qui consomme trop de RAM pour la machine
On a la procédure de relance de l'environnement de test. Je ferme.
A priori ce serait l'apache qui plante: Cas : metawal4.test est dans les choux mais il est possible d'interagir avec le catalogue via un accès en local au tomcat; si l'on stop et relance l'apache, metawal4.test est à nouveau actif.
Récap des erreurs d'indisponibilité de Metawal en test