FATAL: Cannot access share. Unknown reason.

upais commented 2 years ago

Good afternoon. Approximately after updating to version 5, the addon stopped working. From Windows on \10.187.1.6\Backup\Home_Assistant is connected. Files are created and deleted. Message: FATAL: Cannot access share. reason. Tried: 1) Remove and install again 2) Used a different 'target_dir' 3) Tried another account

Config:

host: 10.187.1.6
share: Backup
target_dir: Home_Assistant
username: '!secret NAS_service_user'
password: '!secret NAS_service_pass'
keep_local: '1'
keep_remote: '7'
trigger_time: '02:00'
trigger_days:
  - Mon
  - Tue
  - Wed
  - Thu
  - Fri
  - Sat
  - Sun
exclude_addons: []
exclude_folders: []
log_level: debug
skip_precheck: false

Log:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/00-banner.sh
-----------------------------------------------------------
 Add-on: Samba Backup
 Create backups and store them on a Samba share
-----------------------------------------------------------
 Add-on version: 5.1.1
 You are running the latest version of this add-on.
 System: Home Assistant OS 8.2  (amd64 / qemux86-64)
 Home Assistant Core: 2022.7.5
 Home Assistant Supervisor: 2022.07.0
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
cont-init: info: /etc/cont-init.d/00-banner.sh exited 0
cont-init: info: running /etc/cont-init.d/01-log-level.sh
Log level is set to DEBUG
cont-init: info: /etc/cont-init.d/01-log-level.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[22-07-18 08:21:27] INFO: ---------------------------------------------------
[22-07-18 08:21:27] INFO: Host/Share: 10.187.1.6/Backup
[22-07-18 08:21:27] INFO: Target directory: Home_Assistant
[22-07-18 08:21:27] INFO: Keep local/remote: 1/7
[22-07-18 08:21:27] INFO: Trigger time: 02:00
[22-07-18 08:21:27] INFO: Trigger days: Mon Tue Wed Thu Fri Sat Sun
[22-07-18 08:21:27] INFO: ---------------------------------------------------
[22-07-18 08:21:27] DEBUG: Backups local: 8
[22-07-18 08:21:27] DEBUG: Backups remote: 7
[22-07-18 08:21:27] DEBUG: Total backups succeeded: 6
[22-07-18 08:21:27] DEBUG: Total backups failed: 7
[22-07-18 08:21:27] DEBUG: Last backup: 2022-07-01 01:33
[22-07-18 08:21:27] DEBUG: API Status: 200
[22-07-18 08:21:27] DEBUG: API Response: {"entity_id":"sensor.samba_backup","state":"IDLE","attributes":{"friendly_name":"Samba Backup","backups_local":"8","backups_remote":"7","total_backups_succeeded":"6","total_backups_failed":"7","last_backup":"2022-07-01 01:33"},"last_changed":"2022-07-18T05:21:27.915134+00:00","last_updated":"2022-07-18T05:21:27.915134+00:00","context":{"id":"01G87W24VBBZB96ZQR1YY5ATN9","parent_id":null,"user_id":"f85227081176454cb8e245911bf09897"}}
[22-07-18 08:21:28] WARNING: 
[22-07-18 08:21:28] FATAL: Cannot access share. Unknown reason.
[22-07-18 08:21:28] DEBUG: API Status: 200
[22-07-18 08:21:28] DEBUG: API Response: {"entity_id":"sensor.samba_backup","state":"FAILED","attributes":{"friendly_name":"Samba Backup","backups_local":"8","backups_remote":"7","total_backups_succeeded":"6","total_backups_failed":"7","last_backup":"2022-07-01 01:33"},"last_changed":"2022-07-18T05:21:28.379625+00:00","last_updated":"2022-07-18T05:21:28.379625+00:00","context":{"id":"01G87W259VDKNWE5R69BMR81YM","parent_id":null,"user_id":"f85227081176454cb8e245911bf09897"}}
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

thomasmauerer commented 2 years ago

Hmm... the strange thing here is that the warning message is empty. Actually the status code of smbclient should be displayed there.

Please try if it makes a difference when username and password are specified directly in the config and not using !secret.

upais commented 2 years ago

Yes, I also noticed this strange thing. I tried to enter the credentials in the configuration - nothing changes:

[22-07-22 18:50:17] WARNING: 
[22-07-22 18:50:17] FATAL: Cannot access share. Unknown reason.

If enter the wrong password, then the error is already detailed:

[22-07-22 18:53:40] WARNING: session setup failed: NT_STATUS_LOGON_FAILURE
[22-07-22 18:53:40] FATAL: Cannot access share. Login failed. Please check your credentials.

SMB is available under this account and the files are created:

I don’t even know how else to localize the problem, the Synology logs are empty.

Napalmcold commented 2 years ago

Same issue here. Tried to change synology smb settings, created another share, another user. Nothing helps. Also started new homeassistant test instance, and the same issue there. Here's the log:

`s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting cont-init: info: running /etc/cont-init.d/00-banner.sh

Add-on: Samba Backup Create backups and store them on a Samba share

Add-on version: 5.1.1 You are running the latest version of this add-on. System: Home Assistant OS 8.5 (amd64 / qemux86-64) Home Assistant Core: 2022.8.5 Home Assistant Supervisor: 2022.08.3

Please, share the above information when looking for help or support in, e.g., GitHub, forums or the Discord chat.

cont-init: info: /etc/cont-init.d/00-banner.sh exited 0 cont-init: info: running /etc/cont-init.d/01-log-level.sh Log level is set to DEBUG cont-init: info: /etc/cont-init.d/01-log-level.sh exited 0 s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service legacy-services: starting s6-rc: info: service legacy-services successfully started [22-08-24 16:57:01] INFO: --------------------------------------------------- [22-08-24 16:57:01] INFO: Host/Share: 192.168.0.2/hass [22-08-24 16:57:01] INFO: Target directory: [22-08-24 16:57:01] INFO: Keep local/remote: 5/10 [22-08-24 16:57:01] INFO: Trigger time: 03:00 [22-08-24 16:57:01] INFO: Trigger days: Mon Tue Wed Thu Fri Sat Sun [22-08-24 16:57:01] INFO: --------------------------------------------------- [22-08-24 16:57:01] DEBUG: Backups local: 32 [22-08-24 16:57:01] DEBUG: Backups remote: 10 [22-08-24 16:57:01] DEBUG: Total backups succeeded: 188 [22-08-24 16:57:01] DEBUG: Total backups failed: 9 [22-08-24 16:57:01] DEBUG: Last backup: 2022-07-01 03:06 [22-08-24 16:57:01] DEBUG: API Status: 200 [22-08-24 16:57:01] DEBUG: API Response: {"entity_id":"sensor.samba_backup","state":"IDLE","attributes":{"friendly_name":"Samba Backup","backups_local":"32","backups_remote":"10","total_backups_succeeded":"188","total_backups_failed":"9","last_backup":"2022-07-01 03:06"},"last_changed":"2022-08-24T13:57:01.907320+00:00","last_updated":"2022-08-24T13:57:01.907320+00:00","context":{"id":"01GB828RTKKZ2VDY0727AH40C3","parent_id":null,"user_id":"5083b83ae5434a6e8d6fcef3c4336511"}} [22-08-24 16:57:02] WARNING: [22-08-24 16:57:02] FATAL: Cannot access share. Unknown reason. [22-08-24 16:57:02] DEBUG: API Status: 200 [22-08-24 16:57:02] DEBUG: API Response: {"entity_id":"sensor.samba_backup","state":"FAILED","attributes":{"friendly_name":"Samba Backup","backups_local":"32","backups_remote":"10","total_backups_succeeded":"188","total_backups_failed":"9","last_backup":"2022-07-01 03:06"},"last_changed":"2022-08-24T13:57:02.516403+00:00","last_updated":"2022-08-24T13:57:02.516403+00:00","context":{"id":"01GB828SDM1CYBKXD9JSPWNJ6R","parent_id":null,"user_id":"5083b83ae5434a6e8d6fcef3c4336511"}} s6-rc: info: service legacy-services: stopping s6-rc: info: service legacy-services successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped`

Napalmcold commented 2 years ago

Seems to be the HassOS issue. Tried to set backups to the share folder on the laptop, same error. My friend has Hass.io on Raspberry and everything works for him

Depulsor commented 2 years ago

Hello, I have the same problem. Have updated to version: 5.1.2. Since then I get this error: WARNING: FATAL: Cannot access share. Unknown reason.

