yum install mysql-community-server 安装mysql 报错求大神帮忙！！！！_course

[root@11 mysql]# yum install mysql-community-server Loaded plugins: fastestmirror Setting up Install Process Loading mirror speeds from cached hostfile Resolving Dependencies --> Running transaction check ---> Package mysql-community-server.x86_64 0:8.0.16-1.el7 will be installed --> Processing Dependency: mysql-community-common(x86-64) = 8.0.16-1.el7 for package: mysql-community-server-8.0.16-1.el7.x86_64 --> Processing Dependency: mysql-community-client(x86-64) >= 8.0.11 for package: mysql-community-server-8.0.16-1.el7.x86_64 --> Processing Dependency: systemd for package: mysql-community-server-8.0.16-1.el7.x86_64 --> Processing Dependency: systemd for package: mysql-community-server-8.0.16-1.el7.x86_64 --> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.19)(64bit) for package: mysql-community-server-8.0.16-1.el7.x86_64 --> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.18)(64bit) for package: mysql-community-server-8.0.16-1.el7.x86_64 --> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.17)(64bit) for package: mysql-community-server-8.0.16-1.el7.x86_64 --> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.15)(64bit) for package: mysql-community-server-8.0.16-1.el7.x86_64 --> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.14)(64bit) for package: mysql-community-server-8.0.16-1.el7.x86_64 --> Processing Dependency: libstdc++.so.6(CXXABI_1.3.7)(64bit) for package: mysql-community-server-8.0.16-1.el7.x86_64 --> Processing Dependency: libstdc++.so.6(CXXABI_1.3.5)(64bit) for package: mysql-community-server-8.0.16-1.el7.x86_64 --> Processing Dependency: libc.so.6(GLIBC_2.17)(64bit) for package: mysql-community-server-8.0.16-1.el7.x86_64 --> Processing Dependency: libsasl2.so.3()(64bit) for package: mysql-community-server-8.0.16-1.el7.x86_64 --> Running transaction check ---> Package mysql-community-client.x86_64 0:8.0.16-1.el7 will be installed --> Processing Dependency: mysql-community-libs(x86-64) >= 8.0.11 for package: mysql-community-client-8.0.16-1.el7.x86_64 --> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.19)(64bit) for package: mysql-community-client-8.0.16-1.el7.x86_64 --> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.18)(64bit) for package: mysql-community-client-8.0.16-1.el7.x86_64 --> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.15)(64bit) for package: mysql-community-client-8.0.16-1.el7.x86_64 --> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.14)(64bit) for package: mysql-community-client-8.0.16-1.el7.x86_64 --> Processing Dependency: libstdc++.so.6(CXXABI_1.3.5)(64bit) for package: mysql-community-client-8.0.16-1.el7.x86_64 --> Processing Dependency: libc.so.6(GLIBC_2.14)(64bit) for package: mysql-community-client-8.0.16-1.el7.x86_64 ---> Package mysql-community-common.x86_64 0:8.0.16-1.el7 will be installed ---> Package mysql-community-server.x86_64 0:8.0.16-1.el7 will be installed --> Processing Dependency: systemd for package: mysql-community-server-8.0.16-1.el7.x86_64 --> Processing Dependency: systemd for package: mysql-community-server-8.0.16-1.el7.x86_64 --> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.19)(64bit) for package: mysql-community-server-8.0.16-1.el7.x86_64 --> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.18)(64bit) for package: mysql-community-server-8.0.16-1.el7.x86_64 --> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.17)(64bit) for package: mysql-community-server-8.0.16-1.el7.x86_64 --> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.15)(64bit) for package: mysql-community-server-8.0.16-1.el7.x86_64 --> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.14)(64bit) for package: mysql-community-server-8.0.16-1.el7.x86_64 --> Processing Dependency: libstdc++.so.6(CXXABI_1.3.7)(64bit) for package: mysql-community-server-8.0.16-1.el7.x86_64 --> Processing Dependency: libstdc++.so.6(CXXABI_1.3.5)(64bit) for package: mysql-community-server-8.0.16-1.el7.x86_64 --> Processing Dependency: libc.so.6(GLIBC_2.17)(64bit) for package: mysql-community-server-8.0.16-1.el7.x86_64 --> Processing Dependency: libsasl2.so.3()(64bit) for package: mysql-community-server-8.0.16-1.el7.x86_64 --> Running transaction check ---> Package mysql-community-client.x86_64 0:8.0.16-1.el7 will be installed --> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.19)(64bit) for package: mysql-community-client-8.0.16-1.el7.x86_64 --> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.18)(64bit) for package: mysql-community-client-8.0.16-1.el7.x86_64 --> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.15)(64bit) for package: mysql-community-client-8.0.16-1.el7.x86_64 --> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.14)(64bit) for package: mysql-community-client-8.0.16-1.el7.x86_64 --> Processing Dependency: libstdc++.so.6(CXXABI_1.3.5)(64bit) for package: mysql-community-client-8.0.16-1.el7.x86_64 --> Processing Dependency: libc.so.6(GLIBC_2.14)(64bit) for package: mysql-community-client-8.0.16-1.el7.x86_64 ---> Package mysql-community-libs.x86_64 0:8.0.16-1.el7 will be installed --> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.18)(64bit) for package: mysql-community-libs-8.0.16-1.el7.x86_64 --> Processing Dependency: libstdc++.so.6(CXXABI_1.3.5)(64bit) for package: mysql-community-libs-8.0.16-1.el7.x86_64 --> Processing Dependency: libc.so.6(GLIBC_2.14)(64bit) for package: mysql-community-libs-8.0.16-1.el7.x86_64 ---> Package mysql-community-server.x86_64 0:8.0.16-1.el7 will be installed --> Processing Dependency: systemd for package: mysql-community-server-8.0.16-1.el7.x86_64 --> Processing Dependency: systemd for package: mysql-community-server-8.0.16-1.el7.x86_64 --> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.19)(64bit) for package: mysql-community-server-8.0.16-1.el7.x86_64 --> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.18)(64bit) for package: mysql-community-server-8.0.16-1.el7.x86_64 --> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.17)(64bit) for package: mysql-community-server-8.0.16-1.el7.x86_64 --> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.15)(64bit) for package: mysql-community-server-8.0.16-1.el7.x86_64 --> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.14)(64bit) for package: mysql-community-server-8.0.16-1.el7.x86_64 --> Processing Dependency: libstdc++.so.6(CXXABI_1.3.7)(64bit) for package: mysql-community-server-8.0.16-1.el7.x86_64 --> Processing Dependency: libstdc++.so.6(CXXABI_1.3.5)(64bit) for package: mysql-community-server-8.0.16-1.el7.x86_64 --> Processing Dependency: libc.so.6(GLIBC_2.17)(64bit) for package: mysql-community-server-8.0.16-1.el7.x86_64 --> Processing Dependency: libsasl2.so.3()(64bit) for package: mysql-community-server-8.0.16-1.el7.x86_64 --> Finished Dependency Resolution Error: Package: mysql-community-server-8.0.16-1.el7.x86_64 (mysql80-community) Requires: libstdc++.so.6(GLIBCXX_3.4.18)(64bit) Error: Package: mysql-community-server-8.0.16-1.el7.x86_64 (mysql80-community) Requires: libstdc++.so.6(GLIBCXX_3.4.19)(64bit) Error: Package: mysql-community-client-8.0.16-1.el7.x86_64 (mysql80-community) Requires: libstdc++.so.6(GLIBCXX_3.4.15)(64bit) Error: Package: mysql-community-server-8.0.16-1.el7.x86_64 (mysql80-community) Requires: libstdc++.so.6(CXXABI_1.3.5)(64bit) Error: Package: mysql-community-client-8.0.16-1.el7.x86_64 (mysql80-community) Requires: libstdc++.so.6(GLIBCXX_3.4.14)(64bit) Error: Package: mysql-community-server-8.0.16-1.el7.x86_64 (mysql80-community) Requires: systemd Error: Package: mysql-community-libs-8.0.16-1.el7.x86_64 (mysql80-community) Requires: libstdc++.so.6(CXXABI_1.3.5)(64bit) Error: Package: mysql-community-libs-8.0.16-1.el7.x86_64 (mysql80-community) Requires: libstdc++.so.6(GLIBCXX_3.4.18)(64bit) Error: Package: mysql-community-client-8.0.16-1.el7.x86_64 (mysql80-community) Requires: libc.so.6(GLIBC_2.14)(64bit) Error: Package: mysql-community-server-8.0.16-1.el7.x86_64 (mysql80-community) Requires: libstdc++.so.6(CXXABI_1.3.7)(64bit) Error: Package: mysql-community-server-8.0.16-1.el7.x86_64 (mysql80-community) Requires: libsasl2.so.3()(64bit) Error: Package: mysql-community-server-8.0.16-1.el7.x86_64 (mysql80-community) Requires: libstdc++.so.6(GLIBCXX_3.4.14)(64bit) Error: Package: mysql-community-server-8.0.16-1.el7.x86_64 (mysql80-community) Requires: libc.so.6(GLIBC_2.17)(64bit) Error: Package: mysql-community-server-8.0.16-1.el7.x86_64 (mysql80-community) Requires: libstdc++.so.6(GLIBCXX_3.4.15)(64bit) Error: Package: mysql-community-client-8.0.16-1.el7.x86_64 (mysql80-community) Requires: libstdc++.so.6(GLIBCXX_3.4.19)(64bit) Error: Package: mysql-community-client-8.0.16-1.el7.x86_64 (mysql80-community) Requires: libstdc++.so.6(CXXABI_1.3.5)(64bit) Error: Package: mysql-community-libs-8.0.16-1.el7.x86_64 (mysql80-community) Requires: libc.so.6(GLIBC_2.14)(64bit) Error: Package: mysql-community-server-8.0.16-1.el7.x86_64 (mysql80-community) Requires: libstdc++.so.6(GLIBCXX_3.4.17)(64bit) Error: Package: mysql-community-client-8.0.16-1.el7.x86_64 (mysql80-community) Requires: libstdc++.so.6(GLIBCXX_3.4.18)(64bit) You could try using --skip-broken to work around the problem ** Found 3 pre-existing rpmdb problem(s), 'yum check' output follows: 2:postfix-2.6.6-8.el6.x86_64 has missing requires of libmysqlclient.so.16()(64bit) 2:postfix-2.6.6-8.el6.x86_64 has missing requires of libmysqlclient.so.16(libmysqlclient_16)(64bit) 2:postfix-2.6.6-8.el6.x86_64 has missing requires of mysql-libs

