Understanding the Issue

The problem typically appears in the Panel UI when the Imunify360 agent fails to start. Upon checking the logs, we could see that entries like the following:

tail -f /var/log/imunify360/error.log

This warning indicates that the Imunify360 agent attempted to start, but the necessary database migrations were not applied. As a result, the service cannot fully initialize, leading to the “not running” status in the panel.

Workaround

We can resolve this issue by restarting the Imunify360 services in a specific sequence. Follow these steps from the root account:

1. Stop Imunify360 Agent

systemctl stop imunify360-agent

Stops the Imunify360 agent process if it is partially running.

1. Stop Imunify360 Service

systemctl stop imunify360

Stops the main Imunify360 service to ensure a clean restart.

2. Reset Failed State

systemctl reset-failed imunify360-agent

Clears any failed systemd state that may prevent the agent from starting.

3. Start Imunify360 Service

systemctl start imunify360

Starts the main service first to ensure database migrations can be applied.

4. Pause for 5 Seconds
Gives the service a short buffer to initialize before starting the agent.

5. Start Imunify360 Agent

systemctl start imunify360-agent

Finally, starts the agent successfully after migrations are applied.

Conclusion

The “Imunify360 Agent Not Running” warning is typically related to pending migrations that prevent the service from initializing properly. By following the sequence above, you can quickly restore full functionality without needing to reboot your server or perform complex troubleshooting.

Keep an eye on /var/log/imunify360/error.log after performing this fix to ensure that no further warnings appear. For long-term stability, ensure your Imunify360 installation is fully updated and properly maintained.

If you’re still facing issues after trying these steps for the Imunify360 agent not running fix, our experts can help.we specialize in Server Management Services and Linux Server Support Services, providing 24×7 assistance to diagnose, secure, and optimize your server environment. Contact our team today to get your Imunify360 and server panel running smoothly again!

The post How to Fix “Imunify360 Agent Not Running” in Panel UI and Migration Error in Logs appeared first on Server Management Services | Cloud Management | Skynats.

On Debian Linux, the kdump service provides this functionality by reserving memory for a secondary kernel (called the dump-capture kernel) that boots when the primary kernel fails. In this guide, we’ll enable and configure Kernel Crash Dump on Debian Linux step by step.

Steps to Enable Kernel Crash Dump

Update your package list and install the kdump tools along with debugging support:

#apt-get update
#apt-get install kdump-tools crash kexec-tools makedumpfile "$(uname -r)-dbg"

you will be prompted with a configuration screen like this:

Select Yes → kdump-tools will be enabled immediately (USE_KDUMP=1 will be set).

2. Enable kdump

In order to enable the kdump manually; Edit the kdump configuration file:

#nano /etc/default/kdump-tools
Set:
USE_KDUMP=1

Save and exit.

3. Configure Bootloader (GRUB)

Reserve memory for the crash kernel by editing GRUB:

#vim /etc/default/grub

Modify the GRUB_CMDLINE_LINUX_DEFAULT line:

GRUB_CMDLINE_LINUX_DEFAULT="quiet crashkernel=256M"

Update GRUB:

#update-grub

4. Reboot and Verify

Reboot your system:

After reboot, check kdump status:

#kdump-config show

You should see that the crash kernel is loaded. You can also verify with:

#cat /sys/kernel/kexec_crash_loaded

If it returns 1, the crash kernel is ready.

5. (Optional) Test a Crash

Warning: This will intentionally crash and reboot your system. Only test in a safe environment.

Enable sysrq:

#sysctl -w kernel.sysrq=1

Trigger a crash (do not do in servers in production):

#echo c | sudo tee /proc/sysrq-trigger

After reboot, inspect the crash dump in /var/crash/

Conclusion

By enabling kdump on Debian Linux, you equip your system with a powerful mechanism to capture kernel crash dumps for post-mortem debugging. With the crash dump files available, administrators can analyze the root cause of failures and ensure better stability for production systems.

Whether you’re running servers or development environments, setting up kdump is a best practice for diagnosing critical issues effectively.

If you’re facing challenges configuring or troubleshooting Kernel Crash Dump on Debian Linux, our experts can help. At Skynats, we provide reliable Linux server management services and 24/7 server support services to ensure your systems remain stable, secure, and resilient. Contact us today for professional assistance and seamless server management.

