Page 119 sur 120
Re: MyDomoAtHome - ImperiHome
Publié : 13 nov. 2023, 17:33
par epierre
alors oui mais c'est compliqué... je ne sais pas comment fiare pour différencier les repos...
le mieux est de télécharger
https://e-nef.com/domoticz/mdah/node-my ... -0.3.1.deb et d'installer en CLI
Re: MyDomoAtHome - ImperiHome
Publié : 13 nov. 2023, 17:46
par manuloup
Ok, c'est fait, merci.
Code : Tout sélectionner
root@domoticzvm:/home/pi# dpkg -i node-mydomoathome-0.3.1.deb
(Lecture de la base de données... 198784 fichiers et répertoires déjà installés.)
Préparation du dépaquetage de node-mydomoathome-0.3.1.deb ...
Dépaquetage de mydomoathome (0.3.1) sur (0.2.50) ...
Paramétrage de mydomoathome (0.3.1) ...
rebuilt dependencies successfully
Synchronizing state of mydomoathome.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable mydomoathome
Re: MyDomoAtHome - ImperiHome
Publié : 13 nov. 2023, 17:50
par manuloup
Bon, je crois que ça ne marche plus, le port 5001 ne me répond plus :
Code : Tout sélectionner
root@domoticzvm:/home/pi# service mydomoathome status
mydomoathome.service - MDAH ISS Rest interface for Domoticz to Imperihome
Loaded: loaded (/etc/systemd/system/mydomoathome.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2023-11-13 17:48:41 CET; 1s ago
Process: 2098647 ExecStartPre=/bin/mkdir -p /run/mydomoathome (code=exited, status=0/SUCCESS)
Process: 2098648 ExecStartPre=/bin/chown www-data:www-data /run/mydomoathome (code=exited, status=0/SUCCESS)
Process: 2098649 ExecStartPre=/bin/chown www-data:www-data /etc/mydomoathome/config.json (code=exited, status=0/SUCCESS)
Process: 2098650 ExecStartPre=/bin/chmod 755 /run/mydomoathome (code=exited, status=0/SUCCESS)
Main PID: 2098651 (mydomoathome)
Tasks: 12 (limit: 2307)
Memory: 32.5M
CPU: 1.412s
CGroup: /system.slice/mydomoathome.service
├─2098651 /bin/bash /usr/share/mydomoathome/bin/mydomoathome
└─2098652 node /usr/bin/forever --minUptime 5000 --spinSleepTime 2000 --max-old-space-size=128 -a -l /var/log/mydomoathome/mdah.log /usr/share/mydomoathome/app/mdah.js
nov. 13 17:48:42 domoticzvm MDAH[2098652]: at winston.<computed> [as add] (/usr/share/mydomoathome/app/node_modules/winston/lib/winston.js:87:34)
nov. 13 17:48:42 domoticzvm MDAH[2098652]: at Object.<anonymous> (/usr/share/mydomoathome/app/mdah.js:72:12)
nov. 13 17:48:42 domoticzvm MDAH[2098652]: at Module._compile (node:internal/modules/cjs/loader:1120:14)
nov. 13 17:48:42 domoticzvm MDAH[2098652]: at Module._extensions..js (node:internal/modules/cjs/loader:1174:10)
nov. 13 17:48:42 domoticzvm MDAH[2098652]: at Module.load (node:internal/modules/cjs/loader:998:32)
nov. 13 17:48:42 domoticzvm MDAH[2098652]: at Module._load (node:internal/modules/cjs/loader:839:12)
nov. 13 17:48:42 domoticzvm MDAH[2098652]: at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
nov. 13 17:48:42 domoticzvm MDAH[2098652]: at node:internal/main/run_main_module:17:47
nov. 13 17:48:42 domoticzvm MDAH[2098652]: Node.js v18.6.0
nov. 13 17:48:42 domoticzvm MDAH[2098652]: {"level":"error","message":"Forever detected script exited with code: 1"}
root@domoticzvm:/home/pi# telnet localhost 5001
Trying ::1...
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused
Re: MyDomoAtHome - ImperiHome
Publié : 13 nov. 2023, 19:19
par epierre
oui on m'a parlé du problème de forever, je vais voir cela
Re: MyDomoAtHome - ImperiHome
Publié : 13 nov. 2023, 20:58
par manuloup
Ok merci, du coup ça ne marche plus

Re: MyDomoAtHome - ImperiHome
Publié : 13 nov. 2023, 21:05
par manuloup
La log d'erreur si je le lance direct en shell :
Code : Tout sélectionner
root@domoticzvm:/var/log/mydomoathome# forever --minUptime 5000 --spinSleepTime 2000 --max-old-space-size=128 -a -l /var/log/mydomoathome/mdah.log /usr/share/mydomoathome/app/mdah.js
(node:2249724) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency
(Use `node --trace-warnings ...` to show where the warning was created)
(node:2249724) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency
/usr/share/mydomoathome/app/node_modules/winston/lib/winston/logger.js:448
var instance = created ? transport : (new (transport)(options));
^
TypeError: transport is not a constructor
at Logger.add (/usr/share/mydomoathome/app/node_modules/winston/lib/winston/logger.js:448:41)
at winston.<computed> [as add] (/usr/share/mydomoathome/app/node_modules/winston/lib/winston.js:87:34)
at Object.<anonymous> (/usr/share/mydomoathome/app/mdah.js:72:12)
at Module._compile (node:internal/modules/cjs/loader:1120:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1174:10)
at Module.load (node:internal/modules/cjs/loader:998:32)
at Module._load (node:internal/modules/cjs/loader:839:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
at node:internal/main/run_main_module:17:47
Re: MyDomoAtHome - ImperiHome
Publié : 14 nov. 2023, 07:07
par manuloup
En attendant que les problèmes soient résolus, j'ai downgradé en version 2.50 :
Code : Tout sélectionner
root@domoticzvm:/home/pi# dpkg -i node-mydomoathome-0.2.50.deb
dpkg: avertissement: dégradation (« downgrade ») de mydomoathome depuis 0.3.1 vers 0.2.50
(Lecture de la base de données... 198784 fichiers et répertoires déjà installés.)
Préparation du dépaquetage de node-mydomoathome-0.2.50.deb ...
Dépaquetage de mydomoathome (0.2.50) sur (0.3.1) ...
Paramétrage de mydomoathome (0.2.50) ...
rebuilt dependencies successfully
Synchronizing state of mydomoathome.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable mydomoathome
root@domoticzvm:/home/pi# service mydomoathome status
● mydomoathome.service - MDAH ISS Rest interface for Domoticz to Imperihome
Loaded: loaded (/etc/systemd/system/mydomoathome.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2023-11-14 07:06:10 CET; 6s ago
Process: 4070535 ExecStartPre=/bin/mkdir -p /run/mydomoathome (code=exited, status=0/SUCCESS)
Process: 4070539 ExecStartPre=/bin/chown www-data:www-data /run/mydomoathome (code=exited, status=0/SUCCESS)
Process: 4070542 ExecStartPre=/bin/chown www-data:www-data /etc/mydomoathome/config.json (code=exited, status=0/SUCCESS)
Process: 4070545 ExecStartPre=/bin/chmod 755 /run/mydomoathome (code=exited, status=0/SUCCESS)
Main PID: 4070548 (mydomoathome)
Tasks: 19 (limit: 2307)
Memory: 67.0M
CPU: 1.773s
CGroup: /system.slice/mydomoathome.service
├─4070548 /bin/bash /usr/share/mydomoathome/bin/mydomoathome
├─4070553 node /usr/bin/forever --minUptime 5000 --spinSleepTime 2000 --max-old-space-size=128 -a -l /var/log/mydomoathome/mdah.log /usr/share/mydomoathome/app/mdah.js
└─4070922 /usr/bin/node /usr/share/mydomoathome/app/mdah.js
Re: MyDomoAtHome - ImperiHome
Publié : 14 nov. 2023, 08:57
par epierre
Hello,
tu es sur synology ? tu as utilisé le spk ?
Re: MyDomoAtHome - ImperiHome
Publié : 14 nov. 2023, 09:36
par manuloup
C'est une VM Debian, donc pas de spk.
Re: MyDomoAtHome - ImperiHome
Publié : 14 nov. 2023, 10:27
par epierre
ok donc tu as le bug sur l'image docker toi aussi