Nagios on linux for sparc
wordpress meta
title: 'Nagios on Linux for SPARC'
date: '2016-04-12T05:39:00-05:00'
status: publish
permalink: /nagios-on-linux-for-sparc
author: admin
excerpt: ''
type: post
id: 939
thumbnail: ../uploads/2016/04/l.png
category:
- Linux
- Nagios
tag: []
post_format: []
title: 'Nagios on Linux for SPARC'
date: '2016-04-12T05:39:00-05:00'
status: publish
permalink: /nagios-on-linux-for-sparc
author: admin
excerpt: ''
type: post
id: 939
thumbnail: ../uploads/2016/04/l.png
category:
- Linux
- Nagios
tag: []
post_format: []
I recently experimented a little with Linux for SPARC(more here https://oss.oracle.com/projects/linux-sparc/) and found it to be surprisingly stable. One of the environments I support is a pure OVM for SPARC environment and no luxury of Linux. So I am running some open source tools like Nagios, HAproxy etc on Solaris. Nagios has worked ok but is painful to compile. There are also some bugs that cause high utilization.
I tried a Linux for SPARC instance and since they are pretty much like RedHat/Oracle/CentOS it means a fair bit of packages already exist. Nagios does not exist so I compiled it. Suffice to say installing dependencies from YUM and compiling was a breeze compared to Solaris.
You can pretty much follow this doc to the letter:
https://assets.nagios.com/downloads/nagioscore/docs/Installing_Nagios_Core_From_Source.pdf
Things to note.
1. By default the firewall does not allow inbound http.
2. If you have permission issues in the web frontend or something like Internal server error you can disable(quick test) and then configure selinux for nagios scripts.
# setenforce 0
# chcon -R -t httpd_sys_content_t /usr/local/nagios
3. Redo plugins with openssl for https checks. I wanted to do https checks.
# yum install openssl-devel
# pwd
/usr/src/nagios/nagios-plugins-2.1.1
# ./configure --with-openssl --with-nagios-user=nagios --with-nagios-group=nagios
[..]
--with-openssl: yes
# make
# make install
# /usr/local/nagios/libexec/check_http -H 10.2.10.33 -S -p 215
HTTP OK: HTTP/1.1 200 OK - 2113 bytes in 0.017 second response time |time=0.016925s;;;0.000000 size=2113B;;;0
I made a https command as follow.
command.cfg
# 'check_https' command definition
define command{
command_name check_https
command_line $USER1$/check_http -H $HOSTADDRESS$ -S -p $ARG1$
}
And referenced as follow.
storage.cfg
define service{
use remote-service ; Name of service template to use
host_name zfssa1
service_description HTTPS
check_command check_https!215
notifications_enabled 0
}