Saltstack troubleshooting: Difference between revisions
From wikinotes
(→pip) |
(→pip) |
||
| Line 28: | Line 28: | ||
Unfortunately this is a moving target, so pinning packages becomes a bit of a headache. ungh. | Unfortunately this is a moving target, so pinning packages becomes a bit of a headache. ungh. | ||
Verify using logs: <code>/var/log/salt/minion</code> | |||
</blockquote><!-- pip --> | </blockquote><!-- pip --> | ||
</blockquote><!-- Salt Modules won't Execute --> | </blockquote><!-- Salt Modules won't Execute --> | ||
Revision as of 00:45, 13 March 2022
Invalid Jinja
Check the minion's
/var/log/salt/minionto get the full python stacktrace.
Salt Modules won't Execute
Here there be dragons.
If you're lucky, the salt modules documentation will stipulate a requirement. For example, see the note on salt.modules.gpg.
In most cases, a problem can be pinned down by reading stacktraces in/var/log/salt/minion.Here are some modules that I bang my head against frequently.
gpg
- install gpg
- install python-gpg to saltstack's python interpreter
pip
Most of my problems here come from:
- salt using the global python installation rather than a virtualenv
- my package manager installing a newer package than salt supports.
Unfortunately this is a moving target, so pinning packages becomes a bit of a headache. ungh.
Verify using logs:
/var/log/salt/minion