mysql service mysql restart 启动失败_course

kali linux 64位，通过一键安装包安装了LAMP mysql安装的位置在/web/server/mysql ，系统启动后，所有服务运行正常 但是通过service mysql restart 启动失败 提示：/etc/init.d/mysql:WARING：/etc/mysql/my.cnf cannot be read See README.warnn.gz... 而/etc/ 下根本没有mysql文件夹，只有一个mysql.bak 每次停止mysql后，没办法启动，只能重启电脑 这种情况该怎么办呢？

mysql宕机求高手指教原因_course

============== my.ini配置 START ============== # Example MySQL config file for medium systems. # # This is for a system with little memory (32M - 64M) where MySQL plays # an important part, or systems up to 128M where MySQL is used together with # other programs (such as a web server) # # You can copy this file to # /etc/my.cnf to set global options, # mysql-data-dir/my.cnf to set server-specific options (in this # installation this directory is C:\mysql\data) or # ~/.my.cnf to set user-specific options. # # In this file, you can use all long options that a program supports. # If you want to know which options a program supports, run the program # with the "--help" option. # The following options will be passed to all MySQL clients [client] #password = your_password port = 3306 socket = /tmp/mysql.sock # Here follows entries for some specific programs # The MySQL server [mysqld] port = 3306 socket = /tmp/mysql.sock skip-locking key_buffer = 16M max_allowed_packet = 10M table_cache = 128 sort_buffer_size = 512K net_buffer_length = 8K read_buffer_size = 256K read_rnd_buffer_size = 512K myisam_sort_buffer_size = 64M max_connections = 1000 default-character-set = utf8 thread_cache_size = 8 query_cache_size = 0 query_cache_type = 0 # Don't listen on a TCP/IP port at all. This can be a security enhancement, # if all processes that need to connect to mysqld run on the same host. # All interaction with mysqld must be made via Unix sockets or named pipes. # Note that using this option without enabling named pipes on Windows # (via the "enable-named-pipe" option) will render mysqld useless! # #skip-networking # Disable Federated by default skip-federated # Replication Master Server (default) # binary logging is required for replication log-bin=mysql-bin # binary logging format - mixed recommended binlog_format=mixed # required unique id between 1 and 2^32 - 1 # defaults to 1 if master-host is not set # but will not function as a master if omitted server-id = 1 # Replication Slave (comment out master section to use this) # # To configure this host as a replication slave, you can choose between # two methods : # # 1) Use the CHANGE MASTER TO command (fully described in our manual) - # the syntax is: # # CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>, # MASTER_USER=<user>, MASTER_PASSWORD=<password> ; # # where you replace <host>, <user>, <password> by quoted strings and # <port> by the master's port number (3306 by default). # # Example: # # CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT= 3306, # MASTER_USER='joe', MASTER_PASSWORD='secret'; # # OR # # 2) Set the variables below. However, in case you choose this method, then # start replication for the first time (even unsuccessfully, for example # if you mistyped the password in master-password and the slave fails to # connect), the slave will create a master.info file, and any later # change in this file to the variables' values below will be ignored and # overridden by the content of the master.info file, unless you shutdown # the slave server, delete master.info and restart the slaver server. # For that reason, you may want to leave the lines below untouched # (commented) and instead use CHANGE MASTER TO (see above) # # required unique id between 2 and 2^32 - 1 # (and different from the master) # defaults to 2 if master-host is set # but will not function as a slave if omitted #server-id = 2 # # The replication master for this slave - required #master-host = <hostname> # # The username the slave will use for authentication when connecting # to the master - required #master-user = <username> # # The password the slave will authenticate with when connecting to # the master - required #master-password = <password> # # The port the master is listening on. # optional - defaults to 3306 #master-port = <port> # # binary logging - not required for slaves, but recommended #log-bin=mysql-bin # Point the following paths to different dedicated disks #tmpdir = /tmp/ #log-update = /path-to-dedicated-directory/hostname # Uncomment the following if you are using InnoDB tables #innodb_data_home_dir = C:\mysql\data/ #innodb_data_file_path = ibdata1:10M:autoextend #innodb_log_group_home_dir = C:\mysql\data/ # You can set .._buffer_pool_size up to 50 - 80 % # of RAM but beware of setting memory usage too high #innodb_buffer_pool_size = 16M #innodb_additional_mem_pool_size = 2M # Set .._log_file_size to 25 % of buffer pool size #innodb_log_file_size = 5M #innodb_log_buffer_size = 8M #innodb_flush_log_at_trx_commit = 1 #innodb_lock_wait_timeout = 50 [mysqldump] quick max_allowed_packet = 10M [mysql] no-auto-rehash # Remove the next comment character if you are not familiar with SQL #safe-updates [isamchk] key_buffer = 20M sort_buffer_size = 20M read_buffer = 2M write_buffer = 2M [myisamchk] key_buffer = 20M sort_buffer_size = 20M read_buffer = 2M write_buffer = 2M [mysqlhotcopy] interactive-timeout ============== my.ini配置 END ============== ============== mysql 错误日志 START ============== 180120 18:16:36 InnoDB: Starting shutdown... 180120 18:16:38 InnoDB: Shutdown completed; log sequence number 2 1119799076 180120 18:16:38 [Warning] Forcing shutdown of 1 plugins 180120 18:16:38 [Note] D:\PHPnow-1.5.3\MySQL-5.1.33\bin\mysqld.exe: Shutdown complete 180120 18:16:39 InnoDB: Started; log sequence number 2 1119799076 180120 18:16:39 [Note] Event Scheduler: Loaded 0 events 180120 18:16:39 [Note] D:\PHPnow-1.5.3\MySQL-5.1.33\bin\mysqld.exe: ready for connections. Version: '5.1.33-community-log' socket: '' port: 3306 MySQL Community Server (GPL) 180120 21:12:28 - mysqld got exception 0xc0000005 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8388608 read_buffer_size=262144 max_used_connections=43 max_threads=1000 threads_connected=20 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 782496 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x37f7930 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... 00725584 mysqld.exe!??? 004E6C5A mysqld.exe!??? Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 05CE2E30=select * from massage_common_user where yn=1 and id=29156 thd->thread_id=8430 thd->killed=NOT_KILLED The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. InnoDB: Log scan progressed past the checkpoint lsn 2 1125547569 180120 21:14:56 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 2 1125550276 180120 21:14:56 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed InnoDB: Last MySQL binlog file position 0 4956330, file name .\mysql-bin.000053 180120 21:14:57 InnoDB: Started; log sequence number 2 1125550276 180120 21:14:57 [Note] Recovering after a crash using mysql-bin 180120 21:14:57 [Note] Starting crash recovery... 180120 21:14:57 [Note] Crash recovery finished. 180120 21:14:57 [Note] Event Scheduler: Loaded 0 events 180120 21:14:57 [Note] D:\PHPnow-1.5.3\MySQL-5.1.33\bin\mysqld.exe: ready for connections. Version: '5.1.33-community-log' socket: '' port: 3306 MySQL Community Server (GPL) ============== mysql 错误日志 END ============== 服务器环境 window server 2012 16G

