Search results

Update: Another backend improvement of management server: - Fixed some memory leaks - Faster create / restart / status update of all running nodes

increased testnet slots to 50

Update: Problem solved which prevent using testnet ~

Thanks for this hint ! Its solved :)

testnet is up again, but currently capped to 30 testnet nodes. I will increase it as soon as i see its stable ~ testnet is now on c0a5dfba6121186476966b68139930c29db7918e

Thats not correct, testnet is running on v12 main on v11. V11 is not touched since may(?), v12 is under active development.

sure, but could you explain me why? :)

Im not really new, but not that active in forums. Thats the reason why its currently absolute free. The way the cloud is running came me on night and thought it would be a nice approach. But there are a lot of complications i have to fix until its getting really stable :) Anyways the main-net...

Testnet currently completly disabled. It will be back soon ~

updated testnet to 9e5cd419d0f6ff67c83ec0ffe7a777add6f0110e Edit: Im still beware of dropping masternodes in testnet. But hadnt had any time yet to dig into it further sorry about that ~ Soon theres going to be a patch for more testnet nodes ~

Thanks for keeping me updated, so we have to investigate further.. I did not shutdown any of your nodes, they were already expired as you send me the list. y99Q9aDgmTDpxf2m7tTMwLU4stVUaSA4kU please send me as much as you can ~ Also i noticed the testnet is not bind to 19999, its even possible...

Only a guess of mine: - The reason why they getting payed is that you started them once with the 'normal' start procedure. - You were creating new nodes on our page instead of using the existing ones. - Maybe with wrong node parameters/maybe you were to slow to start them. (they expire after 2...

Thats exactly what im reported. Thanks to bertlebbert and moli for pointing me to it ~

thank you doing my best :)

I investigated, i guess the reason is that you using expired nodes on my cloud system. (Which doesnt exist anymore) Start-many has currently a bug which leads to a successfull response even if theres no node running on the give IP. Check this out: https://github.com/dashpay/dash/issues/436

https://github.com/dashpay/dash/issues/436 please fix this asap :)

hmm thats strange i didnt use any commands except getinfo. Heres my config: rpcuser=<randomString> rpcpassword=<randomString> server=1 daemon=1 masternode=1 masternodeprivkey=<privkey> testnet=1 masternodeaddr=IP:19999 Daemon is started with: dashd --datadir=/d -testnet -txindex=1

Sadly i already noticed this. Anyways it looks like the issue is not on my system. Its the daemon itself which is crashing. Hopefully i get response asap from the devs to solve it. (Thats why i added "Collecting crash logs depending on git commits to help out the devs") Please be patient it...

Nobody replied, the daemons still dieing.. Currently im running on: 7101c951f8ea0a5df6b81fb018725d373d664c86 Main-net is stable and running without issues since ~ 3 weeks

Updates ! Stats on Main-Page Fixed some bugs in autoupdater Restarting VMs/Daemons in case of crash / failure Improved backend monitoring Collecting crash logs depending on git commits to help out the devs