Quote from: michelem on May 29, 2014, 06:40:39 AM

Quote from: dloganbill on May 29, 2014, 04:10:47 AM

Quote from: michelem on May 28, 2014, 07:40:07 PM

Quote from: dloganbill on May 28, 2014, 06:55:23 PM

This may not be the best place to post, but I'm having trouble with MobileMiner. I have two RPIs each with ten 5-chip gridseeds. I set up a MM account and set it up on one RPI. I logged into the app and it showed up right away. I set up the 2nd RPI the same way, except gave it a different name. However, it won't show up in the app. I power cycled the whole system (RPI, hub, PSU, etc) and still nothing. I thought maybe it would take a while for it to register, but it has been over 14 hours since the power cycle and still nothing.

You have a possible problem with php5-curl installation.
Please do exactly what I posted before your post, in particular the upgrade_minera.sh script

I tried what you said (twice actually) and it still hasn't shown up yet. Any other ideas?

Let me understand, is it working everything on that RPi but Mobileminer app? Could you check the application/logs/*.php? You should see some lines telling you it's trying to contact MM every minute. Look at it if there are some errors.

For the problem with the guy who disconnect the network and he's not able to login anymore, I think that's a network problem, not a Minera problem/bug/issue. If you disconnect the main router you (your pc) could have problems finding the right route to the RPI (indeed you get a minute or two to get in ssh), probably also the Ethernet HUB could be the problem, an hub doesn't remember routes neither save anything to regain them.
You can try this too. Instead disconnecting the router LAN cable, try to remove the router WAN cable, so you haven't the internet but everything else should work fine. As soon as you disconnect the router LAN cable too, you start having problems. This is because your hardware still looking at the router (it has the main gateway set to it and it is unreachable) but can't find it. Remember also that probably it's your router to give you the IP and net config via DHCP, so this is another issue to eventually look at.

For the network issue, try assigning a static IP to the Rpi. The hub itself shouldn't be a problem since all it does it broadcast the packet to all it's connected peers, unlike the selective forwarding that a switch does based on ARP cache. The default gateway doesn't matter because the packets are directed at the local network.