Page 2 of 4

Re: CGI and Internal Server Errors

Posted: Fri Jun 12, 2015 12:27 pm
by tgriep
Can you run the following and post the results back?

Code: Select all

getenforce
ls -lR /usr/local/nagios
Is AppArmor installed? If so, try removing it.

Re: CGI and Internal Server Errors

Posted: Mon Jun 15, 2015 6:20 am
by scrusi
Hey!

Code: Select all

$ getenforce
-bash: getenforce: command not found

Code: Select all

$ ls -lR /usr/local/nagios
/usr/local/nagios/:
total 24
drwxrwxr-x  2 nagios nagios 4096 Jun 11 11:02 bin
drwxrwxr-x  3 nagios nagios 4096 Jun 11 11:04 etc
drwxrwxr-x  3 nagios nagios 4096 Jun 11 11:09 libexec
drwxrwxr-x  2 nagios nagios 4096 Jun 11 11:02 sbin
drwxrwxr-x 15 nagios nagios 4096 Jun 11 11:09 share
drwxrwxr-x  5 nagios nagios 4096 Jun 15 12:27 var

/usr/local/nagios/bin:
total 720
-rwxrwxr-- 1 nagios nagios 692640 Jun 11 11:02 nagios
-rwxrwxr-- 1 nagios nagios  39560 Jun 11 11:02 nagiostats

/usr/local/nagios/etc:
total 68
-rw-rw-r-- 1 nagios nagios 12018 Jun 11 11:03 cgi.cfg
-rw-r--r-- 1 root   root      50 Jun 11 11:06 htpasswd.users
-rw-rw-r-- 1 nagios nagios 44519 Jun 11 11:03 nagios.cfg
drwxrwxr-x 2 nagios nagios  4096 Jun 11 11:03 objects
-rw-rw---- 1 nagios nagios  1315 Jun 11 11:03 resource.cfg

/usr/local/nagios/etc/objects:
total 48
-rw-rw-r-- 1 nagios nagios  7707 Jun 11 11:03 commands.cfg
-rw-rw-r-- 1 nagios nagios  2138 Jun 11 11:03 contacts.cfg
-rw-rw-r-- 1 nagios nagios  5375 Jun 11 11:03 localhost.cfg
-rw-rw-r-- 1 nagios nagios  3096 Jun 11 11:03 printer.cfg
-rw-rw-r-- 1 nagios nagios  3265 Jun 11 11:03 switch.cfg
-rw-rw-r-- 1 nagios nagios 10621 Jun 11 11:03 templates.cfg
-rw-rw-r-- 1 nagios nagios  3180 Jun 11 11:03 timeperiods.cfg
-rw-rw-r-- 1 nagios nagios  3991 Jun 11 11:03 windows.cfg

/usr/local/nagios/libexec:
total 7648
-rwxr-xr-x 1 nagios nagios 223804 Jun 11 11:09 check_apt
-rwxr-xr-x 1 nagios nagios   2260 Jun 11 11:09 check_breeze
-rwxr-xr-x 1 nagios nagios 230445 Jun 11 11:09 check_by_ssh
lrwxrwxrwx 1 root   root        9 Jun 11 11:09 check_clamd -> check_tcp
-rwxr-xr-x 1 nagios nagios 169045 Jun 11 11:09 check_cluster
-r-sr-xr-x 1 root   nagios 234517 Jun 11 11:09 check_dhcp
-rwxr-xr-x 1 nagios nagios 219631 Jun 11 11:09 check_dig
-rwxr-xr-x 1 nagios nagios 239476 Jun 11 11:09 check_disk
-rwxr-xr-x 1 nagios nagios   9298 Jun 11 11:09 check_disk_smb
-rwxr-xr-x 1 nagios nagios 246499 Jun 11 11:09 check_dns
-rwxr-xr-x 1 nagios nagios 125428 Jun 11 11:09 check_dummy
-rwxr-xr-x 1 nagios nagios   3358 Jun 11 11:09 check_file_age
-rwxr-xr-x 1 nagios nagios   6324 Jun 11 11:09 check_flexlm
lrwxrwxrwx 1 root   root        9 Jun 11 11:09 check_ftp -> check_tcp
-rwxr-xr-x 1 nagios nagios 222629 Jun 11 11:09 check_hpjd
-rwxr-xr-x 1 nagios nagios 303489 Jun 11 11:09 check_http
-r-sr-xr-x 1 root   nagios 244980 Jun 11 11:09 check_icmp
-rwxr-xr-x 1 nagios nagios 177855 Jun 11 11:09 check_ide_smart
-rwxr-xr-x 1 nagios nagios  15132 Jun 11 11:09 check_ifoperstatus
-rwxr-xr-x 1 nagios nagios  12613 Jun 11 11:09 check_ifstatus
lrwxrwxrwx 1 root   root        9 Jun 11 11:09 check_imap -> check_tcp
-rwxr-xr-x 1 nagios nagios   6896 Jun 11 11:09 check_ircd
-rwxr-xr-x 1 nagios nagios 194788 Jun 11 11:09 check_load
-rwxr-xr-x 1 nagios nagios   5997 Jun 11 11:09 check_log
-rwxr-xr-x 1 nagios nagios  21489 Jun 11 11:09 check_mailq
-rwxr-xr-x 1 nagios nagios 176993 Jun 11 11:09 check_mrtg
-rwxr-xr-x 1 nagios nagios 176278 Jun 11 11:09 check_mrtgtraf
-rwxr-xr-x 1 nagios nagios 195322 Jun 11 11:09 check_nagios
lrwxrwxrwx 1 root   root        9 Jun 11 11:09 check_nntp -> check_tcp
-rwxr-xr-x 1 nagios nagios 234726 Jun 11 11:09 check_nt
-rwxr-xr-x 1 nagios nagios 239907 Jun 11 11:09 check_ntp
-rwxr-xr-x 1 nagios nagios 226354 Jun 11 11:09 check_ntp_peer
-rwxr-xr-x 1 nagios nagios 218851 Jun 11 11:09 check_ntp_time
-rwxr-xr-x 1 nagios nagios 268675 Jun 11 11:09 check_nwstat
-rwxr-xr-x 1 nagios nagios   8783 Jun 11 11:09 check_oracle
-rwxr-xr-x 1 nagios nagios 201141 Jun 11 11:09 check_overcr
-rwxr-xr-x 1 nagios nagios 239330 Jun 11 11:09 check_ping
lrwxrwxrwx 1 root   root        9 Jun 11 11:09 check_pop -> check_tcp
-rwxr-xr-x 1 nagios nagios 232201 Jun 11 11:09 check_procs
-rwxr-xr-x 1 nagios nagios 200139 Jun 11 11:09 check_real
-rwxr-xr-x 1 nagios nagios   9590 Jun 11 11:09 check_rpc
-rwxr-xr-x 1 nagios nagios   1457 Jun 11 11:09 check_sensors
-rwxr-xr-x 1 nagios nagios 229572 Jun 11 11:09 check_smtp
-rwxr-xr-x 1 nagios nagios 287798 Jun 11 11:09 check_snmp
-rwxr-xr-x 1 nagios nagios 196378 Jun 11 11:09 check_ssh
-rwxr-xr-x 1 nagios nagios 173289 Jun 11 11:09 check_swap
-rwxr-xr-x 1 nagios nagios 216078 Jun 11 11:09 check_tcp
-rwxr-xr-x 1 nagios nagios 198301 Jun 11 11:09 check_time
lrwxrwxrwx 1 root   root        9 Jun 11 11:09 check_udp -> check_tcp
-rwxr-xr-x 1 nagios nagios 212523 Jun 11 11:09 check_ups
-rwxr-xr-x 1 nagios nagios 164699 Jun 11 11:09 check_uptime
-rwxr-xr-x 1 nagios nagios 162877 Jun 11 11:09 check_users
-rwxr-xr-x 1 nagios nagios   2945 Jun 11 11:09 check_wave
drwxr-xr-x 4 nagios nagios   4096 Jun 11 11:03 eventhandlers
-rwxr-xr-x 1 nagios nagios 160296 Jun 11 11:09 negate
-rwxr-xr-x 1 nagios nagios 156908 Jun 11 11:09 urlize
-rwxr-xr-x 1 nagios nagios   1895 Jun 11 11:09 utils.pm
-rwxr-xr-x 1 nagios nagios   2791 Jun 11 11:09 utils.sh

/usr/local/nagios/libexec/eventhandlers:
total 28
-rwxr-xr-x 1 nagios nagios  828 Jun 11 11:03 disable_active_service_checks
-rwxr-xr-x 1 nagios nagios  759 Jun 11 11:03 disable_notifications
drwxr-xr-x 2 nagios nagios 4096 Jun 11 11:03 distributed-monitoring
-rwxr-xr-x 1 nagios nagios  827 Jun 11 11:03 enable_active_service_checks
-rwxr-xr-x 1 nagios nagios  760 Jun 11 11:03 enable_notifications
drwxr-xr-x 2 nagios nagios 4096 Jun 11 11:03 redundancy-scenario1
-rwxr-xr-x 1 nagios nagios 1184 Jun 11 11:03 submit_check_result

/usr/local/nagios/libexec/eventhandlers/distributed-monitoring:
total 8
-rwxr-xr-x 1 nagios nagios 1179 Jun 11 11:03 obsessive_svc_handler
-rwxr-xr-x 1 nagios nagios 1216 Jun 11 11:03 submit_check_result_via_nsca

/usr/local/nagios/libexec/eventhandlers/redundancy-scenario1:
total 8
-rwxr-xr-x 1 nagios nagios 2038 Jun 11 11:03 handle-master-host-event
-rwxr-xr-x 1 nagios nagios 1232 Jun 11 11:03 handle-master-proc-event

/usr/local/nagios/sbin:
total 5140
-rwxrwxr-x 1 nagios nagios 320576 Jun 11 11:02 archivejson.cgi
-rwxrwxr-x 1 nagios nagios 301880 Jun 11 11:02 avail.cgi
-rwxrwxr-x 1 nagios nagios 300296 Jun 11 11:02 cmd.cgi
-rwxrwxr-x 1 nagios nagios 273136 Jun 11 11:02 config.cgi
-rwxrwxr-x 1 nagios nagios 314136 Jun 11 11:02 extinfo.cgi
-rwxrwxr-x 1 nagios nagios 265128 Jun 11 11:02 histogram.cgi
-rwxrwxr-x 1 nagios nagios 244504 Jun 11 11:02 history.cgi
-rwxrwxr-x 1 nagios nagios 244496 Jun 11 11:02 notifications.cgi
-rwxrwxr-x 1 nagios nagios 318272 Jun 11 11:02 objectjson.cgi
-rwxrwxr-x 1 nagios nagios 236264 Jun 11 11:02 outages.cgi
-rwxrwxr-x 1 nagios nagios 240376 Jun 11 11:02 showlog.cgi
-rwxrwxr-x 1 nagios nagios 314160 Jun 11 11:02 status.cgi
-rwxrwxr-x 1 nagios nagios 316416 Jun 11 11:02 statusjson.cgi
-rwxrwxr-x 1 nagios nagios 261088 Jun 11 11:02 statusmap.cgi
-rwxrwxr-x 1 nagios nagios 256816 Jun 11 11:02 statuswml.cgi
-rwxrwxr-x 1 nagios nagios 240400 Jun 11 11:02 statuswrl.cgi
-rwxrwxr-x 1 nagios nagios 265024 Jun 11 11:02 summary.cgi
-rwxrwxr-x 1 nagios nagios 252736 Jun 11 11:02 tac.cgi
-rwxrwxr-x 1 nagios nagios 269224 Jun 11 11:02 trends.cgi

/usr/local/nagios/share:
total 192
drwxrwxr-x 4 nagios nagios 4096 Jun 11 11:02 angularjs
drwxrwxr-x 3 nagios nagios 4096 Jun 11 11:02 bootstrap-3.3.0
-rw-rw-r-- 1 nagios nagios  576 Jun 11 11:02 config.inc.php
drwxrwxr-x 2 nagios nagios 4096 Jun 11 11:02 contexthelp
drwxrwxr-x 2 nagios nagios 4096 Jun 11 11:02 d3
drwxrwxr-x 3 nagios nagios 4096 Jun 11 11:02 docs
-rw-rw-r-- 1 nagios nagios  879 Jun 11 11:02 graph-header.html
-rw-rw-r-- 1 nagios nagios 4136 Jun 11 11:02 histogram-form.html
-rw-rw-r-- 1 nagios nagios 5579 Jun 11 11:02 histogram-graph.html
-rw-rw-r-- 1 nagios nagios 2855 Jun 11 11:02 histogram.html
-rw-rw-r-- 1 nagios nagios 2372 Jun 11 11:02 histogram-links.html
drwxrwxr-x 3 nagios nagios 4096 Jun 11 11:02 images
drwxrwxr-x 3 nagios nagios 4096 Jun 11 11:02 includes
-rw-rw-r-- 1 nagios nagios 1652 Jun 11 11:02 index.php
-rw-rw-r-- 1 nagios nagios 1659 Jun 11 11:02 infobox.html
drwxrwxr-x 2 nagios nagios 4096 Jun 11 11:02 js
-rw-rw-r-- 1 nagios nagios 1176 Jun 11 11:02 jsonquery.html
drwxr-xr-x 4 root   root   4096 Jun 11 11:09 locale
-rw-rw-r-- 1 nagios nagios 8729 Jun 11 11:02 main.php
-rw-rw-r-- 1 nagios nagios 1967 Jun 11 11:02 map-directive.html
-rw-rw-r-- 1 nagios nagios 3614 Jun 11 11:02 map-form.html
-rw-rw-r-- 1 nagios nagios 2627 Jun 11 11:02 map.html
-rw-rw-r-- 1 nagios nagios  623 Jun 11 11:02 map-links.html
-rw-rw-r-- 1 nagios nagios 1723 Jun 11 11:02 map-popup.html
drwxrwxr-x 2 nagios nagios 4096 Jun 11 11:02 media
-rw-rw-r-- 1 nagios nagios   26 Jun 11 11:02 robots.txt
-rw-rw-r-- 1 nagios nagios  656 Jun 11 11:02 rss-corebanner.php
-rw-rw-r-- 1 nagios nagios 1064 Jun 11 11:02 rss-corefeed.html
-rw-rw-r-- 1 nagios nagios  895 Jun 11 11:02 rss-corefeed.php
-rw-rw-r-- 1 nagios nagios  540 Jun 11 11:02 rss-newsfeed.html
-rw-rw-r-- 1 nagios nagios 1064 Jun 11 11:02 rss-newsfeed.php
-rw-rw-r-- 1 nagios nagios 5904 Jun 11 11:02 side.php
drwxrwxr-x 2 nagios nagios 4096 Jun 11 11:02 spin
drwxrwxr-x 2 nagios nagios 4096 Jun 11 11:02 ssi
drwxrwxr-x 2 nagios nagios 4096 Jun 11 11:02 stylesheets
-rw-rw-r-- 1 nagios nagios 4243 Jun 11 11:02 trends-form.html
-rw-rw-r-- 1 nagios nagios 4256 Jun 11 11:02 trends-graph.html
-rw-rw-r-- 1 nagios nagios  852 Jun 11 11:02 trends-host-yaxis.html
-rw-rw-r-- 1 nagios nagios 2990 Jun 11 11:02 trends.html
-rw-rw-r-- 1 nagios nagios 3586 Jun 11 11:02 trends-links.html
-rw-rw-r-- 1 nagios nagios 1065 Jun 11 11:02 trends-service-yaxis.html

/usr/local/nagios/share/angularjs:
total 72
drwxrwxr-x 2 nagios nagios  4096 Jun 11 11:02 angular-1.3.9
-rw-rw-r-- 1 nagios nagios 65175 Jun 11 11:02 ui-bootstrap-tpls-0.12.0.min.js
drwxrwxr-x 2 nagios nagios  4096 Jun 11 11:02 ui-utils-0.2.1

/usr/local/nagios/share/angularjs/angular-1.3.9:
total 464
-rw-rw-r-- 1 nagios nagios 125229 Jun 11 11:02 angular.min.js
-rw-rw-r-- 1 nagios nagios 347254 Jun 11 11:02 angular.min.js.map

/usr/local/nagios/share/angularjs/ui-utils-0.2.1:
total 84
-rw-rw-r-- 1 nagios nagios 84014 Jun 11 11:02 ui-utils.js

/usr/local/nagios/share/bootstrap-3.3.0:
total 4
drwxrwxr-x 2 nagios nagios 4096 Jun 11 11:02 css

/usr/local/nagios/share/bootstrap-3.3.0/css:
total 132
-rw-rw-r-- 1 nagios nagios 114011 Jun 11 11:02 bootstrap.min.css
-rw-rw-r-- 1 nagios nagios  19199 Jun 11 11:02 bootstrap-theme.min.css

/usr/local/nagios/share/contexthelp:
total 252
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 A1.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 A2.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 A3.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 A4.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 A5.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 A6.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 A7.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 B1.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 C1.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 D1.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 E1.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 F1.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 G1.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 G2.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 G3.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 G4.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 G5.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 G6.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 H1.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 H2.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 H3.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 H4.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 H5.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 H6.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 H7.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 H8.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 I1.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 I2.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 I3.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 I4.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 I5.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 I6.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 I7.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 I8.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 I9.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 J1.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 K1.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 L10.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 L11.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 L12.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 L13.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 L1.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 L2.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 L3.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 L4.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 L5.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 L6.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 L7.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 L8.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 L9.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 M1.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 M2.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 M3.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 M4.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 M5.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 M6.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 N1.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 N2.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 N3.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 N4.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 N5.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 N6.html
-rw-rw-r-- 1 nagios nagios 890 Jun 11 11:02 N7.html

/usr/local/nagios/share/d3:
total 148
-rw-rw-r-- 1 nagios nagios 150760 Jun 11 11:02 d3.min.js

/usr/local/nagios/share/docs:
total 4
drwxrwxr-x 2 nagios nagios 4096 Jun 11 11:02 images

/usr/local/nagios/share/docs/images:
total 0

/usr/local/nagios/share/images:
total 328
-rw-rw-r-- 1 nagios nagios  856 Jun 11 11:02 ack.gif
-rw-rw-r-- 1 nagios nagios 1252 Jun 11 11:02 action.gif
-rw-r--r-- 1 root   root   1252 Jun 11 11:02 action-graph.gif
-rw-r--r-- 1 root   root    171 Jun 11 11:02 action-nagios.gif
-rw-r--r-- 1 root   root    162 Jun 11 11:02 action-orig.gif
-rw-rw-r-- 1 nagios nagios  324 Jun 11 11:02 b_first2.png
-rw-rw-r-- 1 nagios nagios  318 Jun 11 11:02 b_last2.png
-rw-rw-r-- 1 nagios nagios  241 Jun 11 11:02 b_next2.png
-rw-rw-r-- 1 nagios nagios  244 Jun 11 11:02 b_prev2.png
-rw-rw-r-- 1 nagios nagios  394 Jun 11 11:02 command.png
-rw-rw-r-- 1 nagios nagios  909 Jun 11 11:02 comment.gif
-rw-rw-r-- 1 nagios nagios  253 Jun 11 11:02 contexthelp1.gif
-rw-rw-r-- 1 nagios nagios  253 Jun 11 11:02 contexthelp2.gif
-rw-rw-r-- 1 nagios nagios  382 Jun 11 11:02 critical.png
-rw-rw-r-- 1 nagios nagios  935 Jun 11 11:02 delay.gif
-rw-rw-r-- 1 nagios nagios  961 Jun 11 11:02 delete.gif
-rw-rw-r-- 1 nagios nagios  138 Jun 11 11:02 detail.gif
-rw-rw-r-- 1 nagios nagios  100 Jun 11 11:02 disabled.gif
-rw-rw-r-- 1 nagios nagios  856 Jun 11 11:02 down.gif
-rw-rw-r-- 1 nagios nagios  933 Jun 11 11:02 downtime.gif
-rw-rw-r-- 1 nagios nagios  807 Jun 11 11:02 empty.gif
-rw-rw-r-- 1 nagios nagios   90 Jun 11 11:02 enabled.gif
-rw-rw-r-- 1 nagios nagios  911 Jun 11 11:02 extinfo.gif
-rw-rw-r-- 1 nagios nagios  822 Jun 11 11:02 favicon.ico
-rw-rw-r-- 1 nagios nagios 1294 Jun 11 11:02 flapping.gif
-rw-rw-r-- 1 nagios nagios 5562 Jun 11 11:02 globe-support-150x150.png
-rw-r--r-- 1 root   root   1252 Jun 11 11:02 graph.gif
-rw-rw-r-- 1 nagios nagios  889 Jun 11 11:02 greendot.gif
-rw-rw-r-- 1 nagios nagios 2057 Jun 11 11:02 histogram.png
-rw-rw-r-- 1 nagios nagios  915 Jun 11 11:02 history.gif
-rw-rw-r-- 1 nagios nagios  877 Jun 11 11:02 hostevent.gif
-rw-rw-r-- 1 nagios nagios  390 Jun 11 11:02 info.png
-rw-rw-r-- 1 nagios nagios  203 Jun 11 11:02 left.gif
-rw-rw-r-- 1 nagios nagios 9543 Jun 11 11:02 logofullsize.png
drwxrwxr-x 2 nagios nagios 4096 Jun 11 11:02 logos
-rw-rw-r-- 1 nagios nagios  434 Jun 11 11:02 logrotate.png
-rw-rw-r-- 1 nagios nagios  161 Jun 11 11:02 menu.png
-rw-rw-r-- 1 nagios nagios 2139 Jun 11 11:02 Nagios-clearbg.png
-rw-rw-r-- 1 nagios nagios 3996 Jun 11 11:02 NagiosEnterprises-whitebg-112x46.png
-rw-rw-r-- 1 nagios nagios  266 Jun 11 11:02 ndisabled.gif
-rw-rw-r-- 1 nagios nagios   90 Jun 11 11:02 noack.gif
-rw-rw-r-- 1 nagios nagios  893 Jun 11 11:02 notes.gif
-rw-rw-r-- 1 nagios nagios  264 Jun 11 11:02 notify.gif
-rw-rw-r-- 1 nagios nagios  889 Jun 11 11:02 orangedot.gif
-rw-rw-r-- 1 nagios nagios  882 Jun 11 11:02 passiveonly.gif
-rw-rw-r-- 1 nagios nagios  374 Jun 11 11:02 recovery.png
-rw-rw-r-- 1 nagios nagios 5519 Jun 11 11:02 redudancy.png
-rw-rw-r-- 1 nagios nagios 5519 Jun 11 11:02 redundancy.png
-rw-rw-r-- 1 nagios nagios  260 Jun 11 11:02 restart.gif
-rw-rw-r-- 1 nagios nagios  205 Jun 11 11:02 right.gif
-rw-rw-r-- 1 nagios nagios 3231 Jun 11 11:02 sblogo.png
-rw-rw-r-- 1 nagios nagios  891 Jun 11 11:02 serviceevent.gif
-rw-rw-r-- 1 nagios nagios  469 Jun 11 11:02 sflogo.png
-rw-rw-r-- 1 nagios nagios  939 Jun 11 11:02 splunk1.gif
-rw-rw-r-- 1 nagios nagios  936 Jun 11 11:02 splunk2.gif
-rw-rw-r-- 1 nagios nagios  247 Jun 11 11:02 start.gif
-rw-rw-r-- 1 nagios nagios  173 Jun 11 11:02 status2.gif
-rw-rw-r-- 1 nagios nagios  928 Jun 11 11:02 status3.gif
-rw-rw-r-- 1 nagios nagios  922 Jun 11 11:02 status4.gif
-rw-rw-r-- 1 nagios nagios  152 Jun 11 11:02 status.gif
-rw-rw-r-- 1 nagios nagios  246 Jun 11 11:02 stop.gif
-rw-rw-r-- 1 nagios nagios 2052 Jun 11 11:02 tacdisabled.jpg
-rw-rw-r-- 1 nagios nagios  267 Jun 11 11:02 tacdisabled.png
-rw-rw-r-- 1 nagios nagios 1750 Jun 11 11:02 tacenabled.jpg
-rw-rw-r-- 1 nagios nagios  267 Jun 11 11:02 tacenabled.png
-rw-rw-r-- 1 nagios nagios  567 Jun 11 11:02 thermcrit.png
-rw-rw-r-- 1 nagios nagios  776 Jun 11 11:02 thermok.png
-rw-rw-r-- 1 nagios nagios  676 Jun 11 11:02 thermwarn.png
-rw-rw-r-- 1 nagios nagios  933 Jun 11 11:02 trends.gif
-rw-rw-r-- 1 nagios nagios 2322 Jun 11 11:02 trendshost.png
-rw-rw-r-- 1 nagios nagios 2536 Jun 11 11:02 trendssvc.png
-rw-rw-r-- 1 nagios nagios  406 Jun 11 11:02 unknown.png
-rw-rw-r-- 1 nagios nagios  855 Jun 11 11:02 up.gif
-rw-rw-r-- 1 nagios nagios  394 Jun 11 11:02 warning.png
-rw-rw-r-- 1 nagios nagios 2401 Jun 11 11:02 weblogo1.png
-rw-rw-r-- 1 nagios nagios  889 Jun 11 11:02 zoom1.gif
-rw-rw-r-- 1 nagios nagios  889 Jun 11 11:02 zoom2.gif

