-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
better logging for salt-ssh #16417
Comments
So, here is a sample output from a salt-ssh command - would you expect results to replace [LEVEL] prefixes with [LEVEL] : hostname : Is that what you have in mind? [DEBUG ] Reading configuration from /etc/salt/master [DEBUG ] Results of YAML rendering:
|
Yes, at least for me having [LEVEL] : hostname would make reading logs much more comfortable. |
That would be useful. Thanks for the request! |
Has anything been done in this department? Regardless, I have a couple of other suggestions regarding salt-ssh logging. The base64 dump of the thin shim shows up 2 or 4 times in the debug log. Either find some way to scrub the base64 dump from the log line, or decrease the log level to trace. EDIT: Nevermind this, #27793 The |
I did some work to eliminate the shim printing awhile ago, and thought I had gotten rid of all of them, but I guess I need to do more looking. The reason the command is run with log-level quiet is (if I remember correctly) because we have to parse the output of the command after running it. Getting clean returns back on the console is difficult if there are logs as well... Anyway, thanks for bumping this, it'll get me thinking about the problem again. Because it's a real problem, debugging salt-ssh is a pain right now. |
Salt-call on the client is run with --out json. If log can be part of the output and also be in json format this would simplify parsing. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue. |
Please don't close this issue. |
Thank you for updating this issue. It is no longer marked as stale. |
Actually it's in a funny state; salt-ssh logs:
except I do not seem to be able to create a debug log on the client, and the log it has created has nothing to say about this. Especially hard since doing (In my case it's been |
I use following patch to workaround this:
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue. |
what do you want, bot? |
Thank you for updating this issue. It is no longer marked as stale. |
I think this issue should be a higher priority. It should be easier to see errors output by Also, in addition to modifying the sourcecode (as documented above), you can also call it manually on the host per Debugging salt-ssh - Salt SSH:
|
I agree with that requirement / bug report too. It is essential to get get log output from state/execution modules running on a minion for problem analysis and supporting the salt project. Currently I'm faced with a problem caused by the pip.installed module function, which calls the python interpreter at least once as user |
This helped me when trying to diagnose rbenv brokenness when using salt-ssh as a non-root user. Thanks! |
@kt97679 Closing this due to age, the old version of Salt and Python 2. Noting that with Salt 3006, having to run as root is being reduced with the user and group salt. |
Looking at the salt-ssh log especially using '-l all' it is not always clear if log was generated on local or remote side. It would be good to distinguish local and remote log entries by adding hostnames.
The text was updated successfully, but these errors were encountered: