Quote from: CripLib on July 18, 2014, 02:07:44 PM

Quote from: DyslexicZombei on July 18, 2014, 08:46:29 AM

Quote from: CripLib on July 18, 2014, 02:58:56 AM

Good evening, DZ,

Please let me know if I have been already fit into a node (and which), as I have sent you the "odd amount" of 280 DRK. Also, what is the most convenient solution for this "odd amount thing": I could send you 20 DRK more, in order to complete 300 DRK; or else you could simply make me a 28% stake. If not, then you can send the 30 DRK refund to my previously informed wallet payout address.

Cheers

Hey CripLib,

You would be in Node 5, but the problem is I'm concerned about starting a 5th community node with all the unintended extra work and troubleshooting just 4 beta nodes has caused me.

I'm concerned enough to hold off full node setups unless the full node user only does 1 Node...and they may have to find someone else to manage it because 10% really isn't enough if some nodes require literally 5 rebuilds in a 2 weeks span. I can't be servicing full nodes in volume if each one is going to require excessive troubleshooting or that a cold wallet could get hosed from.

*If* I can get Node 3's control of the stake back into the wallet its meant to be in, I'll continue this service past this month. If not, I'm going to have to consider this too high risk for even someone with my high risk threshhold. This software's essentially Version 0.61 at the moment, before Version 1.0 in a few months.

Let me know if you just want me to send the 280DRK back or if you want to hold off to see if Node 3's phantom self-payment can be resolved.

Oh, thank you, DZ,

I hope you manage to figure out a solution for the node 3 problem.

Please let me know.

Success!

Still working it. Have some promising things to try. One of the DRK talk forum admins has seen this database error problem before but it was on a Linux PC and his fix may not be directly applicable to our error.

As for Node 2 which was down: Couldn't get it working no matter what I tried so I transferred the 1000DRK to a different local wallet and started from scratch on a different server. It was up during the weekend then it went down again yesterday. At least I only had to restart it this time instead of having to do July rebuild #7 for this node.

Node 2 has a new IP address since I had to house it on a new server. I'll just list it here so I don't have to re-share the Node 2's spreadsheet: 54.186.252.193

Node 4 has been steady (knock on wood) and has been up since the 7th without incident. All of these nodes are configured the same; just seems to be random chance whether a node is stable or if it needs constant rebuilds or re activations.