home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
73.98k stars 31.02k forks source link

Synology DSM Transmition failed #97392

Closed mansellrace closed 1 year ago

mansellrace commented 1 year ago

The problem

I have used this integration for years without any problems. Now I have this error. I have tried deleting and reinserting integration and I get the same error.

{'api': 'SYNO.Core.System.Utilization', 'code': 1055, 'reason': 'Unknown', 'details': {'err_line': 182, 'err_msg': 'Transmition failed.'}}

Full debug log here: https://pastebin.com/sAE1958R

image

What version of Home Assistant Core has the issue?

core-2023.7.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Synology DSM

Link to integration documentation on our website

https://www.home-assistant.io/integrations/synology_dsm

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

kbirger commented 1 year ago

The only way I know to do this is to use ssh. Are you familiar with ssh? There may be a package for synology that allows you to edit such files, but I doubt it.

This guy's guides are usually pretty digestible https://mariushosting.com/how-to-ssh-into-a-synology-nas/

You will need to run the command as root by using sudo

@kbirger you mentioned in previous post you only deleted the file and "restarted" ..... what exactly you restarted?

My NAS

mib1185 commented 1 year ago

it might be enough to just restart the snmp service by systemctl restart snmpd from the command line (as root user)

DidierMetral commented 1 year ago

In the /var/lib/net-snmp/ directory you should have only one conf file (snmpd.conf) and a mib_indexes sub-directory.

For standard installation, as I don't know if everyone has the same bad file and if there is only one bad file in your directory, you can run this in ssh (as root user) to rename all the conf file except the good one, restart the service and check if the service is OK : find /var/lib/net-snmp -maxdepth 1 -type f -name "*.conf" -not -name "snmpd.conf" -exec mv {} {}_old \; && systemctl restart snmpd; systemctl show -p SubState snmpd

You should have a return with "SubState=running"

smarthomefamilyverrips commented 1 year ago

it might be enough to just restart the snmp service by systemctl restart snmpd from the command line (as root user)

@mib1185 yes i used this command after deletion of the snmpd.0.conf file using the instruction above of @kbirger @latez @DidierMetral. After doing this I was able to add the integration again and all works as expexted 👍

mib1185 commented 1 year ago

ok ... so all were able to solve their problems, i'm going to close this issue report. if anyone else get in trouble with this, the solution can be read above. thx for all to find a solution 👍