This thread has been moved to MMC-Square: https://www.mmc-square.com/index.php/topic,32.0.html

I am not trying to start a controversial strike!

Wow, I really need to update this post.

I see that the uptime of your pool decrease from 200+ to only 0.3 hrs.  Did you restart ?

I changed the script to provide more logging information... dont know why the uptime is lower now. systemd may have executed an automatic restart. Keeping my eyes peeled.

If it crashes though, I dont have it auto-restarting... so it will be obvious.

EDIT: yep, it crashed. My log was not saved though should not be long now. by the time I am back I will be ready for debugging.

I would really like to see this wallet available for MMC https://play.google.com/store/apps/details?id=de.schildbach.wallet

I know, but I have to work on other things.

I will get to it sometime soon after P2Pool is started and XRamPool XPM is updated.

Can someone please delete this thread?

I dont think it is productive for the coin.

Quote from: KillerByte on April 02, 2014, 04:55:51 am

the mmcexplorer.info pool is actually not intended to be mined on, it is just the starting node for the P2Pool scan. You can debug output P2Pool (which would help me if it prints out some signal of what its doing when the error happens) with the --debug option.

You should mine on 162.243.*.*, that is my mining pool (actually it is the XRam Pool). If you crash it, it will help me determine if the crashes are a problem that happens on my server also, since they are very odd.

I cannot mine with my computer at this time.

As far as I understand, mmcexplorer.info P2Pool can be used by miner to discover currently available/running P2Pool instances, isn't it? If so, what is the procedure? Is there some API/link that will get list of current instances in machine readable format (preferably json)?

Yes, http://mmcexplorer.info:8080/peer_addresses, then you just keep iterating through until you find only duplicate addresses, then you must search each p2pool for local stats and fees, if necessary.

ok toonces, I have made no progress on finding the solution to your errors.

The first 2... there is no error, it just ends.

The last error... if you provide me with the full stacktrace, it would help me quite a bit!

And looking at the tool selection thing... definitely plan to implement that now, hopefully by the time YAM is all ready. We can do even better: Allow the user to implement his address, and then give a command which the user can copy and paste to connect to the pool.

This may take a little bit of time though, the graphs will a database which I must create and manage, and I have to make sure that MMCExplorer is as reliable as possible so that the graphs look correct.