Hi all, attempted to install 3.5B but seem to have an issue with Grafana starting, I have aprevious issue where this happened and grahite needed to be commented out
#Grafana unable to launch after 3.5B upgrade
heady rampart
modern needle
@silk vine have you seen this one?
silk vine
Actually looking into this
silk vine
Well, what I'm looking into is new 3.5 deployment
what you're experiencing here should be fixed but maybe that's something else. what does dc logs grafana says ?
heady rampart
Well i've just fixed it, once I renamed the alert file it worked, a quick dc up -d got it back, but grahite is still commented out and down
west crystal
nabox 3.5?
silk vine
-ish yes, I pulled it from the download and it’s grounded until it has worked on its attitude 😂
Btw you should be able to put back the alert rule config now. It’s a race condition issue in Grafana that even if a dashboard « Nabox » is no longer defined in a yaml file, a rule using « Nabox » folder will crash Grafana, even though the dashboard actually doesn’t exists.
heady rampart
Ah no worries mate, I havent faffed around with the alerting yet
heady rampart
@silk vine I need a favour, Could you email me from the help@nabox.org email address and say your netapp heres my netapp email address we support Nabox etc please? My email with logs has triggered a DLP Process 😦
silk vine
done
heady rampart
Sorry mate, they have came back and said faceless inbox, could you resent and say your Yann from netapp heres my netapp email from the help@nabox email please, sorry bloody processes! its been flagged because of an IP 😦 Which was the docker internal ips