|
I'm still working on recovering the database. Unfortunately very important files were corrupted (earnings essentially), and our backups aren't up to date enough (read: a few hours too early) to recover enough data from them for another payout to be processed.
Ideally we'll be able to recover almost everything, but its a very ugly process to dig through...
|
|
|
|
I wonder how did scrypt mining drop below 100%? I thought it's vsLTC, so if altcoins are lower than LTC, we would mine LTC instead. Also, are we merge-mining dogecoins?
I noticed you have instructions for mining x13, but I don't see any stats for it. What coins would we be mining if we followed your x13 instructions? And what is the profitability?
I'm sure it was probably mentioned somewhere in this thread before, but it's a pretty long thread now. Thanks!
X13 is not working right now. If you try it the port will be dead. As for Scrypt, mining LTC does not always yield 100% "theoretical" LTC earnings due to variance, orphans, etc, and there is also the pool fee. Thanks for the explanation. Strangely, I don't see LTC or DOGE in the stats page, which worried me. Thanks again. We're definitely mining both  The issue is just that we've been reasonably unlucky (still within expected limited) in our LTC mining over the last few days. So when its saying 80% vsLTC, its essentially us mining LTC about 30% of the time (and getting unlucky, so having 0% reward for it), and other things 70% of the time and having regular luck (115%-ish reward). Putting us overall at around 80%. |
|
|
|
Hmm... Let's see... 4 VPS's from different providers, located at various locations all over the world... Nothing has changed and ALL of them are having a problem... Hmm. You must be right! You're working so the rest of the world must be wrong!
Everything should be working fine... All servers are up and running fine, no real changes to code have been made over the last week other than updating of coindaemons (which normally causes a quick disconnect/reconnect, normally less than a second or two). |
|
|
|
Just a heads up, we've essentially written off the Mintpal coins (~2btc). I don't forsee them fixing and recovering from their "upgrade". All of the balances that were outstanding on their end have been archived (we still have them, but they're not counted in stats). In the event that mintpal does come back up, and we can recover those coins, I'll import the user balances back, and everything should work correctly again. With the change though, stats for today will be blatently incorrect. Everything is working properly, and earnings are fine, just stats are off for today. Sorry for the inconvenience  |
|
|
|
Mintpal is gone. How many coin store in there unexchange yet?
Affirmative. "MintPal is currently down for urgent bug fixes, and is additionally moving to new management (away from Moopay LTD). A statement will follow shortly." The question is, when will we get paid? Cheers I unfortunately don't have a good answer for that. Glancing at the coins right now, it looks like we have approx 2btc in unexchanged coins, these coins were all mined within a few hours of mintpal "upgrading", when everything was explained/looked like they would be down for a few hours for upgrades, and then back to working order. Instead, they have been down (essentially) for a few weeks now, and some of the coins that were sent while they were upgrading still haven't shown up in the account. At this point, I honestly don't know whats going on over there. The original site was working fine, and then they botch an upgrade pretty majorly, and now they're either closing down, or changing management (@moolah_io on twitter seems like he's saying completely different things about what is happening every few hours). Essentially if the exchange comes back up and our deposits show up, we'll withdraw the coins and try to manually exchange them on whatever exchanges support those coins (if there are any). If we can't recover those coins (way too early to tell) they'll probably be written off, as there really isn't much we can do there. tldr; we wait and see for now. |
|
|
|
.. snipped ..
I really wouldn't read much into it. Its most likely just someone scanning around for vulnerabilities and spewing data at random ports/ips around the internet. Its obviously passing a cookie (something that isn't even remotely connected to stratum), you're going down a rabbit hole looking for stuff that probably isn't there... Imagine I pulled up a random SMTP vulnerability for a random SMTP server, and fired it at your stratum server. Your server would say "malformed message", and you can either ignore it (very safely), or spend a ton of time tracking down essentially nothing. |
|
|
|
Any idea what this is: 2014-10-13 19:16:37 [Pool] [diamondcoin] (Thread 2) Malformed message from (unauthorized) [117.25.128.139]: �Cookie: mstshash=g http://www.tcpiputils.com/browse/ip-address/117.25.128.139Not much help there, but it is in China is there any way I can examine the malformed message  I suppose I'll have to have some TCP logging of some sort and wait for another one ... only get it a couple times a day ... Looks fine, anything could be a malformed message, as long as it doesn't conform to exactly what NOMP was expecting. So if you connected and just sent "{a:a:a:a:A:a:a:a:a:]" to it, it would probably break and spit out the same line of text (malformed message). Assuming there isn't a flaw in how NOMP parses the data coming in, its just garbage data... |
|
|
|
Oh, and how in the heck does a coin have a negative BTC value? If the exchange rate is so bad that the feeds exceed the value then I hope their engine would just leave it unconverted until there was a positive value.
Thats a bit odd. For a number of the stats we use floats (since most of the time approximates are fine) and there might be a rounding error. Can you post the address you're looking at and I'll check it out? Isn't this from when blocks confirm but are later orphaned, or orphaned blocks are missed? It isn't a negative exchange rate, it's a negative coin balance because coins were paid out but later orphaned. No? This is correct, but thats normally (or at least I thought - I haven't looked into it in a while) listed under confirmed. They get moved from unconfirmed --> confirmed --> paid --> negative confirmed. Its most likely that a re-process of the block chains during maintenance changed that (we wipe tables and rebuild them from blockchains, which would see them as orphaned immediately, instead of immature --> confirmed --> orphaned). I'll check it out. |
|
|
|
Oh, and how in the heck does a coin have a negative BTC value? If the exchange rate is so bad that the feeds exceed the value then I hope their engine would just leave it unconverted until there was a positive value.
Thats a bit odd. For a number of the stats we use floats (since most of the time approximates are fine) and there might be a rounding error. Can you post the address you're looking at and I'll check it out? |
|
|
|
Oh, this is very useful for MinerControl. I'm already parsing the output from the stats call to get earnings per algo.
If possible, please don't parse the output of the stats page, there is an API for that (/api/stats), if theres something missing there, let me know and I can see how tough it is to add. The piece I'm asking about here is for the balance numbers. Here is the same result reformatted by jsonlint.com for easier reading. {
"scrypt": {
"hashrate": 0,
"hashrate_str": "0.00 kH/s",
"stalerate": 0,
"stalerate_str": "0.00 kH/s",
"workers": [],
"balances": {
"sent": 0,
"confirmed": 0,
"unconverted": 0
}
},
"nscrypt": {
"hashrate": 0,
"hashrate_str": "0.00 kH/s",
"stalerate": 0,
"stalerate_str": "0.00 kH/s",
"workers": [],
"balances": {
"sent": 0.00177243,
"confirmed": 0,
"unconverted": 0
}
},
"x11": {
"hashrate": 808137,
"hashrate_str": "808.14 kH/s",
"stalerate": 0,
"stalerate_str": "0.00 kH/s",
"workers": {
"1KSTYGj25RRQ5i1GNVUGTjUsSyZr4uSPiz_R9": {
"hashrate": 808137,
"stalerate": 0,
"str": "808.14 kH/s",
"last_seen": 1412611329
}
},
"balances": {
"sent": 0.02127437,
"confirmed": 0.00039378,
"unconverted": 2.220345987e-7
}
},
"x13": {
"hashrate": 0,
"hashrate_str": "0.00 kH/s",
"stalerate": 0,
"stalerate_str": "0.00 kH/s",
"workers": [],
"balances": {
"sent": 0,
"confirmed": 0,
"unconverted": 0
}
}
}
One thing I like here is that we have hashrate and balance per algorithm. Only NiceHash/WestHash gave me that previously. I'm not too happy seeing numbers like this: "2.220345987e-7". Hopefully the C# JSON parser handles this format correctly. It did pass the JSONLint so that is a good sign. Yep, "e-" and "e+" notation are both valid JSON Since some balances are super low and we're returning them as floats (only other option would be as strings, maybe satoshi integers), they come up with scientific notation. Now, a question. There are three numbers: sent, confirmed, unconverted. I want to see if I understand this correctly: - sent - BTC transferred from the pool to the address.
- confirmed - BTC earned and converted.
- unconverted - approximate BTC of unconverted coins.
Based on this it looks like a person's current balance would be "confirmed + unconverted" although the amount ready for payout is only "confirmed". Does this sound correct? This is correct. Confirmed is how much you have confirmed BTC. This number should only ever go up (until a payout). Unconfirmed will vary a bit as exchange rates fluctuate. On your next payout (assuming you meet the criteria) you'll be paid the amount in Confirmed. |
|
|
|
|
We're having some problems with our database (contacting the host right now) looks to be hard drive related. But mining is disabled for now (should failover to backup pools) until it is sorted out.
Edit: Everything should be fine now.
|
|
|
|
Rejects should be fixed. We had some issues with one of our hosts (first time we've had a host issue) where connections to the network from EU and (only one of) USEast servers would keep dropping, so the coindaemons were getting out of sync and causing some issues. Everything should be fixed, and I'm really sorry for the degraded performance.
And about my 6 hours with 8,5 mh/s earning me 0.0000001? Should i have lost that? If yes its a good time to look for another pool. Things happen, the same with literally any pool, if you pick the perfect 6hr period (which, this is the first we've had stratum problems like this in probably 3-4 months) then yes, stats can look pretty bad. Sorry you feel that its time for a new pool, but I do wish you the best of luck there. |
|
|
|
|
Rejects should be fixed. We had some issues with one of our hosts (first time we've had a host issue) where connections to the network from EU and (only one of) USEast servers would keep dropping, so the coindaemons were getting out of sync and causing some issues. Everything should be fixed, and I'm really sorry for the degraded performance.
|
|
|
|
Wafflepool Seems to be saying one thing the day before a and then something less the next day. This Has happened to me tree times over the last 5 days. Went to be last night an d it said I had just over 0.004. Log in today some 8 Hours after and it says 0.0039. This has happened three times
In unconfirmed and unexchanged balances? Of course it changes - it's unconfirmed or unexchanged, and blocks will be orphaned or exchange rates will fluxcuate. Are you really complaining about a 2.5% decrease in an estimated value? This is also exacerbated by an unfortunate set of coins that were mined. One of our hidden coins had a reasonably low difficulty (thus high profitability) so we mined it pretty hard. Unfortunately, it doesn't adjust difficulty every block like most recent coins do, but makes an adjustment every few hundred blocks. Once the difficulty adjusted (with us mining included), it became unprofitable, so we moved away, and now, blocks that should ideally be taking ~1 minute to find, are taking upwards of an hour to find (extremely high difficulty, extremely low profitability = no one mining). So we have a decent amount of coins that are taking a very long time to finish maturing/exchanging, and are affect the graphs pretty heavily (you can see all the price swings in the graph pretty easily). They should be getting out of there in the next couple days, but short of just removing them from the graphs, there isn't much we can do about them. We have protections in to prevent this from happening in the future as well (this is the first time we've had this type of problem). Waffle pool was showing 220% of ltc profitability clevermining was shwoing 139% while i was mining on each of the servers. How do you explain that? Poor hashing efficiency on waffle is my case too. Difficulty set as adviced to 8192. Any smart and logical explanation to those numbers?
Historical profitability is not an indication of future performance... If waffle is reporting 220% LTC profitability, that is historical data and isn't necessarily what you will earn if you mine for the rest of the day. If you don't mine for at least several days, you shouldn't expect things to average out reasonably. Difficulty is also totally irrelevant to realized profitability. Can you elaborate at all on this? I scan through here and through my emails pretty often, and this is the first complaint I've seen about it. Hashrate on the site hasn't changed much (if I pushed out code that caused the low efficiency, would normally see a hashrate drop associated with it). But we did change the stratum servers a week or so ago to work with merged mining, so its possible its only happening with certain miners. As always, more info is better than less |
|
|
|
|
Numbers might be off for a bit here, had to disable a few things from Mintpal while they're being DDOSed.
|
|
|
|
PoolWaffle, it looks like unconverted script is piling up. I'm seeing almost 3x unconverted verses earned.
Maybe something is stuck?
Don't think so. Our hashrate spiked a good bit today (profitability up significantly since adding merged mining), and combined with mining a large amount of one of our more profitable hidden coins (which has a reasonably long maturation period), our unconfirmed is up. I've gone through it just now and made sure, blocks are maturing properly and exchanging when they confirm |
|
|
|
Dogecoin Merged Mining is enabled on 100% of the pool. You guys should start seeing blocks get found over the next few hours |
|
|
|
Hey guys, quick update: We're actively testing (about 5% of the overall pool) merged mining with Dogecoin. Assuming everything looks good we'll start expanding it to larger sections of the pool in the coming days. You shouldn't notice (or have to) change anything on your side, just keep mining away |
|
|
|
Hi,
does anyone else have a blank miner stat-page?
No, but X13 old balance is gone...and my X11 balance keeps erratic, always correcting to minus. Yep, working on fixing it. Basically going back through and manually processing stuck blocks (orphaned blocks from months ago), as well as disabling X13 and some coins that are no longer being traded. Seems to be affecting the balance logs oddly, so things my look a bit off for now, but everything is working fine and should be back to normal in a bit. Tks for the reply, I also noticed that Startcoinv2 balance was almost totally unexchanged yesterday, some problem related with that coin specifically? That is part of it, but its part of a much larger cleanup that I'm working through now. Just a TON of grunt-work that I've been putting off for forever (just going to take a full 12hr day of the most tedious/boring tracking down of blocks ever to make sure we don't miss anything). |
|
|
|
Hi,
does anyone else have a blank miner stat-page?
No, but X13 old balance is gone...and my X11 balance keeps erratic, always correcting to minus. Yep, working on fixing it. Basically going back through and manually processing stuck blocks (orphaned blocks from months ago), as well as disabling X13 and some coins that are no longer being traded. Seems to be affecting the balance logs oddly, so things my look a bit off for now, but everything is working fine and should be back to normal in a bit. |
|
|
|
|
Show Posts
