cadamwil

Members
  • Posts

    27
  • Joined

  • Last visited

About cadamwil

  • Birthday March 1

Converted

  • Gender
    Male
  • Location
    Nashville, TN

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

cadamwil's Achievements

Newbie

Newbie (1/14)

5

Reputation

  1. Vr2lo, looks like I am kinda screwed on this one. My APC ups is new enough it uses "Microlink" technology and won't talk to much of anything except APC drivers. I guess I could load them into unraid, but it seems like a giant pain for little reward. Anyone want to trade a SMX3000RMLV2UNC for an eaton 5PX/SX or 9PX/SX 1500 or greater?
  2. so I have tried two different methods of connections. An AP940-0625A connected from the serial port and USB A to USB B. I can't seem to get either to work. My older SMT1500 worked just fine. When the new one is hooked up via USB to windows or Linux, it shows USB-HID connected. I have verified both ports, serial or USB work correctly on windows. I really can't understand why this isn't working over anything on UnRAID. My suspicion is something isn't right on the USB driver. However, I don't have a clue why the serial doesn't work. I just tried SNMP and I do have that working. It doens't show nominal power or UPS load, but at least it's working. Any ideas on serial troubleshooting?
  3. so mine doesn't say refreshing, mine just states lost communication. I have verified that the UPS works fine over USB to windows, and I have been able to update it over the APC AP940-0625A cable. I now have both the serial (AP940-0625A) plugged into the serial port on my server and the USB plugged in as well. I have now tried UPSCABLE = Smart / UPSTYPE = MODBUS / PORT=/dev/ttyS0, UPSCABLE = USB / UPSTYPE = USB and UPSCABLE = USB / UPSTYPE = MODBUS. None seem to work. When I have it set to UPSCABLE = Smart / UPSTYPE = MODBUS / PORT=/dev/ttyS0 and run apctest I get the following output 2021-01-29 23:01:33 apctest 3.14.14 (31 May 2016) slackware Checking configuration ... sharenet.type = Network & ShareUPS Disabled cable.type = Custom Cable Smart mode.type = MODBUS UPS Driver Setting up the port ... 0.547 apcupsd: ModbusRs232Comm.cpp:219 ModbusRx: -------------------TIMEOUT 1.091 apcupsd: ModbusRs232Comm.cpp:219 ModbusRx: -------------------TIMEOUT 1.638 apcupsd: ModbusRs232Comm.cpp:219 ModbusRx: -------------------TIMEOUT 1.638 apcupsd: ModbusComm.cpp:212 SendAndWait: Retries exhausted 2.184 apcupsd: ModbusRs232Comm.cpp:219 ModbusRx: -------------------TIMEOUT 2.729 apcupsd: ModbusRs232Comm.cpp:219 ModbusRx: -------------------TIMEOUT 3.275 apcupsd: ModbusRs232Comm.cpp:219 ModbusRx: -------------------TIMEOUT 3.275 apcupsd: ModbusComm.cpp:212 SendAndWait: Retries exhausted When set to UPSCABLE = USB / UPSTYPE = USB and I run apctest, I get the following 2021-01-29 23:02:46 apctest 3.14.14 (31 May 2016) slackware Checking configuration ... sharenet.type = Network & ShareUPS Disabled cable.type = USB Cable mode.type = USB UPS Driver Setting up the port ... apctest FATAL ERROR in apctest.c at line 321 Unable to open UPS device. If apcupsd or apctest is already running, please stop it and run this program again. apctest error termination completed Lastly, when set to UPSCABLE = USB / UPSTYPE = MODBUS and I run apctest, I get the following 2021-01-29 23:05:16 apctest 3.14.14 (31 May 2016) slackware Checking configuration ... sharenet.type = Network & ShareUPS Disabled cable.type = USB Cable mode.type = MODBUS UPS Driver Setting up the port ... apctest FATAL ERROR in apctest.c at line 321 Unable to open UPS device. If apcupsd or apctest is already running, please stop it and run this program again. apctest error termination completed root@Beast:~# apctest I also verified that no apcupsd process was running using "ps aux | grep apcupsd" Any thoughts?
  4. May be getting somewhere now. When I plug in the UPS, I get the following message in the log. Jan 27 19:51:16 Beast kernel: usbhid 3-2:1.0: can't add hid device: -71 Jan 27 19:51:16 Beast kernel: usbhid: probe of 3-2:1.0 failed with error -71 Any ideas? Is this the issue?
  5. Hello All, When I plug in my new UPS (APC SMX3000RMLV2UNC), I get the messages below in the log file. I cannot configure apcupsd to use it. Any suggestions? I have tried both sets of USB ports on the server. USB cable works properly on windows. I have updated the firmware of the UPS to the most current. Jan 27 20:05:15 Beast kernel: usb 3-11: USB disconnect, device number 7 Jan 27 20:05:16 Beast kernel: usb 3-11: new full-speed USB device number 8 using xhci_hcd Jan 27 20:05:17 Beast kernel: usbhid 3-11:1.0: can't add hid device: -71 Jan 27 20:05:17 Beast kernel: usbhid: probe of 3-11:1.0 failed with error -71
  6. That was false, not working at all.
  7. Another small detail, seems to be partially working. My "lost communications" alerts include my name for the UPS
  8. so, I can ssh to it from my unraid server and modbus & snmp are enabled. https, snmpv3 are also enabled. Any suggestions would be greatly appreciated. none of the apcupsd, apcaccess nor apctest seem to work, no matter what the settings. How can I manually test the hid device on USB or Powerchute (PCnet)?
  9. Hello, I have an SPC Smart UPS X 3000, and I can't seem to get UnRAID to see the UPS. My previous old APC SMT1500 worked fine, but I can't get my new one talking. I have tried over the network and over USB. Is there a manual console walkthrough I could follow to establish the device. I have found that it's usb Bus 3, Device 2. But I'm stuck at determining which /dev/?? it would be or how I could talk to it to verify operation like over putty.
  10. Well, apparently not having a fan in FANA or hiding FANA was the issue. Now everything is working well.
  11. OK, got everything close to working, however, I'm missing my ABC fans on my Supermicro X10 motherboard. It's just showing the 1234. Can I just add the lines to the fan.cfg? Can I get it to detect them? Thanks for your time.
  12. any recommendations for editing smb-extra.conf to see the snapshots as shadow copies in windows? My snapshots look like %PoolName/%dataset@autosnap_%Y-%m-%d_%H:%M:%S_%snaptype with %snaptype being daily, weekly, hourly, or frequently. I tried shadow: format = autosnap_%Y-%m-%d_%H:%M:%S any help would be greatly appriciated.
  13. Just FYI, I think I was having a similar issue to Marshalleq. On RC2, when I stopped the unRAID array, which stopped my VM, restarted the unraid array and attempted to restart my VM, it would hang the VM management page (white bottom, no uptime in unraid) and then if you attempted to reboot, it would not reboot successfully. You would have to reset the machine to reboot. However, with RC4, everything seems to be working correctly.
  14. What's different between RC2-RC4?
  15. the rm -rf mounting point got it. Thanks again!