Re: SSI problem
Posted: Thu Jan 23, 2014 4:31 am
Finally i decided modified the extinfo.c directly and not use the ssi files
Thank you for your support
Thank you for your support
and that 'ssi' name in the directory might be misdirecting things here.
On a Redhat6.5/CentOS6.5 system, if you install nagios from the EPEL rpm's, your apache nagios config usually ends up at /etc/httpd/conf.d/nagios.conf
and will looks something like this:
Code: Select all
ScriptAlias /nagios/cgi-bin/ "/usr/lib64/nagios/cgi-bin/"
<Directory "/usr/lib64/nagios/cgi-bin/">
# SSLRequireSSL
Options ExecCGI
AllowOverride None
Order allow,deny
Allow from all
# Order deny,allow
# Deny from all
# Allow from 127.0.0.1
AuthName "Nagios Access"
AuthType Basic
AuthUserFile /etc/nagios/passwd
Require valid-user
</Directory>
Alias /nagios "/usr/share/nagios/html"
<Directory "/usr/share/nagios/html">
# SSLRequireSSL
Options None
AllowOverride None
Order allow,deny
Allow from all
# Order deny,allow
# Deny from all
# Allow from 127.0.0.1
AuthName "Nagios Access"
AuthType Basic
AuthUserFile /etc/nagios/passwd
Require valid-user
</Directory>
If you put a /usr/share/nagios/html/ssi/extinfo-footer.ssi file there that has the content
Code: Select all
<p>IT IS A TEST </p>
For this example, I have just now created a bare Centos6.5 system, installed the EPEL repository, and installed a clean nagios 3.5.1 from it and tested added an extinfo-footer.ssi with the above nagios.conf and it works (no options lines changed). I have also used a compiled nagios 4.0.2 install on a bare Centos6.5 system and verified it continues to work as documented for that version as well. Redhat6.5 is functionally equivalent to Centos6.5 in this context.
Until you can get a simple text string in that ssi file being included in your rendered output in the web interface, it's best not to try getting dynamic content to be included (I'll go over how to do dynamic content at the end of the post, don't skip to it).
Now, as for the second issue of placing
Code: Select all
<!--#echo var="DATE_LOCAL" -->
This is mixing two issues - On the given Ubuntu test, only a
Code: Select all
<p>IT IS A TEST </p>
The important bit from the documentation is likely this:
It is important to note that, unless they are executable, custom header and footer files are not pre-processed in any way before they are displayed. The contents of the header and footer include files are simply read and displayed in the CGI output. That means they can only contain information a web browser can understand (HTML, JavaScript, etc.).
That does not indicate that actual server side includes will work in these files, despite the directory name and the extensions. Only that files that are marked executable will be pre-processed. If you want execution of those files, you've got to write them in a way that it can render output ready made for a browser.
Adding that SSI code into the extinfo-footer.ssi *does* include that bit into the rendered cgi if the file is just readable, but if you look in the source of an extinfo.cgi page load, you'll just find it above the 'produced by nagios' comment that sits above the body close:
Source output of a rendered page when the extinfo-footer.ssi is 644:
Code: Select all
</TD>
</TR>
</TABLE>
</DIV>
<!--#echo var="DATE_LOCAL" -->
<!-- Produced by Nagios (http://www.nagios.org). Copyright (c) 1999-2007 Ethan Galstad. -->
</body>
</html>
If you set that ssi file to be executable, instead what you end up with is something similar to this in the apache errorlog when you try to load the page:
Code: Select all
[Thu Jan 23 03:06:01 2014] [error] [client 192.168.176.64] /usr/share/nagios/html/ssi/extinfo-footer.ssi: line 1: syntax error near unexpected token `newline', referer: http://192.168.176.43/nagios/cgi-bin//extinfo.cgi?type=2&host=localhost&service=Current+Load
[Thu Jan 23 03:06:01 2014] [error] [client 192.168.176.64] /usr/share/nagios/html/ssi/extinfo-footer.ssi: line 1: `<!--#echo var="DATE_LOCAL" -->', referer: http://192.168.176.43/nagios/cgi-bin//extinfo.cgi?type=2&host=localhost&service=Current+Load
The reason for this is the extinfo-footer.ssi file is getting executed on the server before the cgi renders its output - what you are seeing in the error_log is the output that you'd see from the shell if you ran the file by hand:
Code: Select all
[root@nagiostestC ssi]# ./extinfo-footer.ssi
./extinfo-footer.ssi: line 1: syntax error near unexpected token `newline'
./extinfo-footer.ssi: line 1: `<!--#echo var="DATE_LOCAL" -->'
So, instead of
Code: Select all
<!--#echo var="DATE_LOCAL" -->
Code: Select all
#!/usr/bin/perl
#
#
use strict;
my ($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time);
print eval($year+1900) . '-' . eval($mon+1) . '-' . $mday . ' ' . $hour . ':' . $min . ':' . $sec ."\n";
exit(0);
Code: Select all
chmod 755 /usr/share/nagios/html/ssi/extinfo-footer.ssi
And should be runnable from the command line:
Code: Select all
[root@nagiostestC ssi]# /usr/share/nagios/html/ssi/extinfo-footer.ssi
2014-1-23 3:9:59
That output could be img tags, or java script, or adverts (you evil person), or popunders for zombocom (you very evil person) - as long as it's all ready for the browser to process it, you should be good.
Now, the nagios page will dynamically generate a date in the extinfo footer, using whatever the output of the 'ssi' file gives, just like shows from the command line.
See:
- nagios-3.5-included-datefooter
Code: Select all
</TD>
</TR>
</TABLE>
</DIV>
2014-1-23 3:29:31
<!-- Produced by Nagios (http://www.nagios.org). Copyright (c) 1999-2007 Ethan Galstad. -->
</body>
For funsies, a ruby example extinfo-footer.ssi
Code: Select all
#!/usr/bin/ruby
#
#
time = Time.new
puts "Current time: " + time.inspect
Code: Select all
[root@nagiostestC ssi]# ./extinfo-footer.ssi
Current time: Thu Jan 23 03:55:52 -0600 2014
- nagios-3.5-included-datefooter-ruby
