|
RandyFolds
|
 |
July 21, 2013, 09:20:38 AM |
|
Hm, I went for a reinstall for my server and it seems like there is some old data populating back. I have used rm -f primecoin-hp/src and rm --recursive primecoin-hp/src
However, when I reinstall and use these commands, /primecoin-hp/src# primecoind stop
error: incorrect rpcuser or rpcpassword (authorization failed)
primecoind --daemon Error: Cannot obtain a lock on data directory /root/.primecoin. Primecoin is probably already running. I used these commands https://bitbucket.org/mikaelh/primecoin-hpmake -f makefile.unix USE_UPNP=- mkdir ~/.primecoin echo "rpcuser=USER rpcpassword=PASSWORD gen=1" > ~/.primecoin/primecoin.conf sudo mv -f primecoind /usr/local/bin/. primecoind --daemon watch 'primecoind listtransactions & primecoind getmininginfo' Any ideas how to fix the rpcuser problem? I checked sudo nano ~/.primecoin/primecoin.conf and it looks all fine. Edit your primecoin.conf file back to what it was when you started the daemon, then terminate it. Probably old primecoind running. That worked for me when I ran into this. Look guys! You're teaching me linux! Aren't you proud? |
|
|
|
|
|
|
|
|
|
You can see the statistics of your reports to moderators on the "Report to moderator" pages.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
oroqen
|
|
July 21, 2013, 09:23:08 AM |
|
Hm, I went for a reinstall for my server and it seems like there is some old data populating back. I have used rm -f primecoin-hp/src and rm --recursive primecoin-hp/src
However, when I reinstall and use these commands, /primecoin-hp/src# primecoind stop
error: incorrect rpcuser or rpcpassword (authorization failed)
primecoind --daemon Error: Cannot obtain a lock on data directory /root/.primecoin. Primecoin is probably already running. I used these commands https://bitbucket.org/mikaelh/primecoin-hpmake -f makefile.unix USE_UPNP=- mkdir ~/.primecoin echo "rpcuser=USER rpcpassword=PASSWORD gen=1" > ~/.primecoin/primecoin.conf sudo mv -f primecoind /usr/local/bin/. primecoind --daemon watch 'primecoind listtransactions & primecoind getmininginfo' Any ideas how to fix the rpcuser problem? I checked sudo nano ~/.primecoin/primecoin.conf and it looks all fine. Edit your primecoin.conf file back to what it was when you started the daemon. That worked for me when I ran into this. Look guys! You're teaching me linux! Aren't you proud? It's like watching a baby take its first steps, so much pride in the future |
|
|
|
|
|
maco
|
|
July 21, 2013, 09:30:02 AM |
|
you guys are a funny bunch. I have already noted I can access primecoin.conf
That was the whole point, because I have made the edit, and it still comes up.
The information is all available on ubu's sites, so no I don't need the professors teaching me linux.
all I am asking is for ideas to overcome it
|
|
|
|
|
|
RandyFolds
|
|
July 21, 2013, 09:32:13 AM |
|
you guys are a funny bunch. I have already noted I can access primecoin.conf
That was the whole point, because I have made the edit, and it still comes up.
But did you edit primecoin.conf while primecoind was running? Could also just hard reboot, but I have no idea which build you'd end up running or how linux delineates that kind of stuff. e: dude, I am making fun of myself. I had never used linux prior to firing up these DO droplets, but now I think I actually know the solution to your problem because I encountered it myself. Old primcoind wants old primecoin.conf. |
|
|
|
|
|
oroqen
|
|
July 21, 2013, 09:40:05 AM |
|
you guys are a funny bunch. I have already noted I can access primecoin.conf
That was the whole point, because I have made the edit, and it still comes up.
The information is all available on ubu's sites, so no I don't need the professors teaching me linux.
all I am asking is for ideas to overcome it
Seems like you may have changed rpcuser/password while daemon was still running, you could try killing it with "killall primecoind" and give it a second to close before running it again |
|
|
|
|
|
RandyFolds
|
|
July 21, 2013, 09:41:11 AM |
|
you guys are a funny bunch. I have already noted I can access primecoin.conf
That was the whole point, because I have made the edit, and it still comes up.
The information is all available on ubu's sites, so no I don't need the professors teaching me linux.
all I am asking is for ideas to overcome it
Seems like you may have changed rpcuser/password while daemon was still running, you could try killing it with "killall primecoind" and give it a second to close before running it again See, that's what someone who know's how to use linux would tell you to do. |
|
|
|
|
|
maco
|
|
July 21, 2013, 09:51:18 AM |
|
you guys are a funny bunch. I have already noted I can access primecoin.conf
That was the whole point, because I have made the edit, and it still comes up.
The information is all available on ubu's sites, so no I don't need the professors teaching me linux.
all I am asking is for ideas to overcome it
Seems like you may have changed rpcuser/password while daemon was still running, you could try killing it with "killall primecoind" and give it a second to close before running it again Thanks. I have tried that, but it still has the same problem. Says the info is incorrect. I think I was using chemists build before this one. Problem is still open as I am working to find a solution. I don't think daemon is dieing, I am trying to kill the S.O.B! |
|
|
|
|
|
RandyFolds
|
|
July 21, 2013, 10:16:49 AM |
|
you guys are a funny bunch. I have already noted I can access primecoin.conf
That was the whole point, because I have made the edit, and it still comes up.
The information is all available on ubu's sites, so no I don't need the professors teaching me linux.
all I am asking is for ideas to overcome it
Seems like you may have changed rpcuser/password while daemon was still running, you could try killing it with "killall primecoind" and give it a second to close before running it again Thanks. I have tried that, but it still has the same problem. Says the info is incorrect. I think I was using chemists build before this one. Problem is still open as I am working to find a solution. I don't think daemon is dieing, I am trying to kill the S.O.B! Did you write a script to auto start it? If so, why not remove it and just reboot the instance? |
|
|
|
|
|
|
PSL
Member
 Offline
