Reboot intempestif ou programmé?

Plugins Protocole domotique
1

bonjour,

(installation en production sur jeedom 4.2.21)

a titre de paysage je précise que je n’arrive pas à obtenir une plate-forme homebridge stable depuis l’installation d’iOS16.x (iphones et ipads iOS 16.1 et un ipad pro sert de passerelle à home). la partie des équipements que j’envoie remontent bien vers home mais les commandes passées depuis homebridge ne font rien (allumer/éteindre sans réaction depuis la page accessoires de la page web) … et bien sûr il n’y a aucun message d’erreur nulle part, même en activant le debug. mais bon, prenons les choses une par une et je pense que ce sujet est peut être lié au souci que je rencontre :

j’observe dans les logs que chaque jour à quelques minutes d’intervalle entre 9h35 et 9h45, homebridge reboote seul, les logs montrent une demande d’arrêt (Got SIGTERM) et je n’ai rien programmé as far as I know, voilà un exemple :

[04/11/2022 09:37:09] Error: send ENETUNREACH 224.0.0.251:5353
at doSend (node:dgram:705:16)
at defaultTriggerAsyncIdScope (node:internal/async_hooks:464:18)
at afterDns (node:dgram:651:5)
at processTicksAndRejections (node:internal/process/task_queues:84:21)
[04/11/2022 09:37:09] Got SIGTERM, shutting down Homebridge...
[04/11/2022 09:40:06] Loaded config.json with 0 accessories and 3 platforms.
[04/11/2022 09:40:06] Loaded 76 cached accessories from cachedAccessories.
[04/11/2022 09:40:07] ---
[04/11/2022 09:40:10] Loaded plugin: @nebz/homebridge-jeedom@v1.6.0
[04/11/2022 09:40:14] Registering platform '@nebz/homebridge-jeedom.Jeedom'
[04/11/2022 09:40:14] ---
[04/11/2022 09:40:16] Loaded plugin: homebridge-alexa@0.5.63
[04/11/2022 09:40:16] Registering platform 'homebridge-alexa.Alexa'
[04/11/2022 09:40:16] ---
[04/11/2022 09:40:17] Loaded plugin: homebridge-camera-ffmpeg@3.1.4
[04/11/2022 09:40:17] Registering platform 'homebridge-camera-ffmpeg.Camera-ffmpeg'
[04/11/2022 09:40:17] ---
[04/11/2022 09:40:17] Loaded plugin: homebridge-config-ui-x@4.50.0
[04/11/2022 09:40:17] Registering platform 'homebridge-config-ui-x.config'
[04/11/2022 09:40:17] ---
[04/11/2022 09:40:17] Loaded plugin: homebridge-gsh@2.2.0
[04/11/2022 09:40:17] Registering platform 'homebridge-gsh.google-smarthome'
[04/11/2022 09:40:17] ---
[04/11/2022 09:40:17] Loading 3 platforms...
[04/11/2022 09:40:17] [ps] Initializing Jeedom platform...
[04/11/2022 09:40:17] [ps] debugLevel:400
[04/11/2022 09:40:17] [Config] Initializing config platform...
[04/11/2022 09:40:17] [Config] Spawning homebridge-config-ui-x with PID 27393
[04/11/2022 09:40:17] [Camera-ffmpeg] Initializing Camera-ffmpeg platform...
[04/11/2022 09:40:17] [ps] Synchronisation Jeedom <> Homebridge...
Setup Payload:
X-HM://0023ISYWYC7A6
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:
┌────────────┐
│ 031-45-154 │
└────────────┘
[04/11/2022 09:40:18] Homebridge v1.5.0 (HAP v0.10.2) (ps) is running on port 51826.

c’est suivi tout de suite derrière par des messages d’erreur …

