dmacias

I can add it. I have 1.8.17 already compiled. What do you use it for? Someone has created a sweat ipmi plugin but it uses freeipmi.

I believe the -h, -u, -p need to be escaped. The new version starts for me but I don't see any ipmi commands

I removed freeipmi package. Still have this errorUnable to wait for process to finish: exit status 1 Removed ipmi plugin and was able to start. Edit: It's probably because I use a network ipmi connection and not the local kernel mods.

I tried that before. This is the output: root@Server:~# /usr/bin/bash -c /usr/local/emhttp/plugins/controlr/controlr -port 2378 -certdir '/boot/config/ssl/certs' -showups I: 2018/01/20 06:23:14 app.go:55: controlr v2.7.1-313-0b63a2b-v2018.01.19a starting ... I: 2018/01/20 06:23:14 app.go:63: No config file specified. Using app defaults ... I: 2018/01/20 06:23:14 core.go:73: starting service Core ... 2018/01/20 06:23:14 Unable to wait for process to finish: exit status 1 root@Server:~# It's the same with your shortened command also

Added. Very colorful.

I compile them or add them from a trusted repo to the NerdPack repo. This isn't the case with borg but sometimes newer packages may conflict with unRAID packages so they aren't updated. In the case of borgbackup, I compiled that myself. I'll try and update that one when I get a chance.

Unless using complete manual mode the conf files are overwritten using info from /boot/config/plugins/nut/nut.cfg. To me it looks like there was something wrong with your nut.cfg, possibly edited with notepad or another editor that isn't compatible with Linux. I'm not sure why moving to 6.4 broke it though. The disconnects are kernel related and I get them to, even on a fresh reboot with no nut. I even had to disable usb3/xhci in the bios. But they should stop after the nut driver connects. You can also set the display settings at the bottom to manual and enter in your UPS values to get an estimation of power used.

No this would create too many support issues and would only partially work. While the basic mp4 download will work any other extraction e.g. mp3 or formatting will require dozens of other packages. I believe there are dockers for this and I saw one for JDowndloader2 too.

Thanks. I fixed the logic and changed the wording

Sorry for the confusion the Alert is actually a Warning so it follows the warnings settings in Notifications. I initially set it up as alerts but I figured should be more of a warning notification. So I'll change it to read Enable Warning Only Notification: But anyway, it will display the failure(s) in the message next to [Fail]. Either Ping, Download and/or Upload failures. The thresholds for download and upload are for the lower limit. So if you speedtest falls below 10 or 5 you'll get a notification.The ping will notify for anything over the ping you specify. Which one is failing? What are the settings when it failed and what are the results?

NerdPack doesn't inherently install anything. You have to go to Settings/NerdPack and select the packages you wish installed and click apply. They will be installed immediately and on reboot. I will put that in the pop-up notification also. In the future I plan on allowing plugins to call NerdPack or the repo to install packages like python2. No need to worry about version.

Thanks. Update went smoothly. I updated from 4.4.17 to 4.4.18 also. I was still having problems with IPS and DPI saying no data on 5.7.12 and 4.4.17. Seems to be working better now.

I'm not sure if that would fix it for you. I just wanted to use DPI and IPS. If you don't want to wait and want to try 5.7.15, download a backup of 5.7.12 from Maintenance on the controller page first and maybe backup your unifi docker appdata also (I didn't). Then just log in to unRAID and run these commands. This will get the deb file and log you into the docker. # your unifi appdata location cd /mnt/cache/appdata/unifi wget https://dl.ubnt.com/unifi/5.7.15-e9b882be05/unifi_sysvinit_all.deb docker exec -ti Unifi bash Then run these in the docker. (wget isn't in the docker so this was the easiest). There will be some post script error but thats fine. cd data/ cp unifi_sysvinit_all.deb /root/ cd ~ dpkg -i unifi_sysvinit_all.deb Then reboot the docker from the unRAID webgui and go to the unifi controller page. The wizard will come up and you can then load your 5.7.12 backup from there. Just remember if you delete and reinstall the docker you'll be back to 5.7.12. Edit: Also I use the CA Auto Update Applications plugin to disable auto updates for the Unifi dockers.

I see what you mean. My Recent Activities is working.

Do you have IPS or Smart Queues enabled? They disable hardware offload and thus DPI doesn't work. There's a beta USG firmware that allows all of them to work. I'm using 4.4.17 and 4.4.18 was just released. In order to get DPI to work again I disabled IPS, turned off Smart Queues and turned off DPI. Waited till my USG4 was provisioned thenclicked reboot from the Devices page. After reboot I turned on DPI again, waited for provisioning then rebooted again. I then turned on IPS. It's been working for a couple days.

I thought the nut commit for the eaton driver in your pull request computed an approximation of ups.realpower.nominal. Do you not get a ups.realpower.nominal variable? Upon further inspection I believe that was for higher end Eaton UPS. The 0.80 powerfactor is also too high for your UPS. You'll have to use the manual option in the Display Settings and enter 650VA and 360W. Edit: I saw your original nut repo issue. And I see he extrapolated the 0.80 from your Eaton companion readings. But 140W @ 27% on a 650VA/360W rated UPS doesn't seem right. That would add up to over 500W at 100%. Is there any way you could measure the actual watts used with a killawatt adapter or similar.

1) fixed 2) I just replaced protocol with whatever is in use 3) I'll have to think about that. Adding another tab would be confusing since it's part of the Scheduler page. Maybe a click on the tab when it's active to go back.

You need to select screen and click apply from the NerdPack settings menu

76% load and 0 watts sounds about right. Should be fixed now.

Ok. added.

