|
881
|
Bitcoin / Pools / Re: [400GH/s] p2pool: Decentralized, DoS-resistant, Hop-Proof pool
|
on: October 18, 2012, 07:30:00 AM
|
I renamed the dir back to forrestv-p2pool-7aedd00 and then, to accommodate my script which starts p2pool, made a soft link to it named p2pool. That script contains "python ~/src/p2pool/run_p2pool.py". There's still no version output.
[I recognize that this issue is quite trivial and will cheerfully accept lack of a reply.]
P2Pool uses the argv[0] (the path that you give to run_p2pool.py) to find its directory, so it's looking at "~/src/p2pool", and the symlink does nothing. I think it would make most sense to rename it to p2pool_8.2 and run p2pool as "python ~/src/p2pool_8.2/run_p2pool.py". (: forrestv, I'm doing the same thing, that is I untar it and then do a ln -s ./forrestv-p2pool-7aedd00 p2pool
then I start it with a cd p2pool
python ./run_p2pool.py
and it shows, right at the start fatal: Not a git repository (or any parent up to mount parent )
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
2012-10-18 09:25:08.997911 p2pool (version 7aedd00)
So it finds its version even if I start if from a link spiccioli |
|
|
|
|
882
|
Bitcoin / Development & Technical Discussion / Re: Ready for testing: 0.7.1 release candidate 1
|
on: October 12, 2012, 10:19:41 AM
|
It dies on my 10.5.8 mac with this trap: Process: Bitcoin-Qt [437]
Path: /Volumes/Bitcoin-Qt/Bitcoin-Qt.app/Contents/MacOS/Bitcoin-Qt
Identifier: com.yourcompany.Bitcoin-Qt
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: launchd [76]
Interval Since Last Report: 4991 sec
Crashes Since Last Report: 1
Per-App Interval Since Last Report: 4467 sec
Per-App Crashes Since Last Report: 1
Date/Time: 2012-10-12 12:14:29.909 +0200
OS Version: Mac OS X 10.5.8 (9L31a)
Report Version: 6
Anonymous UUID: 51EEDE10-8C88-466A-AEF6-E85F259DF368
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread: 0
Dyld Error Message:
Symbol not found: __ZNKSt13bad_exception4whatEv
Referenced from: /Volumes/Bitcoin-Qt/Bitcoin-Qt.app/Contents/MacOS/../Frameworks/libboost_thread-mt.dylib
Expected in: /usr/lib/libstdc++.6.dylib
Same problem for the 0.7.0 release. spiccioli |
|
|
|
|
883
|
Economy / Services / Re: pyramining links, let's share them here
|
on: October 05, 2012, 07:12:20 AM
|
Hey thansk for this! I have been interested in seeing what this was about!
You're welcome, I think the main thread should be used only to talk about the service and not for sharing links which make it harder to find relevant info in between link sharing messages. spiccioli |
|
|
|
|
885
|
Bitcoin / Hardware / Re: High Efficiency FPGA & ASIC Bitcoin Mining Devices https://BTCFPGA.com
|
on: October 05, 2012, 06:29:23 AM
|
This can be a lot of work when your talking 500+ units, this is the reason I have rented 2000 square feet of office space (pictures coming soon!) and have been recruiting people from the forum to come work for me for about a week to ten days to get the first wave of shipments out. The pay will be reasonable and every night at quitting time the pizza and beer will be plentiful. It stands to be a pretty good time  I wish I could take time off to do this, sounds somewhat fun =p Yeah, if I were not so far away, Italy, I'd be applying in no time for this spiccioli |
|
|
|
|
888
|
Bitcoin / Hardware / Re: "Avalon" ASIC, announcement & pre-order. second wave @ 9:00am EDT, 10/03
|
on: October 03, 2012, 01:26:29 PM
|
Now things get interesting...
how much time do we have to send BTCs to provided address?
spiccioli
I don't think there is a hard time limit. It's the fact that your order went through that guarantees you a spot - also that fact that you're given an order id #. Typically it takes a while to confirm your payment anyways so once it's confirmed you're all set. Sure, it makes sense, but they have to have a "timeout" on my sending of due BTCs to be sure I really have placed/confirmed my order. spiccioli |
|
|
|
|
892
|
Bitcoin / Hardware / Re: "Avalon" ASIC, announcement & pre-order. VERY important notice updated@9/24
|
on: October 01, 2012, 06:46:42 AM
|
PM sent
Ngzhang, I've got a mail from you before your site went online confirming my order (before site went online orders were sent directly to you) but now I did not get the email with the address where to pay nor an answer from Yifu Guo whom I sent an email a few days ago asking for a confirmation of my order. I'm send you a PM with my real name, can you confirm me my order status? Thanks. spiccioli |
|
|
|
|
893
|
Bitcoin / Pools / Re: [45 GH/s] HHTT - User Selected Share Difficulty/PPS/Paid Stales
|
on: September 27, 2012, 03:58:17 PM
|
Wow. Try putting rpc.hhtp.1209k in your hosts file (50.112.109.226) so DNS is removed from the equation. Does anyone know if cgminer caches DNS info?
On linux add to /etc/hosts:
50.112.109.226 rpc.hhtt.1209k.com
bitcoindaddy, your suggestion was right, this is the same test after I put pool name inside hosts $ time curl -u 1FDkoGo8o9tmXD4cYpAqBZeWACJiYjMm3x_1:foo --data '{"method":"getwork","params":[],"id":1}' http://rpc.hhtt.1209k.com:8337/
{"id":1,"error":null,"result":{"midstate":"7e44ba94c313603ed64a65ff6368f9da0e8c3dfada97a819f867ecf2efc9c68b","target":"0000000000000000000000000000000000000000000000000000008000000000","data":"00000002d2ebd8553d06b382352b7f39ead71feae3a2cbee30d28e0a0000019300000000460bb67f0c0b9d72e8766ff88f8068addf9ba4cd1ee99632623a63197b134e17506476dc1a05db8b00000000000000800000000000000000000000000000000000000000000000000000000000000000000000000000000080020000","hash1":"00000000000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000010000"}}
real 0m0.479s
user 0m0.020s
sys 0m0.016s
~$ time curl -u 1FDkoGo8o9tmXD4cYpAqBZeWACJiYjMm3x_1:foo --data '{"method":"getwork","params":[],"id":1}' http://rpc.hhtt.1209k.com:8337/
{"id":1,"error":null,"result":{"midstate":"217855e033bf90b70d2524874cd2ef8ee0327af8fa7b95de884d57680b46435e","target":"0000000000000000000000000000000000000000000000000000008000000000","data":"00000002d2ebd8553d06b382352b7f39ead71feae3a2cbee30d28e0a0000019300000000de1c00bbaaa499116e99e186b8de01a8d086cb9705f49a6e089a12c7ea6a4106506476df1a05db8b00000000000000800000000000000000000000000000000000000000000000000000000000000000000000000000000080020000","hash1":"00000000000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000010000"}}
real 0m0.481s
user 0m0.024s
sys 0m0.016s
~$ time curl -u 1FDkoGo8o9tmXD4cYpAqBZeWACJiYjMm3x_1:foo --data '{"method":"getwork","params":[],"id":1}' http://rpc.hhtt.1209k.com:8337/
{"id":1,"error":null,"result":{"midstate":"eb5c53141e9582c28a54cd28e61e9800e845d4a949596d31ddcc3ce6a4783f24","target":"0000000000000000000000000000000000000000000000000000008000000000","data":"00000002d2ebd8553d06b382352b7f39ead71feae3a2cbee30d28e0a000001930000000004d3deee22fdbabc43f89169b201df1d693f0be54a04f8bba9a21edd6e27fd05506476e21a05db8b00000000000000800000000000000000000000000000000000000000000000000000000000000000000000000000000080020000","hash1":"00000000000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000010000"}}
real 0m0.516s
user 0m0.016s
sys 0m0.024s
So it is name resolution... but nslookup is fast, though. Thanks for your help! spiccioli |
|
|
|
|
894
|
Bitcoin / Pools / Re: [45 GH/s] HHTT - User Selected Share Difficulty/PPS/Paid Stales
|
on: September 27, 2012, 03:51:02 PM
|
fireduck,
I've just made three tests
summary: 20sec,10sec,20sec
spiccioli
Ok, wow. That is certainly a problem. Those should be taking less than a second. I haven't seen any take nearly that long. Can you test some other things around the net to see where that latency is coming from and do some pings and traceroutes around? fireduck, $ ping -U rpc.hhtt.1209k.com
PING rpc.hhtt.1209k.com (50.112.109.226) 56(84) bytes of data.
64 bytes from rpc.hhtt.1209k.com (50.112.109.226): icmp_req=1 ttl=39 time=210 ms
64 bytes from rpc.hhtt.1209k.com (50.112.109.226): icmp_req=2 ttl=39 time=207 ms
64 bytes from rpc.hhtt.1209k.com (50.112.109.226): icmp_req=3 ttl=39 time=208 ms
64 bytes from rpc.hhtt.1209k.com (50.112.109.226): icmp_req=4 ttl=39 time=281 ms
64 bytes from rpc.hhtt.1209k.com (50.112.109.226): icmp_req=5 ttl=39 time=268 ms
64 bytes from rpc.hhtt.1209k.com (50.112.109.226): icmp_req=6 ttl=39 time=257 ms
64 bytes from rpc.hhtt.1209k.com (50.112.109.226): icmp_req=7 ttl=39 time=217 ms
64 bytes from rpc.hhtt.1209k.com (50.112.109.226): icmp_req=8 ttl=39 time=235 ms
64 bytes from rpc.hhtt.1209k.com (50.112.109.226): icmp_req=9 ttl=39 time=208 ms
64 bytes from rpc.hhtt.1209k.com (50.112.109.226): icmp_req=10 ttl=39 time=214 ms
64 bytes from rpc.hhtt.1209k.com (50.112.109.226): icmp_req=11 ttl=39 time=210 ms
64 bytes from rpc.hhtt.1209k.com (50.112.109.226): icmp_req=12 ttl=39 time=208 ms
64 bytes from rpc.hhtt.1209k.com (50.112.109.226): icmp_req=13 ttl=39 time=207 ms
64 bytes from rpc.hhtt.1209k.com (50.112.109.226): icmp_req=14 ttl=39 time=207 ms
64 bytes from rpc.hhtt.1209k.com (50.112.109.226): icmp_req=15 ttl=39 time=208 ms
^C
--- rpc.hhtt.1209k.com ping statistics ---
15 packets transmitted, 15 received, 0% packet loss, time 14017ms
rtt min/avg/max/mdev = 207.457/223.489/281.187/24.204 ms
traceroute shows nothing... $ sudo traceroute rpc.hhtt.1209k.com
traceroute to rpc.hhtt.1209k.com (50.112.109.226), 30 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
it takes a few seconds before first hop is shown, though with -T $ sudo traceroute -T rpc.hhtt.1209k.com
traceroute to rpc.hhtt.1209k.com (50.112.109.226), 30 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 rpc.hhtt.1209k.com (50.112.109.226) 215.003 ms 218.025 ms 214.996 ms
they seem to me as "normal" values... what do you think? spiccioli |
|
|
|
|
896
|
Bitcoin / Pools / Re: [45 GH/s] HHTT - User Selected Share Difficulty/PPS/Paid Stales
|
on: September 27, 2012, 01:17:18 PM
|
Wow. Try putting rpc.hhtp.1209k in your hosts file (50.112.109.226) so DNS is removed from the equation. Does anyone know if cgminer caches DNS info?
On linux add to /etc/hosts:
50.112.109.226 rpc.hhtt.1209k.com
bitcoindaddy, DNS seems fast enough... $ time nslookup rpc.hhtt.1209k.com
Server: 192.168.0.1
Address: 192.168.0.1#53
Non-authoritative answer:
Name: rpc.hhtt.1209k.com
Address: 50.112.109.226
real 0m0.033s
user 0m0.008s
sys 0m0.016s
spiccioli |
|
|
|
|
898
|
Bitcoin / Pools / Re: [45 GH/s] HHTT - User Selected Share Difficulty/PPS/Paid Stales
|
on: September 27, 2012, 06:14:38 AM
|
What does it look like for time when you just do the getwork from the command line?
fireduck, I've just made three tests $ time curl -u 1FDkoGo8o9tmXD4cYpAqBZeWACJiYjMm3x_1:foo --data '{"method":"getwork","params":[],"id":1}' http://rpc.hhtt.1209k.com:8337/
{"id":1,"error":null,"result":{"midstate":"b93b9ac85da42577453db4df5e3743ada4feeb20601db33d9a20efb34e79128a","target":"0000000000000000000000000000000000000000000000000000008000000000","data":"000000020a65d61cf63f18462397845d4c167ec5c0c07fddae5e814e0000056c000000001d9e2f6010bab1416aa90c6b33f49a6e359ab8b13f8115dd7ff8351cb526889a5063ee241a05db8b00000000000000800000000000000000000000000000000000000000000000000000000000000000000000000000000080020000","hash1":"00000000000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000010000"}}
real 0m20.495s
user 0m0.016s
sys 0m0.020s
$ time curl -u 1FDkoGo8o9tmXD4cYpAqBZeWACJiYjMm3x_1:foo --data '{"method":"getwork","params":[],"id":1}' http://rpc.hhtt.1209k.com:8337/
{"id":1,"error":null,"result":{"midstate":"8845cf930b149e17d77b3c63b3c3539a60496654b1493b48bad364ca09458775","target":"0000000000000000000000000000000000000000000000000000008000000000","data":"000000020a65d61cf63f18462397845d4c167ec5c0c07fddae5e814e0000056c0000000090401d646b6125d235380d0bb8f6d18568c623eac643dec293bc5c9efaae93225063ee341a05db8b00000000000000800000000000000000000000000000000000000000000000000000000000000000000000000000000080020000","hash1":"00000000000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000010000"}}
real 0m10.554s
user 0m0.016s
sys 0m0.020s
$ time curl -u 1FDkoGo8o9tmXD4cYpAqBZeWACJiYjMm3x_1:foo --data '{"method":"getwork","params":[],"id":1}' http://rpc.hhtt.1209k.com:8337/
{"id":1,"error":null,"result":{"midstate":"06f5fc3e76d3bf01e2250316ecaa6a96b0e79a1a371efab3799d8ce3296460b2","target":"0000000000000000000000000000000000000000000000000000008000000000","data":"000000020a65d61cf63f18462397845d4c167ec5c0c07fddae5e814e0000056c00000000033d51fe3a9a0142e5576c694639e08d46d854221579742ada1de20609ea235d5063ee4b1a05db8b00000000000000800000000000000000000000000000000000000000000000000000000000000000000000000000000080020000","hash1":"00000000000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000010000"}}
real 0m20.498s
user 0m0.020s
sys 0m0.020s
spiccioli |
|
|
|
|
899
|
Bitcoin / Pools / Re: [30 GH/s] HHTT - User Selected Share Difficulty/PPS/Paid Stales
|
on: September 26, 2012, 08:14:43 PM
|
I'm using difficulty 32.
I'll try to use 256 for a while, but it seems to me that the problem is in requesting more work, not in submitting less.
Cheers,
spiccioli
It could also be the clock on your system. If you clock is off your mining software might think it is unable to change the time on the work unit to scan for more good nonces. If it can't do that, it will end up having to request a lot of work from the server since it will only be able to do 2^32 hashes on each work unit. Hi, time should be ok, I have ntpd running ~$ ntpq
ntpq> pe
remote refid st t when poll reach delay offset jitter
==============================================================================
+2-229-10-127.ip 193.204.114.232 2 u 407 1024 373 19.548 0.912 15.804
-93.62.188.182 193.204.114.233 2 u 370 1024 377 23.031 -2.972 2.715
*2.228.72.62 193.204.114.233 2 u 625 1024 377 30.171 -0.362 1.984
+flo.m4oc.it 193.204.114.232 2 u 747 1024 377 43.694 -0.527 0.608
-europium.canoni 193.79.237.14 2 u 867 1024 377 44.668 6.510 0.836
ntpq> ass
ind assid status conf reach auth condition last_event cnt
===========================================================
1 37325 941a yes yes none candidate sys_peer 1
2 37326 931a yes yes none outlyer sys_peer 1
3 37327 961a yes yes none sys.peer sys_peer 1
4 37328 941a yes yes none candidate sys_peer 1
5 37329 932a yes yes none outlyer sys_peer 2
ntpq>
spiccioli |
|
|
|
|
900
|
Bitcoin / Pools / Re: [30 GH/s] HHTT - User Selected Share Difficulty/PPS/Paid Stales
|
on: September 26, 2012, 03:23:22 PM
|
hi fireduck,
I'm getting more and more of:
Pool 0 not providing work fast enough
when mining here, is there something you can do to improve this?
thanks.
spiccioli
ps. I have a little more than 7 GH/s
What difficulty are you using? If you are seeing that, my guess is that you need to increase that number. At 7GH/s 128 or 256 would probably be good. I'm using difficulty 32. I'll try to use 256 for a while, but it seems to me that the problem is in requesting more work, not in submitting less. Cheers, spiccioli |
|
|
|
|
Show Posts
