[ANN] ptsweb.beeeeer.org - Protoshares mining sub-pool

[MarcusDe]

Its simple, there are no lines with:
[MASTER] submitted share -> SHARE

[soulhouser]

@xolokram
Hey xolo, that new miner is quite fast! Just one small problem: After 1 hour of mining, the miner will "forget" to hand in the collisions it finds. It still finds them, but it never gives them to your server....

So since it never hands them in, it lost shares right 
That sucks, because there was a lot of collisions last night for me.

How did you find out this?

[Silver_Pharaoh]

@xolokram
Hey xolo, that new miner is quite fast! Just one small problem: After 1 hour of mining, the miner will "forget" to hand in the collisions it finds. It still finds them, but it never gives them to your server....

So since it never hands them in, it lost shares right 
That sucks, because there was a lot of collisions last night for me.

[MarcusDe]

@erko

Thanks for help!

Well, there is no endian.h and be64toh in (recursive saerch)
/usr/include
/usr/local/include
or anywhere else ;-/

OS is old suse enterprise, without support.
Any more ideas?

edit:
Heh, I found those defines in system which have them, I will try to put them manually in ptsminer files.
edit2:
Helped myself and others with problem like this:
in sha512.c added:
#include <byteswap.h>
#define be64toh(x) __bswap_64 (x)

Works, on defaults c/m moved from 190 to 200.

[erko]

MarcusDe,

Since this is the error:
    error: ‘be64toh’ was not declared in this scope
you need to make sure be64toh() is defined.

You can run "grep -r be64toh /usr/include/" to see what header file defines be64toh and add it to the top of sha512.c or sha612.h.

For example, my machine shows "/usr/include/endian.h", so I would add
   #include <endian.h>
to the top of sha512.c.

The solution/problem could be a little different, but missing the correct include is one of the more common reasons for this error.

[MarcusDe]

Hi,

I could biuld all miners before without problems;
but 0.7 gives me this:

g++ -c -O2  -fpermissive -o obj/sha512.o sha512.c
sha512.c: In function ‘void _final(SHA512_Context*, uint8_t*, int, int)’:
sha512.c:103:32: error: ‘be64toh’ was not declared in this scope
 #define BYTESWAP64(x) be64toh(x)
                                ^
sha512.c:257:17: note: in expansion of macro ‘BYTESWAP64’
  lengthPad[0] = BYTESWAP64(sc->totalLength[0]);
                 ^
make: *** [obj/sha512.o] Error 1

I even compiled yasm + gcc from source and that didnt help lol.

[Clark]

nearly 6 hours without block found!

Is there anything wrong?

Just paid, was a very big block by the looks of things

24378 2013-11-23 07:28:21 2556 / 1533736 -> 0.04437 PTS / 26.62 PTS -> block waiting for confirmations

got that. Really big.
But I thought maybe the decrease of pool's workers cause the pool, as a whole, become weak.
So we have to wait long time for a block.

Am I right? Just become a miner for two days.

[devilfish]

nearly 6 hours without block found!

Is there anything wrong?

Just paid, was a very big block by the looks of things

24378 2013-11-23 07:28:21 2556 / 1533736 -> 0.04437 PTS / 26.62 PTS -> block waiting for confirmations

[Clark]

nearly 6 hours without block found!

Is there anything wrong?

Maybe I will move to another pool since I have no patience now.

Besides, I test v0.7 on Suse 11. It proves to be very useful.
And I have more memory to use, 8G per core. Can you offer a optimizaiton for this situation?

The 0.6 version of yasm is too old.
Then I test yasm v1.2. It's OK.
So, you can add this issue to help others.

[Riverhead]

Maybe the software is used on bot nets so is getting picked up as malware?

[dma88]

after mining for a week or so, commodo finds malware in the miner, here's a screenshot:

https://www.dropbox.com/sh/dszlyattlss0g74/-pBgTuf5PF

anyone else run into this?  why didn't it spot anything earlier?

[devilfish]

I just posted fixes for the MacOS build at https://github.com/jave27/ptsminer and submitted a Pull request for xolokram. I'm not positive that the CMake changes will work for Windows or 64-bit Linux, though. That should be tested before it gets merged.

I tried this on my mavericks system and got the following upon make:

Code: [Select]

sph_sha2.c:626:5: error: assigning to 'sph_sha224_context *' from incompatible
      type 'void *'
        sc = cc;
           ^ ~~
sph_sha2.c:641:5: error: assigning to 'sph_sha256_context *' (aka
      'sph_sha224_context *') from incompatible type 'void *'
        sc = cc;
           ^ ~~
In file included from sph_sha2.c:653:
./md_helper.c:134:5: error: assigning to 'sph_sha224_context *' from
      incompatible type 'void *'
        sc = cc;
           ^ ~~
./md_helper.c:184:5: error: assigning to 'sph_sha224_context *' from
      incompatible type 'void *'
        sc = cc;
           ^ ~~
./md_helper.c:206:3: error: no matching function for call to 'sha2_round'
                RFUN(data, SPH_VAL);
                ^~~~
sph_sha2.c:650:16: note: expanded from macro 'RFUN'
#define RFUN   sha2_round
               ^~~~~~~~~~
sph_sha2.c:613:1: note: candidate function not viable: cannot convert argument
      of incomplete type 'const void *' to 'const unsigned char *'
sha2_round(const unsigned char *data, sph_u32 r[8])
^
In file included from sph_sha2.c:653:
./md_helper.c:248:5: error: assigning to 'sph_sha224_context *' from
      incompatible type 'void *'
        sc = cc;
I was going to have a play today to see if I could work out what was going on. Were you getting the same errors on make that I was (something to do with the endian.h include?)

[joele]

xolokram,
Can I have the old link of version 0.6, the 0.7 is not properly running in my Ubuntu machines and I need to add more machines.

After compiling v0.7 in Debian 7 and Ubuntu I'm getting Illegal instruction after running. Fyi, any idea how to fix this?

[afr33sl4ve]

It is whining on collisions when I put on 24 threads w/ 26 memory option.

Or whenever I go over 12 threads.

The 0.5a miner is doing the same with 3 threads and default memory size.

EDIT: The 0.7 is stating collisions with 4 threads and default memory on my cloud instance.

[GotExams]

It is whining on collisions when I put on 24 threads w/ 26 memory option.

Or whenever I go over 12 threads.