a way to see what miners are up, what hash rate they have, and what is its current coin from the workers page would be nice. because going to each pool in an "algorithm" mining (for asics or GPUs) is really hard to know what pool it is mining too.

Really interested to know what happened.

I have been frozen too by this group, and they do not answer support tickets at all, now I lost the coins I sent to this service.

Their support is better than if it did not exist, but just barely, not by much.

Regarding my network issue, it seems it is a problem with linux and TCP_DEFER_ACCEPT

as explained here:
https://labs.ripe.net/Members/gih/the-curious-case-of-the-crooked-tcp-handshake

I'll keep investigating.

I can monitor the network, but the funny thing is the network only does this with your miner, it does not happen with any other program or configuration. and it happens only on 1 computer. if what you suggest were true, it would have several disconnections for all computers at the same time. But it doesn't. Everything points to be something in your code triggering some weird configuration on the latest ubuntu update (since I updated both ubuntu and your miner at the same time).

I'll take a look at the NAT/routing tables in the kernel and see if I can find out what is going on.

Sigh.

I have been running it for 1h30m and so far it has not disconnected. not even once. I'll leave them running and report back later.

edit: added a period to make it clearer.
edit2: it happened again it took longer, but same effect.
https://image.prntscr.com/image/isZkxQR2Q5eAaowYdayVCQ.png

I would like colors for temp ranges. and I don't know what the "+" to the right mean... or the ">" signs. oh well.

I have noticed that then it shows disconnection it starts getting lots of TCP errors. The werid part is only the computers that are running ZM miner show this behaviour, so i am sure this is not a network issue.

https://image.prntscr.com/image/seXWVVuuRP6t36sCm3INWw.png
https://prnt.sc/gsy4x3

                                                                                                                     
Systems are wired.

Imagine a memory leak, but made with open sockets. That is what this feels like. could be or not, I am just trying to explain it somehow. Like, if you have a disconect, do you close the socket or does garbage collection close it? do you reuse the sockets? what if the sockets are left alive and for some reason my installation doesn't do garbage collection until network crashes? again, this is pure guesswork. this is a shot in the dark and may not even be possible. Just saying what it "feels" like.

Seems weird. I imaged the system as ubuntu 17.04. I can get the image online if you want to try it or I can get you access to one of the rigs too if this proves too troublesome.

I'll make it with -dev, give me a couple of hours to let it run and I'll send you those.

Yeah, I am pretty sure this is something that should not happen, this is weird.

4.5 and 5

Yes they appear regular, however disconnects only happen when zm is running. Otherwise the computers do not disconnect. I tested this by only running zm in one GPU miner while the others where doing other miners and only the box with zm disconnected.

Not that I am aware of.

It's approximately one hour and it starts counting at the time zm starts running. I don't see any memory leaks. It seems a lot like a build up of connections not being cleaned until network crashes.

This is puzzling, sure, I do have 3 boxes with the same behavior. I'll go ahead and see if I can reproduce this behavior in a freshly installed box.

I agree, but all the connections are closed. And most connections are to servers that are meant for multiple connections (as httpd).

Hard to check if we can't pinpoint where to look.

Sure, what logs do you need?

It most definitively is.

I switched miners to ewbf to test, and the graph I got was no more disconnections. This has to be some sort of throttling, I have 24 cards, I split them in groups of equals. So tot he pool it must seem like I am making 24 separate connections at the exact same time.

you can see the difference between zm disconnecting, and ewbf staying normalized. Something is amiss, but I don't know exactly what it is, nothing changed, only the miner program.
https://image.prntscr.com/image/SkRIFTAmQOWRi5WTz_2ang.png

I keep getting disconnects every hour or so (as you can see in the graphs) and that happened when I upgraded to 0.4.5

I am now trying 0.5

https://image.prntscr.com/image/4YGPv_YCTyiD0A7l2SfRHg.png
https://image.prntscr.com/image/limqbGRARyyb2riP2Z68RA.png

This is really bad for me since the average with this is a lot lower than it should.
Is there a way to just make just one connection instead of one connection per card?

edit:changed image links

when you buy a car, do you pay henry ford for making the first car in mass production? No you don't
When you have the choice to get a Cheap car, or the fastest car, which one costs you more? The fastest car of course.
making those improvements is as hard a job as creating the algorithm in the first place. I am a developer myself and I am pretty sure it is not that sp_ can't do the algorithm but it would be most likely a waste of time.
And maybe, just maybe, some coders are really bad at understanding algo's from text but really good at understanding algo's in code. So why waste time creating an slow algo to then improve it instead of just making one faster?

sp_ do you have a linux version of the skunk mod for signatum?


I have a beta bot that does what nicehash does, with any miners you tell it to use, in windows and linux, as services or batch files.
It depends on whattomine to do the calculations right now. and you can totally make a nicehash only version for linux if you change the configuration file to only use nicehash pools.

It currently does NOT support:
splitting of cards (unless you run multiple copies)
dual mining algos (not listed in whattomine, so can't calculate that)
status of the miner (it starts and stops them, but can't figure out if they are running or not as of now).