Ok. My internet is back.
The solidcoin 1.04 client just doesn't want to play nice with pushpool...... It's back up.
UPDATE: seems memcached is acting up, not so much pushpool.
yes, memcached is zombied. Forcing server reboot, should only be a minute.
UPDATE2: Back up and running full steam.
I am still getting periodic disconnects and stuff. Are you still having solidcoin issues? There was a hardware server restart, it kickstarted the old monitor I had up, which killed solidcoin. That said the client is still buggy. I'm going to modify the new 1.10 beta shortly and pray that it is more reliable. |
|
|
|
|
Ok. My internet is back.
The solidcoin 1.04 client just doesn't want to play nice with pushpool...... It's back up.
UPDATE: seems memcached is acting up, not so much pushpool.
yes, memcached is zombied. Forcing server reboot, should only be a minute.
UPDATE2: Back up and running full steam.
|
|
|
|
|
SQL server update is complete. Both master and slave are running with 4x the ram as before and on mysql 5.5.
Both pools & sites are back online
|
|
|
|
My miners aren't connecting!
Lot of stales!
Site is saying it's broken too!
Pool is definitely acting up again!
Me too, I am getting a ton of downtime and communication errors in CGMiner. Switching overnight to my backup. following suite. i'll again wait till its all back up. Maybe wait till the new server is online. Yes, the issues continue to worsen. I'm going to go ahead and swap to the new pool & db server. There will be a bit of downtime (was going to go for seamless, but now the servers are just building stales). UPDATE: make that just the new sql server. the pool server is ok, but the solidcoin pool will be offline until I can fix the client. UPDATE2: The situation required drastic measures. I'm sorry for the downtime, but the changes should greatly benefit the pool. |
|
|
|
pools down
solidcoin hung and went resource crazy. I haven't been able to modify the new client version yet, so I'm using the old fashioned long-polling method against a single threaded client. It does well for the most part, but randomly just takes down the other processes with it. Once the new pool machine is ready (oh so close), even solidcoin freezing shouldn't be able to take it down. |
|
|
|
Why wont this pot boil!
Stop looking already..... |
|
|
|
bitparking is no longer a solidcoin exchange. anyone have any good solidcoin exchanges to try. i have bee looking into solidcoin24 and moonco.in.
moonco.in is good, and ruxum is fixing theirs. THIS BTC ROUND MUST DIE! |
|
|
|
Looks like the solidcoin client db was corrupted. rebuilding it (sorry for the gazillion longpoll messages).
Basically this, on both! Welcome back! We've been missin' ya around here! This MFing block....Robble...robble! No kidding, this block is BRUTAL. make it end! |
|
|
|
|
Looks like the solidcoin client db was corrupted. rebuilding it (sorry for the gazillion longpoll messages).
|
|
|
|
What is going on with the pool?  The solidcoin pool has had a terrible run of orphans.... the transaction log is a sad sight. (Update: looks like its tied to low difficulty. Going to try to find some better hub nodes) Any other issues you are seeing? I'm currently working from a tablet riding down I 40. I've been mia from the forums for a few days, but ive been monitoring the current servers and working on the new servers from my phone and tablet on tethered 3g. Sorry if i missed any messages, but il be back fulltime in just a few hours. The new site and servers are about 75% ready. Just need some more tuning and ill be swapping them over soon. |
|
|
|
i'll wait till that all clear before starting my miners.
It's all clear now. Running smoothly. The first new server is ready (just needs the new code), and I'm waiting on the 2nd to become available. |
|
|
|
is the pool down?
It's either up, but just a little bit, or cgminer is doing an awful job of rerouting all my work to my backup pool by looking at my hashrate there. Oops! Now my fully 400 MH/s is at my backup, so I suppose we are. Yes, the sql server has died. Thanks to replication, no loss of data and we're back online. Also thankfully I purchased a new server, so less downtime for that machine i think it died again  It did... Syn flooding on the pool server. I guess the sql machine isn't the only issue. I'll have it up as quickly as I can. |
|
|
|
is the pool down?
It's either up, but just a little bit, or cgminer is doing an awful job of rerouting all my work to my backup pool by looking at my hashrate there. Oops! Now my fully 400 MH/s is at my backup, so I suppose we are. Yes, the sql server has died. Thanks to replication, no loss of data and we're back online. Also thankfully I purchased a new server, so less downtime for that machine |
|
|
|
Just rented 2 more servers. Even bigger than the existing 4  I'm not going to go the ec2 route after all. As nice as on demand servers are, the pricing just doesn't compete with my existing service. |
|
|
|
The solidcoin client hard locked again.... Love the coin, but the client needs some work. Oh, and there is now a Contests and Giveaways section to the forum.  |
|
|
|
It's about time you found a block bossman!!!!!!!
And not only one, but two!
Two with under 1 ghash under 4 hours just goes to show that it does not always matter how much. Its how lucky Now i would like to find one just so i doesn't seem like i'm leeching all this time  You leech!  Your hashes are still helping! Think of it this way; each share you get, changes the order of the shares everybody hashes. If you weren't here, another pool may have ended up with that specific share! Boy, it makes more sense in my head! Good work mike! [/thumbup] You're on a roll! Awesome! All this time I thought you were just making your shares up . Nice going mike! Yeah.... No. Of course, now that I got that... one of my machines is giving a hyper transport error  That said, the next BIG site is in the works. |
|
|
|
|
You'll need to add the new table (unrewarded_shares) and look for other sql changes.
|
|
|
|
|
Rebuilt and restarted bitcoind, it had a steady memory leak and was starting to eat into swap and slow responses. That said, the outage should have been around 1minute.
That said, even with a memory leak it ran for a good couple of weeks without a restart.
|
|
|
|
The kicker is that they will all be separate pools, with separate payouts.... There is no way to allow all 3 in one pool as the pool would hemorrhage coins.
UPDATE: The new block info is in place. Unfortunately some of the blocks were combined in archiving, others haven't been archived.
I'll be working on getting the future data in each block cleaned up so we have better stats moving forward.
While I'm all for choice I see two problems with this: - The mining resources will be split and everyone will experience increased variance.
- The proportional payout system is quite complicated and requires much more overhead. If you have the server resources to handle it then fine but I think it's important to let people know what pool-hopping is and give them links to the appropriate threads and software.
Hopefully, it will draw others to the pool. I assume most of our current base enjoys lastNshares. As for overhead, proportional payout is even less overhead than lastNShares (db size is smaller, less range scans). I'm aware that proportional will increase pool hopping, but it won't affect the lastNshares pool as it will be separate. By default, miners will be set to lastNshares. Additionally, if the overhead is significant, I just scale up the servers. |
|
|
|
How about bringing up solidcoin pool so users can withdraw their unconfirmed coins.
This is rediculous.
The pool is up. If there was an outage it corrected itself. I'm looking into the logs now. I don't see an outage in the logs either, or even the monitor restarting a locked service. |
|
|
|
|
Show Posts
