SSH log file isn't created

Hello,

Thank you for contacting us on this matter! Would it be possible for you to send us a screenshot of your current logging configurations in your SSH session? I would like to verify if I can see what is preventing your logs from being created.

Best regards,

options -> types -> terminal -> logging


ssh session:


Regards

Hello,

As a test, could you try removing the variables in both your "Log filename" field in the entry, and in the "default path" in the options (if there are any). I'm wondering if it might be the variables causing issues. If it is, it should be an easy fix.

Regards,

Hello,

I removed the variables from "Log filename" (this is the only place that contained them). There was no change.

Regards.

Thanks for the test. Unfortunately, I'm still unable to reproduce the issue. On my end, RDM successfully creates the filename specified in the "log filename" field, in the path specified in File>Options>Types>Terminal in the "default path" field. These are the fields you showed in your screenshots.

Something I noticed in your first post and want to clarify, you mention the "AdvancedTelnetSSH.log" file. This is only used with the "Rebex" entry types, and not our own terminals (which you are using according to your screenshots). So looking in %LocalAppData%\Devolutions\RemoteDesktopManager would be wrong in this case, you would have to look in the folder specified in your screenshot in the "default path" field for the resulting log file.

Regards,

Yes, I don't use Rebex. The session logging per host is working fine. I wanted to enable a general SSH logging to troubleshoot GSSAPI login attempts (something similar to ssh -vvvv in the OpenSSH client). So is it then possible in the RDM terminal implementation?

I see, I misunderstood the kind of logs you were looking for. Then, could you modify in your entry the "log mode" field to "event", and set the verbose level to 2 (in this RDM version, verbose might still be located in the Advanced tab, but it will be moved to the Logs tab in 2020.3). This should give you something closer to what "ssh -vvv" gives in OpenSSH, rather than printable output.

I understand this is not a "global" setting for this log, but I would like to first make sure these logs work for you.

Regards,

Hello,

thanks for clarifying. So it's either "Event" or "Printable output". I would need the printable output to be logged always (for "safety" reasons) and events in addition.

Also:

this option should clearly state that it's intended for Rebex only, and not for the default SSH client. The docs don't mention it, too.

Regards,

Hello,

Just to be sure, would the same functionality as Rebex, always logging in one file no matter the entry being used, be sufficient for you? I imagine this kind of log would only be enabled once in a while to debug certain servers and see why they aren't connecting properly, but I want to be sure this would work for you.

Regarding the option itself, if the behavior I described would work for you, we could make this option apply to both Rebex and our own terminals.

Regards,

Hello,

yes, it would work for me. Maybe some time later you could consider adding variable support.

Thanks!!!

Regards

We've opened a ticket with this information. We'll update this topic when we have an update on the feature.

Regards,

Hello,

We have added a new option called "Enable global event logging for Telnet and SSH (DevolutionsTerminal.log)" that will be located in File>Options>Advanced. We have also renamed the "Enable advanced Logging for Telnet and SSH (AdvancedTelnetSSH.log)" option to "Enable global logging for Rebex terminals (AdvancedTelnetSSH.log)" for clarity.

These changes will be available in RDM 2020.3.11.0 which we're planning to release October 28th.

Regards,