is there a solution for this in the meantime?

upais commented 2 years ago

I confirm. On 5.1.2 the problem remained.

Depulsor commented 2 years ago

So currently the only way to continue using the add-on is to downgrade?

thomasmauerer commented 2 years ago

Which was the last version that has been working for you?

upais commented 2 years ago

Which was the last version that has been working for you?

I do not remember exactly, somewhere in June it worked.

thomasmauerer commented 2 years ago

Probably v5.0.0. That release had an older version of smbclient (4.14.5), the new version is 4.15.7 which is the latest stable version available in Alpine Linux.

Unfortunately, without a status code it is not possible to tell what the real problem is. Please try two more things:

1) Set skip_precheck to true. This way the addon will start successfully. Most likely it will then fail to copy a backup, but maybe we see a status code there at least.

2) Set compatibility_mode to true

upais commented 2 years ago

Unfortunately, nothing new.

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/00-banner.sh
-----------------------------------------------------------
 Add-on: Samba Backup
 Create backups and store them on a Samba share
-----------------------------------------------------------
 Add-on version: 5.1.2
 You are running the latest version of this add-on.
 System: Home Assistant OS 8.5  (amd64 / qemux86-64)
 Home Assistant Core: 2022.9.0
 Home Assistant Supervisor: 2022.08.5
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
cont-init: info: /etc/cont-init.d/00-banner.sh exited 0
cont-init: info: running /etc/cont-init.d/01-log-level.sh
Log level is set to DEBUG
cont-init: info: /etc/cont-init.d/01-log-level.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[22-09-08 01:15:57] INFO: ---------------------------------------------------
[22-09-08 01:15:57] INFO: Host/Share: 10.187.1.6/Downloads
[22-09-08 01:15:57] INFO: Target directory: test
[22-09-08 01:15:57] INFO: Keep local/remote: all/all
[22-09-08 01:15:57] INFO: Trigger time: 02:00
[22-09-08 01:15:57] INFO: Trigger days: Mon Tue Wed Thu Fri Sat Sun
[22-09-08 01:15:57] INFO: ---------------------------------------------------
[22-09-08 01:15:57] DEBUG: Backups local: 0
[22-09-08 01:15:57] DEBUG: Backups remote: 0
[22-09-08 01:15:57] DEBUG: Total backups succeeded: 0
[22-09-08 01:15:57] DEBUG: Total backups failed: 0
[22-09-08 01:15:57] DEBUG: Last backup: never
[22-09-08 01:15:57] DEBUG: Posting sensor data to API at /core/api/states/sensor.samba_backup
[22-09-08 01:15:57] DEBUG: API Status: 200
[22-09-08 01:15:57] DEBUG: API Response: {"entity_id":"sensor.samba_backup","state":"IDLE","attributes":{"friendly_name":"Samba Backup","backups_local":"0","backups_remote":"0","total_backups_succeeded":"0","total_backups_failed":"0","last_backup":"never"},"last_changed":"2022-09-07T22:13:42.768873+00:00","last_updated":"2022-09-07T22:13:42.768873+00:00","context":{"id":"01GCD0897GYTV2XRTX12Y2D17D","parent_id":null,"user_id":"f85227081176454cb8e245911bf09897"}}
[22-09-08 01:15:57] INFO: Samba Backup started successfully
[22-09-08 01:15:57] DEBUG: Starting stdin listener ...
[22-09-08 01:15:57] DEBUG: Starting main loop ...
[22-09-08 02:00:01] INFO: Backup running ...
[22-09-08 02:00:01] DEBUG: Posting sensor data to API at /core/api/states/sensor.samba_backup
[22-09-08 02:00:02] DEBUG: API Status: 200
[22-09-08 02:00:02] DEBUG: API Response: {"entity_id":"sensor.samba_backup","state":"RUNNING","attributes":{"friendly_name":"Samba Backup","backups_local":"0","backups_remote":"0","total_backups_succeeded":"0","total_backups_failed":"0","last_backup":"never"},"last_changed":"2022-09-07T23:00:02.003915+00:00","last_updated":"2022-09-07T23:00:02.003915+00:00","context":{"id":"01GCD2X3AK9M3PRXMCNFS122XH","parent_id":null,"user_id":"f85227081176454cb8e245911bf09897"}}
[22-09-08 02:00:02] INFO: Creating backup "Samba Backup 2022-09-08 02:00"
[22-09-08 02:01:10] INFO: Copying backup d155526c (Samba_Backup_2022_09_08_02_00.tar) to share
[22-09-08 02:01:10] WARNING: 
[22-09-08 02:01:10] WARNING: Could not copy backup d155526c to share. Trying again ...
[22-09-08 02:01:16] WARNING: 
[22-09-08 02:01:16] DEBUG: Posting sensor data to API at /core/api/states/sensor.samba_backup
[22-09-08 02:01:16] DEBUG: API Status: 200
[22-09-08 02:01:16] DEBUG: API Response: {"entity_id":"sensor.samba_backup","state":"FAILED","attributes":{"friendly_name":"Samba Backup","backups_local":"2","backups_remote":"0","total_backups_succeeded":"0","total_backups_failed":"1","last_backup":"never"},"last_changed":"2022-09-07T23:01:16.571393+00:00","last_updated":"2022-09-07T23:01:16.571393+00:00","context":{"id":"01GCD2ZC4V1KGSWW5YBJEJ4W7Z","parent_id":null,"user_id":"f85227081176454cb8e245911bf09897"}}
[22-09-08 02:01:26] DEBUG: Posting sensor data to API at /core/api/states/sensor.samba_backup
[22-09-08 02:01:26] DEBUG: API Status: 200
[22-09-08 02:01:26] DEBUG: API Response: {"entity_id":"sensor.samba_backup","state":"IDLE","attributes":{"friendly_name":"Samba Backup","backups_local":"2","backups_remote":"0","total_backups_succeeded":"0","total_backups_failed":"1","last_backup":"never"},"last_changed":"2022-09-07T23:01:26.634961+00:00","last_updated":"2022-09-07T23:01:26.634961+00:00","context":{"id":"01GCD2ZNZAVYGWJG5FJSE8XCNM","parent_id":null,"user_id":"f85227081176454cb8e245911bf09897"}}
[22-09-08 02:01:26] INFO: Backup finished

vheijnen commented 2 years ago

I have the same issue. After adding the skip_precheck and compatibilty_mode in my configuration i get this log output:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/00-banner.sh
-----------------------------------------------------------
 Add-on: Samba Backup
 Create backups and store them on a Samba share
-----------------------------------------------------------
 Add-on version: 5.1.2
 You are running the latest version of this add-on.
 System: Home Assistant OS 9.0  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2022.9.7
 Home Assistant Supervisor: 2022.09.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
cont-init: info: /etc/cont-init.d/00-banner.sh exited 0
cont-init: info: running /etc/cont-init.d/01-log-level.sh
Log level is set to DEBUG
cont-init: info: /etc/cont-init.d/01-log-level.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[22-09-30 13:25:13] INFO: ---------------------------------------------------
[22-09-30 13:25:13] INFO: Host/Share: nassi/home
[22-09-30 13:25:13] INFO: Target directory: backup
[22-09-30 13:25:13] INFO: Keep local/remote: 7/31
[22-09-30 13:25:13] INFO: Trigger time: 13:26
[22-09-30 13:25:13] INFO: Trigger days: Mon Tue Wed Thu Fri Sat Sun
[22-09-30 13:25:13] INFO: ---------------------------------------------------
[22-09-30 13:25:14] DEBUG: Backups local: 0
[22-09-30 13:25:14] DEBUG: Backups remote: 0
[22-09-30 13:25:14] DEBUG: Total backups succeeded: 0
[22-09-30 13:25:14] DEBUG: Total backups failed: 0
[22-09-30 13:25:14] DEBUG: Last backup: never
[22-09-30 13:25:14] DEBUG: Posting sensor data to API at /core/api/states/sensor.samba_backup
[22-09-30 13:25:14] DEBUG: API Status: 200
[22-09-30 13:25:14] DEBUG: API Response: {"entity_id":"sensor.samba_backup","state":"IDLE","attributes":{"friendly_name":"Samba Backup","backups_local":"0","backups_remote":"0","total_backups_succeeded":"0","total_backups_failed":"0","last_backup":"never"},"last_changed":"2022-09-30T11:24:32.139705+00:00","last_updated":"2022-09-30T11:24:32.139705+00:00","context":{"id":"01GE7284GBH4PAF321Y2MFRNR0","parent_id":null,"user_id":"07046558faed4d40bb2966dc30e16697"}}
[22-09-30 13:25:14] INFO: Samba Backup started successfully
[22-09-30 13:25:14] DEBUG: Starting stdin listener ...
[22-09-30 13:25:14] DEBUG: Starting main loop ...
[22-09-30 13:26:14] INFO: Backup running ...
[22-09-30 13:26:14] DEBUG: Posting sensor data to API at /core/api/states/sensor.samba_backup
[22-09-30 13:26:14] DEBUG: API Status: 200
[22-09-30 13:26:14] DEBUG: API Response: {"entity_id":"sensor.samba_backup","state":"RUNNING","attributes":{"friendly_name":"Samba Backup","backups_local":"0","backups_remote":"0","total_backups_succeeded":"0","total_backups_failed":"0","last_backup":"never"},"last_changed":"2022-09-30T11:26:14.764805+00:00","last_updated":"2022-09-30T11:26:14.764805+00:00","context":{"id":"01GE72B8QC4EQ74G52PN7CA29B","parent_id":null,"user_id":"07046558faed4d40bb2966dc30e16697"}}
[22-09-30 13:26:14] INFO: Creating backup "Samba Backup 2022-09-30 13:26"
scripts/main.sh: eval: line 54: unexpected EOF while looking for matching `''
scripts/main.sh: eval: line 55: syntax error: unexpected end of file
[22-09-30 13:28:08] INFO: Copying backup 638005d1 (Samba_Backup_2022_09_30_13_26.tar) to share
scripts/helper.sh: eval: line 66: unexpected EOF while looking for matching `''
scripts/helper.sh: eval: line 67: syntax error: unexpected end of file
[22-09-30 13:28:08] WARNING: 
[22-09-30 13:28:08] WARNING: Could not copy backup 638005d1 to share. Trying again ...
scripts/helper.sh: eval: line 66: unexpected EOF while looking for matching `''
scripts/helper.sh: eval: line 67: syntax error: unexpected end of file
[22-09-30 13:28:13] WARNING: 
scripts/sensor.sh: eval: line 78: unexpected EOF while looking for matching `''
scripts/sensor.sh: eval: line 79: syntax error: unexpected end of file
[22-09-30 13:28:13] DEBUG: Posting sensor data to API at /core/api/states/sensor.samba_backup
[22-09-30 13:28:13] DEBUG: API Status: 200
[22-09-30 13:28:13] DEBUG: API Response: {"entity_id":"sensor.samba_backup","state":"FAILED","attributes":{"friendly_name":"Samba Backup","backups_local":"23","backups_remote":"0","total_backups_succeeded":"0","total_backups_failed":"1","last_backup":"never"},"last_changed":"2022-09-30T11:28:13.968167+00:00","last_updated":"2022-09-30T11:28:13.968167+00:00","context":{"id":"01GE72EX4GB974XTCTE3C12PRH","parent_id":null,"user_id":"07046558faed4d40bb2966dc30e16697"}}
[22-09-30 13:28:24] DEBUG: Posting sensor data to API at /core/api/states/sensor.samba_backup
[22-09-30 13:28:24] DEBUG: API Status: 200
[22-09-30 13:28:24] DEBUG: API Response: {"entity_id":"sensor.samba_backup","state":"IDLE","attributes":{"friendly_name":"Samba Backup","backups_local":"23","backups_remote":"0","total_backups_succeeded":"0","total_backups_failed":"1","last_backup":"never"},"last_changed":"2022-09-30T11:28:24.164512+00:00","last_updated":"2022-09-30T11:28:24.164512+00:00","context":{"id":"01GE72F734N73C1KGQ8CYAX4SB","parent_id":null,"user_id":"07046558faed4d40bb2966dc30e16697"}}
[22-09-30 13:28:24] INFO: Backup finished`

Hope this helps!

politician commented 1 year ago

I had an unexpected EOF while looking for matching... error. This was because my password contained that character.

vheijnen commented 1 year ago

Removing special caracters from the password solved it for me. Thanks for the tip @politician

Depulsor commented 1 year ago

Removing special caracters from the password solved it for me. Thanks for the tip @politician

Did you delete only a specific special character or all of them? -> so now only a password consisting of [A-Za-z0-9] works?

vheijnen commented 1 year ago

I removed all of them.

so now only a password consisting of [A-Za-z0-9] works

Correct

Depulsor commented 1 year ago

I can now confirm this. As soon as I remove all special characters from the password, the AddOn can be used again.

Napalmcold commented 1 year ago

removing special charachters from password gave nothing. issue is still there

upais commented 1 year ago

removing special charachters from password gave nothing. issue is still there

+1

Freewilly3d commented 1 year ago

Same here; samba access to share works fine from raspian; synology

s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting cont-init: info: running /etc/cont-init.d/00-banner.sh

Add-on: Samba Backup Create backups and store them on a Samba share

Add-on version: 5.2.0 You are running the latest version of this add-on. System: Home Assistant OS 9.4 (aarch64 / raspberrypi4-64) Home Assistant Core: 2022.12.5 Home Assistant Supervisor: 2022.11.2

Please, share the above information when looking for help or support in, e.g., GitHub, forums or the Discord chat.

cont-init: info: /etc/cont-init.d/00-banner.sh exited 0 cont-init: info: running /etc/cont-init.d/01-log-level.sh Log level is set to DEBUG cont-init: info: /etc/cont-init.d/01-log-level.sh exited 0 s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service legacy-services: starting s6-rc: info: service legacy-services successfully started [22-12-13 15:29:12] INFO: --------------------------------------------------- [22-12-13 15:29:12] INFO: Host/Share: infinity/backups [22-12-13 15:29:12] INFO: Target directory: homeassistant [22-12-13 15:29:12] INFO: Keep local/remote: 3/10 [22-12-13 15:29:12] INFO: Trigger time: 15:30 [22-12-13 15:29:12] INFO: Trigger days: Mon Tue Wed Thu Fri Sat Sun [22-12-13 15:29:12] INFO: --------------------------------------------------- [22-12-13 15:29:13] DEBUG: Backups local/remote: 0/0 [22-12-13 15:29:13] DEBUG: Total backups succeeded/failed: 0/0 [22-12-13 15:29:13] DEBUG: Last backup: never [22-12-13 15:29:17] WARNING: do_connect: Connection to infinity failed (Error NT_STATUS_NOT_FOUND) [22-12-13 15:29:17] FATAL: Cannot access share. Unknown reason. [22-12-13 15:29:17] DEBUG: Posting sensor data to API at /core/api/states/sensor.samba_backup [22-12-13 15:29:17] DEBUG: API Status: 200 [22-12-13 15:29:17] DEBUG: API Response: {"entity_id":"sensor.samba_backup","state":"FAILED","attributes":{"friendly_name":"Samba Backup","backups_local":"0","backups_remote":"0","total_backups_succeeded":"0","total_backups_failed":"0","last_backup":"never"},"last_changed":"2022-12-13T21:25:37.497695+00:00","last_updated":"2022-12-13T21:25:37.497695+00:00","context":{"id":"01GM6P1YJSMMDSYJJZEDH4MEYT","parent_id":null,"user_id":"aa60bb2d6b384bbc94c94c48b54ae549"}} s6-rc: info: service legacy-services: stopping s6-rc: info: service legacy-services successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped

maorcc commented 1 year ago

I just found out that I had this issue too.

What worries me is that for 3 weeks I had no backups, and I was not aware of it. It could have been without backups for months. I hope that this bug will be fixed asap.

For backup systems knowing when it fails consistently is more important than making the effort to fail less, because there can always be bugs or environmental reasons for a backup to fail, and not knowing that you have no backups until you need it is the worst.

So I suggest to add some notification mechanism on fail, or at least, adding an example automation code in the DOCS.md file for getting notified when backups are not created for a while. No matter if it is because the backup process failed a few times, or because the addon failed to start.

makanimike commented 1 year ago

I can confirm that creating a password without any special characters solved this issue for me, too.

Napalmcold commented 1 year ago

I can confirm that creating a password without any special characters solved this issue for me, too.

Are you sure that you had the exact same issue? Because I have a password without any special charachters and it doesn't work for me

makanimike commented 1 year ago

I don't have my faulty logs anymore.
But I can confirm that I had these two critical lines when I did.

[22-07-18 08:21:28] WARNING: 
[22-07-18 08:21:28] FATAL: Cannot access share. Unknown reason.

And if Thomas himself was surprised about the empty Warning line, and I got my case solved with one of the recommended work arounds, there is a high likelihood that I did indeed have the exact same issue as OP.

maorcc commented 1 year ago

I can confirm that creating a password without any special characters solved this issue for me, too.

Are you sure that you had the exact same issue? Because I have a password without any special characters and it doesn't work for me

I don't think that the issue has anything to do with special characters. Changing the password probably restarts the add-on, and therefore temporarily resolves the issue.

makanimike commented 1 year ago

all I can say is that after 2 weeks of troubleshooting that led nowhere (obviously this included dozens of reboots, even full reinstalls and other measures), reading this thread and the specific comment about no special characters in the password immediately fixed it.
Sure, my issue could be unrelated to this one. But it fixed it.

Napalmcold commented 1 year ago

no special characters in the password immediately fixed it. Sure, my issue could be unrelated to this one. But it fixed it.

Unfortunately, not for me(

Seger85 commented 1 year ago

for me it was also the special characters, I discovered something else in yaml, my password had a "&" character at the front, so it caused the password to be passed incorrectly.

Napalmcold commented 1 year ago

...I discovered something else in yaml...

Where exactly you discovered it?

Seger85 commented 1 year ago

I discovered it when I changed the settings from Web Ui to Yaml.

Napalmcold commented 1 year ago

I discovered it when I changed the settings from Web Ui to Yaml.

You mean changing addon config tab into text editor mode?

Seger85 commented 1 year ago

I discovered it when I changed the settings from Web Ui to Yaml.

You mean changing addon config tab into text editor mode?

Exactly :)

gypsydangr commented 1 year ago

I have tried all of the recommended "fixes" and nothing works. The add-on eventually stops and sometimes has to be manually restarted. Is there a way to install the 5.0.0 version? I tried uninstalling and reinstalling, but I don't get the choose version screen.

Edit: I just realized all of my local backups initiated from this add-on are there, so it is only the Samba portion that isn't working.

GeoBau commented 8 months ago

I could not make it work with synology: (Ich also changed PW and tried different combinations of host / share / directory also WebUI / Yaml..) Error ist always the same. In the installation samba share and samba backup is installed - is there a connection? Do I need smba share to get backup running?

Log level is set to DEBUG cont-init: info: /etc/cont-init.d/01-log-level.sh exited 0 s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service legacy-services: starting s6-rc: info: service legacy-services successfully started [24-02-24 10:28:54] INFO: --------------------------------------------------- [24-02-24 10:28:54] INFO: Host/Share: 172.16.1.106/HA-Backup [24-02-24 10:28:54] INFO: Target directory: HomeAssist [24-02-24 10:28:54] INFO: Keep local/remote: 10/20 [24-02-24 10:28:54] INFO: Trigger time: 09:36 [24-02-24 10:28:54] INFO: Trigger days: Mon Tue Wed Thu Fri Sat Sun [24-02-24 10:28:54] INFO: --------------------------------------------------- [24-02-24 10:28:55] DEBUG: Backups local/remote: 0/0 [24-02-24 10:28:55] DEBUG: Total backups succeeded/failed: 0/0 [24-02-24 10:28:55] DEBUG: Last backup: never [24-02-24 10:28:56] WARNING: session setup failed: NT_STATUS_ACCESS_DENIED [24-02-24 10:28:56] FATAL: Cannot access share. Access denied. Please check your share permissions. [24-02-24 10:28:56] DEBUG: Posting sensor data to API at /core/api/states/sensor.samba_backup [24-02-24 10:28:56] DEBUG: API Status: 200 [24-02-24 10:28:56] DEBUG: API Response: {"entity_id":"sensor.samba_backup","state":"FAILED","attributes":{"friendly_name":"Samba Backup","backups_local":"0","backups_remote":"0","total_backups_succeeded":"0","total_backups_failed":"0","last_backup":"never"},"last_changed":"2024-02-23T21:40:27.422610+00:00","last_updated":"2024-02-23T21:40:27.422610+00:00","context":{"id":"01HQBYK6MYWPWX9HETRP4X45JK","parent_id":null,"user_id":"926bfd3803f34ab0b7ef1986b8c33bf6"}}

s6-rc: info: service legacy-services: stopping ...

thomasmauerer / hassio-addons