Activity: 166
Merit: 10
|
|
July 21, 2013, 11:22:57 AM
Last edit: July 21, 2013, 06:44:06 PM by PSL |
|
Hm, I went for a reinstall for my server and it seems like there is some old data populating back.
I have used rm -f primecoin-hp/src and rm --recursive primecoin-hp/src
However, when I reinstall and use these commands,
/primecoin-hp/src# primecoind stop
error: incorrect rpcuser or rpcpassword (authorization failed)
Any ideas how to fix the rpcuser problem?
I checked sudo nano ~/.primecoin/primecoin.conf and it looks all fine.
Try this sequence: mkdir ~/.primecoin
cat <<+++ > ~/.primecoin/primecoin.conf
rpcuser=USER
rpcpassword=PASSWORD
gen=1
+++
chmod 600 ~/.primecoin/primecoin.conf
git clone https://bitbucket.org/mikaelh/primecoin-hp.git
cd primecoin-hp/src
git pull
make -f makefile.unix clean
make -f makefile.unix USE_UPNP=-
strip primecoind
sudo cp -f primecoind /usr/local/bin/.
primecoind --daemon --server
watch 'primecoind listtransactions && primecoind getmininginfo'
|
|
|
|
|
|
mikaelh (OP)
|
|
July 21, 2013, 11:25:53 AM |
|
/primecoin-hp/src# primecoind stop
error: incorrect rpcuser or rpcpassword (authorization failed)
Your primecoin daemon was started with a different password in the config file. Just kill it off by typing: killall primecoind |
|
|
|
|
|
Tuck Fheman
|
|
July 21, 2013, 11:46:40 AM |
|
On testnet, I found that a sievesize=6144000 outperformed every other sievesize I tried (incl. 6000000 & 6246400) by 30% using an i7.
However, when i try to use this sievesize mining live, h5 crashes as soon as mining starts (every time). It's unfortunate because it showed such promise on testnet.
Blocks were coming in 4-5 chunks at a time steadily, even hit 6 blocks in 1 minute (no other setting hit above 4 blocks/min).
same here, 6144000 crashed h5 as soon as it attemps to mine on a i7 3770k with 16gb of ram. Did you get better results on testnet with 4M than 1M ? How do you activate testnet ? I can't check it on the debug window. The best sievesize's I found were ... Build - Sievesize - PPS - Blocks in 10 minutes HP3 - 1000000 - 7387 - 14 HP5 - 2000000 - 7092 - 14 HP5 - 4000000 - 7911 - 15 (3 at a time usually) HP4 - 6000000 - 7819 - 15 HP4 - 6144000 - 7430 - 20 HP3 - 6553600 - 5042 - 20 (steady 2 per minute) HP5 - 5000000 - 7815 - 22 HP5 - 6000000 - 6919 - 23 HP5 - 6144000 - 7876 - 29 (4 at a time usually + 6 in 1 minute) - same result using "-1" or "6" threads. Nothing above 4608000 worked for me mining live w/HP5 and using higher settings live w/HP3 worked (without crashing) but was yielding very low PPS (in the hundreds) live. I get a higher PPS @ 1M or 2M live on HP5. I have no idea if the testnet actually "test" anything to be honest.  None of the data I collected translates over into real world mining ... especially since the client shuts down and no blocks are being found for days using the same settings that worked so well on the testnet. So I'm trying the highest testnet settings that yielded the best results that will still work live and seeing how it goes. So far (6 hours or so, no blocks). To answer your question ... add "-testnet" to the command line. |
|
|
|
|
|
|
mikaelh (OP)
|
|
July 21, 2013, 12:28:16 PM |
|
HP5 - 6144000 - 7876 - 29 (4 at a time usually + 6 in 1 minute) - same result using "-1" or "6" threads.
Use multiples of 200k for sieve size with HP5. One of the internal loops goes over 200k elements. If there's a small bug there somewhere, it might crash when sieve size is not a multiple of 200k. |
|
|
|
|
|
Tuck Fheman
|
|
July 21, 2013, 01:17:40 PM |
|
Use multiples of 200k for sieve size with HP5. One of the internal loops goes over 200k elements. If there's a small bug there somewhere, it might crash when sieve size is not a multiple of 200k.
Thanks for that info! |
|
|
|
|
nmersulypnem
|
|
July 21, 2013, 02:03:15 PM |
|
Use multiples of 200k for sieve size with HP5. One of the internal loops goes over 200k elements. If there's a small bug there somewhere, it might crash when sieve size is not a multiple of 200k.
Thanks for that info! I think their might be some race conditions that don't exist on testnet. Does anyone have timing numbers on how long the sieve takes to wieve and how long we have, on average, to find a block before someone else solves it? |
|
|
|
|
krikunalta
Newbie
Offline
Activity: 16
Merit: 0
|
|
July 21, 2013, 03:45:28 PM |
|
hp5 client crashes on win 7 64bit random
|
|
|
|
|
notlist3d
Legendary
Offline
Activity: 1456
Merit: 1000
|
|
July 21, 2013, 04:25:55 PM |
|
hp5 client crashes on win 7 64bit random
Same here i went back to 4 after a few crashes. |
|
|
|
|
notlist3d
Legendary
Offline
Activity: 1456
Merit: 1000
|
|
July 21, 2013, 04:29:18 PM |
|
Use multiples of 200k for sieve size with HP5. One of the internal loops goes over 200k elements. If there's a small bug there somewhere, it might crash when sieve size is not a multiple of 200k.
Thanks for that info! Sorry for such a newb question. What is command to change sieve size? I didn't see config file for it. |
|
|
|
|
|
Tamis
|
|
July 21, 2013, 04:57:28 PM |
|
Use multiples of 200k for sieve size with HP5. One of the internal loops goes over 200k elements. If there's a small bug there somewhere, it might crash when sieve size is not a multiple of 200k.
Thanks for that info! Sorry for such a newb question. What is command to change sieve size? I didn't see config file for it. in primecoin.conf add "sievesize=...." |
|
|
|
|
|
