Search results

infrastructure completly running.

Interesting, how is it possible that these nodes then are not dropping? and im able to start them / they get payed? admin@xxx:~$ sudo iptables -nvL Chain INPUT (policy ACCEPT 1555K packets, 1405M bytes) pkts bytes target prot opt in out source destination Chain FORWARD (policy ACCEPT 0...

dashninja was never able to detect the nodes version properly (i guess its somehow related to Docker were using), also hat some talks about it with the owner of dashninja but it was never fixed. Ports are open. You can figure out the version on your personal status page. Currently we having...

updated last week.

Hello, Docker hat some issues.. it crashed on some of our servers. We downgraded and fixed to a working version. Thanks for reporting and sorry for the trouble.

Sometimes the Android Widgets are showing wrong data (all 0) is this fixable? :)

Dont worry youre not the only one. Im having beside the masternode service another service running on OVH (+500k users) sadly the poor truth is that you always have issues with this OVH stuff. I fight with them since years, but they are that cheap that even you make your services redundancy...

We had some issues during the last days, sorry about that... well add some extra credits for this issue. All up and running again!

tagged here: https://dashtalk.org/posts/89308/ Which says were out of service / offline. thats not right our systems are up and running, stable since months. If you have any questions just write me a pm so i get notified via email ~

hmm.. didnt get any notifcations for beiing tagged here. The website is up and running (stable for a couple of month now), i dont see any problems.. (hosting myself all my nodes over this page)

small server updates :)

but it was not pinging until i restarted the dashd on the server, anways i wrote a workaround for my cloud service.

fixed a bug / workaround for this trouble here: https://dashtalk.org/threads/56-nodes-not-start-pinging.7986/ (it prevented for restarting nodes properly, they were dropped again after ~1 hour)

Logs: 2016-02-07 11:45:46 mnb - Got NEW Masternode entry - 27c44daa4f9acecf2ec4dad33273684ca87b40589523c3e6971de7c5aa537e44 - 188.165.84.238:9999 - CTxIn(COutPoint(a840f157aa9cc908272688d06563f4cfd3e21accd8882b7f5354383aa4241939, 0), scriptSig=) - 1454760807 2016-02-07 11:46:22...

hey, i got trouble since i run on .56. it seems the nodes dont start to ping. status on the nodes say: { "vin" : "CTxIn(COutPoint(a840f157aa9cc908272688d06563f4cfd3e21accd8882b7f5354383aa4241939, 0), scriptSig=)", "service" : "188.165.84.238:9999", "status" : "Not capable masternode...

very cloudy today.. thats why we released another stability update :). Any feedback would be awesome !

another stability update~

i guessed based on your data is solved, do you still have problems?

Sadly we had an issue with some of our VPSs. It was out of my scope, im sorry for that. Also i further improved the managing software (memory leak workaround) which grants more stability.

hey daz please check your pm. the system is back stable again