The post How to Enable Kernel Crash Dump (kdump) on Debian Linux appeared first on Server Management Services | Cloud Management | Skynats.

Update the System

apt update && sudo apt upgrade -y

Install Nginx

sudo apt install nginx -y
sudo systemctl start nginx
sudo systemctl enable nginx

Install MariaDB

sudo apt install mariadb-server -y
sudo systemctl start mariadb
sudo systemctl enable mariadb

Then run:

mariadb

From here you can create a database and user for Pimcore.

Install PHP and Extensions

Install PHP and all necessary extensions.

apt install php-fpm php-intl php-mysql php-curl php-cli php-zip php-xml \
php-gd php-common php-mbstring php-xmlrpc php-bcmath php-json php-sqlite3 php-soap -y

Ensure you’re using a supported PHP version (e.g., PHP 8.3).

Install Composer

curl -sS https://getcomposer.org/installer | sudo php -- --install-dir=/usr/local/bin --filename=composer

Create Pimcore Project

Navigate to your web root and create the Pimcore project using Composer:-

cd /var/www/
COMPOSER_MEMORY_LIMIT=-1 composer create-project pimcore/demo pimcore

Set the right permissions

chown -R www-data:www-data /var/www/pimcore

Install Pimcore 

Run the Pimcore installer:

cd /var/www/pimcore
sudo -u www-data ./vendor/bin/pimcore-install

Configure Nginx

Create a new config file

vim /etc/nginx/sites-available/pimcore.conf

upstream php-pimcore {
    server unix:/var/run/php/php8.3-fpm.sock;
}

map $args $static_page_root {
    default                                 /var/tmp/pages;
    "~*(^|&)pimcore_editmode=true(&|$)"     /var/nonexistent;
    "~*(^|&)pimcore_preview=true(&|$)"      /var/nonexistent;
    "~*(^|&)pimcore_version=[^&]+(&|$)"     /var/nonexistent;
}

map $uri $static_page_uri {
    default                                 $uri;
    "/"                                     /%home;
}

server {
    listen 80;
    listen [::]:80;
    server_name ip_address;
    root /var/www/pimcore/public;
    index index.php;

    access_log /var/log/nginx/pimcore-access.log;
    error_log /var/log/nginx/pimcore-error.log;

    location ~* ^/admin/external {
        rewrite .* /index.php$is_args$args last;
    }

    location / {
        error_page 404 /meta/404;
        try_files $static_page_root$static_page_uri.html $uri /index.php$is_args$args;
    }

    location ~ ^/index\.php(/|$) {
        fastcgi_split_path_info ^(.+\.php)(/.+)$;
        try_files $fastcgi_script_name =404;
        include fastcgi.conf;
        set $path_info $fastcgi_path_info;
        fastcgi_param SCRIPT_FILENAME $realpath_root$fastcgi_script_name;
        fastcgi_pass php-pimcore;
        internal;
    }
}

Enable the site

sudo ln -s /etc/nginx/sites-available/pimcore.conf /etc/nginx/sites-enabled/

Restart nginx:

sudo systemctl restart nginx

Once Nginx is configured and Pimcore is installed, you can access the Pimcore admin panel in your browser.

http://<your-server-ip>/admin

You’ve now successfully installed and configured Pimcore on an Ubuntu server with a robust LEMP stack.

Conclusion

Need expert help to Install Pimcore on Ubuntu 24 without the hassle? Our team specializes in Linux server management services to handle installations, optimizations, and ongoing support. Contact Skynats today and get your Pimcore setup running smoothly!

The post How to Install Pimcore on Ubuntu 24 appeared first on Server Management Services | Cloud Management | Skynats.

What Makes MTR So Effective?

Unlike traceroute, which merely maps the path of packets, MTR combines path tracing with real-time latency and packet loss metrics across each hop. This integrated view helps pinpoint network bottlenecks and errant routers in one go.

Installing MTR on Linux

Most distributions include MTR in their repositories:Debian/Ubuntu:

apt update && apt upgrade  
apt install mtr-tiny

CentOS/Fedora:

yum update  
yum install mtr

 Other platforms like Arch Linux similarly offer straightforward installs.

Generating and Interpreting MTR Reports

Run:

mtr -rw mydomain.com

Flags:

• -r for report mode
  
• -w for wide output with full hostnames
  
• -c count to specify packet count (default 10).

Each line in the output shows a hop with columns for Loss %, Sent count, Last/Avg/Best/Worst latency, and Standard Deviation. Here’s what to watch for:

• Packet Loss: If loss appears on one hop but vanishes on the next, it’s likely due to ICMP rate limiting, not real network failure. Genuine packet loss persists across multiple hops.
  
• Latency Jumps: Steep latency increases between consecutive hops may indicate congestion, poor peering, or a slow router. But if latency drops at later hops, the issue might not impact final delivery.
  

For example, a high latency spike at hop 4 that subsides afterward often points to a local router issue, not a problem with the destination.

Advanced Techniques

• Bi-directional MTRs: Run MTR from both ends—your local system and the remote Linux host—to catch asymmetric routing problems. Support teams often request both reports for full diagnostics.
  
• TCP Mode: Use sudo mtr –tcp –port 80 –report -c 10 <host> to test TCP reachability where ICMP might be filtered by firewalls.
  

When to Ascend to iperf

To measure raw throughput instead of routing and latency, use iperf:

• Run iperf -s on one host and iperf -c <server_ip> on the other.
  This helps identify bandwidth limits or congestion separate from routing issues.
  

Conclusion

MTR provides a real-time, granular view of your Linux network’s health—highlighting where loss, delay, or misconfiguration is happening. Combine it with bi-directional testing, TCP checks, and throughput tests (like iperf) to build a complete network troubleshooting toolkit.

Let me know if you’d like a deeper dive into interpreting specific MTR outputs or guidance for Windows/macOS users!

If you’re still facing connectivity problems or need expert guidance on how to use mtr command for accurate diagnosis, our team can help. Skynats offers 24/7 Linux server management services to troubleshoot and resolve complex network issues quickly and efficiently.

Contact us today for reliable support and keep your servers running at peak performance.

The post Troubleshooting Network Issues on Linux with mtr appeared first on Server Management Services | Cloud Management | Skynats.

Install Apache2 and enable

sudo apt update
sudo apt install apache2
Enable and start Apache:

sudo systemctl enable apache2
sudo systemctl start apache2

Install MySQL

sudo apt install mysql-server

Create Leantime Database

Log into MySQL:

sudo mysql -u root -p

Run the following SQL commands:

CREATE DATABASE leantime_db;
CREATE USER 'leantime_user'@'localhost' IDENTIFIED BY 'password';
GRANT ALL PRIVILEGES ON leantime_db.* TO 'leantime_user'@'localhost';
FLUSH PRIVILEGES;
EXIT;

Replace ‘password’ with a secure password.

Install PHP and Required Extensions

Install PHP and necessary modules:

sudo apt install php php-cli php-fpm php-mysql php-json php-opcache php-mbstring php-xml php-gd php-curl

Check version:

php -v

Download  Leantime

Navigate to your web root:

cd /var/www/html

Download and extract Leantime:

sudo apt install unzip
sudo wget https://github.com/Leantime/leantime/releases/download/v3.5.5/Leantime-v3.5.5.zip
sudo unzip Leantime-v3.5.5.zip
sudo mv Leantime-v3.5.5 leantime
sudo chown -R www-data:www-data leantime

 Set Up the Environment Configuration File

Leantime uses a .env file to store database and environment configuration.

Navigate to the config directory:

cd /var/www/html/leantime/config

Copy the sample environment file:

sudo cp env.example .env

Edit the .env file:

sudo nano .env

Update the following lines with your database information:

DB_HOST=localhost

DB_NAME=leantime_db

DB_USER=leantime_user

DB_PASSWORD=password

Make sure these match the credentials you created earlier in MySQL.

Save and close the file.

 Configure Apache

Create a virtual host configuration:

sudo nano /etc/apache2/sites-available/leantime.conf

Paste:

<VirtualHost *:80>

    DocumentRoot /var/www/html/leantime/public

    ServerName IP address or domain name

    <Directory /var/www/html/leantime/public>

        AllowOverride All

        Require all granted

    </Directory>

    ErrorLog ${APACHE_LOG_DIR}/leantime_error.log

    CustomLog ${APACHE_LOG_DIR}/leantime_access.log combined

</VirtualHost>

Enable site and modules:

sudo a2ensite leantime.conf
sudo a2enmod rewrite
sudo systemctl restart apache2

Complete Leantime Installation

In your browser, go to:

http://<your-server-ip>/install

Or:

http://yourdomain.com/install

By following this step-by-step guide, you’ve successfully Install Leantime on Ubuntu 24 and configured it on an Ubuntu server using the LAMP stack. Your setup now includes a secure, open-source project management platform that supports agile workflows, kanban boards, Gantt charts, and more—ideal for teams looking to streamline their project planning and execution.

Conclusion

If you face any issues during the installation or need expert assistance, don’t hesitate to reach out for professional Linux Server Management support. A reliable team can help you you Install Leantime on Ubuntu 24, configure, secure, and optimize your setup, ensuring smooth and efficient project management operations.

The post How to Install Leantime on Ubuntu 24 appeared first on Server Management Services | Cloud Management | Skynats.

In this blog post, we’ll dive into understanding what causes the blk_update_request I/O error and provide detailed steps on how to troubleshoot and resolve the issue.

What is the blk_update_request I/O Error in Linux?

The error message is a low-level I/O error that typically occurs when the system tries to read or write data to a block device (like your hard drive, SSD, or USB stick) but encounters a problem. This could be caused by several issues, including:

• Faulty hardware (bad sectors, failing disk).
• Cable or connection issues (loose cables or ports).
• Corrupt file systems.
• Driver issues.

This error can sometimes appear in system logs, particularly in the kernel logs, and may prevent your system from reading or writing to the affected device correctly.

Steps to Troubleshoot blk_update_request I/O Error

1. Check the Physical Connections

The simplest reason for an I/O error could be a loose or faulty connection. If you’re dealing with an external hard drive or USB storage device, start by checking the following:

Cables: Ensure the cables are properly plugged in and not damaged. Try replacing them with known-good cables.

Ports: Plug the device into a different USB port or SATA connector to rule out issues with the specific port.

Power Supply: If you’re using an external hard drive with a separate power supply, ensure the power is stable.

2. Verify Disk Health

A failing disk is a common cause of I/O errors. Most modern hard drives and SSDs have built-in self-monitoring (SMART) systems that provide health reports.

To check the health of a disk on Linux:

Install smartmontools if you don’t have it already:

apt install smartmontools

Run a SMART status check on the affected disk (e.g., /dev/sda):

smartctl -a /dev/sda

Look for any signs of hardware failure, such as high numbers of reallocated sectors or other warnings in the output.

If the SMART test reports any significant errors, the drive may be failing, and replacing the disk is often the best solution.

3. Run Filesystem Check (fsck)

A corrupted file system can lead to I/O errors. Running a file system check can help resolve these issues by repairing any corruption.

To check and repair the file system:

Unmount the filesystem (if it’s not the root filesystem):
umount /dev/sda1

(Replace /dev/sda1 with the actual device name)

Run fsck (File System Consistency Check):

fsck /dev/sda1

This will automatically scan the file system and attempt to fix any errors it finds.

4. Check for available Disk Space

Sometimes, I/O errors can occur if the disk runs out of space or is heavily fragmented.

Check your available disk space using the following command:

df -h

Ensure that there is sufficient space available on the device. If the disk is full, try freeing up space by removing unnecessary files.

Also, check for any file system inconsistencies by running du on large directories:

du -sh /path/to/directory

5. Review Kernel Logs for More Information

Linux kernel logs can provide more details about the I/O error and help you understand which device or operation caused the issue.

You can check the kernel log using dmesg:

dmesg | grep blk_update_request

This will show the relevant log entries related to the blk_update_request I/O error. Review the log for specific details like the device name (e.g., /dev/sda) and any additional error messages that might point to the root cause.

6. Look for Bad Sectors

If the drive has bad sectors, it can cause I/O errors when the system tries to access those damaged areas.

To check for bad sectors, you can use the badblocks tool:

Run the following command to scan the device (replace /dev/sda with your device):

sudo badblocks -v /dev/sda

This will perform a read-only test of the disk for bad sectors.

If bad sectors are detected, the drive may need to be replaced. Some drives allow marking bad sectors so that they aren’t used for storing data.

7. Update Disk Drivers and Firmware

Outdated or incompatible drivers can sometimes cause I/O issues. Ensure that your system’s disk drivers and firmware are up-to-date.

On Linux, ensure your kernel and drivers are up to date.

sudo apt update && sudo apt upgrade

Firmware Updates: Check if your disk manufacturer provides firmware updates for your drive. Visit the manufacturer’s website to see if any new versions are available.

If you’re still experiencing issues after following our guide on how to fix the “blk_update_request I/O Error” in Linux, don’t hesitate to contact our support team. Also, our server management services offer professional support to identify and fix underlying issues quickly and effectively, ensuring your system runs smoothly.

The post How to fix the “blk_update_request I/O Error” in Linux appeared first on Server Management Services | Cloud Management | Skynats.

Let’s have a look at the cause of the error.

An error message will be displayed on the screen when apply configuration fails.

Backend login to the Core Config Manager failed.

While you try to apply the configuration to Nagios core a pop-up error message will be displayed on the screen.

Monitoring engine configuration files have been rolled back to their last known good checkpoint.

The main reason could be the Nagios XI server which is not able to resolve the “localhost”.

What to do when Apply Configuration fails in Nagios

For this, you need to open an SSH session to the Nagios XI server. then execute the following commands.

su nagios
cd /usr/local/nagiosxi/scripts
./reconfigure_nagios.sh
 Output.
URL: http://localhost/nagiosxi/includes/components/ccm/

CMDLINE

/usr/bin/wget --save-cookies nagiosql.cookies --keep-session-cookies http://localhost/nagiosxi/includes/components/ccm/ --no-check-certificate --post-data
'submit=Login&hidelog=true&loginSubmitted=true&username=nagiosxi&password=n@gweb' -O nagiosql.login--2016-08-03 10:10:46-- http://localhost/nagiosxi/includes/components/ccm/

Resolving localhost… failed: Name or service not known.

wget: unable to resolve host address “localhost”

NAGIOSQL LOGIN FAILED!

Run the command to see the contents of the /etc/hosts file:

cat /etc/hosts
Output.

127.0.0.1 localhost.localdomain localhost.localdomain localhost4 localhost4.localdomain4 xi-c6x-x64

::1 localhost.localdomain localhost.localdomain localhost6 localhost6.localdomain6 xi-c6x-x64

Here you can see no” localhost” entries where it has a similar entry but not the “localhost” entries at all.

So we edit /etc/hosts file and ensure the localhost entries in it. For example, we make the below changes in the file.

127.0.0.1 localhost.localdomain localhost.localdomain localhost4 localhost4.localdomain4 localhost xi-c6x-x64

::1 localhost.localdomain localhost.localdomain localhost6 localhost6.localdomain6 localhost xi-c6x-x64

Make the necessary changes and try “Apply configuration” from Core Configuration Manager, most probably the problem must be resolved.

Conclusion

In brief, the main cause of the error is that the Nagios XI server is unable to resolve “localhost.” This issue is often linked to configuration fails in Nagios server. Follow the steps provided to resolve the error, or contact our technical team for support to fix the problem on your behalf.

The post How to Apply Configuration Fails in Nagios Server appeared first on Server Management Services | Cloud Management | Skynats.

Our technical team support will set the PostgreSQL on Linux in the Vesta control panel on your behalf under our server management services plan. You can also take assistance from our technical team support 24/7 for fixing the error or any sort of installation and migration.

 PostgreSQL on Linux in Vesta control panel

Now you can install the Vesta panel on an RHEL, Ubuntu Server, Debian and CentOS.

Setting PostgreSQL on RHEL/CentOS

1. First, need to install PostgreSQL packages
2. # yum install postgresql postgresql-server postgresql-contrib phpPgAdmin
3. Install >> PostgreSQL >> from Remi repository >>then enable explicitly.
4. # yum install –enablerepo=remi postgresql postgresql-server postgresql-contrib phpPgAdmin
5.  Then initialize the database cluster:
6. # service postgresql initdb
7. Download HBA configuration:
8. # wget http://c.vestacp.com/0.9.8/rhel/pg_hba.conf -O /var/lib/pgsql/data/pg_hba.conf
9. Eventually, start the server:
10. # service postgresql start
11. Set oracle user password:
12. # su – postgres
13. # psql -c “ALTER USER postgres WITH PASSWORD ‘pgp4sw0rd’”
14. # exit
15. Then enable pgsql database support in Vesta.
16. Open /usr/local/vesta/conf/vesta.conf and set DB_SYSTEM to ‘mysql,pgsql’
17. Register pg instance in the control panel:
18. # v-add-database-host pgsql localhost postgres pgp4sw0rd
19. Download phpPgAdmin configuration:
20. # wget http://c.vestacp.com/0.9.8/rhel/pga.conf -O /etc/phpPgAdmin/config.inc.php
21. # wget http://c.vestacp.com/0.9.8/rhel/httpd-pga.conf -O /etc/httpd/conf.d/phpPgAdmin.conf
22. Restart the webserver:
23. # service httpd restart

Setting up PostgreSQL on Debian/Ubuntu

1. Install PostgreSQL packages
2. # apt-get install postgresql postgresql-contrib phppgadmin
3. Download HBA configuration:
4. # wget http://c.vestacp.com/0.9.8/debian/pg_hba.conf -O /etc/postgresql/*/main/pg_hba.conf
5. Later,restart the server:
6. # service postgresql restart
7. Set oracle user password:
8. # su – postgres
9. # psql -c “ALTER USER postgres WITH PASSWORD ‘pgp4sw0rd’”
10. # exit
11. Enable pgsql database support in Vesta.
12. Open /usr/local/vesta/conf/vesta.conf and set DB_SYSTEM to ‘mysql,pgsql’
13. In the control panel >> register pg instance.
14. # v-add-database-host pgsql localhost postgres pgp4sw0rd
15. Download phpPgAdmin configuration:
16. # wget http://c.vestacp.com/0.9.8/debian/pga.conf -O /etc/phppgadmin/config.inc.php
17. # wget http://c.vestacp.com/0.9.8/debian/apache2-pga.conf -O /etc/apache2/conf.d/phppgadmin
18. Restart the webserver:
19. # service apache2 restart

Error while we Setup PostgreSQL on Linux in Vesta

One of the clients came across a similar error while he trying to connect with remote PostgreSQL.

The server is not connecting to the PostgreSQL 

To resolve the issue, you need to start the PostgreSQL server on the remote server. (Need technical team support to resolve the error on your behalf)

# /etc/init.d/postgresql start

If we get the error while it is running, we need to enable TCP/IP support.

By default, the PostgreSQL server only allows connections to the database from the local machine or localhost.

Step 1: Allow remote IP address to access PostgreSQL

You need to open the file,/var/lib/pgsql/data/pg_hba.conf.By using the following su commands try to login into Postgres.

$ su – postgres
$ vi /var/lib/pgsql/data/pg_hba.conf

Now append the following line. To give access to the 192.168.1.0/24 network:

host all all 192.168.1.0 255.255.255.0 trust

Then, save and close the file.

Step 2: Allow communication over TCP/IP

We open PostgreSQL configuration file, /var/lib/pgsql/data/postgresql.conf

$ vi /var/lib/pgsql/data/postgresql.conf

Then bind and open TCP/IP port by setting tcpip_socket to true:

tcpip_socket = true

Finally, save and close the file.

Step 3: Restart PostgreSQL server

Use the following commands to restart the PostgreSQL server

# /etc/init.d/postgresql restart

This will open default port 5432.

Step 4: Test the setup

Finally, use the psql command from the client system.

psql -h PostgreSQL-IP-ADDRESS -U USERNAME -d DATABASENAME

Conclusion

In brief, Now you can install the Vesta Control panel on an RHEL, CentOS, Debian, and Ubuntu server. Happy to assist you out with any queries.

The post Setting PostgreSQL on Linux in Vesta control panel appeared first on Server Management Services | Cloud Management | Skynats.

Sometimes, the WordPress user forgets there login credentials especially the password. The WordPress user can change their password easily via the “Lost password”. You can also Reset WordPress admin password by creating the MD5 Hash.

On our server management plans, our experts will help you to reset the WordPress admin password using the Linux or Unix MySQL CLI. You can check with our team at any time for emergency support.

Follow the steps to reset the WordPress admin password wp cli.

Recovering the password by using the MySQL CMD that takes lesser steps.

First, you need to log in as root server by using the SSh command.

ssh -user@debian-10-ec2-server-ip

Later, find the MySQL version.

mysql --version

You can use the latest stable version.

/usr/sbin/mysqld Ver 8.0.23 for Linux on x86_64 (MySQL Community Server - GPL)

