Skip to content

[QA] misleading error messages when using sssh commands #204

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mcm1957 opened this issue Oct 26, 2022 · 1 comment
Open

[QA] misleading error messages when using sssh commands #204

mcm1957 opened this issue Oct 26, 2022 · 1 comment
Labels

Comments

@mcm1957
Copy link
Member

mcm1957 commented Oct 26, 2022

When enebaling debug log shutdwon / reboot logs the following confusing error messages:

synology.0 | 2022-10-26 19:30:55.440 | warn | System reboot
synology.0 | 2022-10-26 19:30:49.076 | debug | *** ERROR : src: SSH Error: code: undefined message: Password:
synology.0 | 2022-10-26 19:30:49.010 | debug | *** ERROR : src: SSH Error: code: undefined message: Could not chdir to home directory /var/services/homes/testiob: No such file or directory
synology.0 | 2022-10-26 19:30:48.845 | debug | SSH:echo '******'\|sudo -S shutdown -r now
synology.0 | 2022-10-26 19:30:48.843 | debug | state synology.0.commands.reboot changed: true (ack = false)

The reason is, that ALL output returned by ssh at stderr is logged as error. BUT the password prompt is no error wat all. And depending on the synology setup the chdir error is no error too but caused by the fact that at this system no user homediectories existe (user home service not enabled)

If possible those misleading erros should be filtered.

@mcm1957 mcm1957 added the QA label Oct 26, 2022
@stale
Copy link

stale bot commented Feb 2, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within the next 7 days. Please check if the issue is still relevant in the most current version of the adapter and tell us. Also check that all relevant details, logs and reproduction steps are included and update them if needed. Thank you for your contributions. Dieses Problem wurde automatisch als veraltet markiert, da es in letzter Zeit keine Aktivitäten gab. Es wird geschlossen, wenn nicht innerhalb der nächsten 7 Tage weitere Aktivitäten stattfinden. Bitte überprüft, ob das Problem auch in der aktuellsten Version des Adapters noch relevant ist, und teilt uns dies mit. Überprüft auch, ob alle relevanten Details, Logs und Reproduktionsschritte enthalten sind bzw. aktualisiert diese. Vielen Dank für Eure Unterstützung.

@stale stale bot added the wontfix This will not be worked on label Feb 2, 2023
@mcm1957 mcm1957 removed the wontfix This will not be worked on label Feb 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant