Failed to initialize the OEM info dictionary - ipmitool 1.8.19 - MacOS Ventura 13.01 #383
Comments
|
Thanks Vincent - removing (in my case on a Mac) /usr/local/Cellar/ipmitool/1.8.19/share/misc/enterprise-numbers did allow it to run, albeit with the 'No such file or directory' error. Will the new IANA text/html format be rolled into a new release - if that resolves #377 shouldn't it have been included in the #382 fix? Or am I not pulling the latest release via brew? Geoff |
AFAIK, the format didn't change, just the URL at which IANA was providing the file did. That was done after 1.8.19 so that version is "broken" until the next tagged release. #382 resolves related issues. The fact that 1.18.19 works with a non-existent file currently is a happy accident I think, so that PR makes the behavior more uniform. It also allows for ipmitool to run if the registry file exists but is malformed. |
|
the other option is fetching the file and replacing your current one from https://www.iana.org/assignments/enterprise-numbers/enterprise-numbers |
|
I guess it's always something. Thanks for the link to the text version of the PEM file! That seems to work fine with 1.8.19 |
|
Just curious - I've been looking at earlier/older ipmitool installs and there does not seem to be a standalone enterprise-numbers files |
It was generated at compile time in previous versions bd0475c#diff-931d169ad902f26c93a6af265b3bbcc571a975737f85e33ce66dea285d4d2d60L53 |
|
DId anyone in this thread get this working? If so what did you do? I've tried every workaround I can find to try. This broke for my entire team. |
You can either remove the malformed file or you can download the IANA PEN registry file and place it in the proper path. #383 (comment) I don't fiddle with MacOS, but you can probably do an strace to find which file paths it's looking in to open the file. Otherwise, this should be fixed once my PR is accepted and a new version is released |
|
Yes, as posted earlier I have it working - I have a MacOS brew install and
my path was /usr/local/Cellar/ipmitool/1.8.19/share/misc/enterprise-numbers
- replacing it with the text file from
https://www.iana.org/assignments/enterprise-numbers/enterprise-numbers
resolved the issue for now (thanks Vincent!)
Geoff
…On Fri, Dec 16, 2022 at 11:14 AM Vincent Fazio ***@***.***> wrote:
DId anyone in this thread get this working? If so what did you do? I've
tried every workaround I can find to try. This broke for my entire team.
You can either remove the malformed file or you can download the IANA PEN
registry file and place it in the proper path. #383 (comment)
<#383 (comment)>
I don't fiddle with MacOS, but you can probably do an strace to find which
file paths it's looking in to open the file.
Otherwise, this should be fixed once my PR is accepted and a new version
is released
—
Reply to this email directly, view it on GitHub
<#383 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEEAJBVBQZL3OBRIGRKETU3WNSIOXANCNFSM6AAAAAAS36RB3U>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
reported to brew as Homebrew/homebrew-core#118705 |
Using Brew on MacOS Ventura 13.01 ipmitool was updated to 1.8.19 - i did not note the exact version prior to the upgrade.
Now any ipmitool command fails with the error:
Failed to initialize the OEM info dictionary
i.e.
ipmitool -I lanplus -H x.x.x.x -U abc123 -P abc123 chassis power status
Failed to initialize the OEM info dictionary
ipmitool -I lanplus -H x.x.x.x -U abc123 -P abc123 fru print 3
Failed to initialize the OEM info dictionary
The text was updated successfully, but these errors were encountered: