Hello, my user parameters module is sqlite.
But, as I set a testing system around shinken in order to evaluate it, I stop it
this WE (full power off). I started it this morning, and the message
disappeared...
As I'm a crazy tester, I just did it again, and the "bug" is repeatable. As the
message disappeared (I don't know if it is because I restarted or because of
time elapse), I'm not sure that it could be call a bug.
 
So, far, it seems that something is purging bad conf of the dashboard.
 
 
Bonus question: what's happened to SKonf ?
 
Best regards,
Franck

  _____  

De : nap [mailto:napar...@gmail.com] 
Envoyé : lundi 12 mai 2014 08:42
À : shinken-devel@lists.sourceforge.net
Objet : Re: [Shinken-devel] Widget inaccessible as bad conf node set on it





On Thu, May 8, 2014 at 4:34 PM, Franck <lapla...@ulukai.net> wrote:


Hi,

        In the SHinkenUI/Dashboard, I added a relation graph widget, I
configured it to display the 'toto' host (without quotes), but the real hostname
was 'Toto'. I made a mistake, but now, the Dashboard is showing me the string
'Error loading this widget!' and I can't set the correct hostname.

        An idea?

Best regards,
Franck



I think you can't easily. What is your user parameters module? (mongo or
sqlite). I thnk the only way is to edit the parameter (yes, not an easy way :)
).

Off topic: maybe we should open a mailing list dediated to webui as it's now an
external modules like any other? Or just a shinken-modules list?


Jean

------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Shinken-devel mailing list
Shinken-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shinken-devel

Reply via email to