I added notifications and alert only notifications. So you can receive a notice for every speedtest or for only speedtest that fall below a certain Mbps or ping. Either one will use the thresholds. I also removed all python 2 packages from the plugin and require NerdPack for python.

I added lbzip2 2.5.

No problem. Not sure how you were logged in but it needs to create a cache in the users home directory. If you were logged in as root you can try deleting /root/.freeipmi. You could also try connecting using the network options. -h ipaddress -u username -p password. Look forward to what you come up with. One other thing that might be useful is that you can't set the timeout for freeipmi commands through the local host. I don't remember how long the timeout is. So if there was an error you could seemingly hang the webgui or your app especially if multiple commands are run. So thanks to[mention=61877]ljm42[/mention] I run this within the plugin to check for local ipmi. ((file_exists('/dev/ipmi0') || file_exists('/dev/ipmi/0') || file_exists('/dev/ipmidev/0')) In case you're wondering why I chose freeipmi over ipmitool or others it's because of the sensor ID variable and you always get a consistent list of variables for each sensor even if a value is missing for that sensor. You'll get a N/A for any missing data.

Nice! Does your board have ipmi? Anyway here's one command I use in the plugin. I added the no header on the second run. The interpret oem data is important for some boards. It may be useful to add a network ip, username and password input. Or I created several bash scripts for the freeipmi commands that pull the info from the ipmi.cfg and accept command-line options just like the regular command. E.g. ipmisensors for ipmi-sensors root@Server:~# ipmi-sensors --comma-separated-output --output-sensor-state --interpret-oem-data ID,Name,Type,State,Reading,Units,Event 4,CPU Temp,Temperature,Nominal,38.00,C,'OK' 71,System Temp,Temperature,Nominal,30.00,C,'OK' 138,Peripheral Temp,Temperature,Nominal,39.00,C,'OK' 205,PCH Temp,Temperature,Nominal,45.00,C,'OK' 272,P1-DIMMA1 Temp,Temperature,Nominal,30.00,C,'OK' 339,P1-DIMMA2 Temp,Temperature,Nominal,31.00,C,'OK' 406,P1-DIMMB1 Temp,Temperature,Nominal,30.00,C,'OK' 473,P1-DIMMB2 Temp,Temperature,Nominal,30.00,C,'OK' 540,FAN1,Fan,Nominal,1100.00,RPM,'OK' 607,FAN2,Fan,Nominal,700.00,RPM,'OK' 674,FAN3,Fan,N/A,N/A,RPM,N/A 741,FAN4,Fan,Nominal,1100.00,RPM,'OK' 808,FANA,Fan,Nominal,300.00,RPM,'OK' 875,Vcpu,Voltage,Nominal,1.84,V,'OK' 942,VDIMM,Voltage,Nominal,1.35,V,'OK' 1009,12V,Voltage,Nominal,12.00,V,'OK' 1076,5VCC,Voltage,Nominal,4.97,V,'OK' 1143,3.3VCC,Voltage,Nominal,3.27,V,'OK' 1210,VBAT,Voltage,Nominal,2.97,V,'OK' 1277,5V Dual,Voltage,Nominal,5.03,V,'OK' 1344,3.3V AUX,Voltage,Nominal,3.28,V,'OK' 1411,1.2V BMC,Voltage,Nominal,1.26,V,'OK' 1478,1.05V PCH,Voltage,Nominal,1.04,V,'OK' 1545,Chassis Intru,Physical Security,Nominal,N/A,N/A,'OK' root@Server:~# ipmi-sensors --comma-separated-output --output-sensor-state --no-header-output --interpret-oem-data 4,CPU Temp,Temperature,Nominal,38.00,C,'OK' 71,System Temp,Temperature,Nominal,30.00,C,'OK' 138,Peripheral Temp,Temperature,Nominal,39.00,C,'OK' 205,PCH Temp,Temperature,Nominal,45.00,C,'OK' 272,P1-DIMMA1 Temp,Temperature,Nominal,30.00,C,'OK' 339,P1-DIMMA2 Temp,Temperature,Nominal,31.00,C,'OK' 406,P1-DIMMB1 Temp,Temperature,Nominal,30.00,C,'OK' 473,P1-DIMMB2 Temp,Temperature,Nominal,30.00,C,'OK' 540,FAN1,Fan,Nominal,1100.00,RPM,'OK' 607,FAN2,Fan,Nominal,700.00,RPM,'OK' 674,FAN3,Fan,N/A,N/A,RPM,N/A 741,FAN4,Fan,Nominal,1100.00,RPM,'OK' 808,FANA,Fan,Nominal,300.00,RPM,'OK' 875,Vcpu,Voltage,Nominal,1.84,V,'OK' 942,VDIMM,Voltage,Nominal,1.34,V,'OK' 1009,12V,Voltage,Nominal,12.00,V,'OK' 1076,5VCC,Voltage,Nominal,4.95,V,'OK' 1143,3.3VCC,Voltage,Nominal,3.27,V,'OK' 1210,VBAT,Voltage,Nominal,2.97,V,'OK' 1277,5V Dual,Voltage,Nominal,5.03,V,'OK' 1344,3.3V AUX,Voltage,Nominal,3.28,V,'OK' 1411,1.2V BMC,Voltage,Nominal,1.26,V,'OK' 1478,1.05V PCH,Voltage,Nominal,1.05,V,'OK' 1545,Chassis Intru,Physical Security,Nominal,N/A,N/A,'OK' root@Server:~# Also you may or may not need the output sensor state. That's the Nominal or N/A

Shutdown modes Battery Level and Runtime Left both require UPS input. Time on Battery does not. So you could use Time on Battery for clients. Either way you could make sure they are set to shutdown before the server shuts down. Direct network connection through SNMP would be best with no server in between.