iHome AutoVac Juno: A Comprehensive Review for 2024

 Introduction

Keeping your floors clean can be a chore, especially in busy households. Robot vacuums offer a convenient solution, promising hands-free cleaning. But with numerous options available, choosing the right one can be overwhelming. This comprehensive review explores the iHome AutoVac Juno, a robot vacuum gaining traction for its sleek design and budget-friendly price tag.

We'll delve into the iHome AutoVac Juno's key features, analyze its cleaning performance on various surfaces, and explore user reviews to understand its strengths and weaknesses. This information empowers you to decide if the iHome AutoVac Juno is the perfect cleaning companion for your home.

Features of the iHome AutoVac Juno

• Mapping Technology: The Juno utilizes mapping technology to navigate your home efficiently, ensuring it cleans all areas in a methodical pattern.

• Strong Suction Power: Equipped with 2000Pa suction power, the Juno tackles dirt, dust, and pet hair effectively from carpets and hard floors.

• App and Remote Control: Control the Juno through a user-friendly smartphone app or the included remote for scheduling cleaning sessions, initiating spot cleaning, and directing the robot to specific areas.

• 120-Minute Runtime: The Juno boasts a 120-minute runtime on a single charge, allowing it to clean larger homes efficiently.

• Slim Design: At a low profile, the Juno seamlessly glides under furniture, reaching hidden dust bunnies and pet hair lurking beneath couches and beds.

• Automatic Docking and Charging: The Juno automatically returns to its charging dock when the battery runs low, ensuring it's always ready for the next cleaning session.

• Multiple Cleaning Modes: Choose from various cleaning modes like auto clean, edge clean, and spot clean to customize your cleaning experience.

Performance Analysis of the iHome AutoVac Juno

Cleaning Capabilities:

• Carpets: User reviews generally praise the Juno's ability to pick up dust, debris, and pet hair from carpets. The 2000Pa suction power proves sufficient for most low- to medium-pile carpets.

• Hard Floors: The Juno performs well on hard floors like tile, laminate, and hardwood. Its sleek design allows it to navigate around obstacles and edges effectively.

• Pet Hair: Pet owners find the Juno effective at tackling pet hair, particularly on hard floors. However, some users with deep-pile carpets might find it struggles with deeply embedded pet hair.

Navigation:

• Mapping Technology: While not the most advanced mapping system, user reviews suggest the Juno's mapping is adequate for most homes. It learns the layout over time, ensuring efficient cleaning patterns.

• Obstacle Avoidance: The Juno features basic obstacle avoidance sensors, allowing it to navigate around furniture and avoid bumping into walls. However, it might struggle with particularly cluttered environments.

Usability:

• App Control: The smartphone app receives positive feedback for its user-friendly interface. Users can easily schedule cleaning sessions, monitor cleaning progress, and control the robot remotely.

• Remote Control: The included remote offers basic control options for those who prefer a non-app approach.

User Reviews and Ratings

Customer reviews on various retail platforms paint a generally positive picture of the iHome AutoVac Juno. Users appreciate its:

• Affordability: Compared to high-end robot vacuums, the Juno offers excellent value for its features and performance.

• Cleaning Performance: Many users are satisfied with its ability to handle dust, debris, and pet hair on various floor surfaces.

• Ease of Use: The app and remote control are praised for their user-friendliness.

Here are some recurring points to consider from user reviews:

• Limited Mapping Features: Compared to high-end models, the Juno's mapping technology might be considered basic. It might not be ideal for very large or complex floor plans.

• Obstacle Avoidance: Some users report the Juno occasionally getting stuck on obstacles, particularly in cluttered environments.

• Deep Carpet Performance: While effective on most carpets, the Juno might struggle with deeply embedded pet hair in high-pile carpets.

Conclusion: Is the iHome AutoVac Juno Right for You?

The iHome AutoVac Juno presents a compelling option for budget-conscious individuals seeking a robot vacuum for basic cleaning needs.  Here's a quick breakdown to help you decide:

Ideal for:

