I had used your brew tap formula before and had everything running with homebrew.
something has broke and I can't figure out what.
mining with mixture of blades and usb BE has been fine for 30+ days.
24+ hours ago blade mining broke with bfgminer. the PXY all show as SICK. I have tried on two different mac's with same result.
The mac's, blades, router are all in the same switch. I can ping the blades and configure them from the either mac.
I have powered everything off and back on.
I ripped out brew and reinstalled.
I noticed in the brew install of bfgminer
==> Installing bfgminer dependency: curl
==> Downloading
http://curl.haxx.se/download/curl-7.34.0.tar.gzAlready downloaded: /Library/Caches/Homebrew/curl-7.34.0.tar.gz
==> ./configure --prefix=/usr/local/Cellar/curl/7.34.0
==> make install
==> Caveats
This formula is keg-only, so it was not symlinked into /usr/local.
Mac OS X already provides this software and installing another version in
parallel can cause all kinds of trouble.
Generally there are no consequences of this for you. If you build your
own software and it requires this formula, you'll need to add to your
build variables:
LDFLAGS: -L/usr/local/opt/curl/lib
CPPFLAGS: -I/usr/local/opt/curl/include
==> Summary
🍺 /usr/local/Cellar/curl/7.34.0: 75 files, 2.0M, built in 2.1 minutes
then noticed this in a debug log of bfgminer
[2014-01-01 16:30:57] No devices detected!
[2014-01-01 16:30:57] Waiting for devices; press 'M+' to add, or 'Q' to quit
[2014-01-01 16:30:57] Probing for an alive pool
[2014-01-01 16:30:57] Testing pool stratum+tcp://mint.bitminter.com:443
===>> [2014-01-01 16:30:57] HTTP request failed: Protocol stratum+tcp not supported or disabled in libcurl
[2014-01-01 16:30:57] Failed to connect in json_rpc_call
[2014-01-01 16:30:57] initiate_stratum with sockbuf=0x0
although with bfgminer running, I can open a web page to the ip of the mac localhost:8332 and get a login request then a work to solve
{"error":null,"result":{"target":"ffffffffffffffffffffffffffffffffffffffffffffffffffffffff00000000","data":"000000021357b4f4e1de19a52a54e5f2f406556706921cdc5793f5d6000000010000000082eb8f9
85bb972edb3cff59b05692cc0b2c9fb49a289533324bd3599253baa4552c4ae481903a30c000000
0000000080000000000000000000000000000000000000000000000000000000000000000000000
0000000000080020000","midstate":"a20eac8b68b458f89803a1b00b3c9a1f4972b05b660ff4312e964fc94cb85f6d","hash1":"0000000000000000000000000000000000000000000000000000000000000000000000800000000
0000000000000000000000000000000000000000000010000"},"id":0}
and if I leave out the --http-port 8332 I get no response to localhost:8332 so even though there are those error messages, it must be taking requests at 8332 ?
I even fired up a parallels windows 7 / installed win32 bfgminer and get the same results. i.e SICK for the blade now pointed to the parallels virtual running bfgminer (interface in bridge and firewall rule in windows to allow 8332)
Thanks for any assistance i this hair pulling session.