NEMS – Nagios Enterprise Monitoring Server for Raspberry Pi 3

NEMS – Nagios Enterprise Monitoring Server for Raspberry Pi

NEMS is a modern pre-configured, customized and ready-to-deploy Nagios Core image designed to run on the Raspberry Pi 3 micro computer. At its core it is a lightweight Debian Stretch deployment optimized for performance, reliability and ease of use.

NEMS is free to download, deploy, and use. Its development however is supported by its community of users. Please consider contributing if you can.

Please Note: NEMS 1.2.x is my most ambitious NEMS release yet. Please consider throwing a little gift in my Tip Jar if you find NEMS saves you time or money. Thanks!

[NEMS Documentation]

Index

NEMS 1.1 Featured on Category5 Technology TV

What Is Nagios Core?

Nagios® Core™ is an Open Source system and network monitoring application. It watches hosts and services that you specify, alerting you when things go bad and when they get better.

Some of the many features of Nagios Core include:

  • Monitoring of network services (SMTP, POP3, HTTP, NNTP, PING, etc.)
  • Monitoring of host resources (processor load, disk usage, etc.)
  • Simple plugin design that allows users to easily develop their own service checks
  • Parallelized service checks
  • Ability to define network host hierarchy using “parent” hosts, allowing detection of and distinction between hosts that are down and those that are unreachable
  • Contact notifications when service or host problems occur and get resolved (via email, pager, or user-defined method)
  • Ability to define event handlers to be run during service or host events for proactive problem resolution
  • Automatic log file rotation
  • Support for implementing redundant monitoring hosts
  • Optional web interface for viewing current network status, notification and problem history, log file, etc.

Why NEMS?

Nagios doesn’t need a big fancy supercomputer to offer exceptional enterprise monitoring of network assets and resources, so our temptation is to re-purpose older servers to perform this reasonably lightweight task.

If you ask me, that’s not only overkill, but the attempt to save money by reusing older hardware will actually cost more due to higher electricity usage vs. a tiny Raspberry Pi 3 Microcomputer… which ironically may in fact have more modern system specifications than that old beast of a server you’ve been using.

It can be a wee bit daunting to setup a Raspberry Pi Nagios server from scratch, and there were no projects I found which were actively maintained at a level adequate for professional use. So I decided to start a new project–called NEMS: Nagios Enterprise Monitoring Server (for Raspberry Pi).

This project uses freely available applications such as Debian Linux, Nagios Core and a variety of other goodies, and I too release a fully ready-to-use image for you to use within yours or your customer’s network environments.

About NEMS

The goal with NEMS is to provide a free, full-featured, up to date drop in Nagios Enterprise Monitoring Server for Raspberry Pi 3. It has all the bells and whistles while being optimized for solid stability and fast performance.

The original NEMS release was based (with big thanks to Ryan Siegel) on NagiosPi, with many of the settings reflective of the NagiosPi Wheezy distro (which is now obsolete).

Here is what Ryan Siegel (the creator of NagiosPi) has to say about NEMS: “I’d love to upgrade NagiosPi, but i don’t have ability to make a GUI that can beat that of NEMS. I strongly feel that it has always been a necessary addition to NagiosPi and NEMS was able to deliver what is essentially an updated and improved version of NagiosPi. No reason not to start using NEMS for the time being. Nice work Robbie!” [source]

NEMS has since become a popular drop-in Nagios distro for Raspberry Pi, with a major release twice per year.

If you like NEMS, please donate: donate.category5.tv

The Out-Of-The-Box NEMS Experience:

System Requirements

  • Raspberry Pi 3 Micro Computer
  • 8GB+ Micro SD Card (Recommend 16GB+)
  • Network Connection (will obtain IP address via DHCP: create your reservation in the DHCP server for ease of access)
  • Internet Connection

Instructions

  • Purchase and assemble your Raspberry Pi 3.
  • Download the most current version of NEMS below.
  • Unzip and “Burn” the image to your Micro SD card.
  • Boot your NEMS server.
  • Login to NEMS console by either connecting a monitor and keyboard, or using ssh (Username: pi / Password: raspberry)
  • Type: sudo nems-init
  • After rebooting, reconnect and restore your backup.nems NEMS-Migrator file if you have one.
  • Edit /etc/nagios3/resource.cfg and add your SMTP information.
  • Login to NagVis and change the password (default is: admin/admin)
  • Reboot your Pi and enjoy NEMS when it comes online (see below for further details).

Buy The Needed Hardware

Raspberry Pi 3 Nagios ServerRaspberry Pi 3 are very affordable, and using our Micro SD image, you simply buy the device, “burn” the image to the Micro SD card, and boot it up.

Here’s our link to buy the device you’ll need, complete with the Micro SD card, a power adapter, a good solid case, and more: shop.category5.tv

Please buy it through that link, or let me know if you need a customized link to a different model. We get a small percentage of the sale, and it helps to make it possible to offer this as a free download.

Download NEMS 1.2.1

NEMS 1.2.1 Raspberry Pi Image

NEMS 1.2.1 Image File – 1.27 GB ZIP File (4.68 GB Uncompressed)

Released May 22, 2017. Fixes the problems with NEMS 1.2 release.

Unzip and “burn” to 8 GB+ Raspberry Pi 3 Micro SD Card (I recommend you use at least a 16 GB card so there’s plenty of room for logs, configs, data and so-on).

BitTorrent seed coming soon.

Upgrade to NEMS 1.2.1

  • Upgrade from NEMS 1.1+
    1. Connect to your existing NEMS dashboard from your computer and press Migrator->Backup. That will give you your backup.nems file.
    2. Deploy NEMS 1.2 on a new card (please use a new card so you can always revert back to your existing NEMS 1.1 if you have a problem).
    3. Boot your Pi into NEMS 1.2 and initialize it as normal (instructions are provided via your web browser when you connect)
    4. Once you get to the dashboard simply click Migrator->Restore to open the documentation which walks you through restoring your settings from your backup.nems file.
  • Upgrade from NEMS 1.0 or nagiospi
    See legacy upgrade documentation here: http://www.baldnerd.com/nems-migrator-legacy-upgrade/

NEMS 1.2.1 Changelog
NEMS 1.2 was released May 6, 2017. NEMS 1.2.1 was released May 22, 2017 to fix bugs with the migrator and improve the overall release following significant user feedback.

Here is a list of the changes I recorded during development.
– NEMS now requires you to run nems-init when you first deploy. This tool takes care of some of those “first boot” prerequisites like setting passwords and expanding your filesystem.
– Underlying OS upgraded to Raspbian Stretch.
– Kernel upgraded to 4.9.28.
– PHP upgraded to 7.0.19.
Reworking of nConf to make compatible with modern software (ie. PHP7.0, mySQLi).
– Maintenance and info scripts moved to /home/pi/nems-scripts.
– NEMS MOTD upon login now shows local IP address. Also improved how it determines some of the info (see info.sh in nems-scripts) and fixes a few bugs. Also set it up to rollover to wlan0 if no response on eth0, in case the user is on wifi.
– Temporary files and Monitorix image cache moved to RAM.
– Added RPi-Monitor as per Hesh’s comment. Reworked the Memory and CPU Frequency modules to correct the accuracy.
– Added nagios-api (JSON on Port 8090) as per Timothy Seibert’s request. [License]
– Added Webmin as per Hesh’s comment. Login as pi user with the password you created when initializing NEMS with the nems-init program.
– Added support for agentless Windows checks using WMI (big thanks to Ryan Siegel).
– Changed Apache log rotation to weekly (was previously daily).
– Upgraded nagvis to 1.9b16.
– Fixed sendemail paths in nConf to ease out-of-the-box email notifications (as they should just work now). Thanks so much to Jim for pointing this typo out!
– Enabled CPU governing (package cpufrequtils). On NEMS 1.0-1.1, NEMS was locked to 600MHz, but now it will automatically go up to 1200 MHz as needed.
– force resolver to generate new DNS resolv.conf at first boot (to ensure the detected DNS servers will be used rather than our development DNS servers which may not work for you).
– NEMS Migrator upgraded to allow direct migration from nagiospi to NEMS.
– Added Monitorix 3.9.0.
– Removed MySQL, replaced with MariaDB 10.1.22.
– Improve quality of Monitorix graphs used on NEMS Dashboard slideshow.
– Minor improvements to Monitorix page based on priority of service and image quality.
– Removed some old (obsolete) kernel modules, InnoDB logs and other bloat to reduce size of stock image.
– Added /var/www/nconf/temp to tmpfs. This way if someone breaks their nCONF (eg., pressing “Back” while generating config) they can just reboot to fix it 😀
nems-init and nems-migrator restore significantly reworked to correct initialization bugs from NEMS 1.2. Now, both initialization of a new NEMS deployment and an import from an old one should work without a hitch.
– nConf and NEMS-Migrator backups now require your password (as set with nems-init).
– NEMS-Migrator no longer replaces the MySQL database with backup. Instead, it now clears the database completely, reconciles your backup with the current set of available commands and services and then imports everything together into the fresh database and activates the hosts. This way, if you restore your NEMS 1.1 settings to NEMS 1.2.1, you don’t miss out on all the WMIC features (which your 1.1 backup would overwrite), for example.
– Documentation updated to reflect changes in commands and versioning.
– I built a quick but lovely interface for Monitorix to make it mobile responsive and a little more dynamic in its functionality.
– Distribution now available via BitTorrent (thanks to our partnership with The Category5 TV Network

Bug fixes:
– number of online users count on MOTD fixed.
– undefined constant in apache error log every 5 minutes leading to a bloated error log.
– added missing icons in check_mk.
– NEMS Migrator mail settings fixed when importing backup.nems from NEMS 1.0/nagiospi.
– Fixed MySQL Initialization Bug – was causing NEMS to lose configuration and no longer work.
– Wifi (wlan0) restored after it broken in 1.2 (due to Debian Stretch upgrade and incompatible firmwares for the Pi).
– Fixed nems-init user creation. In NEMS 1.2 it was not adding the new user to the “admin” group correctly in NEMS nCONF, so upon config generation, user would lose access to Nagios Core and other features requiring admin user.
– many miscellaneous bug fixes.

Configuring Your NEMS Server:
Browse to: http://NEMS.local/nconf (or http://IPADDRESS/nconf)
Make changes to the config as needed for your environment (eg., add a host, service, edit a setting)
I’ve added a few sample configurations in there (v1.1+) to help you get started.
Click: “Generate Nagios Config”
If there are no errors, you will have the option to Deploy the new Nagios Config.

Using Your NEMS Server:
Browse to: http://NEMS.local  (or http://IPADDRESS)
The navigation should be fairly straightforward. To add hosts or configure your environment, use the built in nConf feature. To access reports, choose one of the reporting options under Reporting. To access info specific to your Pi (eg., memory usage) you’ll find those under System.

Passwords:
When you initialize NEMS, you will provide a password for the NEMS web interfaces. This username/password will be what you use to access most NEMS features (eg., nCONF, Nagios Core, Check_MK) however, Nagvis still uses admin:admin. Please be sure to change that when you first login to Nagvis. To login to Webmin, use the username pi and the password you entered for the pi user during nems-init.

Known Issues:

  • PNP4Nagios is installed, but not configured. You may encounter errors, which will be addressed in a future release.
  • If you encounter an issue, please report it in the comments below so I can work on a fix (or please post your fix to help others and possibly to have it integrated into the next build).

TO DO:
This list details features which are planned for future releases of NEMS. NEMS is released on a 6 month schedule, with a major release every May and November. Thanks to the NEMS Migrator, upgrading is a cinch.
– Further improve the mobile responsive layout for tablets and smartphones (It’s really rudimentary at the moment due to the nature of Nagios’ interface… frames? C’mon now.)
– Upgrade Nagios to Nagios Core 4. (?) – Unlikely since most of the cool things about NEMS rely on Nagios Core 3.5.1 … at least for now.
– Further streamline the implementation of Check_MK. Deploy check-mk-server.
– Expand the documentation to include setting up SMTP and mail alerts, including a new video demonstration on Category5 Technology TV.
– Create an OVA of NEMS for deployment on existing virtual infrastructures (just for the challenge/fun of it).
– Build a graphical interface for nems-init.
– Build a graphical interface for NEMS-Migrator’s “Restore” feature.
– I’m open to suggestions! Please post your comments at http://baldnerd.com/nems

Things I Will Not Do:
This is a list of features I will not implement.
– Raspberry Pi Zero, 1 & 2 support. Buy a Raspberry Pi 3. The higher performance of a Pi 3 is a major asset for a project like NEMS, so I will not be focusing any of my efforts on supporting legacy hardware.
– GUI/Desktop. NEMS is a Linux server. If you require a GUI/Desktop Environment, you’re doing it wrong. I have built a very nice, easy to use web interface, and have worked hard to provide good documentation to ease the complication of configuration for novice users. NEMS itself should not even have a screen connected to it. Just power and Ethernet. Everything happens either through your browser, or for advanced users, an SSH connection.

Who Creates NEMS:
Robbie Ferguson is the host of Category5 Technology TV. He’s the kind of guy who when he figures stuff out, he likes to share it with others. That’s part of what makes his show so popular, but also what makes NEMS possible.

Support What We Do:
This project is a part of something much bigger than itself, and we’re all volunteers. Please see our Patreon page for information about our network.
– Please support us by simply purchasing your Raspberry Pi at https://cat5.tv/pi
– We have some support links on the NEMS menu, such as buying from Amazon using our partner link. Please use these every time you use those stores. A small percentage of your purchase will go toward our projects.
– Your donations are VERY MUCH appreciated – https://donate.category5.tv – Please consider how many hours (and hours) of work this project has saved you, and how much you’ll save on hardware and even electrical costs as you consider contributing
– Our network also has a Patreon page – Please consider becoming a patron – https://patreon.com/Category5

Leave a Reply

320 Comments on "NEMS – Nagios Enterprise Monitoring Server for Raspberry Pi 3"

Notify of
avatar
Sort by:   newest | oldest | most voted
Andrew P
Guest

The new NEMS looks fantastic. Clearly a lot of time and thought went into the greatly expanded feature set. I look forward to exploring and making use of all of the new tools.

Similar to Mike, when I restored my NEMS 1.1 config to 1.2.1 everything came up fine. Afterward, I went into NConf to do some cleanup where I attempted to remove the additional hosts that are included by default. I received a couple of errors:

1. Related to the host possibly not being properly linked to a host-preset;
2. NConf cannot read nonexistent file /var/www/html/nconf/temp/test/Default_collector.cfg. I noted that the ownership for /var/www/html/nconf/temp is root:root as well.

As a sanity check, I performed a fresh restore. Afterward, I had NConf generate Nagios configuration files without making any host changes first. The restore and file generation were done twice – once before and once after the prescribed modification to the restore.sh script listed below was applied. I receive the same error message each time.

Additionally, the shell script aborts on line 32 of info.sh, but that only affects the MOTD banner. That may be related to my Pi not being cabled into my network, but using wlan0. I understand and agree with the previously posted recommendation of using a cabled connection. Unfortunately, I do not have any available ports for an Ethernet connection at the moment. I will address that in the near future.

Andrew P
Guest

Thanks, Robbie for the quick response. Nice to know about the update script. That ran successfully. Still getting the error after a fresh import though. Here is the text. We can take this discussion offline if you’d like to dig deeper.

Generate config log:
[INFO] Starting generate_config script
[INFO] Generating global config files
[INFO] Generating config for Nagios-collector ‘Default Nagios’
[ERROR] Failed to get host-alive check for host ‘NEMS’. Make sure the host is linked with a host-preset. Aborting.

Running syntax check:

Default_collectorError generating config

Nagios Core 3.5.1
Copyright (c) 2009-2011 Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 08-30-2013
License: GPL

Website: http://www.nagios.org
Reading configuration data…
Error: Cannot open main configuration file ‘/var/www/html/nconf/temp/test/Default_collector.cfg’ for reading!
Error processing main config file!

***> The name of the main configuration file looks suspicious…

Make sure you are specifying the name of the MAIN configuration file on
the command line and not the name of another configuration file. The
main configuration file is typically ‘/usr/local/nagios/etc/nagios.cfg’

***> One or more problems was encountered while processing the config files…

Check your configuration file(s) to ensure that they contain valid
directives and data defintions. If you are upgrading from a previous
version of Nagios, you should be aware that some variables/definitions
may have been removed or modified in this version. Make sure to read
the HTML documentation regarding the config files, as well as the
‘Whats New’ section to find out what has changed.

Error
Deployment not possible due to errors in configuration.

Mike S
Guest

Great effort on getting 1.2.1 out!
First minor issue, did a NOOB install and deleted all the extra hosts from within NCONF. Error message PHP copy: FAILED recursive copy(/tmp/global/, /etc/nagios3/global/) after pre flight checks OK

ron
Guest

restore works from 1.1 to 1.2.1, but got issue on Nagios config
Got error on Generate Nagios config
Error: Cannot open main configuration file ‘/var/www/html/nconf/temp/test/Default_collector.cfg’ for reading!

Richard
Guest

Afternoon guys!

Iv just been looking through the support and noticed its very active on here so im going to try my luck. I ordered my Pi 3 B and installed NEMS with Win32 Disk Imager. When i put the SD card in the Pi it just loads for around 5 seconds and gives me a colorful test image on the screen and reboots. Iv tried reimaging the SD card and now im just about to try the redownload.

If that doesnt work where do i go next?

A.K.
Guest

Hello, I have a problem with setup. nems-init doesn’t import host-template (new installation, not importing old data)

Mike S
Guest

Hi Robbie, just a quick question… is there a simple way of importing a list of a number of SNMP devices to be monitored, all generic switch types and or other IEDs, or is it a case of one by one handraulic entry?

Mike S
Guest

Not sure what you can do about this one…… probably put to the bottom of the list Webmin reports “Your connection is not secure” as a browser exception… uses an invalid security certificate.

Probably a way around it, other than excepting the exception.

Mike S
Guest

Has the wlan0 interface been disabled some how within the app as the NEMS default image interfaces file contains two wlan IFs, though the pi wont respond to a sudo iwlist wlan0 scan
contents of default /etc/network/interfaces

auto lo
iface lo inet loopback

iface eth0 inet manual

allow-hotplug wlan0
iface wlan0 inet manual
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

allow-hotplug wlan1
iface wlan1 inet manual
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

looks like you have two adapters

my supplicant file

network={
ssid=”PL2″
psk=”********”
id_str=”home”
}

network={
ssid=”*********”
psk=”6y7yaa38″
id_str=”PL6″
}

Is wlan disabled somewhere else?

Mike S
Guest

Hi there, this relates to a NOOB install of 1.2, a couple of things.
1. Webmin pword set on nems-init to user preferences, but wont allow logon
2. Nagios network / process info and sch. queue and config button reveals ‘It appears though you do not have permission……. check authorisations in your CGI file.

All without running nconf and using defaults. Any suggestions welcome to fix, Linux not quite a newbie, but still learning!

Rick
Guest

Thanks for the new release.
Everything went well up to the migration from version 1.1

The following is the output from the restore run. I get a database error when I look at NCONF.

(I did send a little money your way… I do appreciate the turnkey implementation..)

Rick

pi@NEMS:~ $ sudo nems-restore /home/pi/backup.nems
Let me be VERY clear here…
This will WIPE OUT the configuration on this NEMS deployment.
The configuration will be replaced with the one stored in your NEMS backup.

Please do this on a fresh deployment of NEMS to prevent data loss.
I am not responsible for this script breaking everything you have done 🙂
Backup, backup, backup.

Are you sure you want to attempt restore? [y/N] y
Backup file is from NEMS 1.1. Proceeding.
Reconciling 9 files…
Consolidation complete.

[ Initializing NConf perl-API (library version 0.3, written by A. Gargiulo) ]
[ Copyright (c) 2006 – 2013 Sunrise Communications AG, Zurich, Switzerland ]

[INFO] Started executing /var/www/nconf/bin/add_items_from_nagios.pl
DBI connect(‘database=nconf;host=localhost’,’nconf’,…) failed: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2 “No such file or directory”) at /var/www/nconf/bin/lib/NConf/DB.pm line 81.