• Small to Medium Homes: The Juno's runtime and mapping capabilities make it suitable for navigating most homes efficiently.

• Hardwood and Tile Floors: The Juno excels on hard flooring thanks to its strong suction and maneuverability.

• Pet Owners (with limitations): The Juno tackles pet hair well on most surfaces, but users with deep-pile carpets might need a more powerful model for heavily embedded pet hair.

May not be ideal for:

• Large or Complex Homes: The Juno's mapping system might struggle with very large or intricate floor plans.

• High-Pile Carpets: While effective on most carpets, deep cleaning might be necessary for heavily soiled high-pile carpets.

• Highly Cluttered Environments: The Juno's basic obstacle avoidance might lead to getting stuck in rooms with a lot of clutter.

FAQs about the iHome AutoVac Juno

Q: How does the iHome AutoVac Juno navigate my home?

A: The Juno utilizes mapping technology to learn the layout of your home over time. It cleans in a methodical pattern to ensure all areas are covered.

Q: Can I schedule cleaning sessions with the iHome AutoVac Juno?

A: Yes! The user-friendly app allows you to schedule cleaning sessions for specific times and days.

Q: Does the iHome AutoVac Juno work on carpet and hard floors?

A: Yes, the Juno transitions well between carpets and hard floors with its adjustable cleaning settings.

Q: How easy is it to empty the dustbin of the iHome AutoVac Juno?

A: The dustbin is easily accessible and detachable for simple emptying.

Q: Where can I buy the iHome AutoVac Juno?

A: The iHome AutoVac Juno is available from various online retailers and major home appliance stores.

Overall, the iHome AutoVac Juno offers a budget-friendly option for maintaining clean floors, particularly for hard floor surfaces and low- to medium-pile carpets. Users appreciate its ease of use, strong suction power, and convenient app control. However, those with large or complex homes, deep-pile carpets, or highly cluttered environments might need to consider a more advanced robot vacuum.

nagios.lock Changes In 4.3.3 Onwards

 

Problem Description

This KB article is about the nagios.lock file changes that were introduced in Nagios Core 4.3.3. These changes require an update to your nagios.cfg file, otherwise you will most likely experience the following issues.

When you start or restart the nagios service you may see this message:

Running configuration check... Stopping nagios: No lock file found in /var/run/nagios
Starting nagios: Running configuration check... done.

If you check the status of the service:

service nagios status

It will report it is not running:

nagios is not running

However when you check the processes:

ps aux | grep nagios.cfg

You can see that it is running:

nagios    1735  0.0  0.0   7788  1592 ?        Ss   13:39   0:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg
nagios    1767  0.0  0.0   7272   628 ?        S    13:39   0:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg

Explanation

Before Nagios Core 4.3.3 the nagios.lock file location was defined in nagios.cfg as follows:

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

This was identified as a vulnerability described as follows:

CVE-2017-12847

Nagios Core before 4.3.3 creates a nagios.lock PID file after dropping privileges to a non-root account, which might allow local users to kill arbitrary processes by leveraging access to this non-root account for nagios.lock modification before a root script executes a "kill `cat /pathname/nagios.lock`" command.

Changes were introduced in Nagios Core 4.3.3 to remove this vulnerability, the lock file should now be located in /var/run/nagios.lock and hence the nagios.cfg file needs updating to:

lock_file=/var/run/nagios.lock

The Solution section explains how to make this change.

Solution

As per the Explanation section the fix is to update the nagios.cfg file to point to /var/run/nagios.lock. The following command will make the required change for you.

Then you will need to install the latest service from the source code (if not already done so).

After making the change you will also need to kill the existing nagios processes and start the nagios service.

Please follow the steps that are specific to your Operating System (OS).

• Red Hat Enterprise Linux (RHEL)

• CentOS

• Oracle Linux

• Ubuntu

• SUSE SLES | openSUSE Leap

• Debian

• Raspbian

• Fedora

• Arch Linux

• Gentoo

• FreeBSD

• Solaris

• Apple OS X

CentOS | RHEL | Oracle Linux

Update nagios.cfg

This step updates the nagios.cfg file to point to /var/run/nagios.lock:

sed -i 's/^lock_file=.*/lock_file=\/var\/run\/nagios.lock/g' /usr/local/nagios/etc/nagios.cfg
		

Install Service / Daemon

To  install the updated service / daemon file you will need to follow the Downloading the Source and Compile steps in the following documentation first:

Documentation - Installing Nagios Core From Source

Once you have performed those steps please execute the following commands:

===== CentOS 5.x / 6.x | RHEL 5.x / 6.x | Oracle Linux 5.x / 6.x =====

make install-init
		

===== CentOS 7.x | RHEL 7.x | Oracle Linux 7.x =====

make install-init
systemctl daemon-reload
		

Kill Existing Nagios Processes

To kill the existing nagios service you will need to know the PID of the root process. Execute the following command:

ps aux | egrep "PID|nagios.cfg"
		

The output will be something like:

USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
nagios    1735  0.0  0.0   7788  1596 ?        Ss   13:39   0:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg
nagios    1767  0.0  0.0   7272   628 ?        S    13:39   0:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg

Now kill the two Nagios processes, usually the first one (1735) will automatically kill the child process (1767):

kill 1735
		

Then run the ps aux command again to confirm the processes are no longer running.

Start Service / Daemon

This command starts Nagios Core.

===== CentOS 5.x / 6.x | RHEL 5.x / 6.x | Oracle Linux 5.x / 6.x =====

service nagios start
		

===== CentOS 7.x | RHEL 7.x | Oracle Linux 7.x =====

A stop is required first, even though the processes are not running. This appears to be a systemd feature.

systemctl stop nagios.service
systemctl start nagios.service
		

Confirm Nagios Is Running

You can confirm that the nagios service is now running with the following command:

===== CentOS 5.x / 6.x | RHEL 5.x / 6.x | Oracle Linux 5.x / 6.x =====

service nagios status
		

===== CentOS 7.x | RHEL 7.x | Oracle Linux 7.x =====

systemctl status nagios.service
		

Ubuntu

Update nagios.cfg

This step updates the nagios.cfg file to point to /var/run/nagios.lock:

sudo sh -c "sed -i 's/^lock_file=.*/lock_file=\/var\/run\/nagios.lock/g' /usr/local/nagios/etc/nagios.cfg"
		

Install Service / Daemon

To  install the updated service / daemon file you will need to follow the Downloading the Source and Compile steps in the following documentation first:

Documentation - Installing Nagios Core From Source

Once you have performed those steps please execute the following commands:

===== Ubuntu 14.x =====

sudo make install-init
		

===== Ubuntu 15.x / 16.x / 17.x =====

sudo make install-init
sudo systemctl daemon-reload
		

Kill Existing Nagios Processes

To kill the existing nagios service you will need to know the PID of the root process. Execute the following command:

ps aux | egrep "PID|nagios.cfg"
		

The output will be something like:

USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
nagios    1735  0.0  0.0   7788  1596 ?        Ss   13:39   0:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg
nagios    1767  0.0  0.0   7272   628 ?        S    13:39   0:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg

Now kill the two Nagios processes, usually the first one (1735) will automatically kill the child process (1767):

sudo kill 1735
		

Then run the ps aux command again to confirm the processes are no longer running.

Start Service / Daemon

This command starts Nagios Core.

===== Ubuntu 14.x =====

sudo service nagios start
		

===== Ubuntu 15.x / 16.x / 17.x =====

A stop is required first, even though the processes are not running. This appears to be a systemd feature.

sudo systemctl stop nagios.service
sudo systemctl start nagios.service
		

 

Confirm Nagios Is Running

You can confirm that the nagios service is now running with the following command:

===== Ubuntu 14.x =====

sudo service nagios status
		

===== Ubuntu 15.x / 16.x / 17.x =====

sudo systemctl status nagios.service
		

SUSE SLES | openSUSE Leap

Update nagios.cfg

This step updates the nagios.cfg file to point to /var/run/nagios.lock:

sudo sh -c "sed -i 's/^lock_file=.*/lock_file=\/var\/run\/nagios.lock/g' /usr/local/nagios/etc/nagios.cfg"
		

Install Service / Daemon

To  install the updated service / daemon file you will need to follow the Downloading the Source and Compile steps in the following documentation first:

Documentation - Installing Nagios Core From Source

Once you have performed those steps please execute the following commands:

===== SUSE SLES 11.x =====

sudo make install-init
		

===== SUSE SLES 12.x | openSUSE Leap 42.x =====

sudo make install-init
sudo systemctl daemon-reload
		

Kill Existing Nagios Processes

To kill the existing nagios service you will need to know the PID of the root process. Execute the following command:

ps aux | egrep "PID|nagios.cfg"
		

The output will be something like:

USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
nagios    1735  0.0  0.0   7788  1596 ?        Ss   13:39   0:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg
nagios    1767  0.0  0.0   7272   628 ?        S    13:39   0:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg

Now kill the two Nagios processes, usually the first one (1735) will automatically kill the child process (1767):

sudo kill 1735
		

Then run the ps aux command again to confirm the processes are no longer running.

Start Service / Daemon

This command starts Nagios Core.

===== SUSE SLES 11.x =====

sudo /sbin/service nagios start
		

===== SUSE SLES 12.x | openSUSE Leap 42.x =====

A stop is required first, even though the processes are not running. This appears to be a systemd feature.

sudo systemctl stop nagios.service
sudo systemctl start nagios.service
		

 

Confirm Nagios Is Running

You can confirm that the nagios service is now running with the following command:

===== SUSE SLES 11.x =====

sudo /sbin/service nagios status
		

===== SUSE SLES 12.x | openSUSE Leap 42.x =====

sudo systemctl status nagios.service
		

Debian | Raspbian

All steps on Debian require to run as root. To become root simply run:

Debian:

su

Raspbian:

sudo -i

All commands from this point onwards will be as root.

Update nagios.cfg

This step updates the nagios.cfg file to point to /var/run/nagios.lock:

sed -i 's/^lock_file=.*/lock_file=\/var\/run\/nagios.lock/g' /usr/local/nagios/etc/nagios.cfg
		

Install Service / Daemon

To  install the updated service / daemon file you will need to follow the Downloading the Source and Compile steps in the following documentation first:

Documentation - Installing Nagios Core From Source

Once you have performed those steps please execute the following commands:

===== 7.x =====

make install-init
		

===== 8.x / 9.x =====

make install-init
systemctl daemon-reload
		

Kill Existing Nagios Processes

To kill the existing nagios service you will need to know the PID of the root process. Execute the following command:

ps aux | egrep "PID|nagios.cfg"
		

The output will be something like:

USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
nagios    1735  0.0  0.0   7788  1596 ?        Ss   13:39   0:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg
nagios    1767  0.0  0.0   7272   628 ?        S    13:39   0:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg

Now kill the two Nagios processes, usually the first one (1735) will automatically kill the child process (1767):

kill 1735
		

Then run the ps aux command again to confirm the processes are no longer running.

Start Service / Daemon

This command starts Nagios Core.

===== 7.x =====

service nagios start
		

===== 8.x / 9.x =====

A stop is required first, even though the processes are not running. This appears to be a systemd feature.

systemctl stop nagios.service
systemctl start nagios.service
		

Confirm Nagios Is Running

You can confirm that the nagios service is now running with the following command:

===== 7.x =====

service nagios status
		

===== 8.x / 9.x =====

systemctl status nagios.service
		

Fedora

Update nagios.cfg

This step updates the nagios.cfg file to point to /var/run/nagios.lock:

sed -i 's/^lock_file=.*/lock_file=\/var\/run\/nagios.lock/g' /usr/local/nagios/etc/nagios.cfg
		

Install Service / Daemon

To  install the updated service / daemon file you will need to follow the Downloading the Source and Compile steps in the following documentation first:

Documentation - Installing Nagios Core From Source

Once you have performed those steps please execute the following commands:

make install-init
systemctl daemon-reload
		

Kill Existing Nagios Processes

To kill the existing nagios service you will need to know the PID of the root process. Execute the following command:

ps aux | egrep "PID|nagios.cfg"
		

The output will be something like:

USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
nagios    1735  0.0  0.0   7788  1596 ?        Ss   13:39   0:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg
nagios    1767  0.0  0.0   7272   628 ?        S    13:39   0:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg

Now kill the two Nagios processes, usually the first one (1735) will automatically kill the child process (1767):

kill 1735
		

Then run the ps aux command again to confirm the processes are no longer running.

Start Service / Daemon

A stop is required first, even though the processes are not running. This appears to be a systemd feature.

systemctl stop nagios.service
systemctl start nagios.service
		

Confirm Nagios Is Running

You can confirm that the nagios service is now running with the following command:

systemctl status nagios.service
		

Arch Linux

Update nagios.cfg

This step updates the nagios.cfg file to point to /var/run/nagios.lock:

sed -i 's/^lock_file=.*/lock_file=\/var\/run\/nagios.lock/g' /usr/local/nagios/etc/nagios.cfg
		

Install Service / Daemon

To  install the updated service / daemon file you will need to follow the Downloading the Source and Compile steps in the following documentation first:

Documentation - Installing Nagios Core From Source

Once you have performed those steps please execute the following commands:

make install-init
systemctl daemon-reload
		

Kill Existing Nagios Processes

To kill the existing nagios service you will need to know the PID of the root process. Execute the following command:

ps aux | egrep "PID|nagios.cfg"
		

The output will be something like:

USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
nagios    1735  0.0  0.0   7788  1596 ?        Ss   13:39   0:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg
nagios    1767  0.0  0.0   7272   628 ?        S    13:39   0:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg

Now kill the two Nagios processes, usually the first one (1735) will automatically kill the child process (1767):

kill 1735
		

Then run the ps aux command again to confirm the processes are no longer running.

Start Service / Daemon

This command starts Nagios Core. A stop is required first, even though the processes are not running. This appears to be a systemd feature.

systemctl stop nagios.service
systemctl start nagios.service
		

Confirm Nagios Is Running

You can confirm that the nagios service is now running with the following command:

systemctl status nagios.service
		

Gentoo

Update nagios.cfg

This step updates the nagios.cfg file to point to /var/run/nagios.lock:

sed -i 's/^lock_file=.*/lock_file=\/var\/run\/nagios.lock/g' /usr/local/nagios/etc/nagios.cfg
		

Install Service / Daemon

To  install the updated service / daemon file you will need to follow the Downloading the Source and Compile steps in the following documentation first:

Documentation - Installing Nagios Core From Source

Once you have performed those steps please execute the following commands:

===== openrc =====

make install-init
		

===== systemd =====

make install-init
systemctl daemon-reload
		

Kill Existing Nagios Processes

To kill the existing nagios service you will need to know the PID of the root process. Execute the following command:

ps aux | egrep "PID|nagios.cfg"
		

The output will be something like:

USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
nagios    1735  0.0  0.0   7788  1596 ?        Ss   13:39   0:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg
nagios    1767  0.0  0.0   7272   628 ?        S    13:39   0:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg

Now kill the two Nagios processes, usually the first one (1735) will automatically kill the child process (1767):

kill 1735
		

Then run the ps aux command again to confirm the processes are no longer running.

Start Service / Daemon

This command starts Nagios Core.

===== openrc =====

rc-service nagios start
		

===== systemd =====

A stop is required first, even though the processes are not running. This appears to be a systemd feature.

systemctl stop nagios.service
systemctl start nagios.service
		

Confirm Nagios Is Running

You can confirm that the nagios service is now running with the following command:

===== openrc =====

rc-service nagios status
		

===== systemd =====

systemctl status nagios.service
		

FreeBSD

Update nagios.cfg

