Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - zvs

Pages: 1 ... 6 7 8 9 10 11 12 [13]
181
Technical Support / Re: Wallet is out of sync
« on: December 07, 2013, 11:57:50 am »
I cant connect either.   Very frustrating.

edit /users/xxx/appdata/roaming/protoshares/protoshares.conf

or /home/xxx/.protoshares/protoshares.conf

and put

addnode=5.9.24.81

at the bottom

182
Technical Support / Re: HALP! Wallet out of Sync
« on: December 07, 2013, 11:53:04 am »
It's because there are too many people that have incoming connections disabled or firewalled

use 5.9.24.81, it has 300 openings

also, re: 2000 connections, the source doesn't use epoll, so if you got to over 1000 connections I assume your client would crash

183
BitShares PTS / Re: [ANN] ptsweb.beeeeer.org - Protoshares mining sub-pool
« on: December 07, 2013, 11:26:33 am »
EDIT: Nevermind. Reopened the wallet client. Turns out the block chain wasn't updating at all. :\ The transaction is there. :D Thanks again!

I'm also having this issue.  Eventually the wallet client stops updating even though it still says its connected.  Nothing updates, but everything looks fine and says that's it's connected to the network, until I restart it and find that I'm X number of hours behind.  Then I see my recent payouts.  Trying to figure out what's going on.

Probably because a lot of the time there aren't any nodes with incoming connections to connect to?...  I had a friend that had the same problem, not getting blockchain to update, just told him to addnode 5.9.24.81. 

It's at 135/500 connections right now.  I have it set for only 20 outbound connections.. but when it does lose one, it still takes up to a hundred or two tries on average to find a new node to connect to.

184
I got the Coyote Pool miner going with the $200 free at Dimension on the Ubuntu12 option. It is reporting 23 hpm. How fast will this cut into my $200?

Should I have multiple of these going to just get through it fairly quickly? I don't see anything about pricing and there is no report yet.

ETA: AWS coupon came pretty quick so that is up next after HP

I did the first of 4 large on HP before reading 16 small is better. Large is only getting 18hpm. The instructions were confusing because it says to put your public IP in putty but I had none and had to go add a "floating IP". Looks like they charge $0.01/hr for this only if you create one and don't assign it to a server.

Edit #2: My large server crept up to 19 hpm while after a while my small went from about 2.6-3.2 and average about 3. Large is better if this is true at 6x the rate for only 4x the cost. I guess I will test out medium later too.

you can use ssh from your first cloud server, that has the public IP

185
yeah, I get 14-16 from the 1 core ones as well,

they are much cheaper too,  i don't know what the exact pricing is, i don't think it deducts it until the end of the day

it does take a lot longer to set up though

186
hi guys

i tried to mine on an AWS.
But i have this probleme when i'm installing ptsminer (with the makefile)

g++ -Wl,-z,relro -Wl,-z,now  -o ptsminer  obj/cpuid.o obj/sha512_avx.o obj/sha512_sse4.o obj/sha512.o obj/sph_sha2.o obj/sph_sha2big.o obj/main_poolminer.o  -Wl,-Bdynamic -l boost_system -l boost_filesystem -l boost_program_options -l boost_thread -l boost_chrono -Wl,-Bdynamic -l z -l dl -l pthread
/usr/bin/ld: cannot find -lz
collect2: ld returned 1 exit status
make: *** [ptsminer] Error 1


Do you have an idea?

Thanks

You are missing library "lz"

if you have zlib1g-dev already and it doesn't work, try using the 32bit lib32z1-dev

187
BitShares PTS / Re: [ANN] ptsweb.beeeeer.org - Protoshares mining sub-pool
« on: December 05, 2013, 02:45:39 pm »
@xrpbtc:
orphans are normal, it's nothing you can prevent 100%
the orphan "streak" was a f---up on the backend of the pool, read the posts about it here

I am looking at my log and I received all the blocks solved by beeeeer from between 7-10 seconds after it reports them as being found on the website (which means that one or both of our clocks are off but also there shouldn't be a range of 7-10 seconds, shouldn't be greater than 1 second)

but for the one that was orphaned, 28296 2013-12-05 01:43:20, I received:

2013-12-05 01:39:22 received block 0000008c06a5cd9f9d1aa04fff50555e49215efe7a2df6c7fd152f6f7df44348 from xxx
2013-12-05 01:39:22 Committing 91 changed transactions to coin database...
2013-12-05 01:39:22 SetBestChain: new best=0000008c06a5cd9f9d1aa04fff50555e49215efe7a2df6c7fd152f6f7df44348  height=28296  log2_work=37.117473  tx=121129  date=2013-12-05 01:39:16 progress=0.999994
2013-12-05 01:39:22 ProcessBlock: ACCEPTED

about 4m earlier.

I guess the node reaction after block #28295 was received is relevant too:

