Use the below command to set 755 to folder and 644 to file recirsively

find . -type d -exec chmod 0755 {} \;

find . -type f -exec chmod 0644 {} \;

cPanel comes with Default version Python 2.7

If you want to install second version Python 3.4 on server using rpm and via Source

First install epel repository

yum install epel-release

yum install python34

To install PIP on python2.4

yum install python3-pip

On getting the error in Magento

An error has happened during application run. See exception log for details

It can be fixed with below commands

php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento setup:static-content:Deploy -f
chmod -R 777 var/ generated/

You can disable the Proxypass from httpd.conf using below command

This issue occurs in live migration in cpanel to cpanel server

whmapi1 unset_all_service_proxy_backends username=cpanelusername

One of our server had Mysql failing to start on reboot with below error

tail -n 100 /var/log/mysqld.log
2022-03-08 3:53:37 0 [Note] Crash recovery finished.
2022-03-08 3:53:37 0 [Note] Server socket created on IP: ‘127.0.0.1’.
2022-03-08 3:53:37 0 [ERROR] mysqld: Can’t create/write to file ‘/var/run/mysqld/mysqld.pid’ (Errcode: 2 “No such file or directory”)
2022-03-08 3:53:37 0 [ERROR] Can’t start server: can’t create PID file: No such file or directory
2022-03-08 3:58:38 0 [Note] InnoDB: Using Linux native AIO
2022-03-08 3:58:38 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

Solution to this was

Create a new folder mkdir -p /var/run/mysqld/

Chown mysql.mysql /var/run/mysqld/

[root@ok1146s1 run]# mkdir /var/run/mysqld
[root@ok1146s1 run]# chown mysql:mysql /var/run/mysqld/
[root@ok1146s1 run]# /scripts/restartsrv_mysql
Waiting for “mysql” to start ……waiting for “mysql” to initialize ………finished.

Service Status
mariadb (/usr/sbin/mysqld) is running as mysql with PID 5809 (systemd+/proc check method).

Startup Log
Mar 08 04:08:14 ok1146s1.kvchosting.com systemd[1]: Starting MariaDB 10.3.34 database server…
Mar 08 04:08:16 ok1146s1.kvchosting.com mysqld[5809]: 2022-03-08 4:08:16 0 [Note] /usr/sbin/mysqld (mysqld 10.3.34-MariaDB) starting as process 5809 …
Mar 08 04:08:17 ok1146s1.kvchosting.com systemd[1]: Started MariaDB 10.3.34 database server.

mysql started successfully.
[root@ok116s1 run]#

Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

Additionally, a 503 Service Unavailable error was encountered while trying to use an ErrorDocument to handle the request.

While accessing one of the website saw the error mentioned above

Normally this 503 error are related to module PHP-fpm.

You just need to restart it from WHM to fix the issue

This issue is due to some core files in wordpress being corrupt.

The solution to this issue is to download new version of wordpress and upload new files and folders mentioned below

wp-includes , wp-admin and below files

wp-activate.php
wp-blog-header.php
wp-comments-post.php
wp-config.php
wp-config-sample.php
wp-cron.php
wp-links-opml.php
wp-load.php
wp-login.php
wp-mail.php
wp-settings.php
wp-signup.php
wp-trackback.php
xmlrpc.php

This resolved the issue and wordpres site was working fine

We had a Inoddb database crash in server , Where Mysqld was not starting.

So first we checked on what databases tables are crashed or corrupted using

command mysqlcheck -A –all-databases and repaired it using

mysqlcheck --auto-repair –all-databases

You can check in below URL for additional functions using mysqlcheck

https://mariadb.com/kb/en/mysqlcheck/

First thing we did was got mysql in recovery mode using innodb_force

As with 0,1,2 mysql was not coming up we used value 3 to get innodb online in read only mode.

innodb_force_recovery = 3

now as mysql was online we made a full dump of mysql which include all databases

mysqldump –all-databases > all_databases.sql

Once complete dump was ready

We stopped the Mysql services using below command

whmapi1 configureservice service=mysql enabled=1 monitored=0

,We moved the the

mv /var/lib/mysql /var/lib/bkp_mysql

/scripts/restartsrv_mysql –stop

We now reinitialized the mysql using below command

mysqld –initialize –user=mysql

Now we restored the dump which we had created using command

Mysql Mysql < all_databases.sql

After the dump was restored , The mysql was restarted

/scripts/restartsrv_mysql –start

whmapi1 configureservice service=mysql enabled=1 monitored=1

Mysql root password was reset using below command

/scripts/mysqlconnectioncheck

I was getting error “Row size too large (> 8126). Changing some columns to TEXT or BLOB… | Mysql / MariaDB” while dumping database

The fix to this issue is to add below parameter in /etc/my.cnf

innodb_strict_mode = 0


and restart mysql

While Checking Mysql error logs could see below error

2021-03-31 0:04:00 1222 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
2021-03-31 0:04:00 1222 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
2021-03-31 0:04:00 1222 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade

To fix this issue you need to use command

mysql_upgrade

Reference is from https://forums.cpanel.net/threads/cpanel-22320-table-mysql-innodb_index_stats-has-length-mismatch.641493/