/usr/local/nagios/share/images/logos:
total 744
-rw-r--r-- 1 root   root    2389 Jun 11 11:02 aix.gd2
-rw-r--r-- 1 root   root    1385 Jun 11 11:02 aix.gif
-rw-r--r-- 1 root   root    1720 Jun 11 11:02 aix.jpg
-rw-r--r-- 1 root   root    1387 Jun 11 11:02 aix.png
-rw-r--r-- 1 root   root    2389 Jun 11 11:02 amiga.gd2
-rw-r--r-- 1 root   root    2104 Jun 11 11:02 amiga.gif
-rw-r--r-- 1 root   root    1855 Jun 11 11:02 amiga.jpg
-rw-r--r-- 1 root   root    2577 Jun 11 11:02 amiga.png
-rw-r--r-- 1 root   root    2389 Jun 11 11:02 apple.gd2
-rw-r--r-- 1 root   root    1169 Jun 11 11:02 apple.gif
-rw-r--r-- 1 root   root    1353 Jun 11 11:02 apple.jpg
-rw-r--r-- 1 root   root     813 Jun 11 11:02 apple.png
-rw-r--r-- 1 root   root    2389 Jun 11 11:02 beos.gd2
-rw-r--r-- 1 root   root    1579 Jun 11 11:02 beos.gif
-rw-r--r-- 1 root   root    1735 Jun 11 11:02 beos.jpg
-rw-r--r-- 1 root   root    1595 Jun 11 11:02 beos.png
-rw-r--r-- 1 root   root    3868 Jun 11 11:02 bluetooth.png
-rw-r--r-- 1 root   root    2814 Jun 11 11:02 caldera.gd2
-rw-r--r-- 1 root   root    1831 Jun 11 11:02 caldera.gif
-rw-r--r-- 1 root   root    1654 Jun 11 11:02 caldera.jpg
-rw-r--r-- 1 root   root    2210 Jun 11 11:02 caldera.png
-rw-r--r-- 1 root   root    2389 Jun 11 11:02 cat1900.gd2
-rw-r--r-- 1 root   root    2389 Jun 11 11:02 cat2900.gd2
-rw-r--r-- 1 root   root    2389 Jun 11 11:02 cat5000.gd2
-rw-r--r-- 1 root   root    2649 Jun 11 11:02 database.gd2
-rw-r--r-- 1 root   root    1636 Jun 11 11:02 database.gif
-rw-r--r-- 1 root   root    2389 Jun 11 11:02 debian.gd2
-rw-r--r-- 1 root   root    1437 Jun 11 11:02 debian.gif
-rw-r--r-- 1 root   root    1580 Jun 11 11:02 debian.jpg
-rw-r--r-- 1 root   root    1575 Jun 11 11:02 debian.png
-rw-r--r-- 1 root   root    2649 Jun 11 11:02 desktop-server.gd2
-rw-r--r-- 1 root   root    1546 Jun 11 11:02 desktop-server.gif
-rw-r--r-- 1 root   root    3847 Jun 11 11:02 ethernet_card.png
-rw-r--r-- 1 root   root    2649 Jun 11 11:02 fax.gd2
-rw-r--r-- 1 root   root    1895 Jun 11 11:02 fax.gif
-rw-r--r-- 1 root   root    2649 Jun 11 11:02 firewall.gd2
-rw-r--r-- 1 root   root    1579 Jun 11 11:02 firewall.gif
-rw-r--r-- 1 root   root    1455 Jun 11 11:02 freebsd40.gd2
-rw-r--r-- 1 root   root    1491 Jun 11 11:02 freebsd40.gif
-rw-r--r-- 1 root   root    1697 Jun 11 11:02 freebsd40.jpg
-rw-r--r-- 1 root   root    1627 Jun 11 11:02 freebsd40.png
-rw-r--r-- 1 root   root    4671 Jun 11 11:02 globe.png
-rw-r--r-- 1 root   root    1252 Jun 11 11:02 graph.gif
-rw-r--r-- 1 root   root    2389 Jun 11 11:02 hp-printer40.gd2
-rw-r--r-- 1 root   root     717 Jun 11 11:02 hp-printer40.gif
-rw-r--r-- 1 root   root    1501 Jun 11 11:02 hp-printer40.jpg
-rw-r--r-- 1 root   root    1176 Jun 11 11:02 hp-printer40.png
-rw-r--r-- 1 root   root    2470 Jun 11 11:02 hpux.gd2
-rw-r--r-- 1 root   root    1097 Jun 11 11:02 hpux.gif
-rw-r--r-- 1 root   root    1781 Jun 11 11:02 hpux.jpg
-rw-r--r-- 1 root   root     662 Jun 11 11:02 hpux.png
-rw-r--r-- 1 root   root    2649 Jun 11 11:02 hub.gd2
-rw-r--r-- 1 root   root    1557 Jun 11 11:02 hub.gif
-rw-r--r-- 1 root   root    4248 Jun 11 11:02 internet_device.png
-rw-r--r-- 1 root   root    2649 Jun 11 11:02 internet.gd2
-rw-r--r-- 1 root   root    1834 Jun 11 11:02 internet.gif
-rw-r--r-- 1 root   root    2649 Jun 11 11:02 ip-pbx.gd2
-rw-r--r-- 1 root   root    1629 Jun 11 11:02 ip-pbx.gif
-rw-r--r-- 1 root   root    2389 Jun 11 11:02 irix.gd2
-rw-r--r-- 1 root   root    1735 Jun 11 11:02 irix.gif
-rw-r--r-- 1 root   root    1596 Jun 11 11:02 irix.jpg
-rw-r--r-- 1 root   root    2420 Jun 11 11:02 irix.png
-rw-r--r-- 1 root   root    2389 Jun 11 11:02 linux40.gd2
-rw-r--r-- 1 root   root    1642 Jun 11 11:02 linux40.gif
-rw-r--r-- 1 root   root    1666 Jun 11 11:02 linux40.jpg
-rw-r--r-- 1 root   root    1972 Jun 11 11:02 linux40.png
-rw-r--r-- 1 root   root    4389 Jun 11 11:02 logo.gd2
-rw-r--r-- 1 root   root    2389 Jun 11 11:02 mac40.gd2
-rw-r--r-- 1 root   root    1784 Jun 11 11:02 mac40.gif
-rw-r--r-- 1 root   root    1601 Jun 11 11:02 mac40.jpg
-rw-r--r-- 1 root   root    1994 Jun 11 11:02 mac40.png
-rw-r--r-- 1 root   root    2129 Jun 11 11:02 mainframe.gd2
-rw-r--r-- 1 root   root    1555 Jun 11 11:02 mainframe.gif
-rw-r--r-- 1 root   root    2389 Jun 11 11:02 mandrake.gd2
-rw-r--r-- 1 root   root    1487 Jun 11 11:02 mandrake.gif
-rw-r--r-- 1 root   root    1464 Jun 11 11:02 mandrake.jpg
-rw-r--r-- 1 root   root    1471 Jun 11 11:02 mandrake.png
-rw-r--r-- 1 root   root    2847 Jun 11 11:02 monitor.png
-rw-rw-r-- 1 nagios nagios  2649 Jun 11 11:02 nagios.gd2
-rw-rw-r-- 1 nagios nagios   150 Jun 11 11:02 nagios.gif
-rw-rw-r-- 1 nagios nagios 21699 Jun 11 11:02 nagiosvrml.png
-rw-r--r-- 1 root   root    2389 Jun 11 11:02 next.gd2
-rw-r--r-- 1 root   root    2384 Jun 11 11:02 next.gif
-rw-r--r-- 1 root   root    1659 Jun 11 11:02 next.jpg
-rw-r--r-- 1 root   root    3355 Jun 11 11:02 next.png
-rw-r--r-- 1 root   root    2389 Jun 11 11:02 ng-switch40.gd2
-rw-r--r-- 1 root   root    1365 Jun 11 11:02 ng-switch40.gif
-rw-r--r-- 1 root   root    1172 Jun 11 11:02 ng-switch40.jpg
-rw-r--r-- 1 root   root    1128 Jun 11 11:02 ng-switch40.png
-rw-r--r-- 1 root   root    2609 Jun 11 11:02 notebook.gd2
-rw-r--r-- 1 root   root    1777 Jun 11 11:02 notebook.gif
-rw-r--r-- 1 root   root    2389 Jun 11 11:02 novell40.gd2
-rw-r--r-- 1 root   root    1008 Jun 11 11:02 novell40.gif
-rw-r--r-- 1 root   root    1663 Jun 11 11:02 novell40.jpg
-rw-r--r-- 1 root   root     948 Jun 11 11:02 novell40.png
-rw-r--r-- 1 root   root    2389 Jun 11 11:02 openbsd.gd2
-rw-r--r-- 1 root   root    1867 Jun 11 11:02 openbsd.gif
-rw-r--r-- 1 root   root    1817 Jun 11 11:02 openbsd.jpg
-rw-r--r-- 1 root   root    2433 Jun 11 11:02 openbsd.png
-rw-r--r-- 1 root   root    2649 Jun 11 11:02 printer.gd2
-rw-r--r-- 1 root   root    1683 Jun 11 11:02 printer.gif
-rw-r--r-- 1 root   root    2649 Jun 11 11:02 rack-server.gd2
-rw-r--r-- 1 root   root    1522 Jun 11 11:02 rack-server.gif
-rw-r--r-- 1 root   root    2389 Jun 11 11:02 redhat.gd2
-rw-r--r-- 1 root   root    1321 Jun 11 11:02 redhat.gif
-rw-r--r-- 1 root   root    1719 Jun 11 11:02 redhat.jpg
-rw-r--r-- 1 root   root    1319 Jun 11 11:02 redhat.png
-rw-r--r-- 1 root   root    2389 Jun 11 11:02 router40.gd2
-rw-r--r-- 1 root   root    1556 Jun 11 11:02 router40.gif
-rw-r--r-- 1 root   root    1428 Jun 11 11:02 router40.jpg
-rw-r--r-- 1 root   root    1816 Jun 11 11:02 router40.png
-rw-r--r-- 1 root   root    2649 Jun 11 11:02 router.gd2
-rw-r--r-- 1 root   root    1573 Jun 11 11:02 router.gif
-rw-r--r-- 1 root   root    2649 Jun 11 11:02 san.gd2
-rw-r--r-- 1 root   root    1686 Jun 11 11:02 san.gif
-rw-r--r-- 1 root   root    2737 Jun 11 11:02 satellite.png
-rw-r--r-- 1 root   root    3435 Jun 11 11:02 server.png
-rw-r--r-- 1 root   root    3812 Jun 11 11:02 signal.png
-rw-r--r-- 1 root   root    2389 Jun 11 11:02 slackware.gd2
-rw-r--r-- 1 root   root    1949 Jun 11 11:02 slackware.gif
-rw-r--r-- 1 root   root    1624 Jun 11 11:02 slackware.jpg
-rw-r--r-- 1 root   root    2078 Jun 11 11:02 slackware.png
-rw-r--r-- 1 root   root    2389 Jun 11 11:02 stampede.gd2
-rw-r--r-- 1 root   root    1140 Jun 11 11:02 stampede.gif
-rw-r--r-- 1 root   root    1349 Jun 11 11:02 stampede.jpg
-rw-r--r-- 1 root   root     932 Jun 11 11:02 stampede.png
-rw-r--r-- 1 root   root    2389 Jun 11 11:02 station.gd2
-rw-r--r-- 1 root   root    2389 Jun 11 11:02 storm.gd2
-rw-r--r-- 1 root   root    1612 Jun 11 11:02 storm.gif
-rw-r--r-- 1 root   root    1632 Jun 11 11:02 storm.jpg
-rw-r--r-- 1 root   root    1932 Jun 11 11:02 storm.png
-rw-r--r-- 1 root   root    2389 Jun 11 11:02 sun40.gd2
-rw-r--r-- 1 root   root    1903 Jun 11 11:02 sun40.gif
-rw-r--r-- 1 root   root    1618 Jun 11 11:02 sun40.jpg
-rw-r--r-- 1 root   root    3014 Jun 11 11:02 sun40.png
-rw-r--r-- 1 root   root    2769 Jun 11 11:02 sunlogo.gd2
-rw-r--r-- 1 root   root     571 Jun 11 11:02 sunlogo.gif
-rw-r--r-- 1 root   root    1682 Jun 11 11:02 sunlogo.jpg
-rw-r--r-- 1 root   root    1277 Jun 11 11:02 sunlogo.png
-rw-r--r-- 1 root   root    2389 Jun 11 11:02 switch40.gd2
-rw-r--r-- 1 root   root    1321 Jun 11 11:02 switch40.gif
-rw-r--r-- 1 root   root    1113 Jun 11 11:02 switch40.jpg
-rw-r--r-- 1 root   root     869 Jun 11 11:02 switch40.png
-rw-r--r-- 1 root   root    2649 Jun 11 11:02 switch.gd2
-rw-r--r-- 1 root   root    1432 Jun 11 11:02 switch.gif
-rw-r--r-- 1 root   root    2649 Jun 11 11:02 thin-client.gd2
-rw-r--r-- 1 root   root    1619 Jun 11 11:02 thin-client.gif
-rw-r--r-- 1 root   root    2389 Jun 11 11:02 turbolinux.gd2
-rw-r--r-- 1 root   root    1974 Jun 11 11:02 turbolinux.gif
-rw-r--r-- 1 root   root    1875 Jun 11 11:02 turbolinux.jpg
-rw-r--r-- 1 root   root    2491 Jun 11 11:02 turbolinux.png
-rw-r--r-- 1 root   root    2389 Jun 11 11:02 ultrapenguin.gd2
-rw-r--r-- 1 root   root    1677 Jun 11 11:02 ultrapenguin.gif
-rw-r--r-- 1 root   root    1693 Jun 11 11:02 ultrapenguin.jpg
-rw-r--r-- 1 root   root    3112 Jun 11 11:02 ultrapenguin.png
-rw-r--r-- 1 root   root    2389 Jun 11 11:02 unicos.gd2
-rw-r--r-- 1 root   root    2198 Jun 11 11:02 unicos.gif
-rw-r--r-- 1 root   root    1467 Jun 11 11:02 unicos.jpg
-rw-r--r-- 1 root   root    2769 Jun 11 11:02 unicos.png
-rw-rw-r-- 1 nagios nagios  2389 Jun 11 11:02 unknown.gd2
-rw-rw-r-- 1 nagios nagios  1280 Jun 11 11:02 unknown.gif
-rw-r--r-- 1 root   root    4275 Jun 11 11:02 webcamera.png
-rw-r--r-- 1 root   root    2649 Jun 11 11:02 wifi.gd2
-rw-r--r-- 1 root   root    1755 Jun 11 11:02 wifi.gif
-rw-r--r-- 1 root   root    3574 Jun 11 11:02 wifi_modem.png
-rw-r--r-- 1 root   root    2389 Jun 11 11:02 win40.gd2
-rw-r--r-- 1 root   root    1800 Jun 11 11:02 win40.gif
-rw-r--r-- 1 root   root    1777 Jun 11 11:02 win40.jpg
-rw-r--r-- 1 root   root    2288 Jun 11 11:02 win40.png
-rw-r--r-- 1 root   root    2649 Jun 11 11:02 workstation.gd2
-rw-r--r-- 1 root   root    1832 Jun 11 11:02 workstation.gif
-rw-r--r-- 1 root   root    2991 Jun 11 11:02 workstation_locked.png
-rw-r--r-- 1 root   root    2508 Jun 11 11:02 workstation.png
-rw-r--r-- 1 root   root    2349 Jun 11 11:02 yellowdog.gd2
-rw-r--r-- 1 root   root    1332 Jun 11 11:02 yellowdog.gif
-rw-r--r-- 1 root   root    1464 Jun 11 11:02 yellowdog.jpg
-rw-r--r-- 1 root   root    1257 Jun 11 11:02 yellowdog.png

