3-4 hours ago we stated getting an empty graphs (all of them).
No changes were made to the system.
Please advise how can we fix this issue.
(See attached screen shot)
Empty graphs
-
- Posts: 36
- Joined: Sun Jun 13, 2010 4:24 am
Empty graphs
You do not have the required permissions to view the files attached to this post.
-
- Site Admin
- Posts: 256
- Joined: Mon Oct 12, 2009 8:21 am
Re: Empty graphs
Can you provide us with the version of Nagios XI you are running? Older version of XI shipped with an older version of Nagios Core that had this problem pop up. An upgrade to the latest version of XI might resolve this issue.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Ethan Galstad
President
Ethan Galstad
President
-
- Posts: 36
- Joined: Sun Jun 13, 2010 4:24 am
Re: Empty graphs
I cannot upgrade.
See case : http://support.nagios.com/forum/viewtop ... f=16&t=889
Can you be more specific ?
See case : http://support.nagios.com/forum/viewtop ... f=16&t=889
Can you be more specific ?
-
- Posts: 4380
- Joined: Mon Jun 14, 2010 10:21 am
Re: Empty graphs
I read through the above thread with your upgrade issues. Just for our notes, are you on a manual install, and if so which distro, and is it 32 or 64bit?
-
- Posts: 36
- Joined: Sun Jun 13, 2010 4:24 am
Re: Empty graphs
I am not on manual install.
We installed the vendor VMWare image (32 bit).
The only thing was changed is MySQL package due to performance issues (which was rolled-back after starting having trouble with an upgrade)
We installed the vendor VMWare image (32 bit).
The only thing was changed is MySQL package due to performance issues (which was rolled-back after starting having trouble with an upgrade)
-
- Posts: 4380
- Joined: Mon Jun 14, 2010 10:21 am
Re: Empty graphs
Have you attempted the upgrade scripts since rolling back to the original MySql installation? If so, our best recommendation would still be to run the upgrade. If that's not a possibility for some reason let us know and we'll get you more information on what exactly fixed this.