Hi Doug,
I was able to modify the /etc/my.cnf with the desired results.
My Scenario:
1)added to /etc/my.cnf
Code:
[mysqld]
sql_mode="TRADITIONAL,NO_AUTO_CREATE_USER"
2)verified that the mode was previously set
Code:
root@054 [~]# mysql -e 'select @@GLOBAL.sql_mode;'
+-------------------+
| @@GLOBAL.sql_mode |
+-------------------+
| |
+-------------------+
3) restart mysql
Code:
root@054 [~]# /scripts/restartsrv mysql
Waiting for mysql to restart...............finished.
mysqld_safe (/bin/sh /usr/bin/mysqld_safe --datadir=/var/lib/mysql --pid-file=/var/lib/mysql/054.cpanel.test.pid) running as root with PID 26370
mysqld (/usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/054.cpanel.test.pid --skip-external-locking) running as mysql with PID 26394
mysql started ok
4) check mysql
Code:
root@054 [~]# mysql -e 'select @@GLOBAL.sql_mode;'
+-------------------------------------------------------------------------------------------------------------------------------+
| @@GLOBAL.sql_mode |
+-------------------------------------------------------------------------------------------------------------------------------+
| STRICT_TRANS_TABLES,STRICT_ALL_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,TRADITIONAL,NO_AUTO_CREATE_USER |
+-------------------------------------------------------------------------------------------------------------------------------+
root@054 [~]#
The only thing that stands out as a possible oversight is to make sure that you added the variable within the [mysqld] section of the my.cnf
If your problem persists, you may want to open a ticket with cPanel Technical Support.
Regards,
-DavidN