/usr/local/nagios/share/includes:
total 108
-rw-rw-r-- 1 nagios nagios 93868 Jun 11 11:02 jquery-1.7.1.min.js
drwxrwxr-x 3 nagios nagios  4096 Jun 11 11:02 rss
-rw-rw-r-- 1 nagios nagios 10037 Jun 11 11:02 utils.inc.php

/usr/local/nagios/share/includes/rss:
total 52
drwxrwxr-x 2 nagios nagios  4096 Jun 11 11:02 extlib
-rw-rw-r-- 1 nagios nagios  6376 Jun 11 11:02 rss_cache.inc
-rw-rw-r-- 1 nagios nagios 15058 Jun 11 11:02 rss_fetch.inc
-rw-rw-r-- 1 nagios nagios 19640 Jun 11 11:02 rss_parse.inc
-rw-rw-r-- 1 nagios nagios  2056 Jun 11 11:02 rss_utils.inc

/usr/local/nagios/share/includes/rss/extlib:
total 28
-rw-rw-r-- 1 nagios nagios 27402 Jun 11 11:02 Snoopy.class.inc

/usr/local/nagios/share/js:
total 296
-rw-rw-r-- 1 nagios nagios   1868 Jun 11 11:02 histogram-events.js
-rw-rw-r-- 1 nagios nagios   4293 Jun 11 11:02 histogram-form.js
-rw-rw-r-- 1 nagios nagios  11261 Jun 11 11:02 histogram-graph.js
-rw-rw-r-- 1 nagios nagios   3694 Jun 11 11:02 histogram.js
-rw-rw-r-- 1 nagios nagios  93868 Jun 11 11:02 jquery-1.7.1.min.js
-rw-rw-r-- 1 nagios nagios  13926 Jun 11 11:02 jsonquery.js
-rw-rw-r-- 1 nagios nagios 100604 Jun 11 11:02 map-directive.js
-rw-rw-r-- 1 nagios nagios   1541 Jun 11 11:02 map-form.js
-rw-rw-r-- 1 nagios nagios   4984 Jun 11 11:02 map.js
-rw-rw-r-- 1 nagios nagios   2442 Jun 11 11:02 nagios-decorations.js
-rw-rw-r-- 1 nagios nagios   5680 Jun 11 11:02 nagios-time.js
-rw-rw-r-- 1 nagios nagios   4563 Jun 11 11:02 trends-form.js
-rw-rw-r-- 1 nagios nagios  18093 Jun 11 11:02 trends-graph.js
-rw-rw-r-- 1 nagios nagios   6449 Jun 11 11:02 trends.js

/usr/local/nagios/share/locale:
total 8
drwxr-xr-x 3 root root 4096 Jun 11 11:09 de
drwxr-xr-x 3 root root 4096 Jun 11 11:09 fr

/usr/local/nagios/share/locale/de:
total 4
drwxr-xr-x 2 root root 4096 Jun 11 11:09 LC_MESSAGES

/usr/local/nagios/share/locale/de/LC_MESSAGES:
total 8
-rw-r--r-- 1 nagios nagios 8153 Jun 11 11:09 nagios-plugins.mo

/usr/local/nagios/share/locale/fr:
total 4
drwxr-xr-x 2 root root 4096 Jun 11 11:09 LC_MESSAGES

/usr/local/nagios/share/locale/fr/LC_MESSAGES:
total 100
-rw-r--r-- 1 nagios nagios 98419 Jun 11 11:09 nagios-plugins.mo

/usr/local/nagios/share/media:
total 0

/usr/local/nagios/share/spin:
total 8
-rw-rw-r-- 1 nagios nagios 4143 Jun 11 11:02 spin.min.js

/usr/local/nagios/share/ssi:
total 0

/usr/local/nagios/share/stylesheets:
total 112
-rw-rw-r-- 1 nagios nagios 1913 Jun 11 11:02 avail.css
-rw-rw-r-- 1 nagios nagios 1261 Jun 11 11:02 checksanity.css
-rw-rw-r-- 1 nagios nagios  959 Jun 11 11:02 cmd.css
-rw-rw-r-- 1 nagios nagios 9734 Jun 11 11:02 common.css
-rw-rw-r-- 1 nagios nagios  586 Jun 11 11:02 config.css
-rw-rw-r-- 1 nagios nagios 5626 Jun 11 11:02 extinfo.css
-rw-rw-r-- 1 nagios nagios  560 Jun 11 11:02 histogram.css
-rw-rw-r-- 1 nagios nagios 1915 Jun 11 11:02 histogramgraph.css
-rw-rw-r-- 1 nagios nagios  482 Jun 11 11:02 history.css
-rw-rw-r-- 1 nagios nagios  442 Jun 11 11:02 jsonquery.css
-rw-rw-r-- 1 nagios nagios  514 Jun 11 11:02 map.css
-rw-rw-r-- 1 nagios nagios 1439 Jun 11 11:02 map-directive.css
-rw-rw-r-- 1 nagios nagios 4422 Jun 11 11:02 ministatus.css
-rw-rw-r-- 1 nagios nagios 2297 Jun 11 11:02 notifications.css
-rw-rw-r-- 1 nagios nagios  743 Jun 11 11:02 outages.css
-rw-rw-r-- 1 nagios nagios  482 Jun 11 11:02 showlog.css
-rw-rw-r-- 1 nagios nagios 7283 Jun 11 11:02 status.css
-rw-rw-r-- 1 nagios nagios  710 Jun 11 11:02 statusmap.css
-rw-rw-r-- 1 nagios nagios 1748 Jun 11 11:02 summary.css
-rw-rw-r-- 1 nagios nagios 5472 Jun 11 11:02 tac.css
-rw-rw-r-- 1 nagios nagios  481 Jun 11 11:02 trends.css
-rw-rw-r-- 1 nagios nagios 1901 Jun 11 11:02 trendsgraph.css

/usr/local/nagios/var:
total 88
drwxrwxr-x 2 nagios nagios  4096 Jun 14 23:59 archives
-rw-r--r-- 1 nagios nagios    34 Jun 11 23:16 nagios.configtest
-rw-r--r-- 1 nagios nagios     6 Jun 11 23:16 nagios.lock
-rw-r--r-- 1 nagios nagios  2759 Jun 15 12:23 nagios.log
-rw-r--r-- 1 nagios nagios 12663 Jun 11 23:16 objects.cache
-rw-r--r-- 1 nagios nagios 12663 Jun 11 23:16 objects.precache
-rw------- 1 nagios nagios 13155 Jun 15 12:23 retention.dat
drwxrwsr-x 2 nagios nagcmd  4096 Jun 11 23:16 rw
drwxr-xr-x 3 root   root    4096 Jun 11 11:02 spool
-rw-rw-r-- 1 nagios nagios 13598 Jun 15 12:27 status.dat

