Ron and Ella Wiki Page

Extremely Serious

Category: Tool (Page 1 of 4)

Why We Need Modern Software and Tools?

March 1, 2026 / / 0 Comments

Modern software and tools are no longer “nice to have”; they are the infrastructure that lets individuals and organizations work faster, more accurately, and more securely in a digital economy.

The role of modern tools in today’s world

We now build, run, and maintain most services through software, from banking and healthcare to logistics and entertainment. Modern tools encapsulate current best practices, regulations, and technologies, allowing us to keep up with rapidly changing requirements and expectations.

Efficiency and productivity at scale

Modern tools automate repetitive work such as deployments, testing, reporting, and coordination, which dramatically reduces manual effort and context switching. This automation scales: one team can now manage systems that would previously have required many more people, simply because the tools handle orchestration and routine checks.

Accuracy, reliability, and reduced risk

Contemporary platforms embed validation, type checking, automated tests, and monitoring capabilities that reduce the likelihood of human error. As a result, systems become more reliable, analytics more trustworthy, and business decisions less exposed to mistakes arising from inconsistent or incorrect data.

Collaboration in a distributed world

Work has become inherently distributed across locations and time zones, and modern software is designed to support this reality. Shared repositories, real‑time document and code collaboration, integrated chat, and task tracking make it feasible for cross‑functional teams to coordinate effectively without being physically co‑located.

Security, compliance, and maintainability

Security threats evolve constantly, and older tools tend not to receive timely patches or support for new standards. Modern platforms incorporate stronger authentication, encryption, audit trails, and compliance features, helping organizations protect data and meet regulatory obligations while keeping maintenance overhead manageable.

Innovation and competitive advantage

New capabilities—AI-assisted development, advanced analytics, low‑code platforms, cloud‑native services—are exposed primarily through modern tools and ecosystems. Organizations that adopt them can experiment faster, ship features more quickly, and create better user experiences, while those tied to outdated tooling tend to move slowly and lose competitive ground.

In short, we use modern software and tools because they are the practical way to achieve speed, quality, security, and innovation in a world where all of these are moving targets.

Vagrant Basic Commands

November 27, 2021 / / 0 Comments
Command Description
destroy Stops and deletes all traces of the vagrant machine
halt Stops the vagrant machine
init Initializes a new Vagrant environment by creating a Vagrantfile.
Vagrant boxes can be found from the following link:
Discover Vagrant Boxes - Vagrant Cloud (vagrantup.com)
provision Provisions the vagrant machine
reload Restarts vagrant machine, loads new Vagrantfile configuration
resume Resume a suspended vagrant machine
ssh Connects to machine via SSH
ssh-config Outputs OpenSSH valid configuration to connect to the machine
status Outputs status of the vagrant machine
suspend Suspends the machine
up Starts and provisions the vagrant environment
validate Validates the Vagrantfile
version Prints current and latest Vagrant version

Using dos2unix

November 5, 2020 / / 0 Comments

Sometimes we wrote a script intended for linux but we are using windows. However, when we deploy the script to linux it doesn't work.

For example you've created the file helloworld.sh in windows with the following content:

#!/bin/sh
echo "Hello World"

Transport helloworld.sh to linux and make it executable (i.e. using the command chmod 755 helloworld.sh). Execute it using the following command:

./helloworld.sh

Expect to see something similar to the following error:

-bash: ./helloworld.sh: /bin/sh^M: bad interpreter: No such file or directory

To remedy this, run dos2unix command with helloworld.sh as follows:

dos2unix helloworld.sh

Expect an output similar to the following:

dos2unix: converting file helloworld.sh to Unix format...

After this, execute the helloworld.sh again and expect no error.

Requesting for Certificate with certbot-auto

October 16, 2020 / / 0 Comments

Requesting for certificate

certbot-auto certonly -m <EMAIL_NAME> --webroot -w <WEBROOT_PATH> -d <DOMAIN_NAMES>

Example

certbot-auto certonly -m admin@example.com --webroot -w /usr/share/nginx/www -d www.example.com

Expanding your certificates

certbot-auto certonly --webroot --agree-tos -w <WEBROOT_PATH> --expand -d <DOMAIN_NAMES>

Example

certbot-auto certonly --webroot --agree-tos -w /usr/share/nginx/blog --expand -d blog.example.com

Display information about certificates you have from Certbot

certbot-auto certificates

Installing Jenkins in Ubuntu

October 16, 2020 / / 0 Comments

Requirement

  • Java 8 +

