Bug #16991
closedNo way to enable remote execution SSH debug logging easily
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1362630
Description of problem:
Net::SSH is able to have quite detailed logging, but we don't give the user a way to see it - options[:logger] seems empty, so it goes to STDERR. We don't set the verbosity options either, maybe try to keep that the same as proxy's.
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Look in /var/log/foreman-proxy/*
Actual results:
No ssh logs
Expected results:
See ssh logs
Additional info:
Manual way to view the logs:
1. Enable debug logging by editing /opt/theforeman/tfm/root/usr/share/gems/gems/smart_proxy_remote_execution_ssh_core-*/lib/smart_proxy_remote_execution_ssh_core/connector.rb
Line 133 change Net::SSH.start(@host, @user, ssh_options) to Net::SSH.start(@host, @user, ssh_options.merge(:verbose => :debug))
2. Stop smart_proxy_dynflow_core
3. Start as foreman-proxy user in interaactive mode:
sudo -u foreman-proxy /usr/bin/smart_proxy_dynflow_core -p /var/run/foreman-proxy/smart_proxy_dynflow_core.pid
SSH log messages will show on STDERR
Updated by The Foreman Bot over 6 years ago
- Status changed from New to Ready For Testing
- Assignee set to Adam Ruzicka
- Pull request https://github.com/theforeman/foreman_remote_execution/pull/290 added
Updated by The Foreman Bot over 6 years ago
- Pull request https://github.com/theforeman/smart_proxy_remote_execution_ssh/pull/35 added
Updated by Anonymous about 6 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset foreman_plugin|83d7ea11d0b0d8c29e94c85d6839c79882dc05ca.