This step updates the nagios.cfg file to point to /var/run/nagios.lock:

sed -i '' 's/^lock_file=.*/lock_file=\/var\/run\/nagios.lock/g' /usr/local/nagios/etc/nagios.cfg
		

Install Service / Daemon

To  install the updated service / daemon file you will need to follow the Downloading the Source and Compile steps in the following documentation first:

Documentation - Installing Nagios Core From Source

Once you have performed those steps please execute the following commands:

gmake install-init

Kill Existing Nagios Processes

To kill the existing nagios service you will need to know the PID of the root process. Execute the following command:

ps auxww | egrep "PID|nagios.cfg"
		

The output will be something like:

USER    PID  %CPU %MEM    VSZ   RSS TT  STAT STARTED    TIME COMMAND
nagios  571   0.0  0.3  19408  3344  -  Ss    2:12PM 0:00.06 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg
nagios  646   0.0  0.3  19408  3356  -  S     2:12PM 0:00.01 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg

Now kill the two Nagios processes, usually the first one (1735) will automatically kill the child process (1767):

kill 1735
		

Then run the ps auxww command again to confirm the processes are no longer running.

Start Service / Daemon

This command starts Nagios Core.

service nagios start

Confirm Nagios Is Running

You can confirm that the nagios service is now running with the following command:

service nagios status
		

Solaris

Update nagios.cfg

This step updates the nagios.cfg file to point to /var/run/nagios.lock:

perl -p -i -e 's/^lock_file=.*/lock_file=\/var\/run\/nagios.lock/g' /usr/local/nagios/etc/nagios.cfg
		

Install Service / Daemon

To  install the updated service / daemon file you will need to follow the Downloading the Source and Compile steps in the following documentation first:

Documentation - Installing Nagios Core From Source

Once you have performed those steps please execute the following commands:

gmake install-init

Kill Existing Nagios Processes

To kill the existing nagios service you will need to know the PID of the root process. Execute the following command:

ps auxww | egrep "PID|nagios.cfg"
		

The output will be something like:

USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
nagios    1735  0.0  0.0   7788  1596 ?        Ss   13:39   0:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg
nagios    1767  0.0  0.0   7272   628 ?        S    13:39   0:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg

Now kill the two Nagios processes, usually the first one (1735) will automatically kill the child process (1767):

kill 1735
		

Then run the ps aux command again to confirm the processes are no longer running.

Clear Service Maintenance Status

This is required, it resumes the service back into a running state.

svcadm clear nagios

 

Confirm Nagios Is Running

You can confirm that the nagios service is now running with the following command:

svcs -xv nagios
		

The following KB article has important information on Solaris and services:

How To Clear Solaris Service Maintenance Status

Apple OS X

Update nagios.cfg

This step updates the nagios.cfg file to point to /var/run/nagios.lock:

sudo sed -i '' 's/^lock_file=.*/lock_file=\/var\/run\/nagios.lock/g' /usr/local/nagios/etc/nagios.cfg
		

Install Service / Daemon

To  install the updated service / daemon file you will need to follow the Downloading the Source and Compile steps in the following documentation first:

Documentation - Installing Nagios Core From Source

Once you have performed those steps please execute the following commands:

sudo make install-init

Kill Existing Nagios Processes

To kill the existing nagios service you will need to know the PID of the root process. Execute the following command:

ps aux | egrep "PID|nagios.cfg"
		

The output will be something like:

USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
nagios    1735  0.0  0.0   7788  1596 ?        Ss   13:39   0:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg
nagios    1767  0.0  0.0   7272   628 ?        S    13:39   0:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg

Now kill the two Nagios processes, usually the first one (1735) will automatically kill the child process (1767):

sudo kill 1735
		

Then run the ps aux command again to confirm the processes are no longer running.

Start Service / Daemon

This command starts Nagios Core.

sudo /etc/rc.d/init.d/nagios start

Confirm Nagios Is Running

You can confirm that the nagios service is now running with the following command:

sudo /etc/rc.d/init.d/nagios status

SOURCE