![]() Then restart MySQL using the JSS Database Utility or command line noted above and test modifications. Under the |mysqld| section, add the following three variables: innodb_file_per_table = OFFįor example: # For advice on how to change settings please see Sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES # Adjust sizes as needed, experiment to find the optimal values. # The server defaults are faster for transactions and fast SELECTs. # Remove leading # to set options mainly useful for reporting servers. # These are commonly set, remove the # and set as required. # changes to the binary log between backups. # Remove leading # to turn on a very important data integrity option: logging Start at 70% of total RAM for dedicated server, else 10%. # Remove leading # and set to the amount of RAM for the most important data Open up the “my.cnf” file with a text editor, here is the default configuration for MySQL 5.6: # For advice on how to change settings please see This file could be in two different locations: /etc/my.cnf On workaround that might resolve the issue is to edit the configuration of the “my.cnf” file. Then proceed with the manual backup using the JSS Database Utility’s “Save Backup Now…” option. Sudo launchctl load -F /Library/LaunchDaemons/.ist On OS X Yosemite/El Capitan to restart MySQL post 5.7 from the command line: sudo launchctl unload -F /Library/LaunchDaemons/.ist On OS X to restart MySQL pre 5.7 from the command line: sudo /usr/local/mysql/support-files/rver restart Using the JSS Database Utility, select the “Restart MySQL…” command from the “Utilities” menu. # mysql -u root -pĮRROR 2013 (HY000): Lost connection to MySQL server at 'sending authentication information', system error: 32Īlso, passing in the host causes MySQL to throw a different exception: # mysql -u root -p -h 127.0.0.1ĮRROR 2013 (HY000): Lost connection to MySQL server at 'reading authorization packet', system error: 0Ī temporary workaround to make a manual JSS database backup is restarting MySQL: ![]() The issue was repeatable with a simple database import through the mysql client you get the authentication error. ![]() These logs only appear to output information when the databases are backing up, and this MySQL prevented backup. The JSS Database Utility logs are located here: /Library/JSS/Logs/backupDatabase.log The following web page outlines the process of enabling MySQL logging:Īnd JAMF Software doesn’t recommend enabling MySQL logging by default, but only temporarily for troubleshooting purposes, since it may take up a significant amount of disk space without a script to rotate/remove old logs. The following error will occur when trying to do a manual backup of your JSS database using the “JSS Database Utility”:Īlso, you will get errors with scheduled backups:īy default, MySQL, no logs are enabled, except the error log on Windows. Our server is running, JAMF Software Server (JSS) 9.82, OS X 10.10.5 “Yosemite” with server application version 5.0.15, and MySQL MySQL version 14.14 distribution 5.6.24. The Symptoms include, under heavy work loads we see the error: “Lost connection to MySQL server at ‘sending authentication information’, and system error: 32”. ![]() The bug is in the implementation of the MySQL binary running on OS X, and isn’t seen on other platforms like Windows or other Unix servers. On our JAMF Software Server (JSS) we noticed and error occurring during scheduled JSS database backup using the JSS Database Utility.
0 Comments
Leave a Reply. |