[1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 639.

Mobius

hero member

Activity: 988

Merit: 1000

Quote from: jiyu_shi on October 01, 2012, 12:43:30 AM

Quote from: forrestv on September 30, 2012, 02:42:51 PM

Quote from: jiyu_shi on September 30, 2012, 11:16:02 AM

I run p2pool, it returns
...
what's the red box means?

Thus, the miner works at normal speed, but accept is 0, p2pool's Local is also 0,
and there's no show at p2pool.info_active users
bitcoin-qt's datadir is at D:\bitcoin\

how to solve the problem?
thanks

The red box isn't unusual.. It just means that querying bitcoin for something timed out, but unless it's happening all the time, it's harmless.

Local may be displayed as 0 if you're mining to a non-default address, because you've set your miner's username to a Bitcoin address. This isn't recommended - instead you should use P2Pool's -a option. If you need to use the username way, you can look at the graphs on http://127.0.0.1:9332/ to get some information.

I'd already use -a [address], and miner's username was a norml word, not an address.
Another, my GPU is HD6470M which has only ~30Mh/s speed, is it too slowly to get an accept?
http://127.0.0.1:9332/ shows nothing--even no pool speed and other users' speed, but the graphs shows my speed and pool speed.

use http://127.0.0.1:9332/static/

jiyu_shi

member

Activity: 81

Merit: 10

Quote from: forrestv on September 30, 2012, 02:42:51 PM

Quote from: jiyu_shi on September 30, 2012, 11:16:02 AM

I run p2pool, it returns
...
what's the red box means?

Thus, the miner works at normal speed, but accept is 0, p2pool's Local is also 0,
and there's no show at p2pool.info_active users
bitcoin-qt's datadir is at D:\bitcoin\

how to solve the problem?
thanks

The red box isn't unusual.. It just means that querying bitcoin for something timed out, but unless it's happening all the time, it's harmless.

Local may be displayed as 0 if you're mining to a non-default address, because you've set your miner's username to a Bitcoin address. This isn't recommended - instead you should use P2Pool's -a option. If you need to use the username way, you can look at the graphs on http://127.0.0.1:9332/ to get some information.

I'd already use -a [address], and miner's username was a norml word, not an address.
Another, my GPU is HD6470M which has only ~30Mh/s speed, is it too slowly to get an accept?
http://127.0.0.1:9332/ shows nothing--even no pool speed and other users' speed, but the graphs shows my speed and pool speed.

forrestv

hero member

Activity: 516

Merit: 643

Quote from: Aseras on September 28, 2012, 09:39:48 AM

V5 still seems to have problems with memory leaks, seems more to be an issue with how it talks to .7 bitcoin qt as when it happens, both start to consume HUGE amounts of memory. run_p2pool will start blasting lost connection messages or scrolling this message constantly

eventually it'll use up all available ram and blow up.

Aseras, running p2pool with the --debug option and sending me the log might help. It looks like it's leaking sockets for some reason..

rav3n_pl

legendary

Activity: 1361

Merit: 1003

Don`t panic! Organize!

Quote from: Aseras on September 28, 2012, 09:39:48 AM

V5 still seems to have problems with memory leaks, seems more to be an issue with how it talks to .7 bitcoin qt as when it happens, both start to consume HUGE amounts of memory. run_p2pool will start blasting lost connection messages or scrolling this message constantly

eventually it'll use up all available ram and blow up.

Version: 5.0-3-g7585a1c
Node uptime: 3.639 days Peers: 10 out, 1 in
Not see any excessive memory usage.

forrestv

hero member

Activity: 516

Merit: 643

Quote from: jiyu_shi on September 30, 2012, 11:16:02 AM

I run p2pool, it returns
...
what's the red box means?

Thus, the miner works at normal speed, but accept is 0, p2pool's Local is also 0,
and there's no show at p2pool.info_active users
bitcoin-qt's datadir is at D:\bitcoin\

how to solve the problem?
thanks

The red box isn't unusual.. It just means that querying bitcoin for something timed out, but unless it's happening all the time, it's harmless.

Local may be displayed as 0 if you're mining to a non-default address, because you've set your miner's username to a Bitcoin address. This isn't recommended - instead you should use P2Pool's -a option. If you need to use the username way, you can look at the graphs on http://127.0.0.1:9332/ to get some information.

jiyu_shi

member

Activity: 81

Merit: 10

I run p2pool, it returns

what's the red box means?

Thus, the miner works at normal speed, but accept is 0, p2pool's Local is also 0,
and there's no show at p2pool.info_active users
bitcoin-qt's datadir is at D:\bitcoin\

how to solve the problem?
thanks

Aseras

hero member

Activity: 658

Merit: 500

V5 still seems to have problems with memory leaks, seems more to be an issue with how it talks to .7 bitcoin qt as when it happens, both start to consume HUGE amounts of memory. run_p2pool will start blasting lost connection messages or scrolling this message constantly

Quote

exceptions.ValueError: too many file descriptors in select()
2012-09-28 09:44:04.312000 > Unhandled Error
2012-09-28 09:44:04.312000 > Traceback (most recent call last):
2012-09-28 09:44:04.312000 > File "run_p2pool.py", line 5, in
2012-09-28 09:44:04.312000 >
2012-09-28 09:44:04.312000 > File "p2pool\main.pyc", line 781, in run
2012-09-28 09:44:04.312000 >
2012-09-28 09:44:04.312000 > File "twisted\internet\base.pyc", line 1162, in run
2012-09-28 09:44:04.312000 >
2012-09-28 09:44:04.312000 > File "twisted\internet\base.pyc", line 1174, in mainLoop
2012-09-28 09:44:04.312000 >
2012-09-28 09:44:04.312000 > --- ---
2012-09-28 09:44:04.312000 > File "twisted\internet\selectreactor.pyc", line 104, in doSelect
2012-09-28 09:44:04.312000 >
2012-09-28 09:44:04.312000 > File "twisted\internet\selectreactor.pyc", line 40, in win32select
2012-09-28 09:44:04.312000 >
2012-09-28 09:44:04.312000 > exceptions.ValueError: too many file descriptors in select()

eventually it'll use up all available ram and blow up.

rav3n_pl

legendary

Activity: 1361

Merit: 1003

Don`t panic! Organize!

Quote from: Soros Shorts on September 28, 2012, 07:25:22 AM

Are BFL FPGA Singles the only type mining hardware that is currently not compatible with p2pool?

When I upgrade mine to "SC" Singles (hopefully in 2 months) I am expecting these to work with p2pool. Is that a reasonable expectation?

Tell us when you will have them

All this things are still a question mark even for BFL Tongue

Soros Shorts

donator

Activity: 1617

Merit: 1012

Are BFL FPGA Singles the only type mining hardware that is currently not compatible with p2pool?

When I upgrade mine to "SC" Singles (hopefully in 2 months) I am expecting these to work with p2pool. Is that a reasonable expectation?

Syke

legendary

Activity: 3878

Merit: 1193

Quote from: twmz on September 23, 2012, 08:09:22 PM

I can't conceive of a scenario where a scaling problem could be responsible for bad luck. Scaling problems causing more stale shares or more orphaned blocks? Sure. Scaling problems making math stop working? How, exactly could the size of the network have an impact on the likelihood that random numbers are below a defined target?

The only thing that would affect scaling would be some large miners purposefully mining on p2pool and witholding the blocks. That would be very costly to do so, but it is possible.

Ed

member

Activity: 69

Merit: 10

Quote from: mdude77 on September 24, 2012, 07:06:38 PM

Um.. I have p2pool and ozcoin in my config, and I switch from one to the other without a problem (usually manually, as both have always been up as long as I've been using both). Yeah, a get a few rejects before it synchs up, but it always works......

changed backup to mtred and problems gone, booth remote sites

thanks all

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

Quote from: mdude77 on September 24, 2012, 07:06:38 PM

Quote from: twmz on September 24, 2012, 09:08:48 AM

Correct. You can not mix p2pool and non-p2pool entries in the same cgminer instance.

P2Pool, the distributed network itself, is essentially never "down". If you want a backup to your personal p2pool node being down, use someone else's public p2pool node as a backup (there is a thread here somewhere with a list of public p2pool servers) and specify your bitcoin address as the username.

Um.. I have p2pool and ozcoin in my config, and I switch from one to the other without a problem (usually manually, as both have always been up as long as I've been using both). Yeah, a get a few rejects before it synchs up, but it always works.

Maybe you mean something other than "can not mix". Like load balancing maybe?

M

You must ONLY be mining normal BTC or P2Pool at the same time.
Thus any sort of load balancing must only be the same type of pool as the "Priority 0" pool
You also need to use --failover-only or disable all pools that could be 'failed over' to, that are a different type.

Switching may or may not work as expected - YMMV

But think of it in terms of:
At any time, you MUST disable getting work from ALL pools that are not the same as the "Priority 0" pool

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: twmz on September 24, 2012, 09:08:48 AM

Correct. You can not mix p2pool and non-p2pool entries in the same cgminer instance.

P2Pool, the distributed network itself, is essentially never "down". If you want a backup to your personal p2pool node being down, use someone else's public p2pool node as a backup (there is a thread here somewhere with a list of public p2pool servers) and specify your bitcoin address as the username.

Um.. I have p2pool and ozcoin in my config, and I switch from one to the other without a problem (usually manually, as both have always been up as long as I've been using both). Yeah, a get a few rejects before it synchs up, but it always works.

Maybe you mean something other than "can not mix". Like load balancing maybe?

M

rav3n_pl

legendary

Activity: 1361

Merit: 1003

Don`t panic! Organize!

Public nodes list:
http://nodes.p2pmine.com/

You can verify fee of pool using http://node:port/fee

twmz

hero member

Activity: 737

Merit: 500

Quote from: Ed on September 24, 2012, 07:11:05 AM

Quote from: Ed on September 20, 2012, 10:24:03 AM

LAN and WAN miners has deepbit as backup pool, when DOA is go to 100% I am manually close port, then
they automatically switch to deepbit and working with DOA 0.45%

as I can see p2pool and deepbit is not compatible in multipool cgminer sheme
if cgminer goes from p2pool (main) to deepbit (backup), and going back to p2pool, longpooling stop functioning and all work going rejected

everything, bitcoind, p2pool, cgminer is last versions

Correct. You can not mix p2pool and non-p2pool entries in the same cgminer instance.

P2Pool, the distributed network itself, is essentially never "down". If you want a backup to your personal p2pool node being down, use someone else's public p2pool node as a backup (there is a thread here somewhere with a list of public p2pool servers) and specify your bitcoin address as the username.

Ed

member

Activity: 69

Merit: 10

Quote from: Ed on September 20, 2012, 10:24:03 AM

LAN and WAN miners has deepbit as backup pool, when DOA is go to 100% I am manually close port, then
they automatically switch to deepbit and working with DOA 0.45%

as I can see p2pool and deepbit is not compatible in multipool cgminer sheme
if cgminer goes from p2pool (main) to deepbit (backup), and going back to p2pool, longpooling stop functioning and all work going rejected

everything, bitcoind, p2pool, cgminer is last versions

rav3n_pl

legendary

Activity: 1361

Merit: 1003

Don`t panic! Organize!

Quote from: jiyu_shi on September 23, 2012, 10:41:40 PM

Quote from: kjj on September 23, 2012, 10:02:15 PM

-w tells p2pool what port to listen for miners on, not what port to connect to.

try --bitcoind-rpc-port 10332 --bitcoind-p2p-port 10333

I'm just looking at main.py. I don't know if specifying the --net litecoin option changes the names of those two options or not. It doesn't appear to.

it runs successfully!

If you have correct litecoin.conf
run_p2pool --net litecoin
should be enough to run p2pool properly. It reads data (ports, user, password) from config file.
Also remember to restart litecond after you change config file.

In mean time 70% of network is on v5 already

jiyu_shi

member

Activity: 81

Merit: 10

Quote from: kjj on September 23, 2012, 10:02:15 PM

-w tells p2pool what port to listen for miners on, not what port to connect to.

try --bitcoind-rpc-port 10332 --bitcoind-p2p-port 10333

I'm just looking at main.py. I don't know if specifying the --net litecoin option changes the names of those two options or not. It doesn't appear to.

it runs successfully!

kjj

legendary

Activity: 1302

Merit: 1026

-w tells p2pool what port to listen for miners on, not what port to connect to.

try --bitcoind-rpc-port 10332 --bitcoind-p2p-port 10333

I'm just looking at main.py. I don't know if specifying the --net litecoin option changes the names of those two options or not. It doesn't appear to.

jiyu_shi

member

Activity: 81

Merit: 10

I run litcoin with "litecoin.conf":
rpcuser=abc
rpcpassword=123
server=1
rpcport=10332
port=10333

and then run:
run_p2pool --net litecoin -w 10032 abc 123

it returns:

also try:
run_p2pool --net litecoin --p2pool-port 10032 abc 123

itreturns:

so,will anybody help me?Thanks!

Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 639. (Read 2591920 times)