2013-12-05 01:37:22 received block 000000232347bda9f9fffe288b67feda9d7cc37651675cecd2533dd4240c3e20 from xxx
2013-12-05 01:37:22 Committing 16 changed transactions to coin database...
2013-12-05 01:37:22 SetBestChain: new best=000000232347bda9f9fffe288b67feda9d7cc37651675cecd2533dd4240c3e20  height=28295  log2_work=37.117204  tx=121100  date=2013-12-05 01:37:11 progress=0.999990
2013-12-05 01:37:22 ProcessBlock: ACCEPTED
2013-12-05 01:37:22 getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500 from xxx
2013-12-05 01:37:22 getblocks 28294 to 000000232347bda9f9fffe288b67feda9d7cc37651675cecd2533dd4240c3e20 limit 500 from xxx
2013-12-05 01:37:22 getblocks 28294 to 000000232347bda9f9fffe288b67feda9d7cc37651675cecd2533dd4240c3e20 limit 500 from xxx
2013-12-05 01:37:22 getblocks 28294 to 000000232347bda9f9fffe288b67feda9d7cc37651675cecd2533dd4240c3e20 limit 500 from xxx
2013-12-05 01:37:22 getblocks 28294 to 000000232347bda9f9fffe288b67feda9d7cc37651675cecd2533dd4240c3e20 limit 500 from xxx
2013-12-05 01:37:22 getblocks 28294 to 000000232347bda9f9fffe288b67feda9d7cc37651675cecd2533dd4240c3e20 limit 500 from xxx
2013-12-05 01:37:22 getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500 from xxx
2013-12-05 01:37:22 getblocks 28294 to 000000232347bda9f9fffe288b67feda9d7cc37651675cecd2533dd4240c3e20 limit 500 from xxx
2013-12-05 01:37:22 getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500 from xxx
2013-12-05 01:37:22 getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500 from xxx

all those nodes requesting 28294+, never received 28294 2013-12-05 01:35:47, until I sent it to them after block 28295

the same holds true for block 28303 (after beer got 28302 about 65 seconds earlier):

2013-12-05 01:52:57 received block 00000033d992cb9f48c4a53c29e09315bc19674cbcd869d2847530a2604e8859 from xxx
2013-12-05 01:52:57 Committing 40 changed transactions to coin database...
2013-12-05 01:52:57 SetBestChain: new best=00000033d992cb9f48c4a53c29e09315bc19674cbcd869d2847530a2604e8859  height=28303  log2_work=37.119355  tx=121241  date=2013-12-05 01:52:51 progress=0.999994
2013-12-05 01:52:57 ProcessBlock: ACCEPTED
2013-12-05 01:52:57 getblocks 28302 to 00000033d992cb9f48c4a53c29e09315bc19674cbcd869d2847530a2604e8859 limit 500 from xxx
2013-12-05 01:52:57 getblocks 28302 to 00000033d992cb9f48c4a53c29e09315bc19674cbcd869d2847530a2604e8859 limit 500 from xxx
2013-12-05 01:52:57 getblocks 28302 to 00000033d992cb9f48c4a53c29e09315bc19674cbcd869d2847530a2604e8859 limit 500 from xxx
2013-12-05 01:52:57 getblocks 28302 to 00000033d992cb9f48c4a53c29e09315bc19674cbcd869d2847530a2604e8859 limit 500 from xxx
2013-12-05 01:52:58 getblocks 28302 to 00000033d992cb9f48c4a53c29e09315bc19674cbcd869d2847530a2604e8859 limit 500 from xxx
2013-12-05 01:52:58 getblocks 28302 to 00000033d992cb9f48c4a53c29e09315bc19674cbcd869d2847530a2604e8859 limit 500 from xxx
2013-12-05 01:52:58 getblocks 28302 to 00000033d992cb9f48c4a53c29e09315bc19674cbcd869d2847530a2604e8859 limit 500 from xxx
2013-12-05 01:52:58 getblocks 28302 to 00000033d992cb9f48c4a53c29e09315bc19674cbcd869d2847530a2604e8859 limit 500 from xxx
2013-12-05 01:52:58 getblocks 28302 to 00000033d992cb9f48c4a53c29e09315bc19674cbcd869d2847530a2604e8859 limit 500 from xxx

so I think protoshare client connectivity is probably an issue here, for some of these

put 5.9.24.81 on addnode  :D

188


Help? I'm using Ubuntu 12.04 x32

getting the same error..

install libboost-chrono

find it in aptitude by searching for chrono

and then install the boost packages that it wants, and remove the others

libboost-all-dev in 12.04 precise will install an older version of boost w/ no chrono

sudo apt-get install libboost-chrono-dev

189
BitShares PTS / Re: [ANN] ptsweb.beeeeer.org - Protoshares mining sub-pool
« on: December 05, 2013, 09:01:06 am »
33 rejects, 5088 valids on a Buffalo, NY server
29 rejects, 2433 valids on a Las Vegas, NV server
24 rejects, 1773 valids on a Las Vegas, NV server
0 rejects, 158 valids on a Scranton, PA server
2 rejects, 144 valids on a Dallas, TX server
1 reject, 74 valids on a Houston, TX server
42 rejects, 1745 valids on a Germany server

Now it's

92 rejects, 10377 valids on Buffalo, NY server (8 cores)
57 rejects, 5090 valids on Las Vegas, NV server (8 cores)
60 rejects, 4352 valids on Las Vegas, NV server (8 cores)
7 rejects, 1070 valids on Scranton, PA server (*8 cores) --  ed: it just seems like 4 cores.  gimp Xeon =(
10 rejects, 1128 valids on Dallas, TX server (4 cores)
5 rejects, 448 valids on Houston, TX server (varies)
69 rejects, 4053 valids on Germany server, (7 cores)
18 rejects, 1494 valids on Lenoir, NC server (8 cores)

these are all using the latest git pull, diff versions of ubuntu,  about half on 12.04 and the other half on 13.10

they're also all using the 1024mb memory option

oh, jfyi, that Dallas server is from burst.net...  any new customer can get a server for a month for $1 from them, w/ no strings attached (besides having to remember to cancel it in time)

I ran the Windows client for a bit and it started out with 457 accepted and 3 rejects... by the time I saw it to cancel it it was at 677 accepted and 77 rejects.

the linux client disconnects and reconnects if it gets 3 rejects in a row, the windows client doesnt

190
BitShares PTS / Re: [ANN] ptsweb.beeeeer.org - Protoshares mining sub-pool
« on: December 05, 2013, 01:03:42 am »
33 rejects, 5088 valids on a Buffalo, NY server
29 rejects, 2433 valids on a Las Vegas, NV server
24 rejects, 1773 valids on a Las Vegas, NV server
0 rejects, 158 valids on a Scranton, PA server
2 rejects, 144 valids on a Dallas, TX server
1 reject, 74 valids on a Houston, TX server
42 rejects, 1745 valids on a Germany server

Now it's

92 rejects, 10377 valids on Buffalo, NY server (8 cores)
57 rejects, 5090 valids on Las Vegas, NV server (8 cores)
60 rejects, 4352 valids on Las Vegas, NV server (8 cores)
7 rejects, 1070 valids on Scranton, PA server (*8 cores) --  ed: it just seems like 4 cores.  gimp Xeon =(
10 rejects, 1128 valids on Dallas, TX server (4 cores)
5 rejects, 448 valids on Houston, TX server (varies)
69 rejects, 4053 valids on Germany server, (7 cores)
18 rejects, 1494 valids on Lenoir, NC server (8 cores)

these are all using the latest git pull, diff versions of ubuntu,  about half on 12.04 and the other half on 13.10

they're also all using the 1024mb memory option

oh, jfyi, that Dallas server is from burst.net...  any new customer can get a server for a month for $1 from them, w/ no strings attached (besides having to remember to cancel it in time)

191
BitShares PTS / Re: [ANN] ptsweb.beeeeer.org - Protoshares mining sub-pool
« on: December 04, 2013, 04:22:43 pm »
can you two post the # of threads you're using on your servers??

@orphans:
the orphan streak was caused by the stuck protoshares backend like i said before
but the last one is just bad luck, just like Troglodactyl (thank you) said, it's not possible to prevent this completely
on the other hand, if a pool is big enough it could intentionally try to 'orphan' blocks by other pools/users <-- just saying, in theory

- xolokram

re: the 3rd one, I don't think it's done intentionally, but, yeah, there's a... uh... slow quark pool that controls about 80-85% of the hashrate and orphans some godawful number of blocks

germany is 7 cores, dallas is 4 cores, houston is 4 cores, the rest are 8 cores

i have some machines running 2 cores here on my home connection that are ~97% valid

ed: in my protoshares log, there's only 1 orphan in the last 6 hour or so and no reorganizations

192
BitShares PTS / Re: [ANN] ptsweb.beeeeer.org - Protoshares mining sub-pool
« on: December 04, 2013, 04:18:40 pm »
More orphans. What causes these?

yes what does this mean 0 PTS / 0 PTS -> ORPHAN :(

TIA

That means we mined that block, but someone else mined a block as a child to the same parent as ours close to the same time, and the network accepted the other child and thus rejected ours.  Since our block didn't make it into the final chain, we get nothing for it.

or it could be indicative of protoshares client not connected to enough and/or the right peers, or another situation would be a lack of bandwidth and connected to too many peers.  in that case, it'd try to send to them all at once and they'd all get it slow.

I received block 28005 and 28039 from a peer in Germany, despite the pool being in New Jersey (and having over 100 connections in protoshare client).  I imagine it doesn't have very good connectivity (or not enough peers), or maybe it funnels everything through that Hetzner machine (which wouldnt be so hot with the +120-140ms). 

193
BitShares PTS / Re: [ANN] ptsweb.beeeeer.org - Protoshares mining sub-pool
« on: December 04, 2013, 04:01:36 pm »
I have 494 rejects of 3553 valid shares. Is that number of rejects normal?
33 rejects, 5088 valids on a Buffalo, NY server
29 rejects, 2433 valids on a Las Vegas, NV server
24 rejects, 1773 valids on a Las Vegas, NV server
0 rejects, 158 valids on a Scranton, PA server
2 rejects, 144 valids on a Dallas, TX server
1 reject, 74 valids on a Houston, TX server
42 rejects, 1745 valids on a Germany server

keep in mind that it's mining to a location in new jersey


Pages: 1 ... 6 7 8 9 10 11 12 [13]