/usr/local/nagios/var/archives:
total 36
-rw-r--r-- 1 nagios nagios 10926 Jun 11 23:16 nagios-06-12-2015-00.log
-rw-r--r-- 1 nagios nagios  4189 Jun 12 23:23 nagios-06-13-2015-00.log
-rw-r--r-- 1 nagios nagios  4189 Jun 13 23:23 nagios-06-14-2015-00.log
-rw-r--r-- 1 nagios nagios  4189 Jun 14 23:23 nagios-06-15-2015-00.log

/usr/local/nagios/var/rw:
total 0
prw-rw---- 1 nagios nagcmd 0 Jun 11 23:16 nagios.cmd
srw-rw---- 1 nagios nagcmd 0 Jun 11 23:16 nagios.qh

/usr/local/nagios/var/spool:
total 4
drwxrwsr-x 2 nagios nagcmd 4096 Jun 11 23:16 checkresults

/usr/local/nagios/var/spool/checkresults:
total 0
Apparmor doesn't seem to be installed.

Code: Select all

$ sudo apparmor_status
sudo: apparmor_status: command not found
$ sudo service apparmor stop
apparmor: unrecognized service
$ ps aux | grep apparmor
scrusi   25348  0.0  0.0  12360   952 pts/1    S+   12:57   0:00 grep apparmor
ls -l /etc/init.d/ap*
-rwxr-xr-x 1 root root 9974 Jan  7  2014 /etc/init.d/apache2
$ sudo apt-get remove apparmor* -s
*snip*
Package 'apparmor-parser' is not installed, so not removed
Package 'apparmor-easyprof-ubuntu' is not installed, so not removed
Package 'click-apparmor' is not installed, so not removed
Package 'python3-apparmor-click' is not installed, so not removed
Package 'fwknop-apparmor-profile' is not installed, so not removed
Package 'apparmor' is not installed, so not removed
Package 'apparmor-docs' is not installed, so not removed
Package 'apparmor-easyprof' is not installed, so not removed
Package 'apparmor-notify' is not installed, so not removed
Package 'apparmor-profiles' is not installed, so not removed
Package 'apparmor-utils' is not installed, so not removed
Package 'dh-apparmor' is not installed, so not removed
Package 'libapache2-mod-apparmor' is not installed, so not removed
Package 'libapparmor-dev' is not installed, so not removed
Package 'libapparmor-perl' is not installed, so not removed
Package 'libapparmor1' is not installed, so not removed
Package 'libpam-apparmor' is not installed, so not removed
Package 'python-libapparmor' is not installed, so not removed
Package 'python3-apparmor' is not installed, so not removed
Package 'python3-libapparmor' is not installed, so not removed
Package 'python-apparmor' is not installed, so not removed
However, there are some files that suggest the presence of apparmor:

Code: Select all

ls -lR /etc/apparmor.d/
/etc/apparmor.d/:
total 32
drwxr-xr-x 2 root root 4096 Mai  6 13:49 disable
drwxr-xr-x 2 root root 4096 Mai  6 13:50 force-complain
drwxr-xr-x 2 root root 4096 Mai  6 13:50 local
-rw-r--r-- 1 root root 2461 Mär 30 19:23 sbin.dhclient
-rw-r--r-- 1 root root 1048 Apr 20 18:51 usr.sbin.mysqld
-rw-r--r-- 1 root root 1342 Feb 18 14:45 usr.sbin.named
-rw-r--r-- 1 root root 1394 Apr 25 08:26 usr.sbin.rsyslogd
-rw-r--r-- 1 root root 1418 Jan 13  2014 usr.sbin.tcpdump

/etc/apparmor.d/disable:
total 0
lrwxrwxrwx 1 root root 33 Mai  6 13:49 usr.sbin.rsyslogd -> /etc/apparmor.d/usr.sbin.rsyslogd

/etc/apparmor.d/force-complain:
total 0

/etc/apparmor.d/local:
total 20
-rw-r--r-- 1 root root 120 Mai  6 13:50 sbin.dhclient
-rw-r--r-- 1 root root 122 Mai  6 13:50 usr.sbin.mysqld
-rw-r--r-- 1 root root 121 Feb 18 14:45 usr.sbin.named
-rw-r--r-- 1 root root 124 Mai  6 13:50 usr.sbin.rsyslogd
-rw-r--r-- 1 root root 123 Mai  6 13:50 usr.sbin.tcpdump
and

Code: Select all

ls -lR /etc/apparmor/
/etc/apparmor/:
total 4
drwxr-xr-x 3 root root 4096 Mai  6 13:49 init

/etc/apparmor/init:
total 4
drwxr-xr-x 2 root root 4096 Jun 10 13:24 network-interface-security

/etc/apparmor/init/network-interface-security:
total 0
lrwxrwxrwx 1 root root 33 Mai  1 21:44 sbin.dhclient -> ../../../apparmor.d/sbin.dhclient
Not sure what to make of that.
There's also this:

Code: Select all

$ ls -lR /etc/selinux/
/etc/selinux/:
total 8
-rw-r--r-- 1 root root   17 Jun 10 19:21 config
-rw-r--r-- 1 root root 1888 Nov  2  2013 semanage.conf

Re: CGI and Internal Server Errors

Posted: Mon Jun 15, 2015 10:36 am
by tgriep
Could you run this can post back the results?

Code: Select all

cat /etc/selinux/config

Re: CGI and Internal Server Errors

Posted: Mon Jun 15, 2015 1:41 pm
by scrusi
Sure.

Code: Select all

$ cat /etc/selinux/config
SELINUX=disabled

Re: CGI and Internal Server Errors

Posted: Mon Jun 15, 2015 3:47 pm
by tgriep
Could you run this from the folder where you complied the Nagios Core software and see if that fixes it.

Code: Select all

make install-webconf
If not, can you upload your nagios.cfg and resource.cfg files?

Re: CGI and Internal Server Errors

Posted: Mon Jun 15, 2015 4:01 pm
by scrusi
certainly.

Code: Select all

/tmp/nagioscore-master$ sudo make install-webconf
[sudo] password for scrusi:
/usr/bin/install -c -m 644 sample-config/httpd.conf /etc/httpd/conf.d/nagios.conf

*** Nagios/Apache conf file installed ***

$ sudo /etc/init.d/apache2 restart
 * Restarting web server apache2                                                AH00548: NameVirtualHost has no effect and will be removed in the next release /etc/apache2/plesk.conf.d/server.conf:6
                                                                         [ OK ]
$ sudo /etc/init.d/nagios restart
Running configuration check...
Stopping nagios: done.
Starting nagios: done.

No change.