[ Initializing NConf perl-API (library version 0.3, written by A. Gargiulo) ]
[ Copyright (c) 2006 – 2013 Sunrise Communications AG, Zurich, Switzerland ]

[INFO] Started executing /var/www/nconf/bin/add_items_from_nagios.pl
DBI connect(‘database=nconf;host=localhost’,’nconf’,…) failed: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2 “No such file or directory”) at /var/www/nconf/bin/lib/NConf/DB.pm line 81.

[ Initializing NConf perl-API (library version 0.3, written by A. Gargiulo) ]
[ Copyright (c) 2006 – 2013 Sunrise Communications AG, Zurich, Switzerland ]

[INFO] Started executing /var/www/nconf/bin/add_items_from_nagios.pl
DBI connect(‘database=nconf;host=localhost’,’nconf’,…) failed: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2 “No such file or directory”) at /var/www/nconf/bin/lib/NConf/DB.pm line 81.

[ Initializing NConf perl-API (library version 0.3, written by A. Gargiulo) ]
[ Copyright (c) 2006 – 2013 Sunrise Communications AG, Zurich, Switzerland ]

[INFO] Started executing /var/www/nconf/bin/add_items_from_nagios.pl
DBI connect(‘database=nconf;host=localhost’,’nconf’,…) failed: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2 “No such file or directory”) at /var/www/nconf/bin/lib/NConf/DB.pm line 81.

