Performance Graphs Disappear - have to REPEATEDLY reset cred

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Locked
mocjack
Posts: 31
Joined: Fri Dec 17, 2010 10:06 am

Performance Graphs Disappear - have to REPEATEDLY reset cred

Post by mocjack »

My performance graphs repeatedly disappear. I sometimes have to go reset security credentials 3 times a day to get them to appear. I am running XI under CentOS 64bit. Is there any resolution to this or a known issue at this point?

Happy new year all!
tonyyarusso
Posts: 1128
Joined: Wed Mar 03, 2010 12:38 pm
Location: St. Paul, MN, USA
Contact:

Re: Performance Graphs Disappear - have to REPEATEDLY reset cred

Post by tonyyarusso »

Are you running the latest release of XI (2009-1.3G)? I know we had some fixes in there, and I believe even more upcoming. (So yes, it's known, although not 100% understood.)
Tony Yarusso
Technical Services
___
TIES
Web: http://ties.k12.mn.us/
mocjack
Posts: 31
Joined: Fri Dec 17, 2010 10:06 am

Re: Performance Graphs Disappear - have to REPEATEDLY reset cred

Post by mocjack »

Yes sir running that exact release.

Will wait for code update and hopefully addressing issue!

Thanks for the feedback.
mguthrie
Posts: 4380
Joined: Mon Jun 14, 2010 10:21 am

Re: Performance Graphs Disappear - have to REPEATEDLY reset cred

Post by mguthrie »

We've had this issue reported occasionally, although we're not able to reproduce it at will, so we don't know the exact cause of it. Some users have reported that having special characters in their passwords (non-alphanumberic) has caused this problem, and changing their password to alphanumeric only characters made the problem go away. Others have reported that setting the backend credentials to the nagiosadmin password has fixed it permanently, although this isn't ideal since it exposes that password in plain text to anyone with admin privileges. Let us know if either of the above solutions work, and we'll see if we can get this problem pinned down.
Locked