-
Notifications
You must be signed in to change notification settings - Fork 1
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
Some Pools Return "Code: 2 - Msg: Misuse of shell builtins" #8
Comments
According to RedHat, a command or keyword is missing from a shell call. |
Hm, sounds a little complex. Any chance I could get the output of Sounds like something in the performance template is probably going wrong, too, but almost all of the commands are shared between the pool modeler and templates:
Now I'm wondering if there's a TALES evaluation that's failing. If you manually model the server in question in the web UI, are there any lines about that? I'm going off the assumption that zZFSExecPrefix is an empty string in this instance but the *BinaryPath zProperties are default or otherwise non-empty? |
So in the UI modeler, it just says
the manual run does contain serial #s of drives, so kind of a PITA to clean up, but contains no errors, only tons of missing attribute complaints a la |
I'm thinking the Without seeing what command output's making its way to the modeler/template, it's going to be difficult to troubleshoot. Could you send a screenshot of the event details from the |
I've updated the command templates a bit, mind trying the latest commit and seeing if it helps this issue? Do the pools throwing |
I'm seeing a host with 4 pools - single vdev rpool, raidz1 pool, another raidz1, and a 5-wide span of 2-disk mirrors with a SLOG mirror and a 2-diskL2ARC span, only return data for two of the pools (rpool and a raidz1). The other two pools show up as having a warning of
Code: 2 - Msg: Misuse of shell builtins
and no pool state whatsoever. The "stateless" pools VDEVs are not accounted for, nor are their comprising storage devices.The host systems are Arch Linux (so tip bash), its sudoless as root (isolated env), and the ZFS revision is 2.0.0.
The text was updated successfully, but these errors were encountered: