Skip to content
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

Verbose or Debug mode needed #3

Open
zenfish opened this issue Dec 23, 2022 · 0 comments
Open

Verbose or Debug mode needed #3

zenfish opened this issue Dec 23, 2022 · 0 comments

Comments

@zenfish
Copy link

zenfish commented Dec 23, 2022

So kicking the tires... the package looks promising, and it's always good to have new options in the IPMI sphere.

But it's a bit opaque at times... I don't want to have to grep the source the first time or two I'm trying a command.

It'd be great to be able to see more of what's moving to/fro from the host to BMC, both in terms of hidden (e.g. cached) arguments as well as hex codes, with both errors and successful output.

For instance, I run -

pyipmi -H 192.168.0.24 -I lanplus -U ADMIN -U ADMIN lan print 1 PyIntfExcept: Key Exchange Authentication Code is not valid in RAKP 2.

or - perhaps the error PyIntfExcept: Invalid RMCP AuthCode in response when I use the -I lan in the same command. Sure, I was distracted and didn't put in a password and instead used two -U options... but then I get back a couple of mysterious error codes... it's not clear at all what was used as a password, if anything. And when running multiple different -U's, the tool ignores all but the last... yes, this is what ipmitool does, but it's not super user friendly, and since its output isn't the same as ipmitool, you're not doing exactly what it does, so.....

Perhaps echo the command + full args actually used to stderr or something? Or even just when cached values are used (this isn't an issue with ipmitool, since it doesn't cache things.)

If there was a --debug or --hex or whatever option that echoed what was really going back and forth, sort of what ipmitool and others do with the -v -v -v -v -v options, that would have helped me figure out what's going on (admittedly, this wouldn't help many, but hey :))

I'll probably have more comments to come, but thanks for the toolset.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant