Easy Steps To Install Monit Manager on Debian 11 – OrcaCore

This guide will walk you through the process of how to Install Monit Manager on Debian 11. Monit is a powerful and lightweight open-source utility designed for monitoring and managing processes, programs, files, directories, and filesystems on a Unix system. It automatically performs predefined actions when an error or warning condition is detected, ensuring your critical services remain online and healthy. Monit can monitor various aspects of your system, including file size, checksum, permissions, and more. It also boasts a simple web interface for easy configuration and monitoring. Follow these steps from Orcacore to Install Monit Manager on Debian 11 and gain better control over your server’s health.

Before you begin to Install Monit Manager on Debian 11, ensure you’re logged into your Debian 11 server as a non-root user with sudo privileges. It’s also recommended to have a basic firewall set up. If you haven’t already done this, refer to our guide on Initial Server Setup with Debian 11 for detailed instructions.

1. Install Monit on Debian 11

Monit packages are readily available in the default Debian 11 repository. Begin by updating your local package index to ensure you have the latest package information. Execute the following commands:

# sudo apt update
# sudo apt upgrade -y

These commands will refresh the package list and upgrade any existing packages to their newest versions. Now, you can proceed to Install Monit Manager on Debian 11 using the apt package manager:

sudo apt install monit -y

This command will download and install Monit along with all necessary dependencies. The -y flag automatically confirms the installation, saving you from having to manually type "yes."

2. Manage Monit Manager Service

After the installation, the Monit service should automatically start. To verify its status, use the following command:

sudo systemctl status monit --no-pager -l

This command displays the status of the Monit service, including whether it’s active (running), the process ID, and recent logs. The --no-pager option prevents the output from being displayed in a pager, and -l shows the full log lines.

Example output:

● monit.service - LSB: service and resource monitoring daemon
     Loaded: loaded (/etc/init.d/monit; generated)
     Active: active (running) since Mon 2023-03-20 08:09:59 EDT; 13s ago
       Docs: man:systemd-sysv-generator(8)
    Process: 24901 ExecStart=/etc/init.d/monit start (code=exited, status=0/SUCCESS)
      Tasks: 1 (limit: 4679)
     Memory: 1.6M
        CPU: 25ms
     CGroup: /system.slice/monit.service
             └─24911 /usr/bin/monit -c /etc/monit/monitrc
...

If the service isn’t running, start it with:

sudo systemctl start monit

You can also check the installed Monit version:

sudo monit --version

Example output:

This is Monit version 5.27.2
Built with ssl, with ipv6, with compression, with pam and with large files
Copyright (C) 2001-2020 Tildeslash Ltd. All Rights Reserved.

3. Configure Monit Service Manager on Debian 11

The primary configuration file for Monit is located at /etc/monit/monitrc. It’s generally recommended to avoid directly modifying this file. Instead, create separate configuration files for specific services you want to monitor.

Enable Monit httpd port

By default, the Monit web interface, accessible on port 2812, is disabled. To enable it, open the main configuration file using a text editor (like vi):

sudo vi /etc/monit/monitrc

Locate the section that begins with set httpd port 2812. Uncomment the relevant lines by removing the # symbol. Also, to access the web interface remotely, change use address localhost to use address 0.0.0.0. You can also change the default username and password (admin:monit).

set httpd port 2812 and
use address 0.0.0.0  # only accept connection from localhost (drop if you use M/M)
allow 0.0.0.0/0      # allow localhost to connect to the server and
allow admin:monit      # require user 'admin' with password 'monit'

Save and close the file. To verify the configuration for errors, use:

sudo monit -t

Output:

Control file syntax OK

4. Enable Monit Service Manager

To ensure Monit starts automatically on system boot, enable the service using:

sudo /lib/systemd/systemd-sysv-install enable monit

Apply the changes by restarting the Monit service:

sudo systemctl restart monit

Confirm that everything is working correctly with:

sudo monit status

(See the image in the original article for example output).

5. Configure Firewall for Monit

To allow access to the Monit web interface, you need to open port 2812 in your firewall. If you’re using UFW, execute the following commands:

sudo ufw allow 2812
sudo ufw reload

6. Access Monit Service Manager Web Interface

You can now access the Monit web interface by navigating to your server’s IP address followed by port 2812 in your web browser:

http://<your-server-ip-address>:2812

Enter the username and password you configured in the monitrc file (default: admin/monit).

(See the images in the original article for example screenshots).

7. Add Services In Monit on Debian 11

Monit uses configuration files to define the services it should monitor. Pre-configured files for common services are available in /etc/monit/conf-available/.

acpid, at, mdadm, mysql, openntpd, pdns-recursor, rsyslog, snmpd,
apache2, cron, memcached, nginx, openssh-server, postfix and smartmontools.

To enable monitoring for a specific service, create a symbolic link from the corresponding file in /etc/monit/conf-available/ to /etc/monit/conf-enabled/.

For example, to monitor Nginx, use:

sudo ln -s /etc/monit/conf-available/nginx /etc/monit/conf-enabled/

Then, reload the Monit service:

sudo monit reload

(See the image in the original article for example output in the Monit web interface).

If a service you want to monitor doesn’t have a pre-configured file, you can create one manually.

