Below are the commands which are to be used in centos 7 to open port 80
[root@onlinesupport ~]# firewall-cmd --permanent --zone=public --add-port=80/tcp success
[root@onlinesupport]# firewall-cmd --reload
Category Archives: Mysql
Mysql Upgrade Process
While upgrading mysql in server make sure you make a backup of existing mysql
using commmand mysqldump --all-databases > all_databases.sql
Once you have complete backup , You can proceed with with upgrade of mysql.
How to restart ipaliases in centos 7
Please run the command given below to restart ipaliases in centos 7 server with cpanel
/usr/local/cpanel/etc/init/scripts/centos/ipaliases restart
/tmp is 100% due to Mysql
Was having an issue where /tmp was getting 100% full every few minutes
on investigation i see the files of 3Gb over there in /tmp
#sql_436_0.MAD
ddvps20 tmp]# ls -al
total 3779332
drwxrwxrwt 12 root root 4096 Sep 21 10:24 .
dr-xr-xr-x 21 root root 4096 Sep 21 09:17 ..
drwxrwxrwt 2 root root 4096 Sep 21 09:17 .font-unix
drwxr-xr-x 2 cpanelsolr cpanelsolr 4096 Sep 21 10:22 hsperfdata_cpanelsolr
drwxr-xr-x 2 root root 4096 Sep 21 10:21 hsperfdata_root
drwxrwxrwt 2 root root 4096 Sep 21 09:17 .ICE-unix
drwx—— 2 root root 16384 Sep 21 09:56 lost+found
lrwxrwxrwx 1 root root 30 Sep 21 10:23 mysql.sock -> ../../var/lib/mysql/mysql.sock
-rw——- 1 cpdigita cpdigita 4096 Sep 21 10:11 .spamassassin1694OHMO4Dtmp
-rw——- 1 cpdigita cpdigita 0 Sep 21 10:17 .spamassassin1694voSq6Ctmp
-rw——- 1 cpdigita cpdigita 0 Sep 21 10:11 .spamassassin1694y0CJyjtmp
-rw——- 1 cpdigita cpdigita 0 Sep 21 10:04 .spamassassin18453ZHMaRtmp
-rw——- 1 cpdigita cpdigita 0 Sep 21 10:06 .spamassassin1845bypIDCtmp
-rw——- 1 cpdigita cpdigita 0 Sep 21 10:03 .spamassassin1845pCtlHqtmp
-rw-rw—- 1 mysql mysql 3866185728 Sep 21 10:07 #sql_436_0.MAD
-rw-rw—- 1 mysql mysql 8192 Sep 21 10:00 #sql_436_0.MAI
-rw——- 1 cpanelsolr cpanelsolr 165 Sep 21 10:22 start_2180387910403356223.properties
drwx—— 3 root root 4096 Sep 21 09:17 systemd-private-1d4af49159364e018772426d7df23a9d-named.service-8XVCsj
drwx—— 3 root root 4096 Sep 21 09:17 systemd-private-1d4af49159364e018772426d7df23a9d-named.service-FyUDBs
drwxrwxrwt 2 root root 4096 Sep 21 09:17 .Test-unix
drwxrwxrwt 2 root root 4096 Sep 21 09:17 .X11-unix
drwxrwxrwt 2 root root 4096 Sep 21 09:17 .XIM-unix
So mysql was going down due to /tmp being full
So as a work around found a better solution
To change the /tmp file to something else for mysql
vi /etc/my.cnf
tmpdir=/mysqltmp
Save the file with :wq
2. Create the /mysqltmp directory
mkdir /mysqltmp chmod 1777 /mysqltmp 3. Restart MySQL and check that the tmpdir is now /mysqltmp
/etc/init.d/mysql restart mysqladmin var | grep tmpdir
You should see the following return:
# mysqladmin var | grep tmpdir | slave_load_tmpdir | /mysqltmp | tmpdir | /mysqltmp
Install Imagemagick on easyapache4
yum install ImageMagick-devel ImageMagick-c++-devel ImageMagick-perl
/usr/bin/convert --version
/opt/cpanel/ea-php56/root/usr/bin/pecl install imagick
[ERROR] Can’t init tc log Mariadb
2018-03-30 2:06:19 139671858284288 [Note] InnoDB: Dumping buffer pool(s) not yet started
2018-03-30 2:06:19 139672598403328 [Note] Plugin ‘FEEDBACK’ is disabled.
2018-03-30 2:06:19 139672598403328 [Note] Recovering after a crash using tc.log
2018-03-30 2:06:19 139672598403328 [ERROR] Can’t init tc log
2018-03-30 2:06:19 139672598403328 [ERROR] Aborting
Was getting above error in mysql errorlog
The solution to this issue was just to go ahead and delete tc.log
rm -rf /var/lib/mysql/tc.log
Went ahead and restart mysql.. Mysql was online
root@server lib]# rm -rf /var/lib/mysql/tc.log
[root@server lib]# /etc/init.d/mysql restart
MySQL server PID file could not be found! [FAILED]
Starting MySQL.180330 02:07:40 mysqld_safe Logging to ‘/var/lib/mysql/server.cpanel.com.err’.
180330 02:07:40 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
[ OK ]
[root@server lib]#
Column count of mysql.user is wrong
Was getting below error while trying to create mysql user in cpanel
Error from MySQL query :(XID 5yuvwf) The system received an error from the “MySQL” database “mysql”: 1805 (Column count of mysql.user is wrong. Expected 43, found 39. The table is probably corrupted):
The migration used a “mysqldump –all-databases” so it included the “mysql” database. Apparently the “mysql.proc” table changed between the versions. The fix on the new server is to run:
Below command fixed the issue
The system could not create the user “triltch” because it conflicts with an unmanaged MySQL database user and an unmanaged PostgreSQL database user
While creating a new account in server was getting below error
The issue was due to mysql user already being present in server
root@srv1 [~]# /scripts/wwwacct trill.com tritch hood773ud
+===================================+
| New Account Info |
+===================================+
| Domain: trill.com
| UserName: tritch
| PassWord: hood773ud
+===================================+
This ok? yes
Checking input data……Done
Validating system setup……Done
…Done
Validating IP……Done
Validating Username……Done
Validating Contact Email……Done
Checking for database conflicts…(XID vh9sa4) The system could not create the user “tritch” because it conflicts with an unmanaged MySQL database user and an unmanaged PostgreSQL database user.
Steps to fix this issue
Login to WHM
Go to PHPmyadmin
Select database Mysql
Go to Option search
Select all tables inside in option Inside tables
In option Words or values to search for (wildcard: “%”): put up name of mysql user which is conflicting >>
Delete all the tables you get in search tables and issue should be resolved
You can also refer in below URL
Secure Connection Failed while accessing IPMI
Secure Connection Failed
An error occurred during a connection to 216.1x.1xx.xxx. You have received an invalid certificate. Please contact the server administrator or email correspondent and give them the following information: Your certificate contains the same serial number as another certificate issued by the certificate authority. Please get a new certificate containing a unique serial number. Error code: SEC_ERROR_REUSED_ISSUER_AND_SERIAL
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem.
Firefox stores certificates separately from the Operating System. Sometimes the certificate store can become corrupt and won’t let you delete certificates. To solve this, you’ll have to reset it manually.
Go to Start > Run
Type %appdata% and click Ok.
Result: A folder should open up.
Now go to Mozilla, then Firefox, then Profiles, and choose your profile folder (it probably is named a random string of letters, often followed by .default).
Delete the file called “cert8.db”.
This should fix the issue .
Disable WordPress plugins from PHPmyadmin
You can easily disable all WordPress plugins directly from your database. This is useful when you have problems with your WordPress installation, such as not being able to log in to the admin Dashboard, or having blank pages on the website.
If you don’t know which is the database used by your WordPress website, you can check the DB_NAME variable in the WordPress configuration file – wp-config.php. This file is usually located in the document root directory of your application and can be opened via the File Manager in cPanel.
To disable all plugins, go to phpMyAdmin in cPanel and select your WordPress database from the menu on the left.
Browse the table wp_options and find the option active_plugins. Click the pencil icon to edit the table. Its content will vary, depending on what plugins you have enabled. For example, if you have the Akismet and Hello Dolly plugins enabled, the code there will be:
1
|
a:2:{i:0;s:19:“akismet/akismet.php”;i:1;s:9:“hello.php”;}
|
To disable all plugins, simply delete the code and click the Go button to save the change.
Please note that this table may have a different prefix instead of wp_. You will see the correct prefix of the database once you access the phpMyAdmin tool and select the the WordPress database.
Disabling the plugins in this way will not delete them from your WordPress application. They will simply be deactivated. You can easily activate them from your WordPress admin area at any time.