centos6安装mysql5.7出错：yum install mysql-community-server出错_course

安装mysql5.7，参考教程：https://www.php.cn/mysql-tutorials-386847.html 一开始不知道 地址中的el7应该对应自己的centos版本，直接执行该命令进行下载 ``` wget https://dev.mysql.com/get/mysql57-community-release-el7-11.noarch.rpm ``` 然后执行以下命令也没有报错， ``` yum -y localinstall mysql57-community-release-el7-11.noarch.rpm ``` 但是执行下面命令的时候一直报错 ``` yum -y install mysql-community-server ``` 之后重新下载centos6的版本，安装源 ``` # wget https://dev.mysql.com/get/mysql57-community-release-el6-11.noarch.rpm # yum -y localinstall mysql57-community-release-el6-11.noarch.rpm ``` 然而进行安装的时候还是报错 ``` yum -y install mysql-community-server ``` 原因在于他还是跑去安装el7的版本了 ``` ---> Package mysql-community-server.i686 0:5.7.17-1.el7 will be 安装 ``` 尝试了各种方法，重装了好多次，能删除的就删除，结果一直都是这样 获取mysql-community-server的信息，结果如下：  尝试删除无果： ``` [root@localhost ~]# yum remove mysql-community-server 已加载插件：fastestmirror, security 设置移除进程 参数 mysql-community-server 没有匹配 Loading mirror speeds from cached hostfile Package(s) mysql-community-server available, but not installed. 不删除任何软件包 ``` 真的搞了一天，心累啊！如果哪个好心人看到，可以提点提点，真的万分感谢！

linux安装mysql时给/var/lib/mysql赋予权限_course

Linux中安装完mysql之后， 1.用service mysql start启动时，报错没有mysql.service这个文件或者目录 2.此时ls -l 了一下/var/lib之后显示 drwxr-x--x 5 mysql mysql 4096 May 16 19:05 mysql 3.执行命令chown mysql:mysql /var/lib/mysql –R之后mysql正常启动了 4.此时ls -l 了一下/var/lib之后显示 drwxr-x--x 5 mysql mysql 4096 May 16 19:05 mysql 问题：我就纳闷了，这执行命令chown mysql:mysql /var/lib/mysql –R前后 /var/lib/mysql的权限、所属用户、所属组都没变啊，为什么mysql就可以启动了？

Could not load driverClass com.mysql.jbdc.Driver，配置好jar了还是找不到_course

自学线上商城的java web 项目。今天一个下午都在调这个bug，也试过调试jar包，也有重新配置Tomcat与mysql的连接池 我也有把jdbc的包放在jdk的lib文件夹下，然后增加classpath，jre的ext都试过 还看了新的jdbc是com.mysql.cj.jdbc.Driver也试过，似乎都没什么用 在maven和Tomcat的列表里都有jdbc的jar包，包括我自己有新build path也增加了这些jar包，而且我把好几个版本的都放上去了（不知道会不会是这个影响，不过加了也删不掉），pom.xml里面配的是截图中的8.0.17  ********** 如果需要更多信息我也可以再加，感激不尽 ## 报错信息如下：********** ``` 8月 02, 2019 11:30:38 下午 com.mchange.v2.c3p0.impl.AbstractPoolBackedDataSource getPoolManager 信息: Initializing c3p0 pool... com.mchange.v2.c3p0.ComboPooledDataSource [ acquireIncrement -> 3, acquireRetryAttempts -> 2, acquireRetryDelay -> 1000, autoCommitOnClose -> false, automaticTestTable -> null, breakAfterAcquireFailure -> false, checkoutTimeout -> 10000, connectionCustomizerClassName -> null, connectionTesterClassName -> com.mchange.v2.c3p0.impl.DefaultConnectionTester, dataSourceName -> 1hge162a4n0lvdz1eiiv1j|6ccdb29f, debugUnreturnedConnectionStackTraces -> false, description -> null, driverClass -> com.mysql.jbdc.Driver, factoryClassLocation -> null, forceIgnoreUnresolvedTransactions -> false, identityToken -> 1hge162a4n0lvdz1eiiv1j|6ccdb29f, idleConnectionTestPeriod -> 0, initialPoolSize -> 3, jdbcUrl -> jdbc:mysql://localhost:3306/todoList?useUnicode=true&characterEncoding=utf8&serverTimezone=GMT&useSSL=false, maxAdministrativeTaskTime -> 0, maxConnectionAge -> 0, maxIdleTime -> 0, maxIdleTimeExcessConnections -> 0, maxPoolSize -> 30, maxStatements -> 0, maxStatementsPerConnection -> 0, minPoolSize -> 10, numHelperThreads -> 3, numThreadsAwaitingCheckoutDefaultUser -> 0, preferredTestQuery -> null, properties -> {password=******, user=******}, propertyCycle -> 0, testConnectionOnCheckin -> false, testConnectionOnCheckout -> false, unreturnedConnectionTimeout -> 0, usesTraditionalReflectiveProxies -> false ] 8月 02, 2019 11:30:38 下午 com.mchange.v2.c3p0.DriverManagerDataSource ensureDriverLoaded 警告: Could not load driverClass com.mysql.jbdc.Driver java.lang.ClassNotFoundException: com.mysql.jbdc.Driver at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583) at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) at java.base/java.lang.Class.forName0(Native Method) at java.base/java.lang.Class.forName(Class.java:332) at com.mchange.v2.c3p0.DriverManagerDataSource.ensureDriverLoaded(DriverManagerDataSource.java:100) at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:132) at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:182) at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:171) at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:137) at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1014) at com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:32) at com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1810) at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547) 8月 02, 2019 11:30:38 下午 com.mchange.v2.c3p0.DriverManagerDataSource ensureDriverLoaded 警告: Could not load driverClass com.mysql.jbdc.Driver java.lang.ClassNotFoundException: com.mysql.jbdc.Driver at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583) at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) at java.base/java.lang.Class.forName0(Native Method) at java.base/java.lang.Class.forName(Class.java:332) at com.mchange.v2.c3p0.DriverManagerDataSource.ensureDriverLoaded(DriverManagerDataSource.java:100) at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:132) at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:182) at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:171) at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:137) at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1014) at com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:32) at com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1810) at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547) 8月 02, 2019 11:30:38 下午 com.mchange.v2.c3p0.DriverManagerDataSource ensureDriverLoaded 警告: Could not load driverClass com.mysql.jbdc.Driver java.lang.ClassNotFoundException: com.mysql.jbdc.Driver at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583) at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) at java.base/java.lang.Class.forName0(Native Method) at java.base/java.lang.Class.forName(Class.java:332) at com.mchange.v2.c3p0.DriverManagerDataSource.ensureDriverLoaded(DriverManagerDataSource.java:100) at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:132) at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:182) at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:171) at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:137) at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1014) at com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:32) at com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1810) at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547) 8月 02, 2019 11:30:40 下午 com.mchange.v2.c3p0.DriverManagerDataSource ensureDriverLoaded 警告: Could not load driverClass com.mysql.jbdc.Driver java.lang.ClassNotFoundException: com.mysql.jbdc.Driver at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583) at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) at java.base/java.lang.Class.forName0(Native Method) at java.base/java.lang.Class.forName(Class.java:332) at com.mchange.v2.c3p0.DriverManagerDataSource.ensureDriverLoaded(DriverManagerDataSource.java:100) at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:132) at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:182) at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:171) at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:137) at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1014) at com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:32) at com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1810) at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547) 8月 02, 2019 11:30:40 下午 com.mchange.v2.c3p0.DriverManagerDataSource ensureDriverLoaded 警告: Could not load driverClass com.mysql.jbdc.Driver java.lang.ClassNotFoundException: com.mysql.jbdc.Driver at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583) at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) at java.base/java.lang.Class.forName0(Native Method) at java.base/java.lang.Class.forName(Class.java:332) at com.mchange.v2.c3p0.DriverManagerDataSource.ensureDriverLoaded(DriverManagerDataSource.java:100) at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:132) at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:182) at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:171) at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:137) at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1014) at com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:32) at com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1810) at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547) 8月 02, 2019 11:30:40 下午 com.mchange.v2.c3p0.DriverManagerDataSource ensureDriverLoaded 警告: Could not load driverClass com.mysql.jbdc.Driver java.lang.ClassNotFoundException: com.mysql.jbdc.Driver at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583) at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) at java.base/java.lang.Class.forName0(Native Method) at java.base/java.lang.Class.forName(Class.java:332) at com.mchange.v2.c3p0.DriverManagerDataSource.ensureDriverLoaded(DriverManagerDataSource.java:100) at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:132) at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:182) at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:171) at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:137) at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1014) at com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:32) at com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1810) at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547) 8月 02, 2019 11:30:40 下午 com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask run 警告: com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@40eddbb0 -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (2). Last acquisition attempt exception: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown database 'todolist' at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:500) at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:481) at com.mysql.jdbc.Util.handleNewInstance(Util.java:425) at com.mysql.jdbc.Util.getInstance(Util.java:408) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:944) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3978) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3914) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:871) at com.mysql.jdbc.MysqlIO.proceedHandshakeWithPluggableAuthentication(MysqlIO.java:1714) at com.mysql.jdbc.MysqlIO.doHandshake(MysqlIO.java:1224) at com.mysql.jdbc.ConnectionImpl.coreConnect(ConnectionImpl.java:2199) at com.mysql.jdbc.ConnectionImpl.connectOneTryOnly(ConnectionImpl.java:2230) at com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2025) at com.mysql.jdbc.ConnectionImpl.<init>(ConnectionImpl.java:778) at com.mysql.jdbc.JDBC4Connection.<init>(JDBC4Connection.java:47) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:500) at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:481) at com.mysql.jdbc.Util.handleNewInstance(Util.java:425) at com.mysql.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:386) at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:330) at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:134) at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:182) at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:171) at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:137) at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1014) at com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:32) at com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1810) at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547) 8月 02, 2019 11:30:40 下午 com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask run 警告: com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@45eae662 -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (2). Last acquisition attempt exception: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown database 'todolist' at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:500) at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:481) at com.mysql.jdbc.Util.handleNewInstance(Util.java:425) at com.mysql.jdbc.Util.getInstance(Util.java:408) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:944) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3978) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3914) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:871) at com.mysql.jdbc.MysqlIO.proceedHandshakeWithPluggableAuthentication(MysqlIO.java:1714) at com.mysql.jdbc.MysqlIO.doHandshake(MysqlIO.java:1224) at com.mysql.jdbc.ConnectionImpl.coreConnect(ConnectionImpl.java:2199) at com.mysql.jdbc.ConnectionImpl.connectOneTryOnly(ConnectionImpl.java:2230) at com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2025) at com.mysql.jdbc.ConnectionImpl.<init>(ConnectionImpl.java:778) at com.mysql.jdbc.JDBC4Connection.<init>(JDBC4Connection.java:47) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:500) at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:481) at com.mysql.jdbc.Util.handleNewInstance(Util.java:425) at com.mysql.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:386) at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:330) at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:134) at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:182) at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:171) at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:137) at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1014) at com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:32) at com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1810) at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547) 8月 02, 2019 11:30:40 下午 com.mchange.v2.c3p0.DriverManagerDataSource ensureDriverLoaded 警告: Could not load driverClass com.mysql.jbdc.Driver java.lang.ClassNotFoundException: com.mysql.jbdc.Driver at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583) at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) at java.base/java.lang.Class.forName0(Native Method) at java.base/java.lang.Class.forName(Class.java:332) at com.mchange.v2.c3p0.DriverManagerDataSource.ensureDriverLoaded(DriverManagerDataSource.java:100) at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:132) at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:182) at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:171) at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:137) at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1014) at com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:32) at com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1810) at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547) 8月 02, 2019 11:30:40 下午 com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask run 警告: com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@6f8071b9 -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (2). Last acquisition attempt exception: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown database 'todolist' at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:500) at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:481) at com.mysql.jdbc.Util.handleNewInstance(Util.java:425) at com.mysql.jdbc.Util.getInstance(Util.java:408) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:944) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3978) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3914) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:871) at com.mysql.jdbc.MysqlIO.proceedHandshakeWithPluggableAuthentication(MysqlIO.java:1714) at com.mysql.jdbc.MysqlIO.doHandshake(MysqlIO.java:1224) at com.mysql.jdbc.ConnectionImpl.coreConnect(ConnectionImpl.java:2199) at com.mysql.jdbc.ConnectionImpl.connectOneTryOnly(ConnectionImpl.java:2230) at com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2025) at com.mysql.jdbc.ConnectionImpl.<init>(ConnectionImpl.java:778) at com.mysql.jdbc.JDBC4Connection.<init>(JDBC4Connection.java:47) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:500) at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:481) at com.mysql.jdbc.Util.handleNewInstance(Util.java:425) at com.mysql.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:386) at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:330) at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:134) at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:182) at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:171) at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:137) at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1014) at com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:32) at com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1810) at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547) 8月 02, 2019 11:30:40 下午 com.mchange.v2.c3p0.DriverManagerDataSource ensureDriverLoaded 警告: Could not load driverClass com.mysql.jbdc.Driver java.lang.ClassNotFoundException: com.mysql.jbdc.Driver at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583) at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) at java.base/java.lang.Class.forName0(Native Method) at java.base/java.lang.Class.forName(Class.java:332) at com.mchange.v2.c3p0.DriverManagerDataSource.ensureDriverLoaded(DriverManagerDataSource.java:100) at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:132) at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:182) at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:171) at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:137) at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1014) at com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:32) at com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1810) at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547) 8月 02, 2019 11:30:40 下午 com.mchange.v2.c3p0.DriverManagerDataSource ensureDriverLoaded 警告: Could not load driverClass com.mysql.jbdc.Driver java.lang.ClassNotFoundException: com.mysql.jbdc.Driver at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583) at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) at java.base/java.lang.Class.forName0(Native Method) at java.base/java.lang.Class.forName(Class.java:332) at com.mchange.v2.c3p0.DriverManagerDataSource.ensureDriverLoaded(DriverManagerDataSource.java:100) at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:132) at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:182) at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:171) at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:137) at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1014) at com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:32) at com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1810) at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547) ```

