Found a really minor bug in the startup messages :
Sometimes the display is messed up, my guess is that all the worker threads are writing to the output at the same time without using a safe method like a putting messages in a FIFO queue. Is it the case ?
[i]By the way, I improved my monitor program :
With the subprocess module, primeminer was buffering its write to the output, this led to delays when displaying messages . Replaced subprocess with pexpect in order to get realtime output.
Logging : writing to the file is now unbuffered ( instead of line buffered ) to ensure real time logging.
Now logs lost connection and restart messages, like so :
[ERROR] 2013-11-07 11:59:29 CONNECTION LOST
[INFO] 2013-11-07 11:59:32 RESTART
[/i]
EDIT : Just realized that maybe it was not the best topic to speak about the monitor, should I post in the beeeeer.org general topic or create a new topic ?
Just messing with the xolominer 0.8 today and I can set the āSieveExtensionsā and āSieveSizeā and stuff.
What are those? I tried with SieveSize at 2000000 but was getting 1600 prime per sec and only 0.5 chains per day. While if I set SieveSize to 10000, I get 4000 prime per sec but 0.5 chains per day.
With defaults I get about 2000 - 2300 prime per sec and 1.090 - 1.23 chains per day.
Itās and I5-2300 Quad @ 2.8 Ghz.
Will messing with these settings result in more prime chains being found and accepted? or is the defaults the best?
@gumik:
i think if the project is big enough you should give it a try to write it into a seperate thread. otherwise yes, the tech support thread is not the best choice i guess
yes, the log output of the miner threads (just the first few seconds, when everything is warming up) is not thread-safe.
@Silver_Pharaoh:
the default values are probably not the best, it takes alot of time & computing power to get reliable statements about the performance of the miner under specific parameter settings. feel free to experiment with the settings (PPS is not always the best thing you should look at). once the beeeeer webpage is complete iāll offer more information about the mining stats (these will include stats about specific parameter).
[quote=āxolokram, post:286, topic:358ā]@ivanlabrie:
i dont have a clue what happened there
can you find the transaction in one of the public chainblock explorer websites?
xolokram[/quote]
I think I know now, could it be that the wallet that sent it stopped broadcasting the transaction before it got confirmed somehow?
A friend sent me that money it seems, and his pc isnāt working. (he has to replace a faulty motherboard and stopped syncing that wallet shortly after sending the funds)
Looks like some bug in the new 64bit protoshare miner: It just crashed. It was mining fine thenā¦ bam.
This is all I was able to pull from the Event Log:
Version=1
EventType=APPCRASH
EventTime=130285174858248297
ReportType=2
Consent=1
ReportIdentifier=5c650cae-49a0-11e3-b7c0-f80f4113c36c
IntegratorReportIdentifier=5c650cad-49a0-11e3-b7c0-f80f4113c36c
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=ptsminer_64bit.exe
Sig[1].Name=Application Version
Sig[1].Value=0.0.0.0
Sig[2].Name=Application Timestamp
Sig[2].Value=527ea3fd
Sig[3].Name=Fault Module Name
Sig[3].Value=ptsminer_64bit.exe
Sig[4].Name=Fault Module Version
Sig[4].Value=0.0.0.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=527ea3fd
Sig[6].Name=Exception Code
Sig[6].Value=40000015
Sig[7].Name=Exception Offset
Sig[7].Value=000000000043c692
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.1
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=4105
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=14c3
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=14c3b5febc7f62e086da1654817b49b2
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=97b7
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=97b79b56dbd34cfd04ac90a4023b4203
UI[2]=C:\Users\Silver_Pharaoh\Desktop\Prime Miner\Beeeeer\Protominer v0.3 x64\ptsminer_64bit.exe
UI[3]=ptsminer_64bit.exe has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Users\Silver_Pharaoh\Desktop\Prime Miner\Beeeeer\Protominer v0.3 x64\ptsminer_64bit.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\system32\kernel32.dll
LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll
LoadedModule[4]=C:\Windows\system32\ADVAPI32.dll
LoadedModule[5]=C:\Windows\system32\msvcrt.dll
LoadedModule[6]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[7]=C:\Windows\system32\RPCRT4.dll
LoadedModule[8]=C:\Windows\system32\GDI32.dll
LoadedModule[9]=C:\Windows\system32\USER32.dll
LoadedModule[10]=C:\Windows\system32\LPK.dll
LoadedModule[11]=C:\Windows\system32\USP10.dll
LoadedModule[12]=C:\Windows\system32\MSWSOCK.dll
LoadedModule[13]=C:\Windows\system32\WS2_32.dll
LoadedModule[14]=C:\Windows\system32\NSI.dll
LoadedModule[15]=C:\Windows\system32\SHELL32.dll
LoadedModule[16]=C:\Windows\system32\SHLWAPI.dll
LoadedModule[17]=C:\Windows\system32\IMM32.DLL
LoadedModule[18]=C:\Windows\system32\MSCTF.dll
LoadedModule[19]=c:\progra~1\agnitum\outpos~1\wl_hoo~1.dll
LoadedModule[20]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[21]=C:\Windows\system32\rsaenh.dll
LoadedModule[22]=C:\Windows\system32\CRYPTBASE.dll
LoadedModule[23]=C:\Windows\System32\wshtcpip.dll
LoadedModule[24]=C:\Windows\System32\wship6.dll
LoadedModule[25]=C:\Windows\system32\DNSAPI.dll
LoadedModule[26]=C:\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDNSP.DLL
LoadedModule[27]=C:\Windows\system32\PSAPI.DLL
LoadedModule[28]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[29]=C:\Windows\system32\WINNSI.DLL
LoadedModule[30]=C:\Windows\system32\rasadhlp.dll
LoadedModule[31]=C:\Windows\System32\fwpuclnt.dll
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=ptsminer_64bit.exe
AppPath=C:\Users\Silver_Pharaoh\Desktop\Prime Miner\Beeeeer\Protominer v0.3 x64\ptsminer_64bit.exe
I have a screenshot of the miner just after the crash, but I canāt upload pic on this forumā¦
the miner is compiled in release mode, thus the crash info wonāt help but thank you.
iām aware of that, iāll look into it, but itās kinda hard to debug, because itās not crashing on my machineā¦
[quote=āxolokram, post:283, topic:358ā]@gumik:
i think if the project is big enough you should give it a try to write it into a seperate thread. otherwise yes, the tech support thread is not the best choice i guess
yes, the log output of the miner threads (just the first few seconds, when everything is warming up) is not thread-safe.[/quote]
Well I guess no separate thread then, itās a really small script, maybe iāll post it on the general thread.
Okay thanks, yes I was talking about the warming up.
PTS miner is interestingā¦the 64 bit one is good, but ram usage is still huge per thread.
Iām using 3 threads on that, one physical core and two HT ones, and leaving the rest of my I7 3820 to xpm at beeeeer.
your work is saved. iām investigating the problem, which also caused the webfrontend to crash (which is btw. quite strangeā¦)
we have a new shares bundle thatās bigger than the othersā¦i think iāll split this bundle into several smaller ones to make it more likely to be paid early
iām sorry for the inconvenience. that protoshares story really wasted way too much time.
xolokram
ps. the web frontend seems to be (i dont want to say instable) slow atm please be aware of this
Iāve had some trouble compiling the pool miner for Max OS X 10.9 Build 13A598
This is the command I use to compile
sudo make -f makefile.osx
And here comes the error code I get:
In file included from alert.cpp:11:
In file included from /Users/wopex/Desktop/primeC/primecoin/src/alert.h:13:
In file included from /Users/wopex/Desktop/primeC/primecoin/src/util.h:36:
In file included from /Users/wopex/Desktop/primeC/primecoin/src/netbase.h:10:
/Users/wopex/Desktop/primeC/primecoin/src/serialize.h:911:10: error: class member cannot be redeclared
void insert(iterator it, std::vector<char>::const_iterator first, std::vector<char>::const_iterator last)
^
/Users/wopex/Desktop/primeC/primecoin/src/serialize.h:898:10: note: previous declaration is here
void insert(iterator it, const_iterator first, const_iterator last)
^
/Users/wopex/Desktop/primeC/primecoin/src/serialize.h:911:10: error: redefinition of 'insert'
void insert(iterator it, std::vector<char>::const_iterator first, std::vector<char>::const_iterator last)
^
/Users/wopex/Desktop/primeC/primecoin/src/serialize.h:898:10: note: previous definition is here
void insert(iterator it, const_iterator first, const_iterator last)
^
2 errors generated.
make: *** [obj/alert.o] Error 1
the sharelog entries are the āshelvedā shares
they are not dead, they will not loose their value in the sharelog, they will be paid - it just takes some time and adjustment for current share values
the problem with primecoins, in contrast to PPS based payout system for bitcoin, is that the different chain-lengths for shares have different values to prevent cheating.
thus the balance of the pool (low sharelog vs high sharelog) is fluctuating more than on bitcoin pools
I leave my machines running all day while Iām at school, and when I get home the terminal window has several lines of āforce reconnect if possible!ā throughout the day. At this point, I am concerned that I have done something wrong, and am wasting a significant amount of up-time. This is the arguments for the batch file:
please be aware of this