Search found 13 matches
- Fri Jul 31, 2015 2:43 am
- Forum: Open Source Nagios Projects
- Topic: nagiosgraph.js is not installed or wrong version
- Replies: 11
- Views: 13987
Re: nagiosgraph.js is not installed or wrong version
Anything at all? 200s? 302s? Anything? Or is it like it's not even being accessed? Well, of course - tehre is some enries :-) # tail -f /var/log/nagios/nagiosgraph.log /var/log/nagios/nagiosgraph-cgi.log /var/log/nagios/nagios.log ==> /var/log/nagios/nagiosgraph.log <== Fri Jul 31 07:27:58 2015 ins...
- Thu Jul 30, 2015 3:08 am
- Forum: Open Source Nagios Projects
- Topic: nagiosgraph.js is not installed or wrong version
- Replies: 11
- Views: 13987
Re: nagiosgraph.js is not installed or wrong version
Hi, @jolson. Thanks for replay. Are there any notable differences between the servers regarding software versions, OS versions, apache versions, etc? Working server works under CentOS 6 OS, and non-working - under Amazon Linux (which is also based on RHEL ). Both uses same NGINX + PHP-FPM : # nginx ...
- Wed Jul 29, 2015 9:59 am
- Forum: Open Source Nagios Projects
- Topic: nagiosgraph.js is not installed or wrong version
- Replies: 11
- Views: 13987
nagiosgraph.js is not installed or wrong version
Hi. I spent almost whole day, trying solve that problem. Finally - I came here :-( I have installed Nagiosgrapth (manually), but after opening page like " http://nagios.domain.com/nagios/cgi-bin/show.cgi?host=www.cloud.domain.com&service=Tomcat%20memory " - I have next error: JavaScrip...
- Thu Jul 23, 2015 6:12 am
- Forum: Open Source Nagios Projects
- Topic: Nagios: Could not resolve hostname
- Replies: 4
- Views: 6266
Re: Nagios: Could not resolve hostname
Yes, solved, thanks a lot. Topic can be closed.jdalrymple wrote: your issue - resolved? OK to lock the topic?
- Wed Jul 22, 2015 4:57 am
- Forum: Open Source Nagios Projects
- Topic: Nagios: Could not resolve hostname
- Replies: 4
- Views: 6266
Re: Nagios: Could not resolve hostname
$HOSTNAME$ is not what you want, (I don't think) - you want $HOSTADDRESS$. Nagios resolves $HOSTADDRESS$ on restart then passes only IPs to plugins. By using $HOSTNAME$ you're passing whatever you called the host (which could be totally arbitrary) to the plugin. Thanks, $HOSTADDRESS$ is what I need...
- Tue Jul 21, 2015 5:34 am
- Forum: Open Source Nagios Projects
- Topic: Nagios: Could not resolve hostname
- Replies: 4
- Views: 6266
Nagios: Could not resolve hostname
Hi. My setup: hosts.cfg - contains definitions for each host under monitoring, e.g.: define host{ use linux-server host_name rdss-vpn display_name VPN address 54.***.***.176 } hosts_groups.cfg - define groups: define hostgroup{ hostgroup_name rdss-service-server alias RDSS services members [...], rd...
- Thu Jul 09, 2015 9:46 am
- Forum: Open Source Nagios Projects
- Topic: Nagiosgrapth - no graphs
- Replies: 11
- Views: 4786
Re: Nagiosgrapth - no graphs
Yup, thanks.
I just don't see here how change to [SOLVED]
I just don't see here how change to [SOLVED]
- Thu Jul 09, 2015 4:07 am
- Forum: Open Source Nagios Projects
- Topic: Nagiosgrapth - no graphs
- Replies: 11
- Views: 4786
Re: Nagiosgrapth - no graphs
Thanks, @jdalrymple
Problem was in my /opt/nagiosgraph/etc/nagiosgraph.conf.
There was:
Instead of:
This fixed my problem.
Problem was in my /opt/nagiosgraph/etc/nagiosgraph.conf.
There was:
Code: Select all
nagiosgraphcgiurl = /usr/local/nagios/sbin/Code: Select all
nagiosgraphcgiurl = /nagios/cgi-bin- Wed Jul 08, 2015 3:29 am
- Forum: Open Source Nagios Projects
- Topic: Nagiosgrapth - no graphs
- Replies: 11
- Views: 4786
Re: Nagiosgrapth - no graphs
194.105.145.69 - nagiosadmin [07/Jul/2015:15:20:06 +0000] "GET /usr/local/nagios/sbin//showgraph.cgi? HTTP/1.1" 403 25 "http://54.174.182.54/nagios/cgi-bin/show.cgi" "Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.130 Safari/537....
- Tue Jul 07, 2015 10:22 am
- Forum: Open Source Nagios Projects
- Topic: Nagiosgrapth - no graphs
- Replies: 11
- Views: 4786
Re: Nagiosgrapth - no graphs
Start a tail on the access and error logs: tail -f /var/log/httpd/error_log /var/log/httpd/access_log Then open up the page again or refresh and post the output, there should at least be some access_log errors that will give us an indication of what is happening. # tail -f /var/log/nginx/error.log ...