[quote=“masterOfDisaster, post:1148, topic:342”]Btw: do you have some time left (after having fixed the bug you inserted in the pool and after having moved all back to beeeeer.org, where the pool will be ovverun by the hordes and you will be busy fixing the resulting mess) for tightening the compilation on linux?
I’m a bit too linux newbish to figure out myself how to compile it on a machine with only 512 MB RAM where assigning swap is not allowed (yeah, damn virtual server …)
…and I’m too newbish to do a cross compile on an other machine as well^^[/quote]
This is obviously tech-thread material, but for the sake of it: check my blog for a short description on how to set up a swapfile in your existing filesystem (no extra partition needed) blog.whyservices.eu
I’m new in the digital currency world, compiled your miner and using it on coinspara
Occasionally I must use a VPN and when I do primeminer stops network connections ( saying : “force reconnect if possible!” ) until I shutdown the VPN. It is annoying because when the connection is down it continues mining but all the results are lost because once the connection is available again, it doesn’t send the shares it found.
Am I missing something ? Are the shares simply deleted ?
I’m new in the digital currency world, compiled your miner and using it on coinspara
Occasionally I must use a VPN and when I do primeminer stops network connections ( saying : “force reconnect if possible!” ) until I shutdown the VPN. It is annoying because when the connection is down it continues mining but all the results are lost because once the connection is available again, it doesn’t send the shares it found.
Am I missing something ? Are the shares simply deleted ? :([/quote]
Guess your VPN reroutes all traffic through the tunnel and the miner can’t reach the pool anymore, you might be able to fix that with a seperate route (not sure about that, not my field of expertise) but this belongs into the tech thread
I’m new in the digital currency world, compiled your miner and using it on coinspara
Occasionally I must use a VPN and when I do primeminer stops network connections ( saying : “force reconnect if possible!” ) until I shutdown the VPN. It is annoying because when the connection is down it continues mining but all the results are lost because once the connection is available again, it doesn’t send the shares it found.
Am I missing something ? Are the shares simply deleted ? :([/quote]
You can look if your VPN Support “Split Tunneling”. This way you can route company related traffic into the tunnel and any other traffic will bypass the tunnel and go direkt into the net.
[quote=“Scott J, post:214, topic:358”]Using the new miner on my mum’s laptop doesn’t work.
It just keeps saying:
connecting to 176.34.128.129:1337
I have disabled the firewall and tried the other pool addresses, but no luck.
Any suggestions would be appreciated :)[/quote]
I have the same problem, however the IP is 108.162.198.65:1337 and it is also giving me a “system: 10060” error. I can ping the IP so there is something there. Using the new “mandatory” v08 miner, Windows 64. The usual error I get when the pool is down (under V04) is “system: 10043” so this is something different, or the new miner reports things differently.
[quote=“Sy, post:247, topic:358”]Guess your VPN reroutes all traffic through the tunnel and the miner can’t reach the pool anymore, you might be able to fix that with a seperate route (not sure about that, not my field of expertise) but this belongs into the tech thread
Thanks for your answers, I’m sorry I didn’t put enough details. When using the VPN, I still have complete web access, all ports are open. The only thing breaking down is primeminer, I think changing IP/routes breaks the TCP connection that primeminer establishes when the program is started and therefore the connection doesn’t work anymore. Because if I manually close and start primeminer again, it works. What I don’t understand is the “force reconnect if possible!” from primeminer, since it knows it has been disconnected, shouldn’t it try to reestablish the TCP connection on its own ? Thanks for the tech thread, I’ll post this issue there.
About the primeminer itself, what does it do with the shares it found while offline ?
If it continues mining, does it try to send them when the connection works again ?
I posted in the general thread but someone nice pointed out that it would be better here.
I’m having a problem with primeminer when I start my VPN when primeminer is already running. My VPN has complete web access and all ports are open.
The only thing breaking down is primeminer, I think changing IP/routes breaks the TCP connection that primeminer establishes when the program is started and therefore the connection doesn’t work anymore. Because if I manually close and start primeminer again, it works. What I don’t understand is the “force reconnect if possible!” from primeminer, since it knows it has been disconnected, shouldn’t it try to reestablish the TCP connection on its own ?
About the primeminer itself, what does it do with the shares it found while offline ?
If primeminer continues mining, does it try to send them when the connection works again ?
both options have been mentioned in this thread before. give it a try.[/quote]
Thank you this worked perfect. I was only having this issue on 32 bit system anyways, but it is still nice to get it working to test it out, thanks again!!!
is someone of you using the US Pool with the IP “…7.149” ?
i see some ‘almost’ established connections in the log file, can you PM me your setup & xolominer command line???
the latter one is unusual
i can’t really tell you what’s wrong there as i’ve never seen this error before, i’ll try to find something helpful
(very) old topics say “10043” indicates that the TCP/IP stack is not initialized properly, which windows do you use?
@Gumik:
the typical behaviour for the miner when the connection is lost is to continue mining for 5 minutes (this is when the “force reconnect if possible!” log line appears) and when a thread finds a share during this period, the thread waits until the connection is back again to submit it. unfortunately the triggers are not always working correctly (the current implementation is a bit ‘clunky’ regarding connection loss) and a thread continues mining forever on the old block. especially when you have unstable connections or partly blocked connections or any behaviour that’s far off from (let’s say) “normal”.
if you’re lucky and your miner is connected again just in time the found share are valid and every continues normally. if the loss of your connection took to long and a block has been found by the primecoin network (not necessary by the pool itself) the share gets rejected, because it is stale now. i hope this clarifies a few things.
@maybe_just_one:
that’s still not enough sorry if you already mentioned this, but: what exact OS (& 32 or 64 bit?) ? debian, i’m stupid
32 bit? hopefully not! you should use the 64 bit! what version is your boost & gmp library? can you PM me the output of “cat /proc/cpuinfo” ?
It’s Debian 7.0 x86_64. Boost version is 1.49, gmp 2:5.0.5+dfsg-2, I think at least I’m still not great with Linux. One thing I noticed is it seemed my packages are all amd64, shouldn’t I have some i386?
the latter one is unusual
i can’t really tell you what’s wrong there as i’ve never seen this error before, i’ll try to find something helpful
(very) old topics say “10043” indicates that the TCP/IP stack is not initialized properly, which windows do you use?[/quote]
Windows 7 ultimate 64 bit I just installed 10 days ago.
I found the problem. In the past I have always used the DNS name (beeeeer.org) as the -poolip POOLADDRESS, but changing the POOLADDRESS to coinspara.de does not work, and in fact the IP the miner reported kept changing…
I read every post (dozens) for the last couple of weeks, and none shed any light on the matter. Then I went back to the beginning and read the FIRST post of the OTHER thread, and it gave ip addresses. I guess you can smack me for “not reading” but in my defense I had no idea what/where to read. Anyway specifying the IP address works.
[quote=“xolokram, post:254, topic:358”]@Gumik:
the typical behaviour for the miner when the connection is lost is to continue mining for 5 minutes (this is when the “force reconnect if possible!” log line appears) and when a thread finds a share during this period, the thread waits until the connection is back again to submit it. unfortunately the triggers are not always working correctly (the current implementation is a bit ‘clunky’ regarding connection loss) and a thread continues mining forever on the old block. especially when you have unstable connections or partly blocked connections or any behaviour that’s far off from (let’s say) “normal”.
if you’re lucky and your miner is connected again just in time the found share are valid and every continues normally. if the loss of your connection took to long and a block has been found by the primecoin network (not necessary by the pool itself) the share gets rejected, because it is stale now. i hope this clarifies a few things.[/quote]
Yes it does, thanks for all these infos
This morning when I woke up I noticed both my computers were in “force reconnect if possible!” mode, I didn’t lose my internet connection so I don’t know what happened, maybe the pool went offline for a few seconds or something like that.
Anyway I wrote a small python program to prevent that :
It monitors primeminer and if primeminer is terminated/killed or if it sees “force reconnect if possible” it restarts primeminer.
It logs output of primeminer in primeminer.log and has 3 levels of logging :
0 : Logs everything
1 : Doesn’t log work received and prime/s stats lines
2 : Logs only stats lines containing found shares infos.
If the python program is terminated, it ensures that primeminer is terminated too.
If by any chance anyone is interested, I joined the file as an attachment and here are the steps you need to do :
Put the file in your primeminer directory ( needed if you don’t have primeminer as an environment variable )
Open the file and modify “#!/usr/bin/python2.7” if needed.
Modify the cmd variable with your own attributes :
“./primeminer” => If you have primeminer as an environment variable remove the ./
If you choose a different name at compilation, modify accordingly
Modify the primeminer attributes ( pooluser, poolip … ), you can add attribute if you want
If you don’t want to log modify SHARE_LOG to False
Else modify LOG_LEVEL to the level you want
type in terminal : chmod +x primonitor.py
type ./primonitor.py
You should see primeminer infos as usual ! By default the log file will be named “primeminer.log” and be located in the same folder.
I can not install a miner on one of the machines
Ubuntu 10.04
main_poolminer.cpp:19:31: warning: boost/uuid/sha1.hpp: No such file or directory
main_poolminer.cpp: In function ‘int main(int, char**)’:
main_poolminer.cpp:621: error: ‘boost::uuids’ has not been declared
main_poolminer.cpp:621: error: expected ‘;’ before ‘sha’
main_poolminer.cpp:622: error: ‘sha’ was not declared in this scope
make: *** [obj/main_poolminer.o] Error 1
…)