nagios.cfg (should be the default config at the moment:

Code: Select all

##############################################################################
#
# NAGIOS.CFG - Sample Main Config File for Nagios 4.1.0rc1
#
# Read the documentation for more information on this configuration
# file.  I've provided some comments here, but things may not be so
# clear without further explanation.
#
#
##############################################################################


# LOG FILE
# This is the main log file where service and host events are logged
# for historical purposes.  This should be the first option specified 
# in the config file!!!

log_file=/usr/local/nagios/var/nagios.log



# OBJECT CONFIGURATION FILE(S)
# These are the object configuration files in which you define hosts,
# host groups, contacts, contact groups, services, etc.
# You can split your object definitions across several config files
# if you wish (as shown below), or keep them all in a single config file.

# You can specify individual object config files as shown below:
cfg_file=/usr/local/nagios/etc/objects/commands.cfg
cfg_file=/usr/local/nagios/etc/objects/contacts.cfg
cfg_file=/usr/local/nagios/etc/objects/timeperiods.cfg
cfg_file=/usr/local/nagios/etc/objects/templates.cfg

# Definitions for monitoring the local (Linux) host
cfg_file=/usr/local/nagios/etc/objects/localhost.cfg

# Definitions for monitoring a Windows machine
#cfg_file=/usr/local/nagios/etc/objects/windows.cfg

# Definitions for monitoring a router/switch
#cfg_file=/usr/local/nagios/etc/objects/switch.cfg

# Definitions for monitoring a network printer
#cfg_file=/usr/local/nagios/etc/objects/printer.cfg


# You can also tell Nagios to process all config files (with a .cfg
# extension) in a particular directory by using the cfg_dir
# directive as shown below:

#cfg_dir=/usr/local/nagios/etc/servers
#cfg_dir=/usr/local/nagios/etc/printers
#cfg_dir=/usr/local/nagios/etc/switches
#cfg_dir=/usr/local/nagios/etc/routers




# OBJECT CACHE FILE
# This option determines where object definitions are cached when
# Nagios starts/restarts.  The CGIs read object definitions from 
# this cache file (rather than looking at the object config files
# directly) in order to prevent inconsistencies that can occur
# when the config files are modified after Nagios starts.

object_cache_file=/usr/local/nagios/var/objects.cache



# PRE-CACHED OBJECT FILE
# This options determines the location of the precached object file.
# If you run Nagios with the -p command line option, it will preprocess
# your object configuration file(s) and write the cached config to this
# file.  You can then start Nagios with the -u option to have it read
# object definitions from this precached file, rather than the standard
# object configuration files (see the cfg_file and cfg_dir options above).
# Using a precached object file can speed up the time needed to (re)start 
# the Nagios process if you've got a large and/or complex configuration.
# Read the documentation section on optimizing Nagios to find our more
# about how this feature works.

precached_object_file=/usr/local/nagios/var/objects.precache



# RESOURCE FILE
# This is an optional resource file that contains $USERx$ macro
# definitions. Multiple resource files can be specified by using
# multiple resource_file definitions.  The CGIs will not attempt to
# read the contents of resource files, so information that is
# considered to be sensitive (usernames, passwords, etc) can be
# defined as macros in this file and restrictive permissions (600)
# can be placed on this file.

resource_file=/usr/local/nagios/etc/resource.cfg



# STATUS FILE
# This is where the current status of all monitored services and
# hosts is stored.  Its contents are read and processed by the CGIs.
# The contents of the status file are deleted every time Nagios
#  restarts.

status_file=/usr/local/nagios/var/status.dat



# STATUS FILE UPDATE INTERVAL
# This option determines the frequency (in seconds) that
# Nagios will periodically dump program, host, and 
# service status data.

status_update_interval=10



# NAGIOS USER
# This determines the effective user that Nagios should run as.  
# You can either supply a username or a UID.

nagios_user=nagios



# NAGIOS GROUP
# This determines the effective group that Nagios should run as.  
# You can either supply a group name or a GID.

nagios_group=nagios



# EXTERNAL COMMAND OPTION
# This option allows you to specify whether or not Nagios should check
# for external commands (in the command file defined below).  By default
# Nagios will *not* check for external commands, just to be on the
# cautious side.  If you want to be able to use the CGI command interface
# you will have to enable this.
# Values: 0 = disable commands, 1 = enable commands

check_external_commands=1



# EXTERNAL COMMAND FILE
# This is the file that Nagios checks for external command requests.
# It is also where the command CGI will write commands that are submitted
# by users, so it must be writeable by the user that the web server
# is running as (usually 'nobody').  Permissions should be set at the 
# directory level instead of on the file, as the file is deleted every
# time its contents are processed.

command_file=/usr/local/nagios/var/rw/nagios.cmd



# QUERY HANDLER INTERFACE
# This is the socket that is created for the Query Handler interface

#query_socket=/usr/local/nagios/var/rw/nagios.qh



# LOCK FILE
# This is the lockfile that Nagios will use to store its PID number
# in when it is running in daemon mode.

lock_file=/usr/local/nagios/var/nagios.lock



# TEMP FILE
# This is a temporary file that is used as scratch space when Nagios
# updates the status log, cleans the comment file, etc.  This file
# is created, used, and deleted throughout the time that Nagios is
# running.

temp_file=/usr/local/nagios/var/nagios.tmp



# TEMP PATH
# This is path where Nagios can create temp files for service and
# host check results, etc.

temp_path=/tmp



# EVENT BROKER OPTIONS
# Controls what (if any) data gets sent to the event broker.
# Values:  0      = Broker nothing
#         -1      = Broker everything
#         <other> = See documentation

event_broker_options=-1



# EVENT BROKER MODULE(S)
# This directive is used to specify an event broker module that should
# by loaded by Nagios at startup.  Use multiple directives if you want
# to load more than one module.  Arguments that should be passed to
# the module at startup are seperated from the module path by a space.
#
#!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
# WARNING !!! WARNING !!! WARNING !!! WARNING !!! WARNING !!! WARNING
#!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
#
# Do NOT overwrite modules while they are being used by Nagios or Nagios
# will crash in a fiery display of SEGFAULT glory.  This is a bug/limitation
# either in dlopen(), the kernel, and/or the filesystem.  And maybe Nagios...
#
# The correct/safe way of updating a module is by using one of these methods:
#    1. Shutdown Nagios, replace the module file, restart Nagios
#    2. Delete the original module file, move the new module file into place, restart Nagios
#
# Example:
#
#   broker_module=<modulepath> [moduleargs]

#broker_module=/somewhere/module1.o
#broker_module=/somewhere/module2.o arg1 arg2=3 debug=0



# LOG ROTATION METHOD
# This is the log rotation method that Nagios should use to rotate
# the main log file. Values are as follows..
#	n	= None - don't rotate the log
#	h	= Hourly rotation (top of the hour)
#	d	= Daily rotation (midnight every day)
#	w	= Weekly rotation (midnight on Saturday evening)
#	m	= Monthly rotation (midnight last day of month)

log_rotation_method=d



# LOG ARCHIVE PATH
# This is the directory where archived (rotated) log files should be 
# placed (assuming you've chosen to do log rotation).

log_archive_path=/usr/local/nagios/var/archives



# LOGGING OPTIONS
# If you want messages logged to the syslog facility, as well as the
# Nagios log file set this option to 1.  If not, set it to 0.

use_syslog=1



# NOTIFICATION LOGGING OPTION
# If you don't want notifications to be logged, set this value to 0.
# If notifications should be logged, set the value to 1.

log_notifications=1



# SERVICE RETRY LOGGING OPTION
# If you don't want service check retries to be logged, set this value
# to 0.  If retries should be logged, set the value to 1.

log_service_retries=1



# HOST RETRY LOGGING OPTION
# If you don't want host check retries to be logged, set this value to
# 0.  If retries should be logged, set the value to 1.

log_host_retries=1



# EVENT HANDLER LOGGING OPTION
# If you don't want host and service event handlers to be logged, set
# this value to 0.  If event handlers should be logged, set the value
# to 1.

log_event_handlers=1



# INITIAL STATES LOGGING OPTION
# If you want Nagios to log all initial host and service states to
# the main log file (the first time the service or host is checked)
# you can enable this option by setting this value to 1.  If you
# are not using an external application that does long term state
# statistics reporting, you do not need to enable this option.  In
# this case, set the value to 0.

log_initial_states=0



# CURRENT STATES LOGGING OPTION
# If you don't want Nagios to log all current host and service states
# after log has been rotated to the main log file, you can disable this
# option by setting this value to 0. Default value is 1.

log_current_states=1



# EXTERNAL COMMANDS LOGGING OPTION
# If you don't want Nagios to log external commands, set this value
# to 0.  If external commands should be logged, set this value to 1.
# Note: This option does not include logging of passive service
# checks - see the option below for controlling whether or not
# passive checks are logged.

log_external_commands=1



# PASSIVE CHECKS LOGGING OPTION
# If you don't want Nagios to log passive host and service checks, set
# this value to 0.  If passive checks should be logged, set
# this value to 1.

log_passive_checks=1



# GLOBAL HOST AND SERVICE EVENT HANDLERS
# These options allow you to specify a host and service event handler
# command that is to be run for every host or service state change.
# The global event handler is executed immediately prior to the event
# handler that you have optionally specified in each host or
# service definition. The command argument is the short name of a
# command definition that you define in your host configuration file.
# Read the HTML docs for more information.

#global_host_event_handler=somecommand
#global_service_event_handler=somecommand



# SERVICE INTER-CHECK DELAY METHOD
# This is the method that Nagios should use when initially
# "spreading out" service checks when it starts monitoring.  The
# default is to use smart delay calculation, which will try to
# space all service checks out evenly to minimize CPU load.
# Using the dumb setting will cause all checks to be scheduled
# at the same time (with no delay between them)!  This is not a
# good thing for production, but is useful when testing the
# parallelization functionality.
#	n	= None - don't use any delay between checks
#	d	= Use a "dumb" delay of 1 second between checks
#	s	= Use "smart" inter-check delay calculation
#       x.xx    = Use an inter-check delay of x.xx seconds

service_inter_check_delay_method=s



# MAXIMUM SERVICE CHECK SPREAD
# This variable determines the timeframe (in minutes) from the
# program start time that an initial check of all services should
# be completed.  Default is 30 minutes.

max_service_check_spread=30



# SERVICE CHECK INTERLEAVE FACTOR
# This variable determines how service checks are interleaved.
# Interleaving the service checks allows for a more even
# distribution of service checks and reduced load on remote
# hosts.  Setting this value to 1 is equivalent to how versions
# of Nagios previous to 0.0.5 did service checks.  Set this
# value to s (smart) for automatic calculation of the interleave
# factor unless you have a specific reason to change it.
#       s       = Use "smart" interleave factor calculation
#       x       = Use an interleave factor of x, where x is a
#                 number greater than or equal to 1.

service_interleave_factor=s



# HOST INTER-CHECK DELAY METHOD
# This is the method that Nagios should use when initially
# "spreading out" host checks when it starts monitoring.  The
# default is to use smart delay calculation, which will try to
# space all host checks out evenly to minimize CPU load.
# Using the dumb setting will cause all checks to be scheduled
# at the same time (with no delay between them)!
#	n	= None - don't use any delay between checks
#	d	= Use a "dumb" delay of 1 second between checks
#	s	= Use "smart" inter-check delay calculation
#       x.xx    = Use an inter-check delay of x.xx seconds

host_inter_check_delay_method=s



# MAXIMUM HOST CHECK SPREAD
# This variable determines the timeframe (in minutes) from the
# program start time that an initial check of all hosts should
# be completed.  Default is 30 minutes.

max_host_check_spread=30



# MAXIMUM CONCURRENT SERVICE CHECKS
# This option allows you to specify the maximum number of 
# service checks that can be run in parallel at any given time.
# Specifying a value of 1 for this variable essentially prevents
# any service checks from being parallelized.  A value of 0
# will not restrict the number of concurrent checks that are
# being executed.

max_concurrent_checks=0



# HOST AND SERVICE CHECK REAPER FREQUENCY
# This is the frequency (in seconds!) that Nagios will process
# the results of host and service checks.

check_result_reaper_frequency=10




# MAX CHECK RESULT REAPER TIME
# This is the max amount of time (in seconds) that  a single
# check result reaper event will be allowed to run before 
# returning control back to Nagios so it can perform other
# duties.

max_check_result_reaper_time=30




# CHECK RESULT PATH
# This is directory where Nagios stores the results of host and
# service checks that have not yet been processed.
#
# Note: Make sure that only one instance of Nagios has access
# to this directory!  

check_result_path=/usr/local/nagios/var/spool/checkresults




# MAX CHECK RESULT FILE AGE
# This option determines the maximum age (in seconds) which check
# result files are considered to be valid.  Files older than this 
# threshold will be mercilessly deleted without further processing.

max_check_result_file_age=3600




# CACHED HOST CHECK HORIZON
# This option determines the maximum amount of time (in seconds)
# that the state of a previous host check is considered current.
# Cached host states (from host checks that were performed more
# recently that the timeframe specified by this value) can immensely
# improve performance in regards to the host check logic.
# Too high of a value for this option may result in inaccurate host
# states being used by Nagios, while a lower value may result in a
# performance hit for host checks.  Use a value of 0 to disable host
# check caching.

cached_host_check_horizon=15



# CACHED SERVICE CHECK HORIZON
# This option determines the maximum amount of time (in seconds)
# that the state of a previous service check is considered current.
# Cached service states (from service checks that were performed more
# recently that the timeframe specified by this value) can immensely
# improve performance in regards to predictive dependency checks.
# Use a value of 0 to disable service check caching.

cached_service_check_horizon=15



# ENABLE PREDICTIVE HOST DEPENDENCY CHECKS
# This option determines whether or not Nagios will attempt to execute
# checks of hosts when it predicts that future dependency logic test
# may be needed.  These predictive checks can help ensure that your
# host dependency logic works well.
# Values:
#  0 = Disable predictive checks
#  1 = Enable predictive checks (default)

enable_predictive_host_dependency_checks=1



# ENABLE PREDICTIVE SERVICE DEPENDENCY CHECKS
# This option determines whether or not Nagios will attempt to execute
# checks of service when it predicts that future dependency logic test
# may be needed.  These predictive checks can help ensure that your
# service dependency logic works well.
# Values:
#  0 = Disable predictive checks
#  1 = Enable predictive checks (default)

enable_predictive_service_dependency_checks=1



# SOFT STATE DEPENDENCIES
# This option determines whether or not Nagios will use soft state 
# information when checking host and service dependencies. Normally 
# Nagios will only use the latest hard host or service state when 
# checking dependencies. If you want it to use the latest state (regardless
# of whether its a soft or hard state type), enable this option. 
# Values:
#  0 = Don't use soft state dependencies (default) 
#  1 = Use soft state dependencies 

soft_state_dependencies=0



# TIME CHANGE ADJUSTMENT THRESHOLDS
# These options determine when Nagios will react to detected changes
# in system time (either forward or backwards).

#time_change_threshold=900



# AUTO-RESCHEDULING OPTION
# This option determines whether or not Nagios will attempt to
# automatically reschedule active host and service checks to
# "smooth" them out over time.  This can help balance the load on
# the monitoring server.  
# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY

auto_reschedule_checks=0



# AUTO-RESCHEDULING INTERVAL
# This option determines how often (in seconds) Nagios will
# attempt to automatically reschedule checks.  This option only
# has an effect if the auto_reschedule_checks option is enabled.
# Default is 30 seconds.
# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY

auto_rescheduling_interval=30



# AUTO-RESCHEDULING WINDOW
# This option determines the "window" of time (in seconds) that
# Nagios will look at when automatically rescheduling checks.
# Only host and service checks that occur in the next X seconds
# (determined by this variable) will be rescheduled. This option
# only has an effect if the auto_reschedule_checks option is
# enabled.  Default is 180 seconds (3 minutes).
# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY

auto_rescheduling_window=180



# TIMEOUT VALUES
# These options control how much time Nagios will allow various
# types of commands to execute before killing them off.  Options
# are available for controlling maximum time allotted for
# service checks, host checks, event handlers, notifications, the
# ocsp command, and performance data commands.  All values are in
# seconds.

service_check_timeout=60
host_check_timeout=30
event_handler_timeout=30
notification_timeout=30
ocsp_timeout=5
perfdata_timeout=5



# RETAIN STATE INFORMATION
# This setting determines whether or not Nagios will save state
# information for services and hosts before it shuts down.  Upon
# startup Nagios will reload all saved service and host state
# information before starting to monitor.  This is useful for 
# maintaining long-term data on state statistics, etc, but will
# slow Nagios down a bit when it (re)starts.  Since its only
# a one-time penalty, I think its well worth the additional
# startup delay.

retain_state_information=1



# STATE RETENTION FILE
# This is the file that Nagios should use to store host and
# service state information before it shuts down.  The state 
# information in this file is also read immediately prior to
# starting to monitor the network when Nagios is restarted.
# This file is used only if the retain_state_information
# variable is set to 1.

state_retention_file=/usr/local/nagios/var/retention.dat



# RETENTION DATA UPDATE INTERVAL
# This setting determines how often (in minutes) that Nagios
# will automatically save retention data during normal operation.
# If you set this value to 0, Nagios will not save retention
# data at regular interval, but it will still save retention
# data before shutting down or restarting.  If you have disabled
# state retention, this option has no effect.

retention_update_interval=60



# USE RETAINED PROGRAM STATE
# This setting determines whether or not Nagios will set 
# program status variables based on the values saved in the
# retention file.  If you want to use retained program status
# information, set this value to 1.  If not, set this value
# to 0.

use_retained_program_state=1



# USE RETAINED SCHEDULING INFO
# This setting determines whether or not Nagios will retain
# the scheduling info (next check time) for hosts and services
# based on the values saved in the retention file.  If you
# If you want to use retained scheduling info, set this
# value to 1.  If not, set this value to 0.

use_retained_scheduling_info=1



# RETAINED ATTRIBUTE MASKS (ADVANCED FEATURE)
# The following variables are used to specify specific host and
# service attributes that should *not* be retained by Nagios during
# program restarts.
#
# The values of the masks are bitwise ANDs of values specified
# by the "MODATTR_" definitions found in include/common.h.  
# For example, if you do not want the current enabled/disabled state
# of flap detection and event handlers for hosts to be retained, you
# would use a value of 24 for the host attribute mask...
# MODATTR_EVENT_HANDLER_ENABLED (8) + MODATTR_FLAP_DETECTION_ENABLED (16) = 24

# This mask determines what host attributes are not retained
retained_host_attribute_mask=0

# This mask determines what service attributes are not retained
retained_service_attribute_mask=0

# These two masks determine what process attributes are not retained.
# There are two masks, because some process attributes have host and service
# options.  For example, you can disable active host checks, but leave active
# service checks enabled.
retained_process_host_attribute_mask=0
retained_process_service_attribute_mask=0

# These two masks determine what contact attributes are not retained.
# There are two masks, because some contact attributes have host and
# service options.  For example, you can disable host notifications for
# a contact, but leave service notifications enabled for them.
retained_contact_host_attribute_mask=0
retained_contact_service_attribute_mask=0



# INTERVAL LENGTH
# This is the seconds per unit interval as used in the
# host/contact/service configuration files.  Setting this to 60 means
# that each interval is one minute long (60 seconds).  Other settings
# have not been tested much, so your mileage is likely to vary...

interval_length=60



# CHECK FOR UPDATES
# This option determines whether Nagios will automatically check to
# see if new updates (releases) are available.  It is recommend that you
# enable this option to ensure that you stay on top of the latest critical
# patches to Nagios.  Nagios is critical to you - make sure you keep it in
# good shape.  Nagios will check once a day for new updates. Data collected
# by Nagios Enterprises from the update check is processed in accordance 
# with our privacy policy - see http://api.nagios.org for details.

check_for_updates=1



# BARE UPDATE CHECK
# This option deterines what data Nagios will send to api.nagios.org when
# it checks for updates.  By default, Nagios will send information on the 
# current version of Nagios you have installed, as well as an indicator as
# to whether this was a new installation or not.  Nagios Enterprises uses
# this data to determine the number of users running specific version of 
# Nagios.  Enable this option if you do not want this information to be sent.

bare_update_check=0



# AGGRESSIVE HOST CHECKING OPTION
# If you don't want to turn on aggressive host checking features, set
# this value to 0 (the default).  Otherwise set this value to 1 to
# enable the aggressive check option.  Read the docs for more info
# on what aggressive host check is or check out the source code in
# base/checks.c

use_aggressive_host_checking=0



# SERVICE CHECK EXECUTION OPTION
# This determines whether or not Nagios will actively execute
# service checks when it initially starts.  If this option is 
# disabled, checks are not actively made, but Nagios can still
# receive and process passive check results that come in.  Unless
# you're implementing redundant hosts or have a special need for
# disabling the execution of service checks, leave this enabled!
# Values: 1 = enable checks, 0 = disable checks

execute_service_checks=1



# PASSIVE SERVICE CHECK ACCEPTANCE OPTION
# This determines whether or not Nagios will accept passive
# service checks results when it initially (re)starts.
# Values: 1 = accept passive checks, 0 = reject passive checks

accept_passive_service_checks=1



# HOST CHECK EXECUTION OPTION
# This determines whether or not Nagios will actively execute
# host checks when it initially starts.  If this option is 
# disabled, checks are not actively made, but Nagios can still
# receive and process passive check results that come in.  Unless
# you're implementing redundant hosts or have a special need for
# disabling the execution of host checks, leave this enabled!
# Values: 1 = enable checks, 0 = disable checks

execute_host_checks=1



# PASSIVE HOST CHECK ACCEPTANCE OPTION
# This determines whether or not Nagios will accept passive
# host checks results when it initially (re)starts.
# Values: 1 = accept passive checks, 0 = reject passive checks

accept_passive_host_checks=1



# NOTIFICATIONS OPTION
# This determines whether or not Nagios will sent out any host or
# service notifications when it is initially (re)started.
# Values: 1 = enable notifications, 0 = disable notifications

enable_notifications=1



# EVENT HANDLER USE OPTION
# This determines whether or not Nagios will run any host or
# service event handlers when it is initially (re)started.  Unless
# you're implementing redundant hosts, leave this option enabled.
# Values: 1 = enable event handlers, 0 = disable event handlers

enable_event_handlers=1



# PROCESS PERFORMANCE DATA OPTION
# This determines whether or not Nagios will process performance
# data returned from service and host checks.  If this option is
# enabled, host performance data will be processed using the
# host_perfdata_command (defined below) and service performance
# data will be processed using the service_perfdata_command (also
# defined below).  Read the HTML docs for more information on
# performance data.
# Values: 1 = process performance data, 0 = do not process performance data

process_performance_data=0



# HOST AND SERVICE PERFORMANCE DATA PROCESSING COMMANDS
# These commands are run after every host and service check is
# performed.  These commands are executed only if the
# enable_performance_data option (above) is set to 1.  The command
# argument is the short name of a command definition that you 
# define in your host configuration file.  Read the HTML docs for
# more information on performance data.

#host_perfdata_command=process-host-perfdata
#service_perfdata_command=process-service-perfdata



# HOST AND SERVICE PERFORMANCE DATA FILES
# These files are used to store host and service performance data.
# Performance data is only written to these files if the
# enable_performance_data option (above) is set to 1.

#host_perfdata_file=/usr/local/nagios/var/host-perfdata
#service_perfdata_file=/usr/local/nagios/var/service-perfdata



# HOST AND SERVICE PERFORMANCE DATA FILE TEMPLATES
# These options determine what data is written (and how) to the
# performance data files.  The templates may contain macros, special
# characters (\t for tab, \r for carriage return, \n for newline)
# and plain text.  A newline is automatically added after each write
# to the performance data file.  Some examples of what you can do are
# shown below.

#host_perfdata_file_template=[HOSTPERFDATA]\t$TIMET$\t$HOSTNAME$\t$HOSTEXECUTIONTIME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$
#service_perfdata_file_template=[SERVICEPERFDATA]\t$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICEEXECUTIONTIME$\t$SERVICELATENCY$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$



# HOST AND SERVICE PERFORMANCE DATA FILE MODES
# This option determines whether or not the host and service
# performance data files are opened in write ("w") or append ("a")
# mode. If you want to use named pipes, you should use the special
# pipe ("p") mode which avoid blocking at startup, otherwise you will
# likely want the defult append ("a") mode.

#host_perfdata_file_mode=a
#service_perfdata_file_mode=a



# HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING INTERVAL
# These options determine how often (in seconds) the host and service
# performance data files are processed using the commands defined
# below.  A value of 0 indicates the files should not be periodically
# processed.

#host_perfdata_file_processing_interval=0
#service_perfdata_file_processing_interval=0



# HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING COMMANDS
# These commands are used to periodically process the host and
# service performance data files.  The interval at which the
# processing occurs is determined by the options above.

#host_perfdata_file_processing_command=process-host-perfdata-file
#service_perfdata_file_processing_command=process-service-perfdata-file



# HOST AND SERVICE PERFORMANCE DATA PROCESS EMPTY RESULTS
# These options determine wether the core will process empty perfdata
# results or not. This is needed for distributed monitoring, and intentionally
# turned on by default.
# If you don't require empty perfdata - saving some cpu cycles
# on unwanted macro calculation - you can turn that off. Be careful!
# Values: 1 = enable, 0 = disable

#host_perfdata_process_empty_results=1
#service_perfdata_process_empty_results=1


# OBSESS OVER SERVICE CHECKS OPTION
# This determines whether or not Nagios will obsess over service
# checks and run the ocsp_command defined below.  Unless you're
# planning on implementing distributed monitoring, do not enable
# this option.  Read the HTML docs for more information on
# implementing distributed monitoring.
# Values: 1 = obsess over services, 0 = do not obsess (default)

obsess_over_services=0



# OBSESSIVE COMPULSIVE SERVICE PROCESSOR COMMAND
# This is the command that is run for every service check that is
# processed by Nagios.  This command is executed only if the
# obsess_over_services option (above) is set to 1.  The command 
# argument is the short name of a command definition that you
# define in your host configuration file. Read the HTML docs for
# more information on implementing distributed monitoring.

#ocsp_command=somecommand



# OBSESS OVER HOST CHECKS OPTION
# This determines whether or not Nagios will obsess over host
# checks and run the ochp_command defined below.  Unless you're
# planning on implementing distributed monitoring, do not enable
# this option.  Read the HTML docs for more information on
# implementing distributed monitoring.
# Values: 1 = obsess over hosts, 0 = do not obsess (default)

obsess_over_hosts=0



# OBSESSIVE COMPULSIVE HOST PROCESSOR COMMAND
# This is the command that is run for every host check that is
# processed by Nagios.  This command is executed only if the
# obsess_over_hosts option (above) is set to 1.  The command 
# argument is the short name of a command definition that you
# define in your host configuration file. Read the HTML docs for
# more information on implementing distributed monitoring.

#ochp_command=somecommand



# TRANSLATE PASSIVE HOST CHECKS OPTION
# This determines whether or not Nagios will translate
# DOWN/UNREACHABLE passive host check results into their proper
# state for this instance of Nagios.  This option is useful
# if you have distributed or failover monitoring setup.  In
# these cases your other Nagios servers probably have a different
# "view" of the network, with regards to the parent/child relationship
# of hosts.  If a distributed monitoring server thinks a host
# is DOWN, it may actually be UNREACHABLE from the point of
# this Nagios instance.  Enabling this option will tell Nagios
# to translate any DOWN or UNREACHABLE host states it receives
# passively into the correct state from the view of this server.
# Values: 1 = perform translation, 0 = do not translate (default)

translate_passive_host_checks=0



# PASSIVE HOST CHECKS ARE SOFT OPTION
# This determines whether or not Nagios will treat passive host
# checks as being HARD or SOFT.  By default, a passive host check
# result will put a host into a HARD state type.  This can be changed
# by enabling this option.
# Values: 0 = passive checks are HARD, 1 = passive checks are SOFT

passive_host_checks_are_soft=0



# ORPHANED HOST/SERVICE CHECK OPTIONS
# These options determine whether or not Nagios will periodically 
# check for orphaned host service checks.  Since service checks are
# not rescheduled until the results of their previous execution 
# instance are processed, there exists a possibility that some
# checks may never get rescheduled.  A similar situation exists for
# host checks, although the exact scheduling details differ a bit
# from service checks.  Orphaned checks seem to be a rare
# problem and should not happen under normal circumstances.
# If you have problems with service checks never getting
# rescheduled, make sure you have orphaned service checks enabled.
# Values: 1 = enable checks, 0 = disable checks

check_for_orphaned_services=1
check_for_orphaned_hosts=1



# SERVICE FRESHNESS CHECK OPTION
# This option determines whether or not Nagios will periodically
# check the "freshness" of service results.  Enabling this option
# is useful for ensuring passive checks are received in a timely
# manner.
# Values: 1 = enabled freshness checking, 0 = disable freshness checking

check_service_freshness=1



# SERVICE FRESHNESS CHECK INTERVAL
# This setting determines how often (in seconds) Nagios will
# check the "freshness" of service check results.  If you have
# disabled service freshness checking, this option has no effect.

service_freshness_check_interval=60



# SERVICE CHECK TIMEOUT STATE
# This setting determines the state Nagios will report when a
# service check times out - that is does not respond within
# service_check_timeout seconds.  This can be useful if a
# machine is running at too high a load and you do not want
# to consider a failed service check to be critical (the default).
# Valid settings are:
# c - Critical (default)
# u - Unknown
# w - Warning
# o - OK

service_check_timeout_state=c



# HOST FRESHNESS CHECK OPTION
# This option determines whether or not Nagios will periodically
# check the "freshness" of host results.  Enabling this option
# is useful for ensuring passive checks are received in a timely
# manner.
# Values: 1 = enabled freshness checking, 0 = disable freshness checking

check_host_freshness=0



# HOST FRESHNESS CHECK INTERVAL
# This setting determines how often (in seconds) Nagios will
# check the "freshness" of host check results.  If you have
# disabled host freshness checking, this option has no effect.

host_freshness_check_interval=60




# ADDITIONAL FRESHNESS THRESHOLD LATENCY
# This setting determines the number of seconds that Nagios
# will add to any host and service freshness thresholds that
# it calculates (those not explicitly specified by the user).

additional_freshness_latency=15




# FLAP DETECTION OPTION
# This option determines whether or not Nagios will try
# and detect hosts and services that are "flapping".  
# Flapping occurs when a host or service changes between
# states too frequently.  When Nagios detects that a 
# host or service is flapping, it will temporarily suppress
# notifications for that host/service until it stops
# flapping.  Flap detection is very experimental, so read
# the HTML documentation before enabling this feature!
# Values: 1 = enable flap detection
#         0 = disable flap detection (default)

enable_flap_detection=1



# FLAP DETECTION THRESHOLDS FOR HOSTS AND SERVICES
# Read the HTML documentation on flap detection for
# an explanation of what this option does.  This option
# has no effect if flap detection is disabled.

low_service_flap_threshold=5.0
high_service_flap_threshold=20.0
low_host_flap_threshold=5.0
high_host_flap_threshold=20.0



# DATE FORMAT OPTION
# This option determines how short dates are displayed. Valid options
# include:
#	us		(MM-DD-YYYY HH:MM:SS)
#	euro    	(DD-MM-YYYY HH:MM:SS)
#	iso8601		(YYYY-MM-DD HH:MM:SS)
#	strict-iso8601	(YYYY-MM-DDTHH:MM:SS)
#

date_format=us




# TIMEZONE OFFSET
# This option is used to override the default timezone that this
# instance of Nagios runs in.  If not specified, Nagios will use
# the system configured timezone.
#
# NOTE: In order to display the correct timezone in the CGIs, you
# will also need to alter the Apache directives for the CGI path 
# to include your timezone.  Example:
#
#   <Directory "/usr/local/nagios/sbin/">
#      SetEnv TZ "Australia/Brisbane"
#      ...
#   </Directory>

#use_timezone=US/Mountain
#use_timezone=Australia/Brisbane



# ILLEGAL OBJECT NAME CHARACTERS
# This option allows you to specify illegal characters that cannot
# be used in host names, service descriptions, or names of other
# object types.

illegal_object_name_chars=`~!$%^&*|'"<>?,()=



# ILLEGAL MACRO OUTPUT CHARACTERS
# This option allows you to specify illegal characters that are
# stripped from macros before being used in notifications, event
# handlers, etc.  This DOES NOT affect macros used in service or
# host check commands.
# The following macros are stripped of the characters you specify:
#	$HOSTOUTPUT$
#	$LONGHOSTOUTPUT$
#	$HOSTPERFDATA$
#	$HOSTACKAUTHOR$
#	$HOSTACKCOMMENT$
#	$SERVICEOUTPUT$
#	$LONGSERVICEOUTPUT$
#	$SERVICEPERFDATA$
#	$SERVICEACKAUTHOR$
#	$SERVICEACKCOMMENT$

illegal_macro_output_chars=`~$&|'"<>



# REGULAR EXPRESSION MATCHING
# This option controls whether or not regular expression matching
# takes place in the object config files.  Regular expression
# matching is used to match host, hostgroup, service, and service
# group names/descriptions in some fields of various object types.
# Values: 1 = enable regexp matching, 0 = disable regexp matching

use_regexp_matching=0



# "TRUE" REGULAR EXPRESSION MATCHING
# This option controls whether or not "true" regular expression 
# matching takes place in the object config files.  This option
# only has an effect if regular expression matching is enabled
# (see above).  If this option is DISABLED, regular expression
# matching only occurs if a string contains wildcard characters
# (* and ?).  If the option is ENABLED, regexp matching occurs
# all the time (which can be annoying).
# Values: 1 = enable true matching, 0 = disable true matching

use_true_regexp_matching=0



# ADMINISTRATOR EMAIL/PAGER ADDRESSES
# The email and pager address of a global administrator (likely you).
# Nagios never uses these values itself, but you can access them by
# using the $ADMINEMAIL$ and $ADMINPAGER$ macros in your notification
# commands.

admin_email=nagios@localhost
admin_pager=pagenagios@localhost



# DAEMON CORE DUMP OPTION
# This option determines whether or not Nagios is allowed to create
# a core dump when it runs as a daemon.  Note that it is generally
# considered bad form to allow this, but it may be useful for
# debugging purposes.  Enabling this option doesn't guarantee that
# a core file will be produced, but that's just life...
# Values: 1 - Allow core dumps
#         0 - Do not allow core dumps (default)

daemon_dumps_core=0



# LARGE INSTALLATION TWEAKS OPTION
# This option determines whether or not Nagios will take some shortcuts
# which can save on memory and CPU usage in large Nagios installations.
# Read the documentation for more information on the benefits/tradeoffs
# of enabling this option.
# Values: 1 - Enabled tweaks
#         0 - Disable tweaks (default)

use_large_installation_tweaks=0



# ENABLE ENVIRONMENT MACROS
# This option determines whether or not Nagios will make all standard
# macros available as environment variables when host/service checks
# and system commands (event handlers, notifications, etc.) are
# executed.
# Enabling this is a very bad idea for anything but very small setups,
# as it means plugins, notification scripts and eventhandlers may run
# out of environment space. It will also cause a significant increase
# in CPU- and memory usage and drastically reduce the number of checks
# you can run.
# Values: 1 - Enable environment variable macros
#         0 - Disable environment variable macros (default)

enable_environment_macros=0



# CHILD PROCESS MEMORY OPTION
# This option determines whether or not Nagios will free memory in
# child processes (processed used to execute system commands and host/
# service checks).  If you specify a value here, it will override
# program defaults.
# Value: 1 - Free memory in child processes
#        0 - Do not free memory in child processes

#free_child_process_memory=1



# CHILD PROCESS FORKING BEHAVIOR
# This option determines how Nagios will fork child processes
# (used to execute system commands and host/service checks).  Normally
# child processes are fork()ed twice, which provides a very high level
# of isolation from problems.  Fork()ing once is probably enough and will
# save a great deal on CPU usage (in large installs), so you might
# want to consider using this.  If you specify a value here, it will
# program defaults.
# Value: 1 - Child processes fork() twice
#        0 - Child processes fork() just once

#child_processes_fork_twice=1



# DEBUG LEVEL
# This option determines how much (if any) debugging information will
# be written to the debug file.  OR values together to log multiple
# types of information.
# Values: 
#          -1 = Everything
#          0 = Nothing
#	   1 = Functions
#          2 = Configuration
#          4 = Process information
#	   8 = Scheduled events
#          16 = Host/service checks
#          32 = Notifications
#          64 = Event broker
#          128 = External commands
#          256 = Commands
#          512 = Scheduled downtime
#          1024 = Comments
#          2048 = Macros

debug_level=0



# DEBUG VERBOSITY
# This option determines how verbose the debug log out will be.
# Values: 0 = Brief output
#         1 = More detailed
#         2 = Very detailed

debug_verbosity=1



# DEBUG FILE
# This option determines where Nagios should write debugging information.

debug_file=/usr/local/nagios/var/nagios.debug



# MAX DEBUG FILE SIZE
# This option determines the maximum size (in bytes) of the debug file.  If
# the file grows larger than this size, it will be renamed with a .old
# extension.  If a file already exists with a .old extension it will
# automatically be deleted.  This helps ensure your disk space usage doesn't
# get out of control when debugging Nagios.

max_debug_file_size=1000000



# Should we allow hostgroups to have no hosts, we default this to off since
# that was the old behavior

allow_empty_hostgroup_assignment=0



# Normally worker count is dynamically allocated based on 1.5 * number of cpu's
# with a minimum of 4 workers.  This value will override the defaults

#check_workers=3



# EXPERIMENTAL load controlling options
# To get current defaults based on your system issue a command to
# the query handler. Please note that this is an experimental feature
# and not meant for production use. Used incorrectly it can induce
# enormous latency.
# #core loadctl
#   jobs_max - The maximum amount of jobs to run at one time
#   jobs_min - The minimum amount of jobs to run at one time
#   jobs_limit - The maximum amount of jobs the current load lets us run
#   backoff_limit - The minimum backoff_change
#   backoff_change - # of jobs to remove from jobs_limit when backing off
#   rampup_limit - Minimum rampup_change
#   rampup_change - # of jobs to add to jobs_limit when ramping up
# NOTE: The backoff_limit and rampup_limit are NOT used by anything currently,
#       so if your system is under load nothing will actively modify the jobs
#       even if you have these options enabled, they are for external
#       connector information only.  However, if you change the jobs_max or
#       jobs_min manually here or through the query handler interface that
#       WILL affect your system
#loadctl_options=jobs_max=100;backoff_limit=10;rampup_change=5
resource.cfg

Code: Select all

###########################################################################
#
# RESOURCE.CFG - Sample Resource File for Nagios 4.1.0rc1
#
#
# You can define $USERx$ macros in this file, which can in turn be used
# in command definitions in your host config file(s).  $USERx$ macros are
# useful for storing sensitive information such as usernames, passwords, 
# etc.  They are also handy for specifying the path to plugins and 
# event handlers - if you decide to move the plugins or event handlers to
# a different directory in the future, you can just update one or two
# $USERx$ macros, instead of modifying a lot of command definitions.
#
# The CGIs will not attempt to read the contents of resource files, so
# you can set restrictive permissions (600 or 660) on them.
#
# Nagios supports up to 32 $USERx$ macros ($USER1$ through $USER32$)
#
# Resource files may also be used to store configuration directives for
# external data sources like MySQL...
#
###########################################################################

# Sets $USER1$ to be the path to the plugins
$USER1$=/usr/local/nagios/libexec

# Sets $USER2$ to be the path to event handlers
#$USER2$=/usr/local/nagios/libexec/eventhandlers

# Store some usernames and passwords (hidden from the CGIs)
#$USER3$=someuser
#$USER4$=somepassword

Thanks!

Re: CGI and Internal Server Errors

Posted: Mon Jun 15, 2015 4:12 pm
by ssax
Because you're running Ubuntu, I believe you need to run this command from the install directory:

Code: Select all

sudo /usr/bin/install -c -m 644 sample-config/httpd.conf /etc/apache2/sites-enabled/nagios.conf
/etc/init.d/apache2 restart

Re: CGI and Internal Server Errors

Posted: Mon Jun 15, 2015 4:24 pm
by scrusi

Code: Select all

/tmp/nagioscore-master$ sudo /usr/bin/install -c -m 644 sample-config/httpd.conf /etc/apache2/sites-enabled/nagios.conf
$ sudo /etc/init.d/apache2 restart
 * Restarting web server apache2                                                                                                                                                                                                             AH00548: NameVirtualHost has no effect and will be removed in the next release /etc/apache2/plesk.conf.d/server.conf:6
No change, unfortunately.

Re: CGI and Internal Server Errors

Posted: Mon Jun 15, 2015 4:41 pm
by jolson
I am under the impression that everything is working properly under the hood, but plesk is messing things up. Is there any way that you can verify the installation is alright without plesk before we go ahead and add it into the mix?

Re: CGI and Internal Server Errors

Posted: Tue Jun 16, 2015 3:40 am
by scrusi
I'm not sure I can create a plesk free environment on the same server. (Disabling plesk services does nothing and I've not yet been able to create a vhost that ignores plesk. Aside from running a different httpd, I'm not sure how I would go around plesk. I guess I could set up nagios on a different Ubuntu 14.04 machine, but that wouldn't really be a useful test.)

However!
I've found the following in the suexec log:

Code: Select all

[2015-06-16 10:10:22]: command status.cgi not in docroot (10000)
So I'd think that this is suexec being unhappy with the location of the script. I've found this guide http://typo3.cms-jack.ch/de/blog/linux/ ... er-debian/ (german) to install nagios within the docroot. Would that be the right way to go? Is there a more elegant solution?