Mac OS 下MYSQL 的mysql.sock问题_course

情况描述：安装在Mac下的MySQL。刚安装完MySQL可以运行可以使用。在使用完MySQL 后，我会通过系统偏好设置里的按钮关闭MySQL Server。然后过一段时间再使用时就会出现 不能通过/tmp/mysql.sock建立连接这样的提示。然后我去到/tmp目录下，发现不存在mysql.sock文件。 在重新安装MySQL后，在/tmp目录下会重新出现mysql.sock文件。下面是我的提问，希望大家能为我 解答： 1.为什么mysql.sock会消失，重新安装后又会出现 2.网上说MySQL的默认sock路径和Mac下是不一样的。这里我非常不明白。在安装的时候把 mysql.sock安装在Mac的默认sock路径下，然后启动MySQL时又从MySQL的默认路径下找sock， 我这样的理解对吗？求解释 3.我该如何解决该问题。感觉主要问题就是/tmp/mysql.sock会自己消失。如何解决这个问题呢？

linux安装mysql问题~~~~~_course

有root权限 #rpm -ivh mysql-server-5.6.13.i386.rpm 然后就出现这些 Preparing... ########################################### [100%] file /usr/share/mysql/charsets/README from install of MySQL-server-5.6.1 3-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1.el6 _0.1.i686 file /usr/share/mysql/czech/errmsg.sys from install of MySQL-server-5.6. 13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1.el 6_0.1.i686 file /usr/share/mysql/danish/errmsg.sys from install of MySQL-server-5.6 .13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1.e l6_0.1.i686 file /usr/share/mysql/dutch/errmsg.sys from install of MySQL-server-5.6. 13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1.el 6_0.1.i686 file /usr/share/mysql/english/errmsg.sys from install of MySQL-server-5. 6.13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1. el6_0.1.i686 file /usr/share/mysql/estonian/errmsg.sys from install of MySQL-server-5 .6.13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1 .el6_0.1.i686 file /usr/share/mysql/french/errmsg.sys from install of MySQL-server-5.6 .13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1.e l6_0.1.i686 file /usr/share/mysql/german/errmsg.sys from install of MySQL-server-5.6 .13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1.e l6_0.1.i686 file /usr/share/mysql/greek/errmsg.sys from install of MySQL-server-5.6. 13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1.el 6_0.1.i686 file /usr/share/mysql/hungarian/errmsg.sys from install of MySQL-server- 5.6.13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52- 1.el6_0.1.i686 file /usr/share/mysql/italian/errmsg.sys from install of MySQL-server-5. 6.13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1. el6_0.1.i686 file /usr/share/mysql/japanese/errmsg.sys from install of MySQL-server-5 .6.13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1 .el6_0.1.i686 file /usr/share/mysql/korean/errmsg.sys from install of MySQL-server-5.6 .13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1.e l6_0.1.i686 file /usr/share/mysql/norwegian-ny/errmsg.sys from install of MySQL-serv er-5.6.13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1. 52-1.el6_0.1.i686 file /usr/share/mysql/norwegian/errmsg.sys from install of MySQL-server- 5.6.13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52- 1.el6_0.1.i686 file /usr/share/mysql/polish/errmsg.sys from install of MySQL-server-5.6 .13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1.e l6_0.1.i686 file /usr/share/mysql/portuguese/errmsg.sys from install of MySQL-server -5.6.13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52 -1.el6_0.1.i686 file /usr/share/mysql/romanian/errmsg.sys from install of MySQL-server-5 .6.13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1 .el6_0.1.i686 file /usr/share/mysql/russian/errmsg.sys from install of MySQL-server-5. 6.13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1. el6_0.1.i686 file /usr/share/mysql/serbian/errmsg.sys from install of MySQL-server-5. 6.13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1. el6_0.1.i686 file /usr/share/mysql/slovak/errmsg.sys from install of MySQL-server-5.6 .13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1.e l6_0.1.i686 file /usr/share/mysql/spanish/errmsg.sys from install of MySQL-server-5. 6.13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1. el6_0.1.i686 file /usr/share/mysql/swedish/errmsg.sys from install of MySQL-server-5. 6.13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1. el6_0.1.i686 file /usr/share/mysql/ukrainian/errmsg.sys from install of MySQL-server- 5.6.13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52- 1.el6_0.1.i686 file /usr/share/mysql/charsets/Index.xml from install of MySQL-server-5. 6.13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1. el6_0.1.i686 file /usr/share/mysql/charsets/armscii8.xml from install of MySQL-server -5.6.13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52 -1.el6_0.1.i686 file /usr/share/mysql/charsets/ascii.xml from install of MySQL-server-5. 6.13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1. el6_0.1.i686 file /usr/share/mysql/charsets/cp1250.xml from install of MySQL-server-5 .6.13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1 .el6_0.1.i686 file /usr/share/mysql/charsets/cp1251.xml from install of MySQL-server-5 .6.13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1 .el6_0.1.i686 file /usr/share/mysql/charsets/cp1256.xml from install of MySQL-server-5 .6.13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1 .el6_0.1.i686 file /usr/share/mysql/charsets/cp1257.xml from install of MySQL-server-5 .6.13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1 .el6_0.1.i686 file /usr/share/mysql/charsets/cp850.xml from install of MySQL-server-5. 6.13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1. el6_0.1.i686 file /usr/share/mysql/charsets/cp852.xml from install of MySQL-server-5. 6.13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1. el6_0.1.i686 file /usr/share/mysql/charsets/cp866.xml from install of MySQL-server-5. 6.13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1. el6_0.1.i686 file /usr/share/mysql/charsets/dec8.xml from install of MySQL-server-5.6 .13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1.e l6_0.1.i686 file /usr/share/mysql/charsets/geostd8.xml from install of MySQL-server- 5.6.13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52- 1.el6_0.1.i686 file /usr/share/mysql/charsets/greek.xml from install of MySQL-server-5. 6.13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1. el6_0.1.i686 file /usr/share/mysql/charsets/hebrew.xml from install of MySQL-server-5 .6.13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1 .el6_0.1.i686 file /usr/share/mysql/charsets/hp8.xml from install of MySQL-server-5.6. 13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1.el 6_0.1.i686 file /usr/share/mysql/charsets/keybcs2.xml from install of MySQL-server- 5.6.13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52- 1.el6_0.1.i686 file /usr/share/mysql/charsets/koi8r.xml from install of MySQL-server-5. 6.13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1. el6_0.1.i686 file /usr/share/mysql/charsets/koi8u.xml from install of MySQL-server-5. 6.13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1. el6_0.1.i686 file /usr/share/mysql/charsets/latin1.xml from install of MySQL-server-5 .6.13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1 .el6_0.1.i686 file /usr/share/mysql/charsets/latin2.xml from install of MySQL-server-5 .6.13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1 .el6_0.1.i686 file /usr/share/mysql/charsets/latin5.xml from install of MySQL-server-5 .6.13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1 .el6_0.1.i686 file /usr/share/mysql/charsets/latin7.xml from install of MySQL-server-5 .6.13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1 .el6_0.1.i686 file /usr/share/mysql/charsets/macce.xml from install of MySQL-server-5. 6.13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1. el6_0.1.i686 file /usr/share/mysql/charsets/macroman.xml from install of MySQL-server -5.6.13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52 -1.el6_0.1.i686 file /usr/share/mysql/charsets/swe7.xml from install of MySQL-server-5.6 .13-1.linux_glibc2.5.i386 conflicts with file from package mysql-libs-5.1.52-1.e l6_0.1.i686 file /usr/bin/mysqldumpslow from install of MySQL-server-5.6.13-1.linux_ glibc2.5.i386 conflicts with file from package MySQL-client-5.1.7-0.i386

