My SP20 went non-responding yesterday after I added a couple of pools. The web admin GUI never came back after submitting the change, and I could not ssh into the device. It responded to pings, but that was it.
I power cycled the unit and attempted further edits to the pool list. It seemed to work for a little while, then the SP20 hung again.
Operating on a guess that maybe I had specified too many pools, I rebooted again so that I could remove some. Once I saw pings responding, I quickly fired up the web admin GUI and stopped the miner. This allowed me to get back to the pool list and remove a few. Since doing that, the SP20 has run reliably again.
Is there a known problem with too many pools? I had 9 pools specified at the time that the machine went non-responding. I know that's a stupid large number of pools, but I've just been moving disused pools to the bottom of the list with the thinking that if I needed them again, I could just change the order.
If the miner craps out after too many pools are defined, then the UI should probably limit the number that you can specify.
Note that this was with the v2.5.52 firmware.
I have experienced similar behavior from some of my SP20s. Only for me, it was if I made a number of additions or changes on the pool page. So for example, if I added a pool and then did a lot of shuffling of the order or added a bunch of pools at once, the system would sometimes hang. My way around it was to enter a pool, hit submit, navigate to the status page, go back to the pool page and make the next adjustment. I noticed that I could safely make two or three changes to pool order before I experienced a problem. Once I started operating like that, I didn't experience the problem again. Firmware has been upgraded a few times since then and I have not tried it under the latest releases.
