imthekuni

I've been having issues with backups taking forever and/or cleaning up never finishing. I tried to make an AFPS formatted sparse bundle instead and it is much faster and seems to be working "better". Interestingly, during this process my NAS Time Machine folder actually showed up as a destination and allowed me to make a backup there without creating a sparse bundle. I am on macOS 12.0.1.

You're a life saver! Running the first backup now, but looks like it all worked great.

I did a little bit of troubleshooting in the meantime. I noticed that ipmisensors just pulls info from the ipmi.cfg file and passes it to /usr/sbin/ipmisensors via: [ $NETWORK == "enable" ] && OPTIONS=" -h $IPADDR -u $USER -p $(echo $PASSWORD | base64 --decode)" That is when I noticed it is expecting the password to be coded as base64. If I code my PW as base64 it prevents the "base64: invalid input" error I saw earlier. However, I still get the "/usr/sbin/ipmi-sensors: connection timeout" error. If I call /usr/sbin/ipmi-sensors directly I see all the correct info, but for some reason calling it from the script results in a timeout. The only for me to get around this was to comment out the network parsing from ipmi.cfg #!/bin/bash CONFIG="/boot/config/plugins/ipmi/ipmi.cfg" OPTIONS="" IGNORED="" # read our configuration [ -e "$CONFIG" ] && source "$CONFIG" #[ $NETWORK == "enable" ] && OPTIONS=" -h $IPADDR -u $USER -p $(echo $PASSWORD | base64 --decode)" [[ $IGNORE != "" ]] && IGNORED=" -R $IGNORE " /usr/sbin/ipmi-sensors $OPTIONS $IGNORED $@ I have confirmed the IPADDR, USER, and PASSWORD (as base64 or not) are correct in the ipmi.cfg, but something about calling it from the script results in the timeout. Using "whoami" from within the script or the command line shows both are being run as root.

Likewise just throws that base64 error. root@Tower:~# /usr/sbin/ipmisensors base64: invalid input /usr/sbin/ipmi-sensors: connection timeout Much appreciated, I will try and figure out how to convert it to the shell script as well.

I recently noticed that the Controlr plugin is stopped. Disabling and enabling it will set the status to Running for a short while, but then it will switch back to stopped after a few seconds. The controlr.log is: I: 2020/12/20 15:52:51 app.go:58: controlr v2020.05.09|2.19.0 starting ... I: 2020/12/20 15:52:51 app.go:66: No config file specified. Using app defaults ... I: 2020/12/20 15:52:51 app.go:171: host(https://192.168.2.250:443) I: 2020/12/20 15:52:51 core.go:81: starting service Core ... I: 2020/12/20 15:52:51 core.go:307: Created ipmi sensor ... I: 2020/12/20 15:52:51 core.go:334: No ups detected ... I have gone through the topic and tried various suggested troubleshooting steps. If I run /usr/local/emhttp/plugins/controlr/controlr -port 2378 -showups (same results if I include the certs argument), I get: I: 2020/12/20 15:54:30 app.go:58: controlr v2020.05.09|2.19.0 starting ... I: 2020/12/20 15:54:30 app.go:66: No config file specified. Using app defaults ... I: 2020/12/20 15:54:30 app.go:266: cert: found Tower_unraid_bundle.pem I: 2020/12/20 15:54:30 app.go:171: host(https://192.168.2.250:443) I: 2020/12/20 15:54:30 core.go:81: starting service Core ... I: 2020/12/20 15:54:30 core.go:307: Created ipmi sensor ... I: 2020/12/20 15:54:30 core.go:325: Created apc ups ... 2020/12/20 15:54:50 Unable to wait for process to finish: exit status 1 /usr/bin/sensors -A is detecting sensors and providing data. /sbin/apcaccess pulls up my UPS info. However, I think there is an issue with creating the ipmi sensors. I do have a /boot/config/plugins/ipmi/ipmi.cfg. When I run /usr/sbin/ipmisensors --comma-separated-output --output-sensor-state --no-header-output --interpret-oem-data I get base64: invalid input /usr/sbin/ipmi-sensors: connection timeout However, if I run /usr/sbin/ipmi-sensors --comma-separated-output --output-sensor-state --no-header-output --interpret-oem-data It pulls all my info as expected 4,CPU Temp,Temperature,Nominal,53.00,C,'OK' 71,System Temp,Temperature,Nominal,32.00,C,'OK' 138,Peripheral Temp,Temperature,Nominal,0.00,C,'OK' 205,PCH Temp,Temperature,Nominal,48.00,C,'OK' 272,P1-DIMMA1 TEMP,Temperature,Nominal,42.00,C,'OK' 339,P1-DIMMA2 TEMP,Temperature,N/A,N/A,C,N/A 406,P1-DIMMB1 TEMP,Temperature,Nominal,41.00,C,'OK' 473,P1-DIMMB2 TEMP,Temperature,N/A,N/A,C,N/A 540,P1-DIMMC1 TEMP,Temperature,Nominal,45.00,C,'OK' 607,P1-DIMMC2 TEMP,Temperature,N/A,N/A,C,N/A 674,P1-DIMMD1 TEMP,Temperature,Nominal,45.00,C,'OK' 741,P1-DIMMD2 TEMP,Temperature,N/A,N/A,C,N/A 808,FAN 1,Fan,Nominal,375.00,RPM,'OK' 875,FAN 2,Fan,N/A,N/A,RPM,N/A 942,FAN 3,Fan,N/A,N/A,RPM,N/A 1009,FAN 4,Fan,N/A,N/A,RPM,N/A 1076,FAN A,Fan,N/A,N/A,RPM,N/A 1143,Vcore,Voltage,Nominal,1.00,V,'OK' 1210,3.3VCC,Voltage,Nominal,3.30,V,'OK' 1277,12V,Voltage,Nominal,11.98,V,'OK' 1344,VDIMM,Voltage,Nominal,1.35,V,'OK' 1411,5VCC,Voltage,Nominal,5.12,V,'OK' 1478,CPU VTT,Voltage,Nominal,1.06,V,'OK' 1545,VBAT,Voltage,Nominal,3.46,V,'OK' 1612,VSB,Voltage,Nominal,3.55,V,'OK' 1679,AVCC,Voltage,Nominal,3.31,V,'OK' 1746,Chassis Intru,Physical Security,Nominal,N/A,N/A,'OK' Any insight is appreciated!