MySQL，在重启mysql之后会生成之前生成过的ID_course

（1）.在MySQL里插入10条数据，自增id到11了。然后删掉其中的5条数据，下一条插入的数据id为11（这是正常的） **重启MySQL** （2）.在MySQL里插入10条数据，自增id到11了。然后删掉最后的5条数据，【重启一下MySQL之后】下一条插入的数据的id为6 请问如何让mysql的自增id始终为（1）的情景

ubuntu 16.04安装mysql出现mysql-apt-config错误_course

root@ssk:~# sudo dpkg -i mysql-apt-config_0.5.3-1_all.deb (Reading database ... 97834 files and directories currently installed.) Preparing to unpack mysql-apt-config_0.5.3-1_all.deb ... Unpacking mysql-apt-config (0.5.3-1) over (0.5.3-1) ... Setting up mysql-apt-config (0.5.3-1) ... dpkg: error processing package mysql-apt-config (--install): subprocess installed post-installation script returned error exit status 10 Errors were encountered while processing: mysql-apt-config

mysql正常启动后一直报错，直到mysql死掉_course

mysql正常启动后一直报错，直到mysql死掉后不再报错。这时候我再启动mysql，有继续报错。 希望帮忙解决，谢谢  /usr/local/mysql/bin/mysqld_safe: line 183: 8747 Killed nohup /usr/local/mysql/bin/mysqld --basedir=/usr/local/mysql --datadir=/usr/local/mysql/data --plugin-dir=/usr/local/mysqlb/plugin --log-error=VM_161_52_centos.err --pid-file=/usr/local/mysql/data/VM_161_52_centos.pid --socket=/tmp/mysql.sock --port=3306 < /dev/null >> /usr/local/mysql/data/VM_161_52_centos.err 2>&1 >> /usr/local/mysql/data/VM_161_52_centos.err 2>&1 /usr/local/mysql/bin/mysqld_safe: line 183: 9058 Killed nohup /usr/local/mysql/bin/mysqld --basedir=/usr/local/mysql --datadir=/usr/local/mysql/data --plugin-dir=/usr/local/mysqlb/plugin --log-error=VM_161_52_centos.err --pid-file=/usr/local/mysql/data/VM_161_52_centos.pid --socket=/tmp/mysql.sock --port=3306 < /dev/null >> /usr/local/mysql/data/VM_161_52_centos.err 2>&1 >> /usr/local/mysql/data/VM_161_52_centos.err 2>&1 >> /usr/local/mysql/data/VM_161_52_centos.err 2>&1 /usr/local/mysql/bin/mysqld_safe: line 183: 9506 Killed nohup /usr/local/mysql/bin/mysqld --basedir=/usr/local/mysql --datadir=/usr/local/mysql/data --plugin-dir=/usr/local/mysqlb/plugin --log-error=VM_161_52_centos.err --pid-file=/usr/local/mysql/data/VM_161_52_centos.pid --socket=/tmp/mysql.sock --port=3306 < /dev/null >> /usr/local/mysql/data/VM_161_52_centos.err 2>&1 >> /usr/local/mysql/data/VM_161_52_centos.err 2>&1 >> /usr/local/mysql/data/VM_161_52_centos.err 2>&1 >> /usr/local/mysql/data/VM_161_52_centos.err 2>&1 /usr/local/mysql/bin/mysqld_safe: line 183: 10076 Killed nohup /usr/local/mysql/bin/mysqld --basedir=/usr/local/mysql --datadir=/usr/local/mysql/data --plugin-dir=/usr/local/mysqlb/plugin --log-error=VM_161_52_centos.err --pid-file=/usr/local/mysql/data/VM_161_52_centos.pid --socket=/tmp/mysql.sock --port=3306 < /dev/null >> /usr/local/mysql/data/VM_161_52_centos.err 2>&1 >> /usr/local/mysql/data/VM_161_52_centos.err 2>&1 >> /usr/local/mysql/data/VM_161_52_centos.err 2>&1 >> /usr/local/mysql/data/VM_161_52_centos.err 2>&1 >> /usr/local/mysql/data/VM_161_52_centos.err 2>&1 /usr/local/mysql/bin/mysqld_safe: line 183: 10231 Killed nohup /usr/local/mysql/bin/mysqld --basedir=/usr/local/mysql --datadir=/usr/local/mysql/data --plugin-dir=/usr/local/mysqlb/plugin --log-error=VM_161_52_centos.err --pid-file=/usr/local/mysql/data/VM_161_52_centos.pid --socket=/tmp/mysql.sock --port=3306 < /dev/null >> /usr/local/mysql/data/VM_161_52_centos.err 2>&1 >> /usr/local/mysql/data/VM_161_52_centos.err 2>&1 >> /usr/local/mysql/data/VM_161_52_centos.err 2>&1 >> /usr/local/mysql/data/VM_161_52_centos.err 2>&1 >> /usr/local/mysql/data/VM_161_52_centos.err 2>&1 >> /usr/local/mysql/data/VM_161_52_centos.err 2>&1

