Nagios Core 4.1 to 4.3.4

[kwhogster]

Hi

Currently I am running Nagios Core 4.1.1 on Ubuntu 16.0.4

I wish to upgrade my Nagios to 4.3.4 the latest version.

Was wondering if there are any instructions on how to upgrade Nagios Core

All my NSCLient's are 4.3 and higher planning to upgrade them to 5.14

Thanks

Tom

[kyang]

Here's our documentation for upgrading Core.
https://assets.nagios.com/downloads/nag ... ading.html

Make sure to read the important notes in red. Since you are upgrading from 4.1 to 4.3.4

Also do note: We do not support the .5 series of NSClient.

[kwhogster]

kyang

Thanks

one question

Before I run this command should I stop Nagios service first?

rm /usr/local/nagios/share/{main,side,index}.html

I know you do not support nsclient they have their own forum for that.

[npolovenko]

@kwhogster, You may stop the Nagios process. But later on, there's a step to restart it anyway. You should be fine either way.

[kwhogster]

Thank you

This weekends project

Will post results

[lmiltchev]

Let us know how it went. We will keep this thread open for the time being.

[kwhogster]

To All,
The upgrade went smooth.
The instructions where great.

The items in the RED did not work.

After I restarted the Nagios service I was able to browse the site and all services are green yeah.

Code: Select all

Important: If you are upgrading from version 4.2.4 or before, to version 4.3.0 or after, there are changes that need to be made to the 'nagios.conf' apache configuration file. 
You can either update it manually, copying the new parts from 'sample-config/httpd.conf' or run 
cd /etc/httpd/conf.d
cp nagios.conf nagios.conf.bak
cd /<the nagios build directory>
make install-webconf
service httpd restart


Important: If you are upgrading from version 4.3.3 or before, to version 4.3.4 or after, there are changes that need to made to the initialization script, and to your main Nagios configuration file. 
You should be able to simply run make install-init to update your init file - depending on if you've made any customizations. 
For your configuration file, you'll need to update the lock_file directive to point to the new one in use by the initialization file. 
First, let's update our init file: 
make install-init


If you don't know where your initialization script lives, you can find out the value of your new lock file with the following command: 
INITFILE=$(grep ^INIT_DIR= Makefile | sed 's/.*=//' | sed 's/.*/&\/nagios/') && grep ^NagiosRunFile $INITFILE


If you do know where your init script lives, you can find the value of your lock file with the following command: 
grep ^NagiosRunFile INITFILE


Now that you have the value of the lock file, find the part of your nagios.cfg file that has the lock_file directive, and update it with your new value: 
lock_file=[NEW_LOCK_FILE_LOCATION]

The first command fails no such file or directory.
nagios@tgcs017:/$ cd /etc/httpd/conf.d
bash: cd: /etc/httpd/conf.d: No such file or directory

When I LS etc I find no httpd folder
nagios@tgcs017:/$ ls etc
acpi dbconfig-common hosts.allow localtime nsswitch.conf rc5.d subgid
adduser.conf dbus-1 hosts.deny logcheck nsswitch.conf.lwidentity.orig rc6.d subgid-
aliases debconf.conf hosts.lwidentity.orig login.defs opt rc.local subuid
aliases.db debian_version idmapd.conf logrotate.conf os-release rcS.d subuid-
alternatives default init logrotate.d overlayroot.conf request-key.conf sudoers
apache2 deluser.conf init.d logwatch pam.conf request-key.d sudoers.d
apm depmod.d initramfs-tools lsb-release pam.d resolvconf sysctl.conf
apparmor dhcp inputrc ltrace.conf passwd resolv.conf sysctl.d
apparmor.d dictionaries-common insserv lvm passwd- rmt systemd
apport dpkg insserv.conf machine-id pbis rpc terminfo
apt drirc insserv.conf.d magic perl rsyslog.conf timezone
at.deny emacs iproute2 magic.mime php rsyslog.d tmpfiles.d
at-spi2 environment iscsi mailcap phpmyadmin samba ucf.conf
bash.bashrc fonts issue mailcap.order pki sane.d udev
bash_completion fstab issue.net mailname pm screenrc ufw
bash_completion.d ftpusers kbd manpath.config polkit-1 securetty updatedb.conf
bindresvport.blacklist fuse.conf kernel mdadm popularity-contest.conf security update-manager
binfmt.d gai.conf kernel-img.conf mime.types postfix selinux update-motd.d
byobu groff krb5.conf mke2fs.conf ppp sensors3.conf update-notifier
ca-certificates group krb5.conf.lwidentity.orig modprobe.d profile sensors.d vim
ca-certificates.conf group- krb5.keytab modules profile.d services vmware-tools
ca-certificates.conf.dpkg-old grub.d ldap modules-load.d protocols sgml vsftpd.conf
calendar gshadow ld.so.cache mtab python shadow vtrgb
console-setup gshadow- ld.so.conf mysql python2.7 shadow- wgetrc
cron.d gss ld.so.conf.d nagios python3 shells X11
cron.daily gtk-2.0 legal nagios-plugins python3.5 skel xdg
cron.hourly gtk-3.0 libaudit.conf nanorc rc0.d s-nail.rc xml
cron.monthly hdparm.conf libnl-3 netconfig rc1.d snmp yum
crontab host.conf lighttpd network rc2.d sos.conf zsh_command_not_found
cron.weekly hostname locale.alias networks rc3.d ssh
crypttab hosts locale.gen newt rc4.d ssl
nagios@tgcs017:/$ ls


I went from 4.1 to 4.3.4 do I really need those commands?

Thoughts?

[npolovenko]

@kwhogster, You can search for conf.d file:

Code: Select all

 find / -name conf.d

I suspect that your file is in the /etc/apache2/ folder.

Code: Select all

I went from 4.1 to 4.3.4 do I really need those commands?

If everything works as expected I wouldn't worry about it.