highspeed

Members
  • Posts

    19
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

highspeed's Achievements

Newbie

Newbie (1/14)

2

Reputation

  1. Got the machine up and running. Noticing a nice performance increase on 6.7.2. Thanks a bunch!
  2. Great, thanks for the replies. The config in go is ancient stuff I was clearing out. I guess I cleared out a little too much. Does anyone have a copy of a clean go file for 6.7?
  3. Any ideas? Not sure where to look here.
  4. I have an install that's been neglected for some time. I believe it was on 6.1.x. Decided to bring it current, so hopped to 6.3.5, which seemed to work fine, then to 6.7.2 after which I get connection refused on port 80 and 443. I've attached a diagnostics file. Any help would be greatly appreciated. tower-diagnostics-20190731-2051.zip
  5. I've just noticed in my logs that the virtual interfaces in docker appear to be going into a blocking mode, then cycling back to forwarding: Feb 28 12:54:11 NAS kernel: docker0: port 2(vethd01f0ec) entered disabled state Feb 28 12:54:12 NAS kernel: docker0: port 2(vethd01f0ec) entered disabled state Feb 28 12:54:12 NAS kernel: device vethd01f0ec left promiscuous mode Feb 28 12:54:12 NAS kernel: docker0: port 2(vethd01f0ec) entered disabled state Feb 28 12:54:16 NAS kernel: docker0: port 2(veth1a33bbc) entered blocking state Feb 28 12:54:16 NAS kernel: docker0: port 2(veth1a33bbc) entered disabled state Feb 28 12:54:16 NAS kernel: device veth1a33bbc entered promiscuous mode Feb 28 12:54:16 NAS kernel: docker0: port 2(veth1a33bbc) entered blocking state Feb 28 12:54:16 NAS kernel: docker0: port 2(veth1a33bbc) entered forwarding state Feb 28 12:54:16 NAS kernel: docker0: port 2(veth1a33bbc) entered disabled state Feb 28 12:54:18 NAS kernel: eth0: renamed from veth12e0e95 Feb 28 12:54:18 NAS kernel: docker0: port 2(veth1a33bbc) entered blocking state Feb 28 12:54:18 NAS kernel: docker0: port 2(veth1a33bbc) entered forwarding state This appears to be happening on multiple ports about every hour or two. Does anyone have experience with this?
  6. FYI, modbus is now supported as of unRAID 6.3.1. They also bumped the build to the latest 3.14.14. Thanks, Lime-Tech!
  7. I wanted to confirm that modbus is now supported as of unRAID 6.3.1. They also bumped the build to the latest 3.14.14. Thanks, Lime-Tech!
  8. For those interested, I created a slackbuild for unRAID that includes the --modbus-usb flag. You can put it in /boot/extra and it will overwrite the LT-supplied binary at boot, providing modbus support and upgrading to the latest apcupsd 3.14.14 http://alpineapiaries.com/hosted_files/apcupsd-3.14.14-x86_64-1.txz
  9. APC is starting to support the open modbus protocol over USB in their Smart-UPS line. In the newest devices, modbus provides much more data than the proprietary protocol that the USB interface uses by default in apcupsd. I think as more users start purchasing these modbus-enabled APC devices, this feature will be a very helpful addition to unRAID. In order to support this new protocol, apcupsd needs to be built with the './configure --modbus-usb' flag. The binary in unRAID as of version 6.1.9 does not appear to have been built with this flag. I'd like to request that this be included in future versions of unRAID. Thanks!
  10. Unfortunately, I don't think the RS series supports modbus. Modbus has been added mainly to their "Smart-UPS" line, and even then only the very latest firmware. Devices older than ~2013 generally won't support it at all. The main difference is that modbus is an open protocol, allowing better support for third-party monitoring of the UPS by things like unRAID(apcupsd). In my case I have an SMT750 that provided only very basic information over USB. I couldn't even see load percent: APC : 001,027,0653 DATE : 2016-09-19 19:14:17 -0600 HOSTNAME : NAS VERSION : 3.14.14 (31 May 2016) slackware UPSNAME : NAS CABLE : USB Cable DRIVER : USB UPS Driver UPSMODE : Stand Alone STARTTIME: 2016-09-19 19:14:09 -0600 MODEL : Smart-UPS 750 STATUS : ONLINE BCHARGE : 100.0 Percent TIMELEFT : 40.0 Minutes MBATTCHG : 30 Percent MINTIMEL : 10 Minutes MAXTIME : 0 Seconds ALARMDEL : 30 Seconds BATTV : 27.1 Volts NUMXFERS : 0 TONBATT : 0 Seconds CUMONBATT: 0 Seconds XOFFBATT : N/A STATFLAG : 0x05000008 MANDATE : 2013-03-04 SERIALNO : AS1310110083 NOMBATTV : 24.0 Volts FIRMWARE : UPS 09.3 / ID=18 END APC : 2016-09-19 19:14:18 -0600 After enabling modbus, I'm able to collect much more data: APC : 001,039,0902 DATE : 2016-09-19 19:11:58 -0600 HOSTNAME : NAS VERSION : 3.14.14 (31 May 2016) slackware UPSNAME : APCUPS CABLE : USB Cable DRIVER : MODBUS UPS Driver UPSMODE : Stand Alone STARTTIME: 2016-09-17 20:28:53 -0600 MODEL : Smart-UPS 750 STATUS : ONLINE LINEV : 122.4 Volts LOADPCT : 17.5 Percent LOADAPNT : 14.3 Percent BCHARGE : 100.0 Percent TIMELEFT : 41.0 Minutes MBATTCHG : 30 Percent MINTIMEL : 10 Minutes MAXTIME : 0 Seconds OUTPUTV : 122.4 Volts DWAKE : 0 Seconds DSHUTD : 90 Seconds ITEMP : 28.8 C BATTV : 27.1 Volts LINEFREQ : 60.0 Hz OUTCURNT : 0.88 Amps NUMXFERS : 0 TONBATT : 0 Seconds CUMONBATT: 0 Seconds XOFFBATT : N/A SELFTEST : OK STATFLAG : 0x05000008 MANDATE : 2013-03-04 SERIALNO : AS1310110083 BATTDATE : 2013-03-04 NOMOUTV : 120 Volts NOMPOWER : 500 Watts NOMAPNT : 750 VA FIRMWARE : UPS 09.3 / 00.4 END APC : 2016-09-19 19:12:00 -0600 The main factor for me was that I wanted to see realtime load in watts and percent utilization. The good news is it looks like your RS 900G gives quite a bit of data over the standard USB protocol. More than my SMT750 did.
  11. UPDATE: I got this figured out. I found that apcupsd needs to be built with the './configure --modbus-usb' flag in order to enable this functionality. It doesn't appear that the binary in unRAID was built like this. For anyone wanting modbus over USB, I used a full slackware dev system to build a package with the correct flags. I'd be happy to share it. I've got it sitting in /boot/extra for now and it works great.
  12. Man, you're on a roll tonight Thanks for looking into that.
  13. Running unRAID 6.1.9 w/ an APC SMT750 running the latest 9.3 firmware. modbus is enabled on the UPS front panel. Connecting via USB I can get limited info in unraid by setting cabletype and upstype to "usb". When I switch to upstype to "modbus" communication is lost. Has anyone been able to use modbus over USB on any UPS platform? I suspect there may be an issue with the implementation of apcupsd on unRAID. Bonus: Has LT upgraded to the latest 3.14.14 version of apcupsd in 6.2? There are some fixes specific to modbus: https://sourceforge.net/p/apcupsd/svn/HEAD/tree/tags/Release-3_14_14/ReleaseNotes
  14. I don't think this is a 6.2 issue. I rebooted my server running 6.1.9 and now am seeing the same thing. 2016-09-15 20:26:33 [iNFO] *** Install Initiated *** 2016-09-15 20:26:33 [iNFO] Installing BitTorrent Sync... 2016-09-15 20:26:34 [iNFO] Updating dependencies 2016-09-15 20:26:34 [iNFO] No dependencies required for this application 2016-09-15 20:26:34 [iNFO] Updating export file 2016-09-15 20:26:34 [iNFO] Updating shorcut file 2016-09-15 20:26:36 [iNFO] Latest version found: 2.4.0 - Checking USB for same install file 2016-09-15 20:26:36 [iNFO] Copy found on USB, checking for MD5 file 2016-09-15 20:26:36 [iNFO] Located MD5 file - Testing against install file 2016-09-15 20:26:37 [iNFO] MD5 of Btsync-PhAzE-2.4.0-x64.tar.gz is valid - Proceeding with install 2016-09-15 20:26:37 [iNFO] Updating application directories 2016-09-15 20:26:37 [iNFO] Updating application config file 2016-09-15 20:26:37 [ERROR] Install failed: App executable not found