如何在k8s中连接到我的mysql pod或mysql的节点？_course

<div class="post-text" itemprop="text"> <p>我在我的 k8s 上部署了一个 mysql pod，下面是配置代码，我对端口感到很困惑：</p> <pre><code>kind: Deployment ... containers: - ports: - containerPort: 3306 # @1 --- apiVersion: v1 kind: Service metadata: name: mysql labels: app: mysql spec: selector: app: mysql # way 1 ports: - port: 3306 # @2 targetPort: 3306 # @3 # way 2 type: NodePort ports: - port: 3306 targetPort: 3306 nodePort: 30600 </code></pre> <p>问题1：谁代理了这个port？问题2：这是什么port？ 我的意思是container已经暴露了port3306，而且服务也暴露了。那这在单一节点中不冲突吗？ 问题3：这个port是不是意味着其container暴露了？</p> <p>问题4：当我使用方式1部署它时，如何从pods&我的本地机器访问MySQL服务器？</p> <p>问题5：当我使用方法2部署它时，如何从pods&我的本地机器访问MySQL服务器？</p> </div>

Mac Brew Mysql 8.0.16升级8.0.17 出现BUG_course

最开始我用brew安装了mysql8.0.16(brew install mysql)，然而一次brew自动更新，将mysql自动更新到8.0.17，但是以前做了一些配置，不清楚为什么始终报错找不到8.0.16（黑人问号）当然找不到16，因为更新后是17啊，然后谷歌了问题搜不到答案，大概是没有人和我出现相同问题，搜索了有关“完全删除mysql重装”、“mac brew 重装mysql”、“brew mysql环境变量配置”、“mac软连接配置”等一系列问题始终无法解决，尝试了安装低版本mysql5.7（brew install mysql@5.7）始终报错找不到8.0.16，但是能确定mysql正常使用，因为用完整路径名访问mysql -uroot 仍然可以正常使用，出现这个原因造成的仅仅是在初始终端下直接输入mysql -uroot报错找不到8.0.16，我脑洞大开找到了一种解决方式，将17版本的文件夹名改成16，可以正常运行，然而这并不是长久之计我还是希望寻求病因及答案。希望大佬能给予萌新答案quq    没错，时隔一日，我又发现了后遗症。。。。。。 就是我手动修改文件夹名字伪装降级之后，虽然可以正常使用mysql，但是一旦服务没启动，例如刚开机，他就会报错（如下图），然后需要手动把名字改回原来的版本，然后启动mysql服务，然后再改成旧版本，然后启动mysql。  我好难啊。。。。。。

