VNA mysql service fails to start with systemctl command
search cancel

VNA mysql service fails to start with systemctl command


Article ID: 270219


Updated On:


DX NetOps CA Virtual Network Assurance


Mysql service fails to start/stop during the install or systemctl.

wildfly service works as expected

In /var/log/messages and/or systemctl start mysql the following is seen:

mysql.server: line ###: my_print_defaults: command not found
mysql.server: line ###: cd: /usr/local/mysql: No such file or directory
Starting MySQL ERROR! Couldn't find MySQL server (/usr/local/mysql/bin/mysqld_safe

### is the line number which may vary by release.


All supported DX NetOps Virtual Network Assurance 23.3.3 or earlier


The install users umask 0027 settings are incorrect.
Defect: DE572632


Defect DE572632 is fixed in DX Netops VNA 23.3.4 and later.

DX Netops 23.3.4 Release Note:

Symptom: The file permissions for the /etc/my.cnf file are limited to the owner of the file.
Resolution: With this fix, the file now includes explicit read permission through the script.
(23.3.4, DE572632, 33496643)


Additional Information


The install owners umask config should be 022.

  • Check umask settings running "umask". Sample of correct settings.
    • [root@vna ~]# umask
  • Change umask with the command:
    • umask 0022

To completely resolve the failed new install take these steps.

  1. Stop the wildfly and mysql services.
  2. Fix the install owners umask, ensuring it's set to 0022.
  3. Use the chown and chmod commands to fix my.cnf ownership and permissions. Example shown is based on install owner being the root user. Both would be run as the root user.
    • chown root:root /etc/
    • chmod 644 /etc/my.cnf
  4. Start the mysql and wildfly services.
    • Confirm they started properly.
  5. Run the VNA installer again over the top of what's already installed.
    • Confirm it completes without error