For example, to monitor system hardware sensors (using lm-sensors), first install the lm-sensors package:

sudo apt install lm-sensors -y

Then, create a configuration file:

sudo vi /etc/monit/conf-available/sensors

Add the following content:

check program sensors with path /usr/bin/sensors
if status != 0 then alert

Save and close the file. Enable the configuration:

sudo ln -s /etc/monit/conf-available/sensors /etc/monit/conf-enabled/

Finally, reload Monit:

sudo monit reload

Conclusion

You have now successfully learned how to Install Monit Manager on Debian 11 and configure it to monitor services. This allows you to keep a close eye on the health of your server and receive alerts when issues arise.

You may also like these articles:

How To Set up Adminer on Debian 11

Install and Configure Jekyll on Debian 11

How To Install MonoDevelop on Debian 11

Alternative Solutions for Server Monitoring on Debian 11

While Monit is a great solution, other options exist for server monitoring on Debian 11. Here are two alternatives:

1. Using Systemd Built-in Monitoring Capabilities

Systemd, the system and service manager in Debian 11, offers built-in capabilities for monitoring services. Although not as comprehensive as Monit, it can be a simpler solution for basic monitoring needs.

Explanation:

Systemd allows you to define dependencies between services, automatically restart failed services, and set resource limits. You can also configure email notifications for service failures. This approach leverages the existing system infrastructure, reducing the need for external tools.

Example:

To configure automatic restart for a service, edit the service unit file (e.g., /etc/systemd/system/your-service.service). Add the following lines to the [Service] section:

[Service]
Restart=on-failure
RestartSec=5

• Restart=on-failure: Specifies that the service should be restarted if it exits with a non-zero exit code. Other options include always, on-success, on-abort.
• RestartSec=5: Sets the delay (in seconds) before attempting to restart the service.

To configure email notifications, you’ll need to install and configure a mail transfer agent (MTA) like postfix. Then, you can use the OnFailure= directive in the service unit file to execute a script that sends an email:

[Service]
OnFailure=email-alert@%n.service

Create a systemd service unit file named email-alert@.service (e.g., /etc/systemd/system/email-alert@.service) with the following content:

[Unit]
Description=Send email alert for service failure

[Service]
Type=oneshot
ExecStart=/usr/local/bin/email-alert.sh %i

Create the script /usr/local/bin/email-alert.sh (and make it executable with chmod +x /usr/local/bin/email-alert.sh):

#!/bin/bash

SERVICE_NAME=$(echo "$1" | cut -d '@' -f 2 | cut -d '.' -f 1)
EMAIL="your-email@example.com"
SUBJECT="Service ${SERVICE_NAME} failed"
BODY="Service ${SERVICE_NAME} has failed.  Please investigate."

echo "$BODY" | mail -s "$SUBJECT" "$EMAIL"

Remember to replace your-email@example.com with your actual email address. Finally, reload systemd:

sudo systemctl daemon-reload

This approach is suitable for simple monitoring scenarios but lacks the advanced features of Monit, such as file integrity checks and detailed resource usage monitoring.

2. Using Prometheus and Grafana

Prometheus is a powerful open-source monitoring and alerting toolkit designed for time-series data. Grafana is a data visualization and dashboarding tool that integrates seamlessly with Prometheus. Together, they provide a comprehensive solution for monitoring server metrics and visualizing performance data.

Explanation:

Prometheus collects metrics from your server using exporters (agents that expose metrics in a specific format). Grafana then queries Prometheus to retrieve these metrics and displays them in customizable dashboards. This approach offers advanced features such as alerting based on complex queries, historical data analysis, and detailed performance insights.

Example:

1. Install Prometheus and Grafana: Follow the official documentation for installing Prometheus and Grafana on Debian 11.

2. Install Node Exporter: Install the Node Exporter on your server to collect system metrics (CPU usage, memory usage, disk I/O, etc.):

   sudo apt update
   sudo apt install prometheus-node-exporter

3. Configure Prometheus: Configure Prometheus to scrape metrics from the Node Exporter. Add the following to your prometheus.yml configuration file:

   scrape_configs:
     - job_name: 'node_exporter'
       static_configs:
         - targets: ['localhost:9100']

4. Import Grafana Dashboard: Import a pre-built Grafana dashboard for Node Exporter. There are many community-created dashboards available on Grafana’s website.

5. Create Alerts: Configure alerts in Prometheus to notify you when certain metrics exceed predefined thresholds. This is done using Prometheus’s Alertmanager. For example, to create an alert when CPU usage exceeds 80%, you would define a rule in your prometheus.yml file:

   groups:
   - name: example
     rules:
     - alert: HighCPUUsage
       expr: 100 - (avg by (instance) (irate(node_cpu_seconds_total{job="node_exporter",mode="idle"}[5m])) * 100) < 80
       for: 5m
       labels:
         severity: warning
       annotations:
         summary: "High CPU usage detected on {{ $labels.instance }}"
         description: "CPU usage on {{ $labels.instance }} is above 80% for 5 minutes."

This approach is more complex than using Monit or Systemd’s built-in monitoring, but it offers significantly more powerful features and scalability for larger environments. The Install Monit Manager on Debian 11 method is simpler for basic use cases.