Harvester Setup and Configuration

Harvester is an open-source hyperconverged infrastructure (HCI) software that provides a powerful and easy-to-use platform for deploying and managing virtual machines (VMs). Built on Kubernetes, it simplifies the process of setting up and maintaining a virtualized environment. 

The following steps will guide you in setting up Harvester 

Download the Harvester ISO from the website.

Make a bootable USB from the ISO with any of the following tools

• https://etcher.balena.io/
• https://rufus.ie/en/

Once the machine has been booted from USB we will get the following Page

Once booted, follow the steps to complete the installatoon

1. Cluster Creation:
• Select "Create a new Harvester Cluster"
2. Disk Selection:
• Use the right arrow key to navigate and choose a disk for Harvester's system.
• Select a separate disk dedicated to storing virtual machine data.
3. Host Configuration:
• Enter a hostname for your Harvester node.
4. Network Setup:
• Use the right arrow key to select your network interface card (NIC).
• Choose between DHCP or static IP configuration.
• If using Static, provide the necessary network details (IP address, subnet mask, gateway).
• Configure DNS server addresses.
5. VIP Configuration:
• Use the right arrow key to navigate, Choose between DHCP or static IP for the Virtual IP (VIP) address.
• If using Static, enter the desired VIP.
6. Cluster Token:
• Set a cluster token. This is crucial for adding more nodes to your cluster later.
7. Password and SSH:
• Set a strong password for accessing the node (default SSH user is 'rancher').
8. NTP Servers:
• Configure NTP servers (defaults to 0.suse.pool.ntp.org) to ensure time synchronization across all nodes. Use commas to separate multiple server addresses.
9. Optional Configurations:
• HTTP Proxy: If needed, provide the proxy URL.
• SSH Keys: Import SSH keys by providing their HTTP URL (e.g., GitHub public keys).
• Harvester Configuration: If you have a specific configuration file, enter its HTTP URL.
10. Review and Install:
• Review all the settings you've configured.
• Confirm to start the installation process. This might take a few minutes.
11. Access Harvester:
• After the node restarts, the Harvester console will show the management URL and node status.
• Access the web interface using the provided URL (defaults to https://your-virtual-ip).
• Use F12 to switch to the shell if needed, and type exit to return to the console.

Latest Steps can be found @  https://github.com/harvester/harvester

Enabling the MsSQL Extension in cPanel/WHM: A Manual Installation Guide

While cPanel/WHM offers a wide range of PHP extensions out of the box, the MsSQL extension for connecting to Microsoft SQL Server databases requires a bit of manual effort. In this guide, we'll walk you through the step-by-step process of installing and configuring the MsSQL extension on your cPanel server.

Prerequisites:

• Root Access: You'll need root privileges on your server to perform these steps.
• Source Code: Instead of using RPM packages (which can lead to dependency issues), we'll compile the necessary components from source code.

Installing Required Modules

1. unixODBC:

   • Download: Get the source code from the official unixODBC website.
   • Extract: tar -xvf unixODBC-X.X.X.tar.gz (replace X.X.X with the version you downloaded).
   • Configure and Install:

     cd unixODBC-X.X.X
     ./configure --prefix=/usr/local --enable-gui=no
     make
     make install
     

     FreeTDS:
2. • Download: Download FreeTDS version 0.82 (or a compatible older version) from ftp://ftp.freetds.org/pub/freetds/old/0.82/freetds-0.82.tar.gz.
   • Extract: tar -xvf freetds-0.82.tar.gz
   • Configure and Install:

     cd freetds-0.82
     ./configure --with-tdsver=8.0 --with-unixODBC=/usr/local
     make
     make install
     

     Configure FreeTDS:
3. • Edit freetds.conf: Find the freetds.conf file (usually in /usr/local/etc or /etc) and add the following, replacing placeholders:

     [MSHOSTNAME]
     host = your_sql_server_hostname_or_IP
     port = 1433 
     tds version = 8.0
     

Compiling mssql.so

1. Navigate to PHP Extension Directory:

   cd /home/cpeasyapache/src/php-X.X.X/ext/mssql

   (Replace X.X.X with your PHP version.)

2. Prepare and Build:

   phpize
   ./configure
   make
   make install

Activating the Extension

1. Locate php.ini: Find your PHP configuration file (php.ini). Its location can vary depending on your setup.
2. Add Extension: Open php.ini in a text editor and add the following line:

   extension="mssql.so"
   

3. Restart Apache:

   service httpd restart

Verifying Installation

To confirm that the extension is loaded, you have two options:

• Check Modules: Run php -m | grep mssql. If the installation was successful, you'll see "mssql" in the output.
• Create a phpinfo Page: Create a PHP file with the following content:

  <?php phpinfo(); ?>
  Open this file in your browser and search for "mssql." You should see detailed information about the MsSQL extension.

Troubleshooting Tip:

If you encounter an error during the FreeTDS configuration related to unixODBC, try using an older version of FreeTDS (like 0.82), as newer versions might have compatibility issues.

By carefully following these steps, you can manually install and enable the MsSQL extension in your cPanel/WHM environment, allowing your PHP applications to seamlessly interact with Microsoft SQL Server databases.

PEAR Management in cPanel

Installing PEAR in cPanel: A Guide for PHP Developers

PEAR (PHP Extension and Application Repository) is a valuable resource for PHP developers, offering a framework and distribution system for reusable PHP components. Whether you're building custom web applications or need specific functionality, PEAR can streamline your development process.

In this guide, we'll walk you through the steps for installing PEAR in your cPanel environment. The process varies slightly depending on your PHP version:

PHP Versions Less Than 5.3

1. Download go-pear: Use the following command in your terminal or SSH session:

   wget http://pear.php.net/go-pear

2. Install PEAR: Run the downloaded script:

   php go-pear.php

   Follow the on-screen prompts to customize your installation.

PHP Versions 5.3 and Above

1. Download go-pear.phar: Fetch the updated installer:

   wget http://pear.php.net/go-pear.phar

2. Install PEAR: Execute the installer using the following command:

   php go-pear.phar
   

   Again, follow the instructions to configure PEAR to your liking.

Important Notes

• Root Access: You'll need root access (via SSH or console) to perform these commands. If you're not comfortable with server administration, contact your hosting provider for assistance.
• Alternative Method: cPanel may have a built-in PEAR installer available in the software section. Check if this option exists for a more user-friendly installation.

Once PEAR is installed, you can manage packages using the pear command line tool:

• Installing a Package:

  pear install <package_name>
• Upgrading a Package:

  pear upgrade <package_name>
• Uninstalling a Package:

  pear uninstall <package_name>
• Listing Installed Packages:

  pear list

Why PEAR Matters

PEAR simplifies PHP development by providing:

• Reusable Components: A vast library of code packages for various tasks.
• Consistent Structure: A standardized way to organize and manage PHP projects.
• Easy Installation: Simple commands for adding and updating packages.
• Community Support: A large and active community of developers for troubleshooting and support.

By leveraging PEAR's capabilities, you can save time and effort while building robust and reliable PHP applications.

Let me know if you have any further questions about using PEAR with cPanel!

Resolving "Sorry, that domain is already setup (remove it from httpd.conf)" Error in cPanel/WHM

If you're a cPanel/WHM administrator, you might have encountered the frustrating error "Sorry, that domain is already set up (remove it from httpd.conf)" when trying to add a new domain. This error typically indicates that the domain name you're attempting to use is already associated with another account or configuration on your server.

In this guide, we'll break down the causes of this error and provide step-by-step instructions on how to resolve it.

Why Does This Error Occur?

There are two main reasons you might encounter this error:

Reason 1: The domain is already in use.

• The domain could be assigned as a primary, addon, or parked domain on another cPanel account.
• It might be lingering in the server's configuration even after being removed from an account.

Reason 2: Technical Glitches

• The removal process for the domain might not have been completed correctly, leaving remnants in the system.

Troubleshooting and Resolution

1. Check if the Domain is Actively Used

If the error is due to the domain already being associated with another account:

• Remove the domain: Log into the cPanel account that's using the domain and remove it as an addon, parked, or primary domain.

If you encounter the error "Error from park wrapper: Sorry, you do not control the domain" while trying to remove it, proceed to the next step.

2. Identify the Domain Owner and Remove Entries

1. Find the Owner: Use the following commands in the server's command line (SSH) to determine which account the domain is associated with:

   /scripts/whoowns example.com 

   If this doesn't yield results, try:

   grep example.com /var/cpanel/users/*

   (Replace "example.com" with the actual domain name.)

2. Remove Domain Entries: Once you know the owner account, remove any references to the domain from the following files:

   • /var/named/example.com.db
   • /etc/httpd/conf/httpd.conf (remove the virtual host entry)
   • /var/cpanel/users/username (remove entries related to the domain)
   • /etc/userdomains
   • /etc/localdomains
   • /etc/named.conf (remove entries related to the domain)
   • Remove DNS entry in WHM: Go to the DNS Zone Manager in WHM and remove the DNS zone for the domain.

3. Update User Domains: Finally, run the following command as root:

   /scripts/updateuserdomains

Important Considerations:

• Backups: Before making any changes to configuration files, it's crucial to have a backup of your server in case of unintended consequences.
• Technical Expertise: If you're not comfortable with editing configuration files, consider seeking help from your hosting provider or a qualified system administrator.

By following these steps, you should be able to resolve the "Sorry, that domain is already set up" error and successfully add the domain to the desired cPanel account.

Recovering Mistakenly Deleted LVM Partitions: A Lifesaver for Linux Admins

We've all been there – a moment of inattention or a typo, and suddenly a crucial LVM partition is gone. Thankfully, Linux offers a built-in safety net for these scenarios. The vgcfgrestore command can be your lifeline for recovering accidentally deleted LVM partitions, saving you from potential data loss and downtime.

Understanding the Safety Net: LVM Configuration Backups

Linux diligently maintains backup copies of your LVM configurations in the /etc/lvm/archive directory. This archive acts as a time machine, allowing you to rewind and restore your LVM setup to a previous state.

Recovering a Deleted LVM Partition: Step-by-Step

Let's walk through a real-world scenario. Suppose you've accidentally deleted a 10GB LVM partition belonging to a volume group named "my-vg." Here's how to recover it:

Step 1: Locate the Backup Configuration

First, you need to find the relevant backup file in the /etc/lvm/archive directory. The vgcfgrestore command makes this easy:

sudo vgcfgrestore --list my-vg

This will list all available backup configurations for your "my-vg" volume group. The output might look something like this:

my-vg_00001-123456789.vg
my-vg_00002-692643462.vg  
... 

Identify the backup file you want to use (e.g., my-vg_00002-692643462.vg).

Step 2: Restore the LVM Partition

Now, you can restore the LVM configuration using the backup file and the vgcfgrestore command:

sudo vgcfgrestore -f /etc/lvm/archive/my-vg_00002-692643462.vg my-vg

If successful, you'll see the message:

Restored volume group my-vg

Important Note: Before restoring, double-check that you've selected the correct backup file! Restoring the wrong configuration could lead to unintended consequences.

After the Restoration

Once the volume group is restored, you'll need to reactivate it:

sudo vgchange -ay my-vg

You should now be able to see and use your recovered LVM partition again.

Prevention is Key

While vgcfgrestore is a lifesaver, it's always better to prevent data loss in the first place. Consider these best practices:

• Regular Backups: Always maintain up-to-date backups of your entire system, including LVM metadata.
• Double-Check Commands: Be extremely careful when executing commands that modify LVM partitions.
• Use Snapshots: If you're unsure about a change, create an LVM snapshot first to have a rollback point.

Conclusion

The vgcfgrestore command is a powerful tool that can rescue you from the panic of accidentally deleting an LVM partition. By understanding how to use it and following preventive measures, you can confidently manage your LVM environment and ensure the safety of your data.

Using mdadm to Manage RAID and Multipath Storage on Linux: A Practical Guide with Examples

The mdadm command is a powerful tool for managing multiple device sets on Linux systems. It plays a crucial role in creating and maintaining RAID arrays, which provide redundancy and performance benefits, and multipath setups, which ensure data availability in case of hardware failure. Let's delve into how you can use mdadm to harness these powerful storage features, complete with practical examples.

Creating RAID Devices with mdadm

1. Define Your Configuration:

The /etc/mdadm.conf file is where you specify the devices and RAID level for your array.

Example: RAID 1 (Mirroring)

DEVICE /dev/sd[b,c]1  
ARRAY /dev/md0 level=raid1 raid-devices=2 /dev/sdb1 /dev/sdc1

This configuration creates a RAID 1 array (/dev/md0) that mirrors data across two devices (/dev/sdb1 and /dev/sdc1).

Example: RAID 5 (Striping with Parity)

DEVICE /dev/sd[b-d]1
ARRAY /dev/md0 level=raid5 raid-devices=3 /dev/sdb1 /dev/sdc1 /dev/sdd1

This configuration creates a RAID 5 array (/dev/md0) that stripes data across three devices with parity information for fault tolerance.

2. Create the RAID Array:

Use mdadm with the -C (create) option and the details from your configuration:

# RAID 1 example
sudo mdadm -C /dev/md0 --level=raid1 --raid-devices=2 /dev/sdb1 /dev/sdc1

# RAID 5 example
sudo mdadm -C /dev/md0 --level=raid5 --raid-devices=3 /dev/sdb1 /dev/sdc1 /dev/sdd1

3. Verify RAID Status:

Check the status of your newly created RAID array:

sudo mdadm --detail /dev/md0

You should see information about the RAID level, state (active, syncing, etc.), device status, and more.

Creating Multipath Devices with mdadm

Multipathing provides an additional layer of reliability by creating multiple paths to access a storage device.

sudo mdadm -C /dev/md1 --level=multipath --raid-devices=2 /dev/mapper/mpatha /dev/mapper/mpathb

This command creates a multipath device (/dev/md1) using two paths (/dev/mapper/mpatha and /dev/mapper/mpathb) that likely correspond to different physical disks.

Key Considerations

• Choose the Right RAID Level:
  • RAID 0: Best for performance but no redundancy.
  • RAID 1: Offers redundancy with mirroring.
  • RAID 5: Good balance of performance and redundancy.
  • RAID 6: More redundancy than RAID 5 but slightly slower.
  • RAID 10: Combines mirroring and striping for both performance and redundancy.
• Data Backup: RAID is not a backup solution; always maintain regular backups.
• Hardware Compatibility: Ensure your hardware (controllers, disks) supports your chosen RAID level.

Conclusion

mdadm empowers you to create robust and fault-tolerant storage solutions on Linux. By mastering its capabilities, you can optimize your server's performance and protect your valuable data.

Let me know if you'd like more in-depth examples or have any specific scenarios you'd like to explore!

Google Apps Wizard cPanel plugin

This tool was developed for web hosting companies, webmasters and website developers that have to setup domains with Google Apps in the everyday work. The purpose of Google Apps Wizard cPanel plugin is to facilitate the steps needed to work with Google Apps services. cPanel end user doesn’t need to have any prior knowledge of DNS records management while working with this tool.

http://code.google.com/p/google-apps-wizard-cpanel-plugin/

Installation

Run the following shell commands as root via SSH:

# wget http://google-apps-wizard-cpanel-plugin.googlecode.com/files/gaw-2.0.tar
# tar -xf gaw-2.0.tar
# cd gaw-2.0
# ./gawinstall.sh
# cd ..
# rm -Rfv gaw-2.0/ gaw-2.0.tar

Go to WHM >> Main >> Plugins >> Google Apps Wizard and click Update Now.
Upgrade

If you running version 2+ please skip this part.

# wget http://google-apps-wizard-cpanel-plugin.googlecode.com/files/gaw-2.0.tar
# tar -xf gaw-2.0.tar
# cd gaw-2.0
# ./gawupdate.sh
# cd ..
# rm -Rfv gaw-2.0/ gaw-2.0.tar

Uninstall

# wget http://google-apps-wizard-cpanel-plugin.googlecode.com/files/gaw-2.0.tar
# tar -xf gaw-2.0.tar
# cd gaw-2.0
# ./gawuninstall.sh
# cd ..
# rm -Rfv gaw-2.0/ gaw-2.0.tar

Multi-languages support

The language files folder is located at: /usr/local/cpanel/base/3rdparty/GoogleAppsWizard/lang/
The en.php is the default fallback language file so do not delete it!
To create new language files you must use an existing cPanel prefix.
You can see your available languages by navigating to: Main >> Locales >> View Available Locales.

Templates support

The Google Apps Wizard plugin support third party cPanel templates.
All you need to do is to copy the default template to your third party template folder.
Template path: /usr/local/cpanel/base/frontend/x3/gaw
Example command: # cp /usr/local/cpanel/base/frontend/x3/gaw /usr/local/cpanel/base/frontend/{Your custom template folder name}/

Mastering Installatron: A Guide to Installing and Uninstalling on Linux Servers

Installatron is a powerful web application installer that simplifies the deployment of popular scripts and CMS platforms like WordPress, Joomla, Drupal, and many more. It's a valuable tool for web hosting providers and system administrators who want to automate the process of setting up websites and applications for their clients.

In this guide, we'll walk you through the steps for installing and uninstalling Installatron on your Linux or FreeBSD server.

Installing Installatron

1. Download the Installer Script: Open your terminal and run the following command to download the Installatron installation script:

wget http://data.installatron.com/installatron-plugin.sh

2. Make the Script Executable: Give the script execute permissions:

chmod +x installatron-plugin.sh

3. Run the Installer: Execute the script to begin the installation process:

./installatron-plugin.sh -f

The -f flag indicates a forced installation, which might be necessary in some cases.

The script will automatically install Installatron and its dependencies.

Uninstalling Installatron

If you need to remove Installatron from your server, follow these steps:

1. Remove the Core Components: Execute the following commands to remove the core Installatron files:

rpm -e installatron-server
rm -fr /usr/local/installatron
rm -f /etc/cron.d/installatron

2. Delete User Install Data (Optional): If you want to completely remove all traces of Installatron and the applications it installed, you can delete the user install data. Exercise caution here, as this will delete all data associated with installed applications.

rm -fr /var/installatron

Important Considerations:

• Backups: Before installing or uninstalling any software, including Installatron, it's always a good practice to back up your server's data. This ensures you can easily restore your system in case anything goes wrong.
• Dependencies: Installatron may rely on certain dependencies (like PHP or MySQL). Make sure these dependencies are installed and configured correctly before installing Installatron.
• User Data: If you decide to remove user install data, be absolutely sure you don't need any of the installed applications or their data.

By following these instructions, you can confidently install and uninstall Installatron on your Linux server, giving you a versatile tool for managing web applications efficiently.

Lynis: Elevate Your Server Security with a Powerful Auditing Tool

In the ever-evolving landscape of cybersecurity, proactive security measures are paramount. One tool that can significantly bolster your server's defenses is Lynis, a comprehensive auditing and hardening tool designed to uncover vulnerabilities and security issues.

What is Lynis?

Lynis is an open-source security auditing tool that meticulously scans your server, assessing its configuration, software components, and potential weaknesses. It provides valuable insights into your system's overall security posture, enabling you to take proactive steps to harden it against potential threats.

Why Choose Lynis?

• Comprehensive Scanning: Lynis analyzes a wide range of aspects, including operating system settings, network configuration, installed software, user accounts, file permissions, and much more.
• Customizable Tests: You can tailor Lynis to focus on specific areas of concern, ensuring it aligns with your unique security requirements.
• Detailed Reports: The tool generates detailed reports highlighting potential vulnerabilities, configuration issues, and recommendations for remediation.
• Easy to Use: Lynis is designed to be user-friendly, even for those without deep security expertise.

Installing Lynis

1. Create a Directory: Use the following command to create a directory where you'll store Lynis:

   mkdir /usr/local/lynis

2. Download Lynis: Navigate to the new directory and download the latest stable version:

   cd /usr/local/lynis
   wget http://www.rootkit.nl/files/lynis-1.3.0.tar.gz 
   

   (Note: Always check the official Lynis website for the most up-to-date version and download link.)

3. Extract the Files: Unpack the downloaded archive:

   tar -xvf lynis-1.3.0.tar.gz

Running and Using Lynis

1. Become Root: You'll need root privileges to run Lynis because it accesses system-level information and writes logs.

2. Run Lynis: Navigate to the Lynis directory and execute the script:

   cd lynis-1.3.0
   ./lynis

Lynis will begin its comprehensive scan, analyzing your server's configuration and security settings. The process may take a while, depending on the size and complexity of your system.

Reviewing the Report

Once the scan completes, Lynis will generate a detailed report. Typically, you'll find it in /var/log/lynis.log. This report is a goldmine of information, including:

• Warnings: Potential vulnerabilities or misconfigurations that need your attention.
• Suggestions: Recommendations for hardening your system based on Lynis' findings.
• Details: In-depth explanations of each issue and why it matters.

Take the time to carefully review the report, prioritize the identified issues, and implement the suggested fixes.

Regular Audits

Remember, security is an ongoing process. Schedule regular Lynis scans to keep your server's security posture up-to-date and address any new vulnerabilities that may arise.

Lynis is an indispensable tool in your arsenal for maintaining a secure and resilient server environment. By proactively identifying and addressing vulnerabilities, you'll be well-equipped to protect your data and defend against potential threats.

Effortlessly Manage Perl Modules with cPanel's Built-in CPAN Installer

Working with Perl scripts on your cPanel server often requires additional modules for specific functionalities. Thankfully, cPanel simplifies this process with its integrated CPAN (Comprehensive Perl Archive Network) installer script. Let's dive into how you can leverage this powerful tool to install, update, and even empower your users to manage Perl modules.

Meet the /scripts/perlinstaller

cPanel comes equipped with a handy script called /scripts/perlinstaller that makes interacting with CPAN a breeze. Whether you prefer the convenience of the WHM interface or the flexibility of the command line, cPanel's got you covered.

WHM Interface: User-Friendly Module Management

For those who prefer a visual approach, the WHM (WebHost Manager) interface provides a straightforward way to install Perl modules. Head over to WHM -> Software -> Install a Perl Module. Here you can:

• Search: Easily find the module you need using the search feature.
• Install: Click a button to install the selected module directly from CPAN.

This is a great option when you're not entirely sure of the exact module name or want to explore available modules.

Command-Line Installation: Quick and Efficient

If you're comfortable with the command line, the perlinstaller script offers a fast and efficient way to install modules. The syntax is simple:

/scripts/perlinstaller <module_name>

For example:

/scripts/perlinstaller MD5
/scripts/perlinstaller IO::Compress::Base

Force Reinstall or Update

Need to update or reinstall a module? Use the --force flag:

/scripts/perlinstaller --force MD5

Empowering Your Users (cPanel 11 and above)

cPanel 11 introduced a fantastic feature that allows your users to install Perl modules within their own home directories (/home/$user/perl). This means they don't need to bother you or have SSH access to get the modules they need.

To enable this self-service option:

1. Go to WHM -> Module Installers -> Perl Module [Manage].
2. Make sure you have compilers enabled for users in WHM -> Security Center -> Compilers Tweak.

Key Benefits

• Convenience: cPanel eliminates the need to manually download and install modules from CPAN.
• Flexibility: You can choose the interface or command line method that suits your preference.
• User Empowerment: Give your users the ability to manage their own Perl modules.

The cPanel CPAN installer streamlines the process of working with Perl modules on your server, making it easier to build and maintain dynamic web applications. So, the next time you need a specific Perl module, don't hesitate to use this powerful tool at your disposal!

Account DNS Check Plugin for cPanel/WHM: Simplifying Server Migration and Domain Cleanup

Managing a cPanel/WHM server often involves tasks like migrating accounts to new servers or cleaning up old, inactive domains. One of the most tedious aspects of these tasks is ensuring that all domains are pointing to the correct server IP address. This is where the Account DNS Check plugin comes to the rescue!

What is the Account DNS Check Plugin?

The Account DNS Check plugin is a handy tool designed specifically for cPanel/WHM administrators. It streamlines the process of verifying whether hosted domains resolve to the correct IP address of your server. This can be a lifesaver when:

• Migrating Servers: When moving accounts from one server to another, this plugin quickly identifies domains that still point to the old server, ensuring a smooth transition.
• Auditing Your Server: It helps you pinpoint domains that are no longer active or that might have mistakenly been pointed elsewhere, allowing you to free up resources.

Key Features

• Easy Domain Verification: The plugin automatically checks the DNS records for all domains hosted on your cPanel/WHM server.
• Clear Reporting: It generates a clear list of domains that are either resolving correctly or those that need attention.
• Multiple Usage Options: You can use the plugin directly within WHM's graphical interface or execute it from the command line, offering flexibility for different workflows.

Installation Instructions

1. SSH Access: Log into your server as the root user via SSH or the console.
2. Download and Install:
   Bash

   cd /home
   rm -f latest-accountdnscheck  # Remove old version (if exists)
   wget http://www.ndchost.com/cpanel-whm/plugins/accountdnscheck/download.php
   sh latest-accountdnscheck

How to Use the Plugin

Within WHM:

1. Log in to your WHM panel.
2. Go to Plugins and click on Account DNS Check.
3. The plugin will take a few minutes to process, depending on the number of domains you have. Once complete, you'll see a list of domains with their DNS status.

From the Command Line:

1. SSH into your server as the root user.
2. Run the following command:
   Bash

   /var/cpanel/accountdnscheck/scripts/cli_run.sh
   The results will be displayed in your terminal.

Why This Plugin Matters

• Saves Time: Manual DNS checks can be extremely time-consuming, especially on servers with a large number of domains.
• Reduces Errors: The plugin automates the process, minimizing the chance of human error.
• Improves Efficiency: It gives you a quick overview of your domain's DNS health, allowing you to take corrective action promptly.

The Account DNS Check plugin is an indispensable tool for any cPanel/WHM administrator. By simplifying a critical but often tedious task, it helps ensure smooth server migrations and a clean, well-organized server environment.

Resizing EBS Volumes for Your EC2 Instances: A Step-by-Step Guide

Running out of space on your Amazon EC2 instance? Don't worry, you're not alone. Thankfully, with Elastic Block Store (EBS) volumes, expanding your storage capacity is a straightforward process. In this guide, we'll walk you through the steps to seamlessly resize your EBS volumes and ensure your EC2 instance has ample room to grow.

Why Resize EBS Volumes?

EBS volumes provide persistent block storage for your EC2 instances. As your applications and data grow, you might find the initial storage allocation becoming insufficient. Resizing EBS volumes allows you to increase the storage capacity without the need to create a new instance or migrate data, minimizing downtime and disruption.

Steps to Resize Your EBS Volume:

1. Stop Your Instance: Navigate to the EC2 Instances console within the AWS Management Console and stop the instance whose EBS volume you want to resize. Note the availability zone of your instance – this is crucial for later steps. Also, make a note of the mount point of the volume (e.g., /dev/sdxx).

2. Create a Snapshot: Go to the EBS Volumes console and locate the volume attached to your stopped instance. Select the volume and choose the "Take Snapshot" option. This creates a point-in-time backup of your data.

3. Create a New Volume from the Snapshot: Find the newly created snapshot in the EBS Snapshots console. Select it and click "Create Volume." Specify the desired increased size for the new volume and ensure you select the same availability zone as your EC2 instance.

4. Detach and Attach Volumes:

   • Head back to the EBS Volumes console.
   • Select the old volume, choose "Actions," and then "Detach Volume."
   • Select the new volume, choose "Actions," and then "Attach Volume."
   • Choose your instance from the list.
   • In the "Device" field, ensure you enter the correct mount point you noted in step 1 (e.g., /dev/sdxx).

5. Start Your Instance: Restart your EC2 instance from the EC2 Instances console.

6. Extend the Filesystem:

   • Once the instance is running, SSH into it.
   • Run df -h to list partitions. You'll see the new volume, likely mounted at /dev/xvda1 (or similar). Note that the displayed size won't reflect the increased capacity yet.
   • Extend the filesystem to utilize the full volume size by running:
     Bash

     resize2fs /dev/xvda1 
     (Replace /dev/xvda1 if your volume has a different mount point.)

Important Tips:

• Snapshots Are Your Friends: Always take a snapshot before resizing volumes, ensuring you have a rollback point in case of unexpected issues.
• Choose the Right Volume Type: If your workload demands high performance, consider using Provisioned IOPS SSD (io1) or General Purpose SSD (gp3) volumes for optimal results.
• Monitor Storage Usage: Regularly monitor your EBS volume usage to ensure you have enough headroom and plan for future resizing.

By following these steps, you can effortlessly resize your EBS volumes and scale your EC2 instances to meet the demands of your growing applications and workloads.