Linux 安装 MySQL 到mysql_install_db --user=mysql执行出错_course

linux 手动编译安装 mysql 完成后 执行 /usr/local/mysql/bin/mysql_install_db --user=mysql 出错.. 以下是错误信息.. 我还是没太明白... 帮忙看下... Installing MySQL system tables... 110823 20:55:57 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead. /usr/local/mysql/libexec/mysqld: File './mysql-bin.index' not found (Errcode: 13) 110823 20:55:57 [ERROR] Aborting 110823 20:55:57 [Note] /usr/local/mysql/libexec/mysqld: Shutdown complete Installation of system tables failed! Examine the logs in /var/lib/mysql for more information. You can try to start the mysqld daemon with: shell> /usr/local/mysql/libexec/mysqld --skip-grant & and use the command line tool /usr/local/mysql/bin/mysql to connect to the mysql database and look at the grant tables: shell> /usr/local/mysql/bin/mysql -u root mysql mysql> show tables Try 'mysqld --help' if you have problems with paths. Using --log gives you a log in /var/lib/mysql that may be helpful. Please consult the MySQL manual section 'Problems running mysql_install_db', and the manual section that describes problems on your OS. Another information source are the MySQL email archives available at http://lists.mysql.com/. Please check all of the above before mailing us! And remember, if you do mail us, you MUST use the /usr/local/mysql/bin/mysqlbug script!

关于MySQL移植到arm的问题_course

移植过去后尝试使用指令 ./mysql_install_db --user=root --force --ba sedir=/usr/local/mysql --datadir=var/lib/mysql 时出现以下错误： /usr/local/mysql/bin/my_print_defaults: line 2: T: not found /usr/local/mysql/bin/my_print_defaults: line 8: syntax error: unexpected ")" /usr/local/mysql/bin/my_print_defaults: line 1: ELF

: not found Installing MySQL system tables... /usr/local/mysql/libexec/mysqld: line 1: syntax error: unexpected "(" 网上查询了说是shell 不一致的问题： 但是我修改本地PC配置为： /home/shenyuan/nfs_root # echo $0 sh /home/shenyuan/nfs_root # ls -l /bin/sh lrwxrwxrwx 1 root root 12 Jun 30 22:10 /bin/sh -> /bin/busybox arm端配置为： root@freescale /usr/local/mysql/bin$ echo $0 -sh root@freescale /usr/local/mysql/bin$ ls -l /bin/sh lrwxrwxrwx 1 root root 7 Jun 30 2018 /bin/sh -> busybox root@freescale /usr/local/mysql/bin$ 还是出现一样的问题！

安装mysql 配置时报错_course

Beginning configuration step: Initializing Database Deleting the data directory from a previous (failed) configuration... Attempting to run MySQL Server with --initialize-insecure option... Starting process for MySQL Server 8.0.13... Starting process with command: C:\Program Files\MySQL\MySQL Server 8.0\bin\mysqld.exe --defaults-file="C:\ProgramData\MySQL\MySQL Server 8.0\my.ini" --console --initialize-insecure=on --lower-case-table-names=1... 2018-11-01T16:28:35.442346Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release. 2018-11-01T16:28:35.442449Z 0 [System] [MY-013169] [Server] C:\Program Files\MySQL\MySQL Server 8.0\bin\mysqld.exe (mysqld 8.0.13) initializing of server in progress as process 12668 mysqld: File '.\绁炴鑸?bin.index' not found (OS errno 2 - No such file or directory) 2018-11-01T16:28:35.449875Z 0 [ERROR] [MY-013236] [Server] Newly created data directory C:\ProgramData\MySQL\MySQL Server 8.0\Data\ is unusable. You can safely remove it. 2018-11-01T16:28:35.450071Z 0 [ERROR] [MY-010119] [Server] Aborting 2018-11-01T16:28:35.450295Z 0 [System] [MY-010910] [Server] C:\Program Files\MySQL\MySQL Server 8.0\bin\mysqld.exe: Shutdown complete (mysqld 8.0.13) MySQL Community Server - GPL. Process for mysqld, with ID 12668, was run successfully and exited with code 1. Failed to start process for MySQL Server 8.0.13. Database initialization failed. Ended configuration step: Initializing Database

docker mysql创建密码和权限的问题_course

 这是docker logs tensquare_mysql 这个命令 从头说下问题连接虚拟机，启动docker 创建mysql镜像（下载就不说了） docker run -di --name tensquare_mysql -p 3306:3306 -e MYSQL_ROOT_PASSWORD=rootroot centos/mysql-57-centos7 到这步的话就发现一个问题，就是进入bash后，mysql -uroot -p的密码不对，默认为空而不是rootroot 然后我通过空密码进入mysql后修改了root的密码 alter user 'root'@'localhost' IDENTIFIED BY 'rootroot' 在bash可以通过，但是通过mysqlworkbench连接工具连接不了 并且在stop这个镜像后从新启动不了，这就是logs的提示，对docker不太熟，也是照着案例做项目，请大神解惑

为什么MySql 5.5.6服务器绿色版不需要安装mysql？_course

之前听别人说安装mysql后卸载很麻烦，我在网上下载了MySql 5.5.6服务器绿色版(一打开就是navicat的界面跳过)，直接点击就可以使用。可是网上说NavicatForMySql只是mysql这个数据库的图形化管理界面，像MyYog一样，需要你安装mysql在先，才可以使用。  很怀疑我的是mysql服务器与Navicat for mysql的结合绿色版（笑哭，真方便）

如何设置 MySQL 日期时间列的默认值？_course

<div class="post-text" itemprop="text"> 如何设置MySQL Datetime列的默认值? 在SQL Server中是 <code>getdate()</code>. MySQL的等效功能是什么？ 如果这是一个原因的话，那么我来使用MySQL5.x尝试一下。</p> </div> <p>转载于:https://stackoverflow.com/questions/168736/how-do-you-set-a-default-value-for-a-mysql-datetime-column</p>

qt隐式调用mysql库函数_course

系统是64位，安装的qt也是64位的，vs2013也是64位的，mysql在c盘，采用隐式调用，用qt编译项目的时候，已经在Pro中添加了LIBS += -LC:\mysql\lib -llibmysql，在头文件中也写了#include <C:/mysql/include/mysql.h>，可是项目中有mysql_init的时候，编译时候报错无法解析的外部符号mysql_init，请教是什么问题啊？？？？