-
Notifications
You must be signed in to change notification settings - Fork 64
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
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory #27
Comments
Hello, |
I used the command on the README.md file here, but with my own values:
I never tried the docker-compose, as it didn't seem like starting the container was the issue, only connecting to the local iDRAC devices. I ended up writing my own script using ipmitools directly and putting it in cron and it works. |
I think it's just a typo that crept into the README. On your Dell PowerEdge Docker host, check your IPMI interface name using : ls /dev/ipmi* Then adapt the IPMI interface name, if necessary, in the following docker run -d \
--name Dell_iDRAC_fan_controller \
--restart=unless-stopped \
-e IDRAC_HOST=local \
-e FAN_SPEED=0x0f \
-e CPU_TEMPERATURE_TRESHOLD=55 \
-e CHECK_INTERVAL=60 \
--device=/dev/ipmi0:/dev/ipmi0:r \
tigerblue77/dell_idrac_fan_controller:latest Tell me if it works so that I update the README file. |
Same error.
My device is at /dev/ipmi0, and like I said I currently have a script utilizing ipmitools directly and it works, so I'm not sure what the problem is. |
I think the IPMI interface is not made available inside your container. I can suggest you two tests:
and/or
|
Yeah, I can confirm that it's a problem with accessing the ipmi device from within the docker container. I'm not too worried about it, it's something to look into later. Thanks for the help. |
Okay, glad that it helped. Don't hestitate to tell here if you have any other information. |
That fix didn't work. Running the script outside of the container worked. It's probably a problem with my setup more than with your container or script. I've not done any real configuration on this server beyond throwing Ubuntu on it for some game servers. |
Btw, I decided to take another shot at this and use docker-compose (which I hadn't tried before) and it doesn't give me the device error anymore. It does still give me the bad value fan percentage error though:
Seems to be a printing error only, as the actual fan speed works properly. |
Which Dell PowerEdge server are you running ? Can you add |
I had time to investigate about this fix and found what was wrong : my script needs both read and write permissions on IPMI device so I'll just wait your feedback about the second error that you encounter. |
I am running a PowerEdge R420. No need to add echos to the script, I can confirm with ipmitool that my server doesn't report an exhaust temperature. Since the |
Same issue, the only temp my r710 ipmi can read is Ambient. |
Okay so you are talking about another issue which is already known. Please check this Github issue which I already worked on and corresponds to your problem. I'm just waiting for some people to test my fix before merging it. |
Same answer as previous message, please check this Github issue which I already worked on and corresponds to your problem. I'm just waiting for some people to test my fix in PR #40 before merging it. About using |
Trying to run this container gives me two errors, the one in the title, and one saying my fan speed is invalid (despite correctly interpreting it as 15%).
I assume the first error is leading to the second. I've tested using ipmitools and they can connect to the local ipmi device just fine. Any help would be appreciated.
The text was updated successfully, but these errors were encountered: