Monitor Server Logs in Real-Time with “” Tool on RHEL/CentOS 7/6 is a small simple but effective application build on top of Node.js and, which allows to monitor Linux servers log files in real time through web interface screen widgets.

Install In CentOS – Real Time Server Log Monitoring

This tutorial will guide you on how you can install and monitor any local log files in real time with installed on RHEL/CentOS 7/6.x by configuring harvester file to monitor any local changes to log files.

Step 1: Add Epel Repositories

1. CentOS Epel repositories provides the binary packages for Node.js and NPMNode Packaged Modules. Install Epel repositories by issuing the following command.

On RHEL/CentOS 7
# yum install
On RHEL/CentOS 6
--------------------- On RHEL/CentOS 6.x - 32 Bit ---------------------
# yum install

--------------------- On RHEL/CentOS 6.x - 64 Bit ---------------------
# yum install
Install Epel Repository in CentOS 7
Install Epel Repository

2. After you added Epel Repos on your system, do a system upgrade by running the following command.

# yum update

Step 2: Install Node.js and NPM Packages

3. Node.js is a Javascript server-side programming platform which allows you to create network applications with backend functionality. NPM (Node Package Manager) is practically the package manager for Node.js. So, on the next step go ahead and install Node.js and NMP binaries on your system through YUM package manager by issuing the following commands.

# curl --silent --location | bash - 
# yum install -y nodejs
Install Node js in CentOS
Install Node js in CentOS 7

Step 3: Install and Configure Application

4. application must be installed on your system through NPM by specifying a valid local system user, through which the installation must take place. While you can use any valid system user to install, I personally recommend installing the application through root user or other system user with root privileges.

The reason for using this approach is that must have access to read locally log files and a user with non-privileges root privileges usually can’t access and read some important log files.

So, login with root account and install application through root account by issuing the following command (if you use other user replace root account with your system user accordingly).

# npm install -g --user “root”
Install in CentOS
Install Monitoring

5. After the application has been installed change your working directory to folder, which is hidden, and do a directory listing to visualize folder content in order to configure the application further.

# pwd  		[Make sure you are on the right path]
# cd
# ls Files Files

6. Now it’s time to configure to monitor local log files in real time. Let’s get an inside on how works.

  1. The harvester file watches for changes in the specified local log files declared in its configuration and sends its output via TCP
    protocol which further send the messages to local server or any other remote server declared with its IP Address ( address specified on harvesters broadcasts to all listening servers) – file harvester.conf
  2. server binds on all network interfaces (if not specified otherwise in log_server.conf file) and waits for messages from locally or remote harvesters nodes and sends their output to Web server ( means that it waits for messages from any local or remote harvesters) file log_server.conf
  3. Web server binds on all network interfaces, listens for web clients connections on port 28778 and processes and outputs the messages that it receives internally from server – file web_server.conf

First open harvester.conf file for editing, which by default only monitors Apache log files, and replace nodeName statement to match your hostname and define the logStreams statements with what internal log files you want to monitor (in this case I’m monitoring multiple log files such as audit, messages and secure logs). Use the below file excerpt as a guide.

# nano harvester.conf

Harvester file excerpt.

exports.config = {
  nodeName: "pxe-server",
  logStreams: {

audit: [

messages: [

secure: [

  server: {
    host: '',
    port: 28777
} Harvester Configuration Harvester Configuration

Also if you don’t need harvester output to be sent to a remote server change the line host on server statement to only send its output locally by modifying address with loopback address (

7. For security reasons, if you are not expecting remote harvesters output to your local server open log_server.conf file and replace address with loopback address (

# nano log_server.conf
Configure Linux Logs
Configure Logs

8. Other security features such as credentials login, HTTPS or restriction based on IPs to web server can be applied on web server-side. For this tutorial I will only use as a security measure just credential login.

So, open web_server.conf file, uncomment the entire auth statement by deleting all slashes and asterisks and replace user and pass directives accordingly as suggested on the bottom screenshot.

# nano web_server.conf
Configure Monitoring
Configure Monitoring

Step 4: Add Firewall Rule and Start Application

9. In order to gain web access to server add a rule on RHEL/CentOS 7 Firewall to open TCP 28778 port by issuing the following command.

# firewall-cmd --add-port=28778/tcp --permanent
# firewall-cmd --reload
Open Port on Firewall
Open Port on Firewall

Note: RHEL/CentOS 6.x users can open port 28778 on iptable firewall.

Step 5: Start Application and enter Web Interface

10. In order to start log monitoring application assure that your current working directory is root’s home and use the following commands in the following order to start application.

------------ First start server, put it in background and press Enter key ------------
# & 

------------ Start log harvester in background ------------
# & 
Start Service
Start Service

11. After the server has been started open a browser, enter your servers IP followed by 28778 port number using HTTP protocol on URL address and a prompt demanding your login credentials should appear.

Enter your user and password configured on step 8 to proceed further and application should now be visible on your browser presenting monitored log files in real time.
Login to Monitoring
Login to Monitoring
Real Time Log Monitoring with
Real Time Log Monitoring with

On Web interface add new screens and organize your streams or nodes accordingly.

12. To stop application run the following command.

# pkill node

Step 6: Create Manage Script

13. In order to use a command that manages application with three switches ( start, stop and status) create the following script named on /usr/local/bin executable directory and append execution permissions to this script.

# nano /usr/local/bin/
# chmod +x /usr/local/bin/

Add the following excerpt to this script file.


                start() {
                echo "Starting process..."
                /usr/bin/ &
                /usr/bin/ &

                stop() {
                echo "Stopping io-log process..."
                pkill node

                status() {
                echo "Status io-log process..."
                netstat -tlp | grep node

case "$1" in
echo "Usage: start|stop|status"
Esac Startup Script Startup Script

14. To start, stop or view status login with root account (or the user that app has been installed) and just run the following commands to easily manage the application.

# start
# status
# stop
Manage Script
Manage Script

That’s all! In my opinion is an excellent and effective web application to monitor local or remote servers log files is real time and get an outlook on what is going internally in the systems and especially to debug server problems when systems tend to become unresponsive or crashes, without the need to use a console.

Hey TecMint readers,

Exciting news! Every month, our top blog commenters will have the chance to win fantastic rewards, like free Linux eBooks such as RHCE, RHCSA, LFCS, Learn Linux, and Awk, each worth $20!

Learn more about the contest and stand a chance to win by sharing your thoughts below!

Matei Cezar
I'am a computer addicted guy, a fan of open source and linux based system software, have about 4 years experience with Linux distributions desktop, servers and bash scripting.

Each tutorial at TecMint is created by a team of experienced Linux system administrators so that it meets our high-quality standards.

Join the TecMint Weekly Newsletter (More Than 156,129 Linux Enthusiasts Have Subscribed)
Was this article helpful? Please add a comment or buy me a coffee to show your appreciation.

Got Something to Say? Join the Discussion...

Thank you for taking the time to share your thoughts with us. We appreciate your decision to leave a comment and value your contribution to the discussion. It's important to note that we moderate all comments in accordance with our comment policy to ensure a respectful and constructive conversation.

Rest assured that your email address will remain private and will not be published or shared with anyone. We prioritize the privacy and security of our users.