Forum Francophone Home Assistant

Plantage addon Network UPS Tools 0.4.0

Add-Ons
#1

Bonjour,

depuis la dernière mise à jour de l’addon de gestion des onduleurs,
j’ai un plantage de cette addon :

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] nut: applying... 
[fix-attrs.d] nut: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 

-----------------------------------------------------------
 Add-on: Network UPS Tools
 Manage battery backup (UPS) devices
-----------------------------------------------------------
 Add-on version: 0.4.0
 You are running the latest version of this add-on.
 System: Ubuntu 20.04.1 LTS  (amd64 / qemux86-64)
 Home Assistant Core: 2021.1.5
 Home Assistant Supervisor: 2021.01.7
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] nut.sh: executing... 
[17:47:25] INFO: Setting mode to netserver...
[17:47:26] INFO: Generating /etc/nut/upsd.users...
[17:47:26] INFO: Configuring user: stephane
[17:47:27] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[17:47:30] INFO: Configuring Device named myups...
[17:47:30] INFO: Starting the UPS drivers...
Network UPS Tools - UPS driver controller 2.7.4
Network UPS Tools - Generic HID driver 0.41 (2.7.4)
No matching HID UPS found
Driver failed to start (exit status=1)
USB communication driver 0.33
[cont-init.d] nut.sh: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing... 
-----------------------------------------------------------
                Oops! Something went wrong.

 We are so sorry, but something went terribly wrong when
 starting or running this add-on.
 
 Be sure to check the log above, line by line, for hints.
-----------------------------------------------------------
[cont-finish.d] 99-message.sh: exited 0.
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.

j’ai tenté de supprimer et réinstaller l’addon mais c’est identique !

une idée ?

#2

Bonjour,

Je pense à 2 choses :

  • supprimer l’addon depuis l’interface, puis dans le .storage
  • restaurer une version de l’addon qui fonctionnait depuis une sauvegarde

Peut-etre :wink:

#3

SUPER !
ça marche bien d’avoir supprimé l’addon et réinstallé la version 0.3.1
donc il semble bien y avoir un bug avec la 0.4.0

je n’ai plus qu’à attendre la prochaine màj pour voir si c’est mieux …

en tout cas merci pepite !

1 J'aime
#4

bonsoir,

je reviens sur mon sujet d’onduleur,
mon système a planté hier,
démarrage de hass en mode sans échec !
depuis, j’ai de nouveau le même message d’erreur sur mon addon UPS tools
sauf que en plus, même en supprimant et mettant une sauvegarde ancienne, cela ne corrige plus le problème
il y a depuis une nouvelle version 0.5.0 mais toujours pareil

@pepite
tu m’avait conseillé de supprimer le dossier de l’addon dans le répertoire .storage
mais sais tu ce qu’il faut supprimer ?

