KB labels


Ticket Product Version

Ticket Category

Ticket Assignee


Hot Fixes

Published Fixes
Your Arcserve Support User Profile
First Name:
Last Name:
email:
Phone:
Company:*
Customer Type:
Language:

Country:
Region:

Time zone:
Follow

arcserve-KB : While the RHA file server scenario is running clients receive error (111) unable to read mysql.sock file

Last Update: 2015-12-15 22:19:06 UTC

Description:

This issue occurs when running a File Server scenario on Red Hat Enterprise Linux 5.x with MySQL 5.x installed. What happens is that during the scenario run the XOFS module mount point creates a lock on non-standard files such as the mysql.sock file used by MySQL.  

To determine if the file is a non-standard file you can use the 'lsof -a -p ' command. First find the process ID for MySQL with 'ps -ef | grep mysql':

[root@RMDM-Linux1 ~]# ps -ef | grep mysql
root      1737  1559  0 17:11 pts/2    00:00:00 grep mysql
root      9326     1  0 Sep05 pts/1    00:00:00 /bin/sh /usr/bin/mysqld_safe --d                      atadir=/var/lib/mysql --pid-file=/var/lib/mysql/mysql.pid
mysql    10169  9326  0 Sep05 pts/1    00:00:00 /usr/sbin/mysqld --basedir=/usr                       --datadir=/var/lib/mysql --plugin-dir=/usr/lib/mysql/plugin --user=mysql --log-e                      rror=/var/lib/mysql/mysql-error.err --open-files-limit=8192 --pid-file=/var/lib/                      mysql/mysql.pid --socket=/var/lib/mysql/mysql.sock --port=3306

Then run lsof with the above information 'lsof -a -p 10169':

mysqld  10169 mysql   16u  unix 0xe5239040             24443 /var/lib/mysql/mysql.sock
mysqld  10169 mysql   17u   REG      253,0      2048 4980754 /mysql/mysql/host.MYI

Notice that the file TYPE is unix, instead of REG.

 

Solution:

This issue is resolved with the CA ARCserve RHA R16.1. SP2 patch T5TM083 which can be acquired through a support ticket with CA Technologies Support.

The fix requires the implementation of the XOFS kernel module and may require a reboot of the machine prior to update to make sure that the module can be properly unloaded.

More Information:

[How to Install Driver]

 

1) Stop all the running scenarios

2) Stop ARCserveRHA engine (/etc/init.d/ARCserveRHA stop)

3) unload the loaded xofs module (lsmod | grep xofs; rmmod xofs)

4) Change to directory (cd /opt/CA/ARCserveRHA/kernel/fs)

5) Make a copy of the existing xofs module ( cp -p xofs.o.2.6.18-164.el5 xofs.o.2.6.18-164.el5.BK)

6) Extract the fix in a tmp location (/var/tmp)

7) Copy the extracted xofs module (cp /var/tmp/xofs.o.2.6.18-164.el5 /opt/CA/ARCserveRHA/kernel/fs)

8) Make sure that the file permissions are same as the original. (chmod 500 opt/CA/ARCserveRHA/kernel/fs/xofs.o.2.6.18-164.el5)

9) Change to directory /etc/init.d/

10) Make a copy of the existing ARCserveRHA script (cp ARCserveRHA ARCserveRHA.BK)

11) Copy the new ARCserveRHA script to the folder /etc/init.d/

12) Make sure the file permissions are the same as the original. (chmod 755 /etc/init.d/ARCserveRHA)

9) Start ARCserveRHA engine (/etc/init.d/ARCserveRHA start)

10) Start the scenarios.

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments