• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

[dashninja.pl] Dash Masternode Ninja - Free Masternode Monitoring

elbereth said:
Well OVH is crappy for customer support so I will probably never get any answer regarding the outage.
Or they will just plain lie about it.

If you want to know more:
1) The dashboard for monitoring the server said it as online the whole time.
2) When I tried to create a support ticket it did not work until after 1h into the outtage
3) They did not answer the support ticket (still open)
4) The weathermap of their datacenter never showed anything (all green, no servers down anywhere) for the whole duration of the outtage
5) I know for a fact (From their incidents page) that almost 250 servers were down for almost 7h for the most unlucky ones. But in the incident those servers were in another room of the datacenter (not where my server is). Still the weathermap was green for the whole duration of the incident...
6) I tried a cold reboot thinking it was my server alone having a problem. Twice the automatic answer was that the server was not pinging after reboot (OVH monitoring page still saying everything was OK) and that a tecnician will have a look (never had).

So their monitoring sucks, the weathermap is a lie and the support team never answers (or not correctly).

It was actually my offsite (not at OVH) monitoring that alerted me the server was down.

They are just awful... But cheap and with a good network.
Click to expand...
Oh, OVH? Not a ringing endorsement. They have been adequate for me to run a couple of Masternodes on, though. I'll keep monitoring them, because I dont like bad customer service. If I need them for something, and they don't respond to me, its arrivaderci...
 
elbereth said:
Changed a bit how the back-end retrieve blocks values (especially the BlockMNPayeeExpected and BlockMNRatio values).
It should be more accurate, display the result even if the blocktemplate was never retrieved and be a little bit faster.
Click to expand...
I have a question if you don't mind: what rpc you use (used to use before) to get them?
 
I did not change the RPC calls just the query in the API.
You see I store the values for all the nodes and before this change I was forcing the use of NodeID = 16 (p2pool). So if p2pool did not retrieve anything the block was missing.
Now I just get the majority consensus from the table.
 
elbereth said:
Well OVH is crappy for customer support so I will probably never get any answer regarding the outage.
Or they will just plain lie about it.

If you want to know more:
1) The dashboard for monitoring the server said it as online the whole time.
2) When I tried to create a support ticket it did not work until after 1h into the outtage
3) They did not answer the support ticket (still open)
4) The weathermap of their datacenter never showed anything (all green, no servers down anywhere) for the whole duration of the outtage
5) I know for a fact (From their incidents page) that almost 250 servers were down for almost 7h for the most unlucky ones. But in the incident those servers were in another room of the datacenter (not where my server is). Still the weathermap was green for the whole duration of the incident...
6) I tried a cold reboot thinking it was my server alone having a problem. Twice the automatic answer was that the server was not pinging after reboot (OVH monitoring page still saying everything was OK) and that a tecnician will have a look (never had).

So their monitoring sucks, the weathermap is a lie and the support team never answers (or not correctly).

It was actually my offsite (not at OVH) monitoring that alerted me the server was down.

They are just awful... But cheap and with a good network.
Click to expand...
WOW! This is so great to read. I thought I was alone in being lied to by OVH support when they basically said my gear didn't go down even though it did go down three times. Glad to see this is pretty much the norm for their customer experience.
 
Just a heads up: to make the api calls faster and have less strain on the database I have finally added cache.
Most query results are cached for 5 minutes.
When you hit the cache it should answer without delay.
No way to bypass the cache atm.
 
elbereth said:
Just a heads up: to make the api calls faster and have less strain on the database I have finally added cache.
Most query results are cached for 5 minutes.
When you hit the cache it should answer without delay.
No way to bypass the cache atm.
Click to expand...
Nice one - but where did the 'last seen' info go?

upload_2015-6-27_15-6-1.png
 
Back-end (API) and front-end updated to support v0.12.0.
Beware of API changes! See OP for API info.
v0.12.0 masternodes are identified by their vin hash and index.
Country data for the IP was moved to the port checker structure.
Some fields were renamed.
 
Added budgets page:
https://dashninja.pl/budgets.html

Still basic, but I have plans to add a budget detail page with all masternodes that voted.

On another note, I am starting to open source Dash Ninja.
There are several parts (Back-End, Database, Control scripts, Front-End and IRC bot).
For now:
- Back-End: https://github.com/elbereth/dashninja-be
- Front-End: https://github.com/elbereth/dashninja-fe
- Database: https://github.com/elbereth/dashninja-db
Are available. I still need to tidy up the rest before open sourcing but I will try to be quick.
 
Last edited by a moderator:
Added IPv6 support.

Almost all scripts are now published on:
- Control Scripts: https://github.com/elbereth/dashninja-ctl

The only missing one is dmnctl, the central one because it is a huge mess (still leftovers from the first ever script I created for my first monitoring page that generated HTML directly). Once cleaned up it will also be pushed.
 
Last edited by a moderator:
Something wrong with site - Last Paid (from dashd) and Last Paid (from blocks) on most MNs are desynchronized , and block explorer not work.
 
You must log in or register to reply here.
Back
Top