drwxr-xr-x    5 root     root          4096 Feb 10 20:10 .
drwxr-xr-x   16 root     root          4096 Feb 10 20:13 ..
-rw-------    1 root     root         32727 Feb 10 20:10 auth
-rw-------    1 root     root           168 Jan  3 08:16 auth_module.totp
-rw-------    1 root     root           827 Nov 26 10:49 auth_provider.homeassistant
-rw-r--r--    1 root     root          1348 Mar 28  2020 core.area_registry
-rw-------    1 root     root           393 Nov 29 07:14 core.config
-rw-r--r--    1 root     root         35720 Feb 10 18:02 core.config_entries
-rw-r--r--    1 root     root        120210 Feb  9 22:57 core.device_registry
-rw-r--r--    1 root     root        322875 Feb  9 22:32 core.entity_registry
-rw-r--r--    1 root     root        107909 Feb 10 20:02 core.restore_state
-rw-------    1 root     root           116 Jun 10  2020 core.uuid
-rw-r--r--    1 root     root          1833 Feb  9 22:34 esphome.04bdc22723d37c1e8c8b30b6f1d0e718
-rw-r--r--    1 root     root           686 May  6  2020 esphome.095685601ec24e888c4b5484aae0e12d
-rw-r--r--    1 root     root          2030 Jun  8  2020 esphome.09693d5999fe49f0a8359411ad459c7a
-rw-r--r--    1 root     root           871 Feb  9 22:34 esphome.0df8a6430a6311ebbcbea754e1198d8e
-rw-r--r--    1 root     root          1552 Feb  5 20:26 esphome.0eb6db47bcd598e621387098485f69f5
-rw-r--r--    1 root     root          2030 Jun  9  2020 esphome.283a3213285647c1b6e103d39ac1f670
-rw-r--r--    1 root     root          1225 Dec 14 17:30 esphome.37005554c58f460a814639372f49484c
-rw-r--r--    1 root     root          1315 Apr  9  2020 esphome.412c3d6de52c4505864bef071f1e3d19
-rw-r--r--    1 root     root           686 May  6  2020 esphome.463d0c7ca6ab4dad8fbd5bba213d3111
-rw-r--r--    1 root     root          2028 May  2  2020 esphome.48c42033366c4ba6a46c9749903892d7
-rw-r--r--    1 root     root          2109 Feb  9 22:34 esphome.62633704ff2911eabbafe30b7c00df10
-rw-r--r--    1 root     root          1629 Dec 24 13:41 esphome.62aac0c90ce13c76f75b20264ca23f54
-rw-r--r--    1 root     root           995 Jan  9 23:39 esphome.6437d666301f07af90ac158144f04490
-rw-r--r--    1 root     root          1278 Jun  1  2020 esphome.691bb31612d149498b2d9e663586c419
-rw-r--r--    1 root     root          3865 Oct 13 19:36 esphome.6d515277fbd211ea8f60dd8604ff72f6
-rw-r--r--    1 root     root          1635 Feb 10 06:59 esphome.74a98a98ccfdb543065b7c517353d2d2
-rw-r--r--    1 root     root          6464 Feb  9 22:34 esphome.888296920d8211ebb37a0d51e5a061f0
-rw-r--r--    1 root     root          1308 Feb  9 22:34 esphome.a5df52c29d0b48a2a54d5f33e1da623c
-rw-r--r--    1 root     root          1114 Aug  1  2020 esphome.c4b48f31faa047859cf9f595d3884b0d
-rw-r--r--    1 root     root          1641 May 31  2020 esphome.c96a2a0ff277460195156cc402344559
-rw-r--r--    1 root     root          1629 Jan  9 23:39 esphome.e1d1001066c98076a8262c6cbd0038b2
-rw-r--r--    1 root     root          1811 Feb  9 22:34 esphome.f84c34ae10a311eb8df19d29fd01ee5d
-rw-r--r--    1 root     root           686 May  6  2020 esphome.faacb2ff07bc4637b5f1d992b4c4fa4d
drwxr-xr-x    2 root     root          4096 Apr 24  2020 freebox
-rw-r--r--    1 root     root           230 Apr  8  2020 frontend.user_data_73ee4ea3732b4de7a2571132bfe04edd
-rw-r--r--    1 root     root           159 Feb 10 08:21 frontend_theme
drwxr-xr-x    2 root     root          4096 Feb 10 20:02 hacs
-rw-r--r--    1 root     root           295 Feb  9 20:53 hacs.critical
-rw-r--r--    1 root     root           150 Feb  9 20:53 hacs.hacs
-rw-r--r--    1 root     root        980793 Feb 10 19:32 hacs.repositories
-rw-r--r--    1 root     root           120 Mar 22  2020 hassio
-rw-r--r--    1 root     root           538 Feb  9 22:18 homekit.64b09babfc79517d87ed6fe158508c9b.aids
-rw-r--r--    1 root     root           236 Feb  9 22:18 homekit.64b09babfc79517d87ed6fe158508c9b.state
-rw-r--r--    1 root     root          4265 Feb  8 17:43 homekit.6e5aac123ca707d8b2aed566770706f7.aids
-rw-r--r--    1 root     root           236 Feb  8 17:43 homekit.6e5aac123ca707d8b2aed566770706f7.state
-rw-r--r--    1 root     root           283 Feb  9 22:31 http
drwxr-xr-x    2 root     root          4096 Apr  1  2020 icloud
-rw-r--r--    1 root     root           362 Sep 18 06:46 image
-rw-r--r--    1 root     root          1488 Dec 20 07:06 input_boolean
-rw-r--r--    1 root     root            90 Dec  4 16:23 input_datetime
-rw-r--r--    1 root     root          1929 Jan  9 07:01 input_number
-rw-r--r--    1 root     root         75016 Feb  8 16:55 lovelace
-rw-r--r--    1 root     root           696 Dec 27 20:11 lovelace_resources
-rw-r--r--    1 root     root        214930 Feb 10 19:48 mobile_app
-rw-------    1 root     root           167 Mar 22  2020 onboarding
-rw-r--r--    1 root     root          1345 Nov 30 08:50 person
-rw-r--r--    1 root     root          5998 Dec 23 07:38 scheduler.storage
-rw-r--r--    1 root     root           311 Dec 23 20:45 tag
-rw-------    1 root     root             0 Dec 30 19:24 tmpg8mx1jzb
-rw-r--r--    1 root     root          1359 Dec 26 14:51 zone
.storage $

merci pour vos conseils
stéphane

#5

Bonjour,

Il ne faut pas que tu supprimes un des fichiers.
Il faut que tu ailles LIRE un fichier et trouver dans lequel est ton addon. Je n’ai pas sous les yeux.
Je dirais dans un des "core."xxxxxxxxx