dmacias

No. Those are actual ipmi events from your system's bmc. It's from the event monitor. Ipmitool uses ipmievd (ipmi event daemon) to monitor the ipmi event log. Any ipmi events are put in unRAID's system log. I assume the second warning is if you ran a test event from the command line (ipmitool event 1) since there's no sensor number listed. Also along side the event daemon, a system log tail is run checking for ipmi events. If you have notifications setup in unRAID's settings you can also receive webgui or notifications like pushbullet. Freeipmi is used in the newer version using its ipmiseld (ipmi system event list daemon) the same way plus some other features. I need to write a script to automatically remove the old plugin and install the new on upgrade.

Yes. The first notice is that your CMOS battery is low and probably needs replacing. The second looks like a test event. Also I noticed that you are running the old plugin. I switched the name to just ipmi.plg and dropped ipmitool for freeipmi. I would uninstall the plugin then install the link in the original post. You'll have to setup everything again though.

A little bit of an update.

iperf3. You can always use the tab key from the CLI to fill in command or file names. And tab again to get a list of matches.

Thanks for the feedback. I knew about the footer (I don't remember if it worked before or not). I didn't want to spend much time on it since that version of the plugin is really a month or two old. I wanted to fix the webgui lag issue right away in case someone without ipmi or with a vm installs the plugin again. Everything works in the current version I'm working on. Including fan control for select ASRock boards only, ipmi configuration editor (like the vm xml editor) and a few other fixes and extras. I just need to finish a couple more things.

I think there's just something I missed in checking for local ipmi. There's a long timeout for freeipmi. Go to the command line and try ps aux | grep ipmi and ps aux | grep php. Killall ipmi and killall php Then setup networking. Already removed the plugin manually from the flash drive to get my system back online. But thanks. I just tried from scratch and I get the same. I thought I had fixed it. If you try again you can just "killall php" a couple of times from the command line to get the webgui back then just setup networking. Once network ipmi is setup the problem is gone. I'll work on a fix when I get home.

I think there's just something I missed in checking for local ipmi. There's a long timeout for freeipmi. Go to the command line and try ps aux | grep ipmi and ps aux | grep php. Killall ipmi and killall php Then setup networking.

That's the old ipmi-plugin. Remove that and install the one from the first post.

Under the Settings/IPMI menu. Or click settings from the Tools/IPMI menu

You should be able to show any temp or fan that's available through ipmi in the footer of the webgui. You just have to set up ip, username and password to the ipmi interface then select the sensors you want shown. Make sure you're using the ipmi.plg from the original post.

I got mine out along time ago. I'll see if I can push a new version of the old plugin that notifies to uninstall it and install the new. Or try again to automatically uninstall the old and install the new plugin through the plugin system.

Make sure your bmc is using the latest firmware. Usually different than bios and can be updated through the board's ipmi web interface. I assume you're using the latest version of the plugin. The ipmi.plg from the original post and not the previous ipmitool-plugin. I would delete the /boot/config/plugins/ipmi directory too. So no sensors are selected for display in the footer and no monitoring enabled. No errors in the system log? Are you using local or network based? If local, try enabling network with the ip of your bmc, username and password. If that works there might be a problem communicating with ipmi through the kernel driver. The plugin checks for modprobe ipmi_si success but if that works and there are communication errors, freeipmi doesn't have an adjustable timeout for local connections like ipmitool did. I think it's 20 sec. Try running the commands from the command prompt (ipmi-sensors, ipmi-sel, ipmi-fru) and see if they lag. Also if you install the plugin and it's lagging run "ps aux | grep ipmi" and "pd aux | grep php" from the command line and see if anything from the plugin is holding up the webgui/emttp. That's all I can think of right now. Let me know. Edit: And I hope everything's ok

You can add temps and fans to the bottom of the webgui.

I applied the warm reset, and then set it to optimal using the command above, and my fans lowered, and don't seem to be cycling. I'll keep an eye on this and see how it goes. Thanks for the info. I'll incorporate this into the current fan control script I've been testing. And add a reset button.

If the board in your sig is what you are using, I don't believe you have ipmi. You can go to the command line and type ps aux | grep ipmi pe aux | grep php Then killall the processes. How can i kill what? Run those commands from the command line and let me know what the result is. ps aux | grep php: 16938 0.0 0.0 5100 1720 pts/0 S+ 03:36 0:00 grep php ps aux | grep ipmi: 17208 0.0 0.0 5100 1676 pts/0 S+ 03:36 0:00 grep ipmi I'm not sure. Nothing from this plugin is running. Maybe try a different browser or crtrl-f5 in the browser. If you run diagnostics from the command line and post the diagnostics zip here I'll take a look.

If the board in your sig is what you are using, I don't believe you have ipmi. You can go to the command line and type ps aux | grep ipmi pe aux | grep php Then killall the processes. How can i kill what? Run those commands from the command line and let me know what the result is.

If the board in your sig is what you are using, I don't believe you have ipmi. You can go to the command line and type ps aux | grep ipmi pe aux | grep php Then killall the processes.

Thanks for all the info and testing saarg and cyriouslydylan. You can reset the bmc without having to pull the plug. bmc-device --warm-reset Also saarg, I think group commands would be the most beneficial. Since FANA&B are usually CPU, group 1 could be throttled based on drive temps.

hmm nope, looks like they are still sitting at 1900, 1400, and 1300: root@NeverlandUNRAID:~# ipmi-raw 00 30 45 01 02 rcvd: 45 00 root@NeverlandUNRAID:~# ipmi-sensors -t fan ID | Name | Type | Reading | Units | Event 607 | FAN1 | Fan | 1900.00 | RPM | 'At or Above (>=) Upper Critical Thresh old' 674 | FAN2 | Fan | 1400.00 | RPM | 'OK' 741 | FAN3 | Fan | N/A | RPM | N/A 808 | FAN4 | Fan | 1300.00 | RPM | 'OK' 875 | FANA | Fan | N/A | RPM | N/A root@NeverlandUNRAID:~# ipmi-sensors -t fan ID | Name | Type | Reading | Units | Event 607 | FAN1 | Fan | 1900.00 | RPM | 'At or Above (>=) Upper Critical Threshold' 674 | FAN2 | Fan | 1400.00 | RPM | 'OK' 741 | FAN3 | Fan | N/A | RPM | N/A 808 | FAN4 | Fan | 1300.00 | RPM | 'OK' 875 | FANA | Fan | N/A | RPM | N/A I would try adjusting your thresholds with the ipmi-sensors-config command again. Your upper critical is set too low. Should be 2000 or higher given your fan speed. A thresh too low can cause fans to rev up too. Any error or bad fan and they all rev up.

Then try ipmi-raw 00 30 45 01 00

This one might work ipmi-raw 00 30 45 01 02

I'd love to test these out for you, I'm just unfamiliar with how to do so. Where can I implement these and report back to you. That same config file you had me export earlier? The ipmi-sensors-config command it's only for config options. I won't change fan speeds. If your drives are hot with fans at full speed, I'd look at the air flow in the case and over the drives. The ipmi-raw commands are entered in the command line. So you'd have to run one of the commands, it should give a received response or error and then see if the fans respond as intended. You can run ipmi-sensors -t fan to check fan speeds. The fans weren't running at full speed, which is why the HD temp was spiking. I just used ipmi-raw 00 30 45 01 01 and it put them all up to full speed, worked perfectly. If I want to use your temperature-dependent commands I just put this into the command line like so? if ($max_temp > 39) { # at least one hard drive is 40 deg C or higher # set fan speed control to Full `ipmi-raw 00 30 45 01 01` } elsif ($max_temp == 39 ){ # maximum drive temperature is 39 deg C # set fan speed to 50% duty cycle `ipmi-raw 00 30 70 66 01 00 32` } else { # all hard drive temperatures are 38 deg C or cooler # set fan speed control to Optimal `ipmi-raw 00 30 45 01 02` } Nice. Did you try any other commands? What board do you have? Also what does ipmi-fru display? That was an excerpt from a script I found. Just examples to try. But I can add functionality to my ipmifan script if we can figure out the right codes. It would be nice if this command could control particular fans. Maybe if you change the 00 32 to 01 32 or 02 32. You could try setting it to 64 for full fan speed too. ipmi-raw 00 30 70 66 01 00 32

I'd love to test these out for you, I'm just unfamiliar with how to do so. Where can I implement these and report back to you. That same config file you had me export earlier? The ipmi-sensors-config command it's only for config options. I won't change fan speeds. If your drives are hot with fans at full speed, I'd look at the air flow in the case and over the drives. The ipmi-raw commands are entered in the command line. So you'd have to run one of the commands, it should give a received response or error and then see if the fans respond as intended. You can run ipmi-sensors -t fan to check fan speeds.

Thanks. I wonder how the 0 byte file got there though. It checks the sha1 and deletes the file if the download fails. I'll check the packages during install too.

Thanks. What failed exactly.