Bug #16991

No way to enable remote execution SSH debug logging easily

Added by Adam Ruzicka 12 months ago. Updated 12 months ago.

Status:New
Priority:Normal
Assigned To:-
Category:-
Target version:Foreman - Team Ivan backlog
Difficulty: Pull request:
Bugzilla link:1362630
Story points-
Velocity based estimate-

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

History

#1 Updated by Adam Ruzicka 12 months ago

  • Target version set to Team Ivan backlog

Also available in: Atom PDF