[ Initializing NConf perl-API (library version 0.3, written by A. Gargiulo) ]
[ Copyright (c) 2006 – 2013 Sunrise Communications AG, Zurich, Switzerland ]

[INFO] Started executing /var/www/nconf/bin/add_items_from_nagios.pl
DBI connect(‘database=nconf;host=localhost’,’nconf’,…) failed: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2 “No such file or directory”) at /var/www/nconf/bin/lib/NConf/DB.pm line 81.

[ Initializing NConf perl-API (library version 0.3, written by A. Gargiulo) ]
[ Copyright (c) 2006 – 2013 Sunrise Communications AG, Zurich, Switzerland ]

[INFO] Started executing /var/www/nconf/bin/add_items_from_nagios.pl
DBI connect(‘database=nconf;host=localhost’,’nconf’,…) failed: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2 “No such file or directory”) at /var/www/nconf/bin/lib/NConf/DB.pm line 81.

[ Initializing NConf perl-API (library version 0.3, written by A. Gargiulo) ]
[ Copyright (c) 2006 – 2013 Sunrise Communications AG, Zurich, Switzerland ]

[INFO] Started executing /var/www/nconf/bin/add_items_from_nagios.pl
DBI connect(‘database=nconf;host=localhost’,’nconf’,…) failed: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2 “No such file or directory”) at /var/www/nconf/bin/lib/NConf/DB.pm line 81.

[ Initializing NConf perl-API (library version 0.3, written by A. Gargiulo) ]
[ Copyright (c) 2006 – 2013 Sunrise Communications AG, Zurich, Switzerland ]

[INFO] Started executing /var/www/nconf/bin/add_items_from_nagios.pl
DBI connect(‘database=nconf;host=localhost’,’nconf’,…) failed: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2 “No such file or directory”) at /var/www/nconf/bin/lib/NConf/DB.pm line 81.

[ Initializing NConf perl-API (library version 0.3, written by A. Gargiulo) ]
[ Copyright (c) 2006 – 2013 Sunrise Communications AG, Zurich, Switzerland ]

[INFO] Started executing /var/www/nconf/bin/add_items_from_nagios.pl
DBI connect(‘database=nconf;host=localhost’,’nconf’,…) failed: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2 “No such file or directory”) at /var/www/nconf/bin/lib/NConf/DB.pm line 81.

[ Initializing NConf perl-API (library version 0.3, written by A. Gargiulo) ]
[ Copyright (c) 2006 – 2013 Sunrise Communications AG, Zurich, Switzerland ]

[INFO] Started executing /var/www/nconf/bin/add_items_from_nagios.pl
DBI connect(‘database=nconf;host=localhost’,’nconf’,…) failed: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2 “No such file or directory”) at /var/www/nconf/bin/lib/NConf/DB.pm line 81.

[ Initializing NConf perl-API (library version 0.3, written by A. Gargiulo) ]
[ Copyright (c) 2006 – 2013 Sunrise Communications AG, Zurich, Switzerland ]

[INFO] Started executing /var/www/nconf/bin/add_items_from_nagios.pl
DBI connect(‘database=nconf;host=localhost’,’nconf’,…) failed: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2 “No such file or directory”) at /var/www/nconf/bin/lib/NConf/DB.pm line 81.

[ Initializing NConf perl-API (library version 0.3, written by A. Gargiulo) ]
[ Copyright (c) 2006 – 2013 Sunrise Communications AG, Zurich, Switzerland ]

[INFO] Started executing /var/www/nconf/bin/add_items_from_nagios.pl
DBI connect(‘database=nconf;host=localhost’,’nconf’,…) failed: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2 “No such file or directory”) at /var/www/nconf/bin/lib/NConf/DB.pm line 81.

[ Initializing NConf perl-API (library version 0.3, written by A. Gargiulo) ]
[ Copyright (c) 2006 – 2013 Sunrise Communications AG, Zurich, Switzerland ]

[INFO] Started executing /var/www/nconf/bin/add_items_from_nagios.pl
DBI connect(‘database=nconf;host=localhost’,’nconf’,…) failed: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2 “No such file or directory”) at /var/www/nconf/bin/lib/NConf/DB.pm line 81.

[ Initializing NConf perl-API (library version 0.3, written by A. Gargiulo) ]
[ Copyright (c) 2006 – 2013 Sunrise Communications AG, Zurich, Switzerland ]

[INFO] Started executing /var/www/nconf/bin/add_items_from_nagios.pl
DBI connect(‘database=nconf;host=localhost’,’nconf’,…) failed: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2 “No such file or directory”) at /var/www/nconf/bin/lib/NConf/DB.pm line 81.
Importing: $USER1$=/usr/lib/nagios/plugins
Importing: $USER5$=kd4pyr@fuse.net
Importing: $USER7$=smtp.fuse.net
Importing: $USER9$=kd4pyr@fuse.net
Importing: $USER10$=***************
Consolidation complete.

I hope everything worked okay for you.
Please let me know if you had any trouble.

PS – I saved a backup for you of the old config. /root/backup.nems
… just in case

etsi
Guest

Thanks for the new version. When I “Generate Nagios config” & deploy nothing appears at nagios core – nagvis –
check_mk, no hosts.

Armand
Guest

Is it me or am I missing how we can upgrade to 1.2?

Ian
Guest

Downloaded release 1.2, it took 6 attempts to get it, the file size changed each time eventually got the correct 1.2gb file size. There is something wrong there.

Loaded and started OK. Only issue so far the pi/raspberry password has vanished and can no longer connect with ssh. Web interface seems ok so far.

wpDiscuz