# Comments to support LSB init script conventions ### BEGIN INIT INFO # Provides: mysql # Required-Start: $local_fs $network $remote_fs # Should-Start: ypbind nscd ldap ntpd xntpd # Required-Stop: $local_fs $network $remote_fs # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: start and stop My SQL # Description: My SQL is a very fast and reliable SQL database engine.
### END INIT INFO # If you install My SQL on some other places than /usr/local/mysql, then you # have to do one of the following things for this script to work: # # - Run this script from within the My SQL installation directory # - Create a /etc/file with the following information: # [mysqld] # basedir= # - Add the above to any other configuration file (for example ~/ini) # and copy my_print_defaults to /usr/bin # - Add the path to the mysql-installation-directory to the basedir variable # below.
Now Maria DB fails to start with error "failed to start mariadb with customized my.cnf, restart with default configuration"I have deleted &/or renamed in the etc/My SQL/ folder, and uninstalled mariadb, reboot, reinstall but still get the same error. Hi, I have the same problem, but the fix did not work for me.
Previously I did modify to fix the binding issue that prevented xbmc from connecting. have found the following in /var/services/My SQL/diskstation.err140310 mysqld_safe Starting mysqld daemon with databases from /var/services/mysql/usr/bin/mysqld: error while loading shared libraries: 5: cannot open shared object file: No such file or directory140310 mysqld_safe mysqld from pid file /run/mysqld/ended Not sure if that helps anyone. With no SQL option i have a bunch of dead in the water websites I need back up. I have even tried removing the app and DB's, on re install it still fails to start."System Event Failed to start Maria DB with customized my.cnf, Restart with default configuration."I do not run any custom configs with this at all. Before applying the fix noted above, I had this in Disk Station.err:/usr/bin/mysqld: error while loading shared libraries: 5: cannot open shared object file: No such file or directory After copying the file per the post above, I now get this in Disk Station.err:/usr/bin/mysqld: error while loading shared libraries: /lib/5: file too short Any ideas? Marc Hi, I have the same problem, but the fix did not work for me.
# Set some defaults pid_file= server_pid_file= use_mysqld_safe=1 user=mysql if test -z "$basedir" then basedir=/var/lib/mysql bindir=./bin if test -z "$datadir" then datadir=/var/lib/mysql fi sbindir=./bin libexecdir=./bin else bindir="$basedir/bin" if test -z "$datadir" then datadir="$basedir/data" fi sbindir="$basedir/sbin" libexecdir="$basedir/libexec" fi # If the manager pid_file doesn't exist, try the server's if test -s "$pid_file" then mysqlmanager_pid=`cat $pid_file` echo $echo_n "Shutting down My SQL" kill $mysqlmanager_pid # mysqlmanager should remove the pid_file when it exits, so wait for it.
All are basically the same with little differences here and there. But what did work (so far) is taking bits and pieces from a post here and a post there to finally get something working.
Thanks goes out to all those other bloggers who provided the information found here.
Keep in mind that this is my attempt at a new install of My SQL on my newly acquired Mac Book Pro (MBP hereinafter).
Centralized Management System, CIFS cluster, Cloud Sync for easier integration with cloud services, multiple Disk Station support as well as complete 2 way synchronization between 2 Disk Stations in Cloud Station 3.0, Quick Connect connection for both DSM and all mobile applications, streaming on Samsung Smart TV with a new DS video, an upgraded DS file with notably improved link sharing and advanced search options, a new DS download for Windows Phone 8, and much more Forum rules 1) This is a user forum for Synology users to share experience/help out each other: if you need direct assistance from the Synology technical support team or would simply like to report a bug, here is our support form:https://myds.synology.com/support/suppo ... lang=enu2) To avoid putting users' Disk Station at risk, please don't paste links to any patches provided by our Support team as we will systematically remove them.