Samba share not starting

1

hi I´m using hassio on pi, suddenly I cound´t reach my directory through my computer anymore, tried to update the samba share, even reinstall and nothing, here´s my configuration:

{
  "workgroup": "WORKGROUP",
  "username": "hassio",
  "password": "secretpassword",
  "interface": "",
  "allow_hosts": [
    "10.0.0.0/8",
    "172.16.0.0/12",
    "192.168.0.0/16"
  ]
}

when I hit start I received nothing back, nothing on my logs as well.

Anyone could help?

2

anyone with the same problem

1 Like
3

justa check my supervisor logs and is showing this:

18-11-25 14:26:14 WARNING (SyncWorker_6) [hassio.docker.interface] Can't grep logs from homeassistant/armhf-addon-samba: 500 Server Error: Internal Server Error ("can not get logs from container which is dead or marked for removal")
18-11-25 14:26:16 INFO (SyncWorker_9) [hassio.docker.interface] Clean homeassistant/armhf-addon-samba Docker application
18-11-25 14:26:16 ERROR (SyncWorker_9) [hassio.docker] Can't create container from addon_core_samba: 409 Client Error: Conflict ("Conflict. The container name "/addon_core_samba" is already in use by container "a4b5eefeebe19641bd72958c47580b0c557143113c1b3908a6cc60404faa5339". You have to remove (or rename) that container to be able to reuse that name.")
18-11-25 14:26:22 WARNING (SyncWorker_16) [hassio.docker.interface] Can't grep logs from homeassistant/armhf-addon-samba: 500 Server Error: Internal Server Error ("can not get logs from container which is dead or marked for removal")
4

Bit late I know but I came across this problem.

I copied the configuration, uninstalled the addon, reinstalled it, copied back the configuration and it started fine.

I had had to reinstall hassIO over an existing setup so I don’t think it liked that!