You will get the WordPress database name from the wp-config.php

Grep DB­_NAME wp-config.php

Output

define( ‘DB_NAME’, ‘examplewp’ );

Run the MySQL client as

Mysql –u root –p examplewp

Enter password:  

mysql>

Run “show tables command” to display the table list. Try to note the table name that ends with _users.

+-----------------------+
| Tables_in_examplewp  |
+-----------------------+
| wp_commentmeta        |
| wp_comments           |
| wp_links              |
| wp_options            |
| wp_postmeta           |
| wp_posts              |
| wp_term_relationships |
| wp_term_taxonomy      |
| wp_termmeta           |
| wp_terms              |
| wp_thesis_backups     |
| wp_usermeta           |
| wp_users              |
+-----------------------+
13 rows in set (0.00 sec)

From the WordPress get the list of user that has been stored and note the ID.

SELECT ID, user_login, user_pass, user_email FROM wp_users;

+----+------------+------------------------------------+-------------------------+
| ID | user_login | user_pass                          | user_email              |
+----+------------+------------------------------------+-------------------------+
|  1 | vadmin     | $P$xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxy | webmaster@example.com |
+----+------------+------------------------------------+-------------------------+
1 row in set (0.00 sec)

By following the commands reset the WordPress user password. This will replace the existing password with the new one.

UPDATE wp_users SET user_pass = MD5('my-new-password-here') WHERE ID = 1;

We can see a confirmation on the screen:

Query OK, 1 row affected (0.00 sec)
Rows matched: 1  Changed: 1  Warnings: 0

Later, exit from the MySQL session.
Mysql > \q

Before resetting the password we need to install the wp-cli

Installing the wp-cli

Before you start installing the WP-CLI, ensure that you will meet the minimum requirements. Then start downloading the wp-cli.phar file.

PHP 5.6 or later

WordPress 3.7 or later

Unix, Linux, FreeBSD, Cygwin like environment.

curl -O https://raw.githubusercontent.com/wp-cli/builds/gh-pages/phar/wp-cli.phar

check and verify whether the phar file is working.

php wp-cli.phar --info

Try to executive and move the files to any suitable PATH.

chmod +x wp-cli.phar
sudo mv wp-cli.phar /usr/local/bin/wp

Once the installation is done, you can run the following commands wp–info it displays the screen as shown below.

$ wp --info
OS: Darwin 16.7.0 Darwin Kernel Version 16.7.0: Thu Jan 11 22:59:40 PST 2018; root:xnu-3789.73.8~1/RELEASE_X86_64 x86_64
Shell: /bin/zsh
PHP binary: /usr/local/bin/php
PHP version: 7.0.22
php.ini used: /etc/local/etc/php/7.0/php.ini
WP-CLI root dir: /home/wp-cli/.wp-cli/vendor/wp-cli/wp-cli
WP-CLI vendor dir: /home/wp-cli/.wp-cli/vendor
WP-CLI packages dir: /home/wp-cli/.wp-cli/packages/
WP-CLI global config: /home/wp-cli/.wp-cli/config.yml
WP-CLI project config:
WP-CLI version: 2.4.0

Updating the WP-CLI 

If suppose the WP-CLI is owned by any other system user, for that you need to run the following commands.

sudo wp cli update

Reset WordPress admin password with following commands.

## Grab it ##
curl -O https://raw.githubusercontent.com/wp-cli/builds/gh-pages/phar/wp-cli.phar
 
## Make sure it is working ##
php wp-cli.phar --info
 
## Switch to your webserver user ##
su - wwwuser
 # OR #
sudo -u wwwuser -i
chmod +x wp-cli.phar
 
## Get a list of users ##
./wp-cli.phar --path=/http/public user list
 
## Set up a new password for user ID number 1 ##
./wp-cli.phar --path=/http/public user update 1 --user_pass=NEW_PASSWORD_HERE
 
## Remove wp-cli if you are not going to use it again (optional) ##
rm wp-cli.phar
 
## Get back to our root shell ##
exit

Test it

Try to login

Conclusion 

\From this blog, you will get an apparent view regarding how to reset the WordPress administrator password via the MySQL command prompt. Get assistance from expert team support.

The post Resetting the WordPress admin password using Linux or Unix MySQL CLI appeared first on Server Management Services | Cloud Management | Skynats.