[04/11/2022 09:40:18] [ps] ERROR #2 Erreur de récupération des données Jeedom:  Error: connect ENETUNREACH 192.168.1.4:80 - Local (0.0.0.0:0)
at internalConnect (node:net:1010:16)
at defaultTriggerAsyncIdScope (node:internal/async_hooks:464:18)
at node:net:1103:9
at processTicksAndRejections (node:internal/process/task_queues:78:11) {
errno: -101,
code: 'ENETUNREACH',
syscall: 'connect',
address: '192.168.*.*',
port: 80
}
Error: connect ENETUNREACH 192.168.*.*:80 - Local (0.0.0.0:0)
at internalConnect (node:net:1010:16)
at defaultTriggerAsyncIdScope (node:internal/async_hooks:464:18)
at node:net:1103:9
at processTicksAndRejections (node:internal/process/task_queues:78:11)
e[0;37m[04/11/2022 09:40:29] e[0me[0;36m[Homebridge UI]e[0m e[0;33mHomebridge Config UI X v4.50.0 is listening on :: port 33221e[0m
e[0;37m[05/11/2022 01:10:14] e[0me[0;36m[Homebridge UI]e[0m Running job to cleanup config.json backup files older than 60 days...

et le lendemain idem,

[05/11/2022 09:41:39] Error: send ENETUNREACH 224.0.0.251:5353
at doSend (node:dgram:705:16)
at defaultTriggerAsyncIdScope (node:internal/async_hooks:464:18)
at afterDns (node:dgram:651:5)
at processTicksAndRejections (node:internal/process/task_queues:84:21)
[05/11/2022 09:41:39] Got SIGTERM, shutting down Homebridge...

et ainsi de suite, ça se recharge …

une idée de la manière dont je peux diagnostiquer ce souci et peut être aussi le fait qu’aucun dialogue n’est fonctionnel (home → homebridge et homebridge → home) ?

2

Bonjour,

Pouvez vous fournir les logs complets de homebridge ainsi que http.error svp.

3

A quoi correspond cette ip ?

4

Ceci indique un problème de réseau. De multicast probablement ou juste votre réseau.

5

je vais voir pour récupérer les logs complets, là c’est ce qui sort à l’affichage depuis jeedom que j’ai copié et il y a guère plus. je vais relancer et laisser tourner jusqu’à demain.

ps : j’ai un réseau local avec supervision et il n’y a aucune erreur remontée de transmission sur le port ethernet en question.

j’ai mis à jour le core a midi, on ne sait jamais :

image
image2816×626 119 KB

voilà tout ce qu’il y a dans http.error

[Sun Oct 09 08:30:53.451293 2022] [mpm_prefork:notice] [pid 724] AH00163: Apache/2.4.38 (Debian) configured -- resuming normal operations
[Sun Oct 09 08:30:53.451538 2022] [core:notice] [pid 724] AH00094: Command line: '/usr/sbin/apache2'
[Sun Oct 09 08:52:59.069022 2022] [php7:error] [pid 1614] [client 192.168.1.4:47542] PHP Fatal error:  Uncaught Error: Class 'homebridge' not found in /var/www/html/core/class/event.class.php:143
Stack trace:
#0 /var/www/html/core/class/event.class.php(129): event::filterEvent(Array, 'homebridge')
#1 /var/www/html/core/api/jeeApi.php(419): event::changes('1665298366.8544...', '30', 'homebridge')
#2 {main}
  thrown in /var/www/html/core/class/event.class.php on line 143
[Thu Oct 13 08:53:28.961197 2022] [mpm_prefork:notice] [pid 684] AH00163: Apache/2.4.38 (Debian) configured -- resuming normal operations
[Thu Oct 13 08:53:28.962052 2022] [core:notice] [pid 684] AH00094: Command line: '/usr/sbin/apache2'
[Fri Oct 28 09:59:24.925052 2022] [mpm_prefork:notice] [pid 722] AH00163: Apache/2.4.38 (Debian) configured -- resuming normal operations
[Fri Oct 28 09:59:24.925591 2022] [core:notice] [pid 722] AH00094: Command line: '/usr/sbin/apache2'

je ne vois rien d’annormal, juste des prefork d’apache pour ajuster les worker threads, ce qui me semble « normal » selon l’activité qui peut varier. par contre il y a une erreur homebridge que je ne sais pas expliquer … peut être du fait que apache se reconfigure ? enfin, je n’ai rien bricolé à ce niveau, donc tout devrait fonctionner en jeedom comme prévu. mais bon ces messages sont vieux …

6

voilà le log de démarrage homebridge côté jeedom:

[2022-11-06 13:30:48][INFO] : Mode debug : 
[2022-11-06 13:30:48][INFO] : Génération du fichier config.json de Homebridge :nok
[2022-11-06 13:30:48][DEBUG] : On prend l'API de l'utilisateur : admin configuré localOnly=0| apiMode=Activé
[2022-11-06 13:30:49][DEBUG] : CMD=export AVAHI_COMPAT_NOWARN=1; /var/www/html/plugins/homebridge/core/class/../../resources/node_modules/homebridge/bin/homebridge -I --no-qrcode -U /var/www/html/plugins/homebridge/core/class/../../resources/homebridge >> /var/www/html/core/class/../../log/homebridge_daemon 2>&1 &
[2022-11-06 13:30:50][INFO] : Démon homebridge lancé
[2022-11-06 13:31:01][INFO] : Demande de Sync Homebridge
[2022-11-06 13:31:02][DEBUG] : cache updated with : ["2264","2316","2509","2298","2300","2367","3178","3252","2325","2505","3427","2289","2233","2235","2990","2988","2989","2991","2992","3270","3267","3268","3269","2360","2362","3684","3685","3686","3687","3688","3266","3263","3264","3265","353","351","352","2171","2173","2174","3313","3314","3315","3316","3317","1051","1053","1055","1054","1056","2828","2831","2829","2830","2832","2833","2855","2858","2856","2857","2859","2860","3613","3614","3615","3616","3617","3596","3597","3598","3599","3600","1141","1140","1138","1136","1137","1139","1142","1135","973","974","975","976","977","3370","3371","3372","3373","3374","3504","3503","3501","3505","3502","3506","2356","2359","2358","1041","1042","1043","1044","1045","1710","1711","1712","1713","1714","1031","1032","1033","1034","1035","1914","1912","1913","2939","2936","2937","2938","2941","2942","3376","3377","3378","426","427","429","428","430","3523","3524","3525","3527","3526","2190","2187","2188","2189","2191","2192","2205","2206","2207","2209","2208","2210","2196","2193","2194","2195","2197","2198","2202","2199","2200","2201","2203","2204","2149","2146","2147","2148","2150","2151","2924","2921","2922","2923","2925","2926","2143","2140","2141","2142","2144","2145","2161","2158","2159","2160","2162","2163","259","260","261","262","2656","2659","2657","2658","2994","2995","2996","2997","2998","1705","1706","1707","1708","1709","2982","2983","2984","2985","2986","1021","1022","1023","1024","1025","3659","3656","3660","3676","3677","3679","3670","3678","3671","3658","3663","3664","3657","3661","3662","2949","3003","3000","2951","3029","3030","2955","2953","2617","2618","1905","1792","1791","1785","1784","1786","1795","1796","1797","3756","3757","3511","3441","3539","3540","3541","3542","3543","3544","3535","3536","3537","2371","2372","2373","3562","3563","3564","3565","3566","3567","1788","1787","1789","3443","3444","2484"]
[2022-11-06 13:47:02][DEBUG] : On prend l'API de l'utilisateur : admin configuré localOnly=0| apiMode=Activé
[2022-11-06 17:25:09][INFO] : Mode debug : 
[2022-11-06 17:25:09][INFO] : Génération du fichier config.json de Homebridge :nok
[2022-11-06 17:25:10][DEBUG] : On prend l'API de l'utilisateur : admin configuré localOnly=0| apiMode=Activé
[2022-11-06 17:25:11][DEBUG] : CMD=export AVAHI_COMPAT_NOWARN=1; /var/www/html/plugins/homebridge/core/class/../../resources/node_modules/homebridge/bin/homebridge -I --no-qrcode -U /var/www/html/plugins/homebridge/core/class/../../resources/homebridge >> /var/www/html/core/class/../../log/homebridge_daemon 2>&1 &
[2022-11-06 17:25:12][INFO] : Démon homebridge lancé
[2022-11-06 17:25:21][INFO] : Demande de Sync Homebridge
[2022-11-06 17:25:22][DEBUG] : cache updated with : ["2264","2316","2509","2298","2300","2367","3178","3252","2325","2505","3427","2289","2233","2235","2990","2988","2989","2991","2992","3270","3267","3268","3269","2360","2362","3684","3685","3686","3687","3688","3266","3263","3264","3265","353","351","352","2171","2173","2174","3313","3314","3315","3316","3317","1051","1053","1055","1054","1056","2828","2831","2829","2830","2832","2833","2855","2858","2856","2857","2859","2860","3613","3614","3615","3616","3617","3596","3597","3598","3599","3600","1141","1140","1138","1136","1137","1139","1142","1135","973","974","975","976","977","3370","3371","3372","3373","3374","3504","3503","3501","3505","3502","3506","2356","2359","2358","1041","1042","1043","1044","1045","1710","1711","1712","1713","1714","1031","1032","1033","1034","1035","1914","1912","1913","2939","2936","2937","2938","2941","2942","3376","3377","3378","426","427","429","428","430","3523","3524","3525","3527","3526","2190","2187","2188","2189","2191","2192","2205","2206","2207","2209","2208","2210","2196","2193","2194","2195","2197","2198","2202","2199","2200","2201","2203","2204","2149","2146","2147","2148","2150","2151","2924","2921","2922","2923","2925","2926","2143","2140","2141","2142","2144","2145","2161","2158","2159","2160","2162","2163","259","260","261","262","2656","2659","2657","2658","2994","2995","2996","2997","2998","1705","1706","1707","1708","1709","2982","2983","2984","2985","2986","1021","1022","1023","1024","1025","3659","3656","3660","3676","3677","3679","3670","3678","3671","3658","3663","3664","3657","3661","3662","2949","3003","3000","2951","3029","3030","2955","2953","2617","2618","1905","1792","1791","1785","1784","1786","1795","1796","1797","3756","3757","3511","3441","3539","3540","3541","3542","3543","3544","3535","3536","3537","2371","2372","2373","3562","3563","3564","3565","3566","3567","1788","1787","1789","3443","3444","2484"]

dans le log daemon il n’y a pas la moindre erreur en parallèle, il est très gros je vais voir comment vous le faire parvenir si c’est indispensable.

7

J’ai besoin de tous les logs

8

C’est une vm ? Si oui avec quel hyperviseur ? Et quelle est la configuration du réseau ?

9

Je ne parle pas d’erreur de transmission mais bien de multicast qui ne serait pas autorisé ou dropé… qu’elle est votre configuration igmp snooping ? Avez vous des points d’accès multiples ? Du routage ?

10

Elle date du 9 octobre, probablement pendant l’install des dépendances ou du plugin ?

11

En fait je demande tout car vous sortez les erreurs du log mais vous ne fournissez pas le contexte, les lignes avant par exemple qui peuvent avoir une incidence capitale, j’ai aussi besoin du log demon lors de son demarrage (en debug évidemment) car vous avez également tronqué ce log.

12

Et vous ne répondez pas à mes questions

13

En fait ce message ça veut dire que ce système ne réponds pas quand le demon essaie de communiquer avec, si c’est votre jeedom ça veut dire qu’il y a un problème apache par exemple…

14

C’est une vm ? Si oui avec quel hyperviseur ? Et quelle est la configuration du réseau ?

non ce n’est pas une vm c’est une machine physique et le superviseur c’est pour le monitoring des switches. elle est sur un vlan qui a tous les droits et sur le même que les périphériques apple.

je ne parle pas d’erreur de transmission mais bien de multicast qui ne serait pas autorisé ou dropé… qu’elle est votre configuration igmp snooping ? Avez vous des points d’accès multiples ? Du routage ?

je ne filtre pas les multicast sur ce segment physique, ni d’ailleurs sur les autres et d’ailleurs ça marche bien puisque le NAS en AFP et les imprimantes sont bien propagés.

igmp snooping est activé.

il y a un bon paquet de points d’accès en mesh, des swiches et du routage inter-vlan, firewall, etc… jeedom n’est pas filtré en sortie justement pour propager les éventuels services.

15

En fait ce message ça veut dire que ce système ne réponds pas quand le demon essaie de communiquer avec, si c’est votre jeedom ça veut dire qu’il y a un problème apache par exemple…

ok. du coup c’est étrange car c’est le seul service qui délire, tout le reste est parfaitement fonctionnel.

16

Bonjour

Il me semblait qu’avec ios16 et la nouvelle architecture maison, un ipad ne peut plus servir de bridge. Et à priori tu as un ipad comme concentrateur. Ton problème ne viendrait pas de là?
Il faut soit un homepod, soit une apple tv

17

Du coup c’est étrange car vous êtes le seul utilisateur qui a le probleme, chez tous les autres c’est parfaitement fonctionnel.

18

je peux le désactiver, mais à priori les machines affichent bien un popup comme quoi l’ipad pro est détecté en concentrateur. cela dit c’est utilisé que depuis l’extérieur, pas l’intérieur.

ps : il est sur le même lan que jeedom.

19

Du coup c’est étrange car vous êtes le seul utilisateur qui a le probleme, chez tous les autres c’est parfaitement fonctionnel.

je sais, c’est étrange… du coup peut être qu’une réinstallation à zéro et un passage à redéfinir les dizaines d’objets ne serait pas un luxe

20

Oui et non… ça a été démenti après.

En fait l’iPad ne fonctionnera pas pour matter, c’est tout. Mais je vous suis par contre concernant l’iPad en concentrateur, c’est le pire concentrateur qui existe, car il doit rester en permanence au domicile et être branché en permanence également… ce qui n’est pas le but d’un concentrateur !

Il vaut mieux une Apple TV c’est la meilleure (ethernet et alimentée) ensuite le homepods et enfin l’iPad.