Installing Jenkins

  1. Install the jenkins key: 
    wget -q -O - https://pkg.jenkins.io/debian/jenkins.io.key | sudo apt-key add -
  2. Register the jenkins source: 
    sudo sh -c 'echo deb http://pkg.jenkins.io/debian-stable binary/ > /etc/apt/sources.list.d/jenkins.list'
  3. Add the universe repository: 
    sudo add-apt-repository universe
  4. Update the repository: 
    sudo apt-get update
  5. Install jenkins: 
    sudo apt-get install jenkins -y

Preparing Jenkins

  1. Access jenkins: 
    http://localhost:8080/
  2. Use the password found from the following file for Administrator Password: 
    sudo less /var/lib/jenkins/secrets/initialAdminPassword
  3. In Getting Started page select: 
    Install suggested plugins
  4. Create the first admin user.
  5. Provide the Jenkins URL in the Instance Configuration.
  6. Click the Start using Jenkins button.

Monitoring Artifactory Service with Nagios

October 15, 2020 / / 0 Comments

Requirement

  • check_jmx plugin

Enable JMX on Artifactory

  1. Update the /var/opt/jfrog/artifactory/etc/default file to add the following: 
    export JAVA_OPTIONS="$JAVA_OPTIONS -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=5000 -Dcom.sun.management.jmxremote.local.only=false -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false"

    If you wanted to connect remotely (e.g. jconsole) add the following argument:

    -Djava.rmi.server.hostname=<IP_ADDRESS>
  2. Restart the artifactory service: 
    sudo systemctl restart artifactory.service

Testing with check_jmx plugin

/usr/local/nagios/libexec/check_jmx/nagios/plugin/check_jmx -U service:jmx:rmi:///jndi/rmi://localhost:5000/jmxrmi -O "org.jfrog.artifactory:instance=Artifactory, type=Storage,prop=Binary Storage" -A Size

Expect to see something similar to the following output:

JMX OK Size=377653571

Related Post
Downloading the Nagios check_jmx Plugin in Ubuntu

Compiling Nagios Plugin 2.3.3 to Ubuntu 20.04

October 13, 2020 / / 0 Comments

Installing the Nagios Plugins

  1. Refresh the repository: 
    sudo apt-get update
  2. Install the dependencies: 
    sudo apt-get install -y autoconf gcc libc6 libmcrypt-dev make libssl-dev wget bc gawk dc build-essential snmp libnet-snmp-perl gettext
  3. Change the directory to your home directory: 
    cd ~
  4. Download the nagios plugins source codes: 
    wget --no-check-certificate -O nagios-plugins.tar.gz https://github.com/nagios-plugins/nagios-plugins/archive/release-2.3.3.tar.gz
  5. Extract the downloaded source codes: 
    tar zxf nagios-plugins.tar.gz
  6. Change to the directory of the newly extracted source codes: 
    cd nagios-plugins-release-2.3.3
  7. Setup and configure: 
    sudo ./tools/setup
sudo ./configure
  8. Compile the source codes: 
    sudo make
  9. Install the plugins to /usr/local/nagios/libexec directory: 
    sudo make install

Configuring NRPE 4 Daemon and Plugin to Ubuntu 20.04

October 12, 2020 / / 0 Comments

Installing NRPE

    1. Refresh the repository: 
      sudo apt-get update
    2. Install the dependencies: 
      sudo apt-get install autoconf automake gcc libc6 libmcrypt-dev make libssl-dev wget openssl -y
    3. Change the directory to your home directory: 
      cd ~
    4. Download the nrpe 4 source codes: 
      wget https://github.com/NagiosEnterprises/nrpe/releases/download/nrpe-4.0.3/nrpe-4.0.3.tar.gz
    5. Extract the downloaded source codes: 
      tar xvf nrpe-4.0.3.tar.gz
    6. Change to the directory of the newly extracted source codes: 
      cd nrpe-4.0.3
    7. Run the configure script that enables the command arguments for clients and uses ssl library: 
      sudo ./configure --enable-command-args --with-ssl-lib=/usr/lib/x86_64-linux-gnu/
    8. Compile the source codes: 
      sudo make all
    9. Install the nagios user and group: 
      sudo make install-groups-users
    10. Install both NRPE daemon and check_nrpe plugin: 
      sudo make install
    11. Install the nrpe config file (i.e. /usr/local/nagios/etc/nrpe.cfg): 
      sudo make install-config
    12. Install the init script: 
      sudo make install-init
    13. Enable the nrpe daemon: 
      sudo systemctl enable nrpe.service
    14. Update allowed_hosts field in the /usr/local/nagios/etc/nrpe.cfg file: to include your nagios server address (e.g. your nagios server address is 10.0.0.174 the allowed hosts is as follows): 
      allowed_hosts=127.0.0.1,::1,10.0.0.174
    15. Update the dont_blame_nrpe field: to 1 on the same configuration file to allow your clients to specify arguments: 
      dont_blame_nrpe=1
    16. Start the nrpe daemon: 
      sudo systemctl start nrpe.service

      The NRPE service is listening with the port 5666 by default.

Testing The NRPE Plugin

/usr/local/nagios/libexec/check_nrpe -H localhost

Expect to see the version of NRPE daemon

Related Post
Compiling NRPE 4 Plugin to Tinkerboard
Compiling Nagios Plugin 2.3.3 to Ubuntu 20.04

Compiling NRPE 4 Plugin to Tinkerboard

October 12, 2020 / / 0 Comments

Installing NRPE

  1. Refresh the repository: 
    sudo apt-get update
  2. Install the dependencies: 
    sudo apt-get install libssl-dev -y
  3. Change the directory to your home directory: 
    cd ~
  4. Download the nrpe 4 source codes: 
    wget https://github.com/NagiosEnterprises/nrpe/releases/download/nrpe-4.0.3/nrpe-4.0.3.tar.gz
  5. Extract the downloaded source codes: 
    tar xvf nrpe-4.0.3.tar.gz
  6. Change to the directory of the newly extracted source codes: 
    cd nrpe-4.0.3
  7. Run the configure script: 
    ./configure
  8. Compile the check_nrpe plugin only: 
    sudo make check_nrpe
  9. Install the newly compiled plugin: 
    sudo make install-plugin
  10. Update the file /usr/local/nagios/etc/objects/commands.cfg to add the following entry: 
    define command {
	command_name    check_nrpe
	command_line    /usr/local/nagios/libexec/check_nrpe -H $HOSTADDRESS$ -t 30 -c $ARG1$ $ARG2$
}

Testing The Plugin

Using the command check_nrpe we can check the load on the host 10.0.0.202 (i.e. NRPE daemon must be configured and listening on port 5666) using the following command:

/usr/local/nagios/libexec/check_nrpe -H 10.0.0.202 -c check_load

Expect to see the output of the check_load plugin executed on the host 10.0.0.202

Configuring Nagios 4 to Tinkerboard

October 12, 2020 / / 0 Comments

Installing Nagios

  1. Update the system: 
    sudo apt-get update && sudo apt-get upgrade
  2. Install the dependencies: 
    sudo apt-get install autoconf gcc libc6 make wget unzip apache2 php libapache2-mod-php libgd-dev libsasl2-modules mailutils -y
  3. Change the directory to your home directory: 
    cd ~
  4. Download the nagios 4 source codes: 
    wget https://assets.nagios.com/downloads/nagioscore/releases/nagios-4.4.6.tar.gz
  5. Extract the downloaded source codes: 
    tar xzf nagios-4.4.6.tar.gz
  6. Change to the directory of the newly extracted source codes: 
    cd nagios-4.4.6
  7. Run the configure script with integration to apache2: 
    ./configure --with-httpd-conf=/etc/apache2/sites-enabled
  8. Compile the source: 
    sudo make all
  9. Install the nagios user and group: 
    sudo make install-groups-users
  10. Make nagios user a member of the www-data group: 
    sudo usermod -aG nagios www-data
  11. Install nagios. 
    sudo make install
  12. Install the init script: 
    sudo make install-init
  13. Initialize the init script: 
    sudo make install-daemoninit
  14. Install and configures permissions on the directory for holding the external command: 
    sudo make install-commandmode
  15. Install the sample config files on the /usr/local/nagios/etc directory: 
    sudo make install-config
  16. Install the nagios config file to apache2: 
    sudo make install-webconf
  17. Update the SUID of the ping command: 
    sudo chmod 4755 /bin/ping

Installing the Nagios Plugins

  1. Run the following command: 
    sudo apt install nagios-plugins
  2. Update the $USER1$ property in the /usr/local/nagios/etc/resource.cfg file to have /usr/lib/nagios/plugins like as follows: 
    $USER1$=/usr/lib/nagios/plugins

Configuring Apache2 Web Server

  1. Enable the rewrite module: 
    sudo a2enmod rewrite
  2. Enable the CGI module: 
    sudo a2enmod cgi
  3. Create nagiosadmin as a nagios web user: 
    sudo htpasswd -c /usr/local/nagios/etc/htpasswd.users nagiosadmin

    Assign a strong password

  4. Restart the apache2 service: 
    sudo systemctl restart apache2

Related Post
Configuring NRPE 4 Daemon and Plugin to Ubuntu 20.04
Compiling NRPE 4 Plugin to Tinkerboard

« Older posts

© 2026 Ron and Ella Wiki Page

Theme by Anders Noren — Up ↑