try below to see if helps:
Cause 1: After recent upgrade, perform the following steps:
- Check to see if the link to /usr/bin/mysqldump has been removed. If so, add this link back during the upgrade script, as the link is removed but not added back.
- Check the output from the following command:
ls -l /usr/bin | grep mysqldump - If this gives no output, then run the following command to fix:
ln -s /opt/mysql/server-5.6/bin/mysqldump /usr/bin/mysqldump
Cause 2: If the backup fails even though there is a link to the mysqldump, perform the following steps:
- In some cases, it might be necessary to add an additional entry for jboss into the /etc/sudoers file. Add the following line to the /etc/sudoers file:
jboss ALL=(ALL) NOPASSWD: /usr/bin/mysqldump
The resulting output will look similar to the following:
[root@oum-xxx1 ocum-backup]# cat /etc/sudoers | grep jboss
jboss ALL=(ALL) NOPASSWD: /usr/bin/mysqldump
[root@oum-xxx1 ocum-backup] - If the customer has run the upgrade on the vApp from 6.3 -> 6.3P1, check to see if the link to /usr/bin/mysqldump has been removed. If so, add this link back during the upgrade script, as the link is removed but not added back.
- Check the output from the following command:
ls -l /usr/bin | grep mysqldump - If this gives no output, then run the following command to fix:
ln -s /opt/mysql/server-5.6/bin/mysqldump /usr/bin/mysqldump