sorry I'm a windows person so don't have those Linux problems jokes

I have another problem, my own miners don't seem to show the payout on my pool. I have someone else on there now and their payout graph is showing just fine.
http://www.norgzpool.net.au/graphs.html?Hour

see my ant on 1CmHNDfj43tsQgSpSum5tDQ6kT4MwcUP6V doesn't show any payout and my payout to default address doesn't seem to change when I mine it with a username so it defaults to default payout. I changed it to a wallet address and still nothing.

have you tried:
•sudo apt-get install python-zope.interface python-twisted python-twisted-web

to install the packages? maybe the upgrade installed newer packages than is supported in which case you'll need to downgrade them.

Hi Luke,

 serial "0000098681", but mcp2210 lowlevel driver failed to open it

is the main error. i'll look into what you suggested when I'm back in my office tomorrow.

EDIT: I just tried that and it bombed out:
On commit c4c06166a2ab6937d2d6e198842289ca83c67770
c4c06166a2ab6937d2d6e198842289ca83c67770 build failure (log) - skipping
sh: ./make-release: No such file or directory

found this, may be useful to others:
http://www.rcgroups.com/forums/showthread.php?t=1005309&page=35

hey Nate, yeah I tried that and confirmed the comm port numbers from device manager. It's a funny one. just don't know if it's a bfgminer thing or a mm thing. right now I have a delay when starting but it finally gets going.

hey Nate,

I think I've found some strangeness with new bfgminer. it reports a comport error when run as right click launch and from mm it hangs for ages and sometimes even fails to start https://bitcointalk.org/index.php?topic=626361.msg6962740#msg6962740

mm 3.0.2 and bfgminer 4.0.0

multiminer is actually passing the following:

-S antminer:\\.\com3 -d antminer@\\.\com3 etc if I strip all extra switches out it still shows the error. is it a multiminer issue?

same thing the other message came back " serial "0000098681", but mcp2210 lowlevel driver failed to open it

I'm getting an error when running the following:

-S antminer:all -S NFY:ALL --set-device NFY:osc6_bits=53 --set-device antminer:clock=x0B81 --icarus-options=115200:1:1 --icarus-timing long --no-getwork

About cannot open serial driver. "ft_getcomportnumber(01e008a8 (0), 5) then it finally starts up with Error trying to wake notifier. 32bit windows.

nice work! will test with network and usb devices I have. any more info on the new device options, does auto overclock work with the antminers?

yeah look at your other addresses. I saw similar and I had a change amount come in on a different address. Electrum shows a final balance for all addresses it has.

Great to hear. Please feel free to give feedback or requests for features.

Ah ok great, thanks. Just a matter of understanding how it works 😁

There is only one thing that could be better. On the WP version, when you turn push alerts on, it sends a lot of them. Multiple alerts for one entry on full mm. When you have time could you look at that and/or maybe put more finite settings in for what alerts get sent to WP app.
Eg. Don't want profitably alerts, just miner down alerts.

this is a really great extension to a really great app. It works on all platforms including Windows phone! kudos to a developer who actually believes in cross platform support and active development that continually improves this already great software.

looks like I had a NAT rule missing on the au node. If you were unable to connect before please try again. The au node is hosted in the Sydney Equinix data center so should be very low latency.

try restarting your wallet. I find Electrum sometimes doesn't reflect new transactions still restarted. The blockchain should include the transactions though, check it by going to https://blockchain.info/address/{your wallet address}

that way you can confirm the blockchain does at least include your payments. you just then need to work out whats wrong with your wallet.

Just wanted to point out that I've done a lot of work to ensure all stats on my front end are working on a remote web server. Using a separate web server takes some risk of a hack away from your pool node and means the web page will tell you if your node is down.

If you want to run it locally you can run any interface but they don't all work remotely, I learned that the hard way lol

ok so I have deployed out a copy of p2pool.info and it looks like it is still updating but it's a backup at least.

http://p2poolinfo.azurewebsites.net/

if you appreciate this work I am doing you can always donate to my addy in my profile.

looks interesting. I've written mine to be independent of the node so you can take all the web files off the node server. In my mind this means the node is much more secure as no web traffic is on that box. (ultimately I want to disable the web-static directory and/or even the web server entirely).

It also means that if any one node is down you can tell and the main front end stays up.

Have you thought about pulling it from the /web/log json feed instead?