You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
It's impossible to load any Python.d plugin due to the header of those scripts which uses which to find a path to python or python2 or python3, it throws a which: command not found in the error.log.
To Reproduce
Steps to reproduce the behavior:
Install netdata, enable Python plugins.
Set an error log.
Run. Look at the error log and look at the web interface, no Python.d plugins and the above-mentioned error.
Expected behavior
Netdata should run Python.d plugins fine.
Additional context
It seems like previous issues like this already existed, I suppose this behavior was introduced during an unproperly tested upgrade of the package. I don't know how to rollback nixpkgs easily so I cannot bisect to find the root cause.
Describe the bug
It's impossible to load any Python.d plugin due to the header of those scripts which uses
which
to find a path to python or python2 or python3, it throws awhich: command not found
in the error.log.To Reproduce
Steps to reproduce the behavior:
Expected behavior
Netdata should run Python.d plugins fine.
Additional context
It seems like previous issues like this already existed, I suppose this behavior was introduced during an unproperly tested upgrade of the package. I don't know how to rollback nixpkgs easily so I cannot bisect to find the root cause.
Metadata
Maintainer information:
The text was updated successfully, but these errors were encountered: