mysql安装失败怎么办?InnoDB: Error: unable to create temporary file

我想请问一下,mysql安装失败怎么办?图片描述

我自己电脑本身是装过mysql的,但之前卸载过,我百度查了一下怎么卸载干净,其中参考了https://blog.csdn.net/weixin_41792162/article/details/89921559
https://blog.csdn.net/qq_34266804/article/details/82822416 等文章,但每次重装还是同样的问题,我也试过mysql8.0版本的重装也都一样,试过使用命令行和像图片引导式的安装,都是同样的问题,数据库初始化不了,
根据提示的【error】
我试过
https://blog.csdn.net/fengda2870/article/details/12677685 等文章的方案,但还是不可以,我想请问下各位大佬这怎么解决?

Csdn user default icon
上传中...
上传图片
插入图片
抄袭、复制答案,以达到刷声望分或其他目的的行为,在CSDN问答是严格禁止的,一经发现立刻封号。是时候展现真正的技术了!
其他相关推荐
mysql InnoDB: Error: "mysql"."innodb_table_stats
附上错误日志: 2015-06-23 22:39:06 1252 [Note] Giving 0 client threads a chance to die gracefully 2015-06-23 22:39:06 1252 [Note] Shutting down slave threads 2015-06-23 22:39:06 1252 [Note] Forcefully disconnecting 0 remaining clients 2015-06-23 22:39:06 1252 [Note] Binlog end 2015-06-23 22:39:09 1252 [Note] Shutting down plugin 'partition' 2015-06-23 22:39:09 1252 [Note] Shutting down plugin 'BLACKHOLE' 2015-06-23 22:39:09 1252 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA' 2015-06-23 22:39:09 1252 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES' 2015-06-23 22:39:09 1252 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES' 2015-06-23 22:39:09 1252 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS' 2015-06-23 22:39:09 1252 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN' 2015-06-23 22:39:09 1252 [Note] Shutting down plugin 'INNODB_SYS_FIELDS' 2015-06-23 22:39:09 1252 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS' 2015-06-23 22:39:09 1252 [Note] Shutting down plugin 'INNODB_SYS_INDEXES' 2015-06-23 22:39:09 1252 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS' 2015-06-23 22:39:09 1252 [Note] Shutting down plugin 'INNODB_SYS_TABLES' 2015-06-23 22:39:09 1252 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE' 2015-06-23 22:39:09 1252 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE' 2015-06-23 22:39:09 1252 [Note] Shutting down plugin 'INNODB_FT_CONFIG' 2015-06-23 22:39:09 1252 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED' 2015-06-23 22:39:09 1252 [Note] Shutting down plugin 'INNODB_FT_DELETED' 2015-06-23 22:39:09 1252 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD' 2015-06-23 22:39:09 1252 [Note] Shutting down plugin 'INNODB_METRICS' 2015-06-23 22:39:09 1252 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS' 2015-06-23 22:39:09 1252 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU' 2015-06-23 22:39:09 1252 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE' 2015-06-23 22:39:09 1252 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET' 2015-06-23 22:39:09 1252 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX' 2015-06-23 22:39:09 1252 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET' 2015-06-23 22:39:09 1252 [Note] Shutting down plugin 'INNODB_CMPMEM' 2015-06-23 22:39:09 1252 [Note] Shutting down plugin 'INNODB_CMP_RESET' 2015-06-23 22:39:09 1252 [Note] Shutting down plugin 'INNODB_CMP' 2015-06-23 22:39:09 1252 [Note] Shutting down plugin 'INNODB_LOCK_WAITS' 2015-06-23 22:39:09 1252 [Note] Shutting down plugin 'INNODB_LOCKS' 2015-06-23 22:39:09 1252 [Note] Shutting down plugin 'INNODB_TRX' 2015-06-23 22:39:09 1252 [Note] Shutting down plugin 'InnoDB' 2015-06-23 22:39:09 1252 [Note] InnoDB: FTS optimize thread exiting. 2015-06-23 22:39:09 1252 [Note] InnoDB: Starting shutdown... 2015-06-23 22:39:12 1252 [Note] InnoDB: Shutdown completed; log sequence number 44832642 2015-06-23 22:39:12 1252 [Note] Shutting down plugin 'ARCHIVE' 2015-06-23 22:39:12 1252 [Note] Shutting down plugin 'MyISAM' 2015-06-23 22:39:12 1252 [Note] Shutting down plugin 'CSV' 2015-06-23 22:39:12 1252 [Note] Shutting down plugin 'MRG_MYISAM' 2015-06-23 22:39:12 1252 [Note] Shutting down plugin 'MEMORY' 2015-06-23 22:39:12 1252 [Note] Shutting down plugin 'sha256_password' 2015-06-23 22:39:12 1252 [Note] Shutting down plugin 'mysql_old_password' 2015-06-23 22:39:12 1252 [Note] Shutting down plugin 'mysql_native_password' 2015-06-23 22:39:12 1252 [Note] Shutting down plugin 'binlog' 2015-06-23 22:39:12 1252 [Note] /usr/sbin/mysqld: Shutdown complete 150623 22:39:12 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 150623 22:39:39 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 2015-06-23 22:39:39 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 2015-06-23 22:39:39 1190 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000) 2015-06-23 22:39:39 1190 [Warning] Buffered warning: Changed limits: table_cache: 431 (requested 2000) 2015-06-23 22:39:39 1190 [Note] Plugin 'FEDERATED' is disabled. 2015-06-23 22:39:39 1190 [Note] InnoDB: Using atomics to ref count buffer pool pages 2015-06-23 22:39:39 1190 [Note] InnoDB: The InnoDB memory heap is disabled 2015-06-23 22:39:39 1190 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2015-06-23 22:39:39 1190 [Note] InnoDB: Memory barrier is not used 2015-06-23 22:39:39 1190 [Note] InnoDB: Compressed tables use zlib 1.2.3 2015-06-23 22:39:39 1190 [Note] InnoDB: Using Linux native AIO 2015-06-23 22:39:39 1190 [Note] InnoDB: Not using CPU crc32 instructions 2015-06-23 22:39:39 1190 [Note] InnoDB: Initializing buffer pool, size = 1.0G 2015-06-23 22:39:40 1190 [Note] InnoDB: Completed initialization of buffer pool 2015-06-23 22:39:40 1190 [Note] InnoDB: Highest supported file format is Barracuda. 2015-06-23 22:39:40 1190 [Note] InnoDB: 128 rollback segment(s) are active. 2015-06-23 22:39:40 1190 [Note] InnoDB: Waiting for purge to start 2015-06-23 22:39:40 1190 [Note] InnoDB: 5.6.22 started; log sequence number 44832642 2015-06-23 22:39:41 1190 [Note] Server hostname (bind-address): '*'; port: 3306 2015-06-23 22:39:41 1190 [Note] IPv6 is available. 2015-06-23 22:39:41 1190 [Note] - '::' resolves to '::'; 2015-06-23 22:39:41 1190 [Note] Server socket created on IP: '::'. 2015-06-23 22:39:41 1190 [ERROR] Incorrect definition of table mysql.db: expected column 'User' at position 2 to have type char(16), found type char(80). 2015-06-23 22:39:41 1190 [ERROR] Incorrect definition of table mysql.event: expected column 'definer' at position 3 to have type char(77), found type char(141). 2015-06-23 22:39:41 1190 [ERROR] Incorrect definition of table mysql.event: expected column 'sql_mode' at position 14 to have type set('REAL_AS_FLOAT','PIPES_AS_CONCAT','ANSI_QUOTES','IGNORE_SPACE','NOT_USED','ONLY_FULL_GROUP_BY','NO_UNSIGNED_SUBTRACTION','NO_DIR_IN_CREATE','POSTGRESQL','ORACLE','MSSQL','DB2','MAXDB','NO_KEY_OPTIONS','NO_TABLE_OPTIONS','NO_FIELD_OPTIONS','MYSQL323','MYSQL40','ANSI','NO_AUTO_VALUE_ON_ZERO','NO_BACKSLASH_ESCAPES','STRICT_TRANS_TABLES','STRICT_ALL_TABLES','NO_ZERO_IN_DATE','NO_ZERO_DATE','INVALID_DATES','ERROR_FOR_DIVISION_BY_ZERO','TRADITIONAL','NO_AUTO_CREATE_USER','HIGH_NOT_PRECEDENCE','NO_ENGINE_SUBSTITUTION','PAD_CHAR_TO_FULL_LENGTH'), found type set('REAL_AS_FLOAT','PIPES_AS_CONCAT','ANSI_QUOTES','IGNORE_SPACE','IGNORE_BAD_TABLE_OPTIONS','ONLY_FULL_GROUP_BY','NO_UNSIGNED_SUBTRACTION','NO_DIR_IN_CREATE','POSTGRESQL','ORACLE','MSSQL','DB2','MAXDB','NO_KEY_OPTIONS','NO_TABLE_OPTIONS','NO_FIELD_OPTIONS','MYSQL323','MYSQL40','ANSI','NO_AUTO_VALUE_ON_ZERO','NO_BACKSLASH_ESCAPES','STRICT_TRANS_TABLES','STRICT_A 2015-06-23 22:39:41 1190 [ERROR] Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler. 2015-06-23 22:39:41 1190 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.6.22' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL) 2015-06-23 23:00:47 7f7038bc0700 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch). 2015-06-23 23:00:47 7f7038bc0700 InnoDB: Error: Fetch of persistent statistics requested for table "moodle"."mdl_config" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
mysql服务启动报错1607 求助大神!
错误日志: InnoDB: The first specified data file .\ibdata1 did not exist: InnoDB: a new database to be created! 160817 17:41:01 InnoDB: Setting file .\ibdata1 size to 10 MB InnoDB: Database physically writes the file full: wait... 160817 17:41:02 InnoDB: Log file .\ib_logfile0 did not exist: new to be created InnoDB: Setting log file .\ib_logfile0 size to 10 MB InnoDB: Database physically writes the file full: wait... 160817 17:41:02 InnoDB: Log file .\ib_logfile1 did not exist: new to be created InnoDB: Setting log file .\ib_logfile1 size to 10 MB InnoDB: Database physically writes the file full: wait... InnoDB: Doublewrite buffer not found: creating new InnoDB: Doublewrite buffer created InnoDB: Creating foreign key constraint system tables InnoDB: Foreign key constraint system tables created 160817 17:41:03 InnoDB: Started; log sequence number 0 0 160817 17:41:03 [Note] E:\mysqlserver\bin\mysqld-nt: ready for connections. Version: '5.0.22-community-nt' socket: '' port: 3306 MySQL Community Edition (GPL) 160826 16:38:33 [Note] E:\mysqlserver\bin\mysqld-nt: Normal shutdown 160826 16:38:35 InnoDB: Starting shutdown... 160826 16:38:38 InnoDB: Shutdown completed; log sequence number 0 133556 160826 16:38:38 [Note] E:\mysqlserver\bin\mysqld-nt: Shutdown complete 160826 16:40:24 InnoDB: Started; log sequence number 0 133556 160826 16:40:25 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist 160827 17:28:58 InnoDB: Started; log sequence number 0 133556 160827 17:28:58 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist 160827 19:25:59 InnoDB: Started; log sequence number 0 133556 160827 19:25:59 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist 160827 19:26:03 InnoDB: Started; log sequence number 0 133556 160827 19:26:03 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist 160827 19:26:07 InnoDB: Started; log sequence number 0 133556 160827 19:26:07 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist 160827 19:32:24 InnoDB: Started; log sequence number 0 133556 160827 19:32:24 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist 160827 19:36:18 InnoDB: Started; log sequence number 0 133556 160827 19:36:18 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist 160827 19:37:25 InnoDB: Started; log sequence number 0 133556 160827 19:37:26 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist 160827 19:40:55 InnoDB: Started; log sequence number 0 133556 160827 19:40:55 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist InnoDB: The first specified data file .\ibdata1 did not exist: InnoDB: a new database to be created! 160827 19:50:49 InnoDB: Setting file .\ibdata1 size to 10 MB InnoDB: Database physically writes the file full: wait... 160827 19:50:49 InnoDB: Log file .\ib_logfile0 did not exist: new to be created InnoDB: Setting log file .\ib_logfile0 size to 10 MB InnoDB: Database physically writes the file full: wait... 160827 19:50:50 InnoDB: Log file .\ib_logfile1 did not exist: new to be created InnoDB: Setting log file .\ib_logfile1 size to 10 MB InnoDB: Database physically writes the file full: wait... InnoDB: Doublewrite buffer not found: creating new InnoDB: Doublewrite buffer created InnoDB: Creating foreign key constraint system tables InnoDB: Foreign key constraint system tables created 160827 19:50:50 InnoDB: Started; log sequence number 0 0 160827 19:50:50 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist 160827 19:50:55 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... 160827 19:50:55 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 36808. InnoDB: Doing recovery: scanned up to log sequence number 0 43655 160827 19:50:55 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 160827 19:50:56 InnoDB: Started; log sequence number 0 43655 160827 19:50:56 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist 160827 19:58:23 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... 160827 19:58:23 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 36808. InnoDB: Doing recovery: scanned up to log sequence number 0 43655 160827 19:58:23 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 160827 19:58:24 InnoDB: Started; log sequence number 0 43655 160827 19:58:24 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist InnoDB: The first specified data file .\ibdata1 did not exist: InnoDB: a new database to be created! 160827 20:00:24 InnoDB: Setting file .\ibdata1 size to 10 MB InnoDB: Database physically writes the file full: wait... 160827 20:00:24 InnoDB: Log file .\ib_logfile0 did not exist: new to be created InnoDB: Setting log file .\ib_logfile0 size to 10 MB InnoDB: Database physically writes the file full: wait... 160827 20:00:24 InnoDB: Log file .\ib_logfile1 did not exist: new to be created InnoDB: Setting log file .\ib_logfile1 size to 10 MB InnoDB: Database physically writes the file full: wait... InnoDB: Doublewrite buffer not found: creating new InnoDB: Doublewrite buffer created InnoDB: Creating foreign key constraint system tables InnoDB: Foreign key constraint system tables created 160827 20:00:25 InnoDB: Started; log sequence number 0 0 160827 20:00:25 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist 160827 20:01:54 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... 160827 20:01:54 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 36808. InnoDB: Doing recovery: scanned up to log sequence number 0 43655 160827 20:01:54 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 160827 20:01:55 InnoDB: Started; log sequence number 0 43655 160827 20:01:55 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist 160827 20:02:09 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... 160827 20:02:09 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 36808. InnoDB: Doing recovery: scanned up to log sequence number 0 43655 160827 20:02:09 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 160827 20:02:10 InnoDB: Started; log sequence number 0 43655 160827 20:02:10 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist 160827 21:37:52 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... 160827 21:37:52 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 36808. InnoDB: Doing recovery: scanned up to log sequence number 0 43655 160827 21:37:52 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 160827 21:37:52 InnoDB: Started; log sequence number 0 43655 160827 21:37:52 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist
服务器断电后mysql无法启动
因意外导致服务器断电,重启后发现mysql起不来了 ``` [root@cacti ~]# service mysqld restart 停止 mysqld: [确定] MySQL Daemon failed to start. 正在启动 mysqld: [失败] ``` 查看日志: ``` [root@cacti ~]# tail -100 /var/log/mysqld.log 150520 12:21:12 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 150520 12:21:12 InnoDB: Initializing buffer pool, size = 8.0M 150520 12:21:12 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 2 1552263436 150520 12:21:12 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... 150520 12:21:12 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 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: Database page corruption on disk or a failed InnoDB: file read of page 206. InnoDB: You may have to recover from a backup. 150520 12:21:12 InnoDB: Page dump in ascii and hex (16384 bytes): len 16384; hex cc507667000000ce0000000000000000000000025cabb0bc000200000000000000000000000000021e751eb0ffffffff0000ffffffff000000021dbb0000000000000002123200000001000000ce002c000000ce002c000000000304a196000000000304a1970001011000000000000000000000014....... .... .... .... oDB: End of page dump 150520 12:21:12 InnoDB: Page checksum 3392922109, prior-to-4.0.14-form checksum 1831220034 InnoDB: stored checksum 3427825255, prior-to-4.0.14-form stored checksum 2455963898 InnoDB: Page lsn 2 1554755772, low 4 bytes of lsn at page end 1556408857 InnoDB: Page number (if stored to page already) 206, InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0 InnoDB: Page may be an update undo log page InnoDB: Database page corruption on disk or a failed InnoDB: file read of page 206. InnoDB: You may have to recover from a backup. InnoDB: It is also possible that your operating InnoDB: system has corrupted its own file cache InnoDB: and rebooting your computer removes the InnoDB: error. InnoDB: If the corrupt page is an index page InnoDB: you can also try to fix the corruption InnoDB: by dumping, dropping, and reimporting InnoDB: the corrupt table. You can use CHECK InnoDB: TABLE to scan your table for corruption. InnoDB: See also http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. InnoDB: Ending processing because of a corrupt database page. 150520 12:21:12 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended ``` mysql新手一个,希望大家能帮帮忙分析下,谢谢!
xtrabackup备份并恢复到新mysql中时出错
各位用过xtrabackup做主从搭建的时候,从库搭起来后没法正常访问,可能因为备份出来的单库文件过大,导致新的mysql服务起来后,那个库没法访问;增加innodb_force_recovery配置强制后,能访问表数据,但是无法创建表了。如果利用单表备份的话,一切正常,再根据日志显示如下,觉得可能是因为文件过大导致,各位有解决过吗,先谢过了: 2017-04-18 09:57:51 18963 [ERROR] InnoDB: InnoDB: Unable to allocate memory of size 18446744073709540768. 2017-04-18 09:57:51 7f6376233700 InnoDB: Assertion failure in thread 140065160509184 in file ha_innodb.cc line 18178 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html InnoDB: about forcing recovery.
mysql非安装版无法启动 报1067错误
在网上查说是配置文件的事。 my.ini复制自my_small.ini。 只增加了 mysql字段 basedir = D:/mysql-5.5.24-winx64 datadir = D:/mysql-5.5.24-winx64/data character-set-server=utf8 client字段 default-character-set = utf8 另外在安装时候cmd使用管理员身份启动的。是不是这个有影响??? 错误日志: 140217 9:59:30 [Note] Plugin 'FEDERATED' is disabled. 140217 9:59:30 InnoDB: The InnoDB memory heap is disabled 140217 9:59:30 InnoDB: Mutexes and rw_locks use Windows interlocked functions 140217 9:59:30 InnoDB: Compressed tables use zlib 1.2.3 140217 9:59:30 InnoDB: Initializing buffer pool, size = 128.0M 140217 9:59:30 InnoDB: Completed initialization of buffer pool InnoDB: The first specified data file .\ibdata1 did not exist: InnoDB: a new database to be created! 140217 9:59:30 InnoDB: Setting file .\ibdata1 size to 10 MB InnoDB: Database physically writes the file full: wait... 140217 9:59:30 InnoDB: Log file .\ib_logfile0 did not exist: new to be created InnoDB: Setting log file .\ib_logfile0 size to 5 MB InnoDB: Database physically writes the file full: wait... 140217 9:59:30 InnoDB: Log file .\ib_logfile1 did not exist: new to be created InnoDB: Setting log file .\ib_logfile1 size to 5 MB InnoDB: Database physically writes the file full: wait... InnoDB: Doublewrite buffer not found: creating new InnoDB: Doublewrite buffer created InnoDB: 127 rollback segment(s) active. InnoDB: Creating foreign key constraint system tables InnoDB: Foreign key constraint system tables created 140217 9:59:31 InnoDB: Waiting for the background threads to start 140217 9:59:32 InnoDB: 1.1.8 started; log sequence number 0 **140217 9:59:32 [ERROR] MySQL: unknown variable 'default-character-set=gbk'** 140217 9:59:32 [ERROR] Aborting 140217 9:59:32 InnoDB: Starting shutdown... 140217 9:59:33 InnoDB: Shutdown completed; log sequence number 1595675 140217 9:59:33 [Note] MySQL: Shutdown complete 各种查资料各种解决不了。求大神帮忙。 附加:很神奇的是为什么会有 unknown variable 'default-character-set=gbk' 我根本就没有设置default-character-set=gbk,设置了default-character-set=tutf8也还是这个错误。
linux下mysql启动失败
在一次重启linux服务器之后,发现mysql启动不了了,这个是日志 170225 0:46:41 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead. 170225 0:46:41 [Note] Plugin 'FEDERATED' is disabled. 170225 0:46:41 InnoDB: The InnoDB memory heap is disabled 170225 0:46:41 InnoDB: Mutexes and rw_locks use GCC atomic builtins 170225 0:46:41 InnoDB: Compressed tables use zlib 1.2.8 170225 0:46:41 InnoDB: Using Linux native AIO 170225 0:46:41 InnoDB: Initializing buffer pool, size = 128.0M InnoDB: mmap(137363456 bytes) failed; errno 12 170225 0:46:41 InnoDB: Completed initialization of buffer pool 170225 0:46:41 InnoDB: Fatal error: cannot allocate memory for the buffer pool 170225 0:46:41 [ERROR] Plugin 'InnoDB' init function returned error. 170225 0:46:41 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 170225 0:46:41 [ERROR] Unknown/unsupported storage engine: InnoDB 170225 0:46:41 [ERROR] Aborting 170225 0:46:41 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead. 170225 0:46:41 [Note] Plugin 'FEDERATED' is disabled. 170225 0:46:41 InnoDB: The InnoDB memory heap is disabled 170225 0:46:41 InnoDB: Mutexes and rw_locks use GCC atomic builtins 170225 0:46:41 InnoDB: Compressed tables use zlib 1.2.8 170225 0:46:41 InnoDB: Using Linux native AIO 170225 0:46:41 InnoDB: Initializing buffer pool, size = 128.0M InnoDB: mmap(137363456 bytes) failed; errno 12 170225 0:46:41 InnoDB: Completed initialization of buffer pool 170225 0:46:41 InnoDB: Fatal error: cannot allocate memory for the buffer pool 170225 0:46:41 [ERROR] Plugin 'InnoDB' init function returned error. 170225 0:46:41 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 170225 0:46:41 [ERROR] Unknown/unsupported storage engine: InnoDB 170225 0:46:41 [ERROR] Aborting
mysql还原后启动出问题
2018-04-15 15:18:11 24653 [Note] Plugin 'FEDERATED' is disabled. 2018-04-15 15:18:11 24653 [Note] InnoDB: Using atomics to ref count buffer pool pages 2018-04-15 15:18:11 24653 [Note] InnoDB: The InnoDB memory heap is disabled 2018-04-15 15:18:11 24653 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2018-04-15 15:18:11 24653 [Note] InnoDB: Memory barrier is not used 2018-04-15 15:18:11 24653 [Note] InnoDB: Compressed tables use zlib 1.2.3 2018-04-15 15:18:11 24653 [Note] InnoDB: Using Linux native AIO 2018-04-15 15:18:11 24653 [Note] InnoDB: Using CPU crc32 instructions 2018-04-15 15:18:11 24653 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2018-04-15 15:18:11 24653 [Note] InnoDB: Completed initialization of buffer pool 2018-04-15 15:18:11 24653 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB 2018-04-15 15:18:11 24653 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB 2018-04-15 15:18:12 24653 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0 2018-04-15 15:18:12 24653 [Warning] InnoDB: New log files created, LSN=48585617787 2018-04-15 15:18:12 24653 [Note] InnoDB: Highest supported file format is Barracuda. 2018-04-15 15:18:12 7ffa03794740 InnoDB: Error: page 7 log sequence number 254015752729 InnoDB: is in the future! Current system log sequence number 48585617932. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html InnoDB: for more information. 2018-04-15 15:18:12 7ffa03794740 InnoDB: Error: page 1 log sequence number 249801886007 InnoDB: is in the future! Current system log sequence number 48585617932. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html InnoDB: for more information. 2018-04-15 15:18:12 7ffa03794740 InnoDB: Error: page 3 log sequence number 73815057441 InnoDB: is in the future! Current system log sequence number 48585617932. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See
急求关于mysql数据库自动停止的问题
数据库:mysql5.6.17 OS: 2008SERVER 32位 业务正在运行,突然数据库就自动停止服务了,日志如下: 2016-12-03 11:14:06 4860 [ERROR] Can't create thread to handle request (errno= 12) 2016-12-03 11:15:25 4860 [ERROR] InnoDB: InnoDB: Unable to allocate memory of size 1065016. 2016-12-03 11:15:25 1398 InnoDB: Assertion failure in thread 5016 in file ha_innodb.cc line 17080 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 2016-12-03 11:15:39 4860 [ERROR] Error log throttle: 7 'Can't create thread to handle new connection' error(s) suppressed 2016-12-03 11:15:39 4860 [ERROR] Can't create thread to handle request (errno= 12) 2016-12-03 11:16:40 4860 [ERROR] Error log throttle: 963 'Can't create thread to handle new connection' error(s) suppressed 2016-12-03 11:16:40 4860 [ERROR] Can't create thread to handle request (errno= 12) 2016-12-03 11:18:00 5108 [Note] Plugin 'FEDERATED' is disabled. 2016-12-03 11:18:00 171c InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator. 2016-12-03 11:18:00 5108 [Note] InnoDB: Using atomics to ref count buffer pool pages 2016-12-03 11:18:00 5108 [Note] InnoDB: The InnoDB memory heap is disabled 2016-12-03 11:18:00 5108 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 2016-12-03 11:18:00 5108 [Note] InnoDB: Compressed tables use zlib 1.2.3 2016-12-03 11:18:00 5108 [Note] InnoDB: Not using CPU crc32 instructions 2016-12-03 11:18:00 5108 [Note] InnoDB: Initializing buffer pool, size = 823.0M 2016-12-03 11:18:00 5108 [Note] InnoDB: Completed initialization of buffer pool 2016-12-03 11:18:00 5108 [Note] InnoDB: Highest supported file format is Barracuda. 2016-12-03 11:18:00 5108 [Note] InnoDB: Log scan progressed past the checkpoint lsn 37892781681 2016-12-03 11:18:00 5108 [Note] InnoDB: Database was not shutdown normally! 2016-12-03 11:18:00 5108 [Note] InnoDB: Starting crash recovery. 2016-12-03 11:18:00 5108 [Note] InnoDB: Reading tablespace information from the .ibd files... 2016-12-03 11:18:04 5108 [Note] InnoDB: Restoring possible half-written data pages 2016-12-03 11:18:04 5108 [Note] InnoDB: from the doublewrite buffer... InnoDB: Doing recovery: scanned up to log sequence number 37893927335 InnoDB: 6 transaction(s) which must be rolled back or cleaned up InnoDB: in total 63 row operations to undo InnoDB: Trx id counter is 12591616 2016-12-03 11:18:05 5108 [Note] InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percent: 0 1 2 3 4 5 6 7 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 2016-12-03 11:18:06 5108 [Note] InnoDB: 128 rollback segment(s) are active. InnoDB: Starting in background the rollback of uncommitted transactions 我挂了五个tomcat搭载了nginx 。大约有100个客户端会频繁访问。想着应该没问题,但是连续两天数据库突然停止,急求大神帮忙解决,谢谢!
wampserver安装好后mysql启动不了(内有mysql日志 ),求大神帮忙!
170319 12:23:55 [Note] Plugin 'FEDERATED' is disabled. 170319 12:23:55 InnoDB: The InnoDB memory heap is disabled 170319 12:23:55 InnoDB: Mutexes and rw_locks use Windows interlocked functions 170319 12:23:55 InnoDB: Compressed tables use zlib 1.2.3 170319 12:23:55 InnoDB: Initializing buffer pool, size = 128.0M 170319 12:23:55 InnoDB: Completed initialization of buffer pool 170319 12:23:55 InnoDB: highest supported file format is Barracuda. 170319 12:23:55 InnoDB: Operating system error number 87 in a file operation. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html InnoDB: File name .\ib_logfile0 InnoDB: File operation call: 'aio read'. InnoDB: Cannot continue operation.
mysql经常挂掉,重启主机就好了
# mysq日志 > 141211 10:50:25 mysqld_safe Starting mysqld daemon with databases from /alidata/server/mysql/data > 141211 10:50:26 [Note] Plugin 'FEDERATED' is disabled. > 141211 10:50:26 InnoDB: The InnoDB memory heap is disabled > 141211 10:50:26 InnoDB: Mutexes and rw_locks use GCC atomic builtins > 141211 10:50:26 InnoDB: Compressed tables use zlib 1.2.3 > 141211 10:50:26 InnoDB: Using Linux native AIO > 141211 10:50:26 InnoDB: Initializing buffer pool, size = 128.0M > 141211 10:50:26 InnoDB: Completed initialization of buffer pool > 141211 10:50:26 InnoDB: highest supported file format is Barracuda. > InnoDB: The log sequence number in ibdata files does not match > InnoDB: the log sequence number in the ib_logfiles! > 141211 10:50:26 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... > 141211 10:50:27 InnoDB: Waiting for the background threads to start > 141211 10:50:28 InnoDB: 5.5.37 started; log sequence number 1595675 > 141211 10:50:28 [Note] Recovering after a crash using mysql-bin > 141211 10:50:28 [Note] Starting crash recovery... > 141211 10:50:28 [Note] Crash recovery finished. > 141211 10:50:28 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306 > 141211 10:50:28 [Note] - '0.0.0.0' resolves to '0.0.0.0'; > 141211 10:50:28 [Note] Server socket created on IP: '0.0.0.0'. > 141211 10:50:28 [Note] Event Scheduler: Loaded 0 events > 141211 10:50:28 [Note] /alidata/server/mysql/bin/mysqld: ready for connections. > Version: '5.5.37-log' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Server (GPL) > 141211 10:53:25 [Note] /alidata/server/mysql/bin/mysqld: Normal shutdown > > 141211 10:53:25 [Note] Event Scheduler: Purging the queue. 0 events > 141211 10:53:25 InnoDB: Starting shutdown... > 141211 10:53:26 InnoDB: Shutdown completed; log sequence number 1595675 > 141211 10:53:26 [Note] /alidata/server/mysql/bin/mysqld: Shutdown complete > > 141211 10:53:26 mysqld_safe mysqld from pid file /alidata/server/mysql/data/iZ280q00p7cZ.pid ended > 141211 10:57:45 mysqld_safe Starting mysqld daemon with databases from /alidata/server/mysql/data > 141211 10:57:46 [Note] Plugin 'FEDERATED' is disabled. > 141211 10:57:46 InnoDB: The InnoDB memory heap is disabled > 141211 10:57:46 InnoDB: Mutexes and rw_locks use GCC atomic builtins > 141211 10:57:46 InnoDB: Compressed tables use zlib 1.2.3 > 141211 10:57:46 InnoDB: Using Linux native AIO > 141211 10:57:46 InnoDB: Initializing buffer pool, size = 128.0M > 141211 10:57:46 InnoDB: Completed initialization of buffer pool > 141211 10:57:46 InnoDB: highest supported file format is Barracuda. > 141211 10:57:46 InnoDB: Waiting for the background threads to start > 141211 10:57:47 InnoDB: 5.5.37 started; log sequence number 1595675 > 141211 10:57:47 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306 > 141211 10:57:47 [Note] - '0.0.0.0' resolves to '0.0.0.0'; > 141211 10:57:47 [Note] Server socket created on IP: '0.0.0.0'. > 141211 10:57:47 [Note] Event Scheduler: Loaded 0 events > 141211 10:57:47 [Note] /alidata/server/mysql/bin/mysqld: ready for connections. > Version: '5.5.37-log' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Server (GPL) > 141213 21:56:24 [Warning] IP address '42.156.250.117' could not be resolved: Name or service not known > 141215 0:09:33 [Warning] IP address '107.150.52.84' could not be resolved: Name or service not known > 141215 2:23:23 [Warning] IP address '114.113.55.141' could not be resolved: Name or service not known > 141215 16:43:01 [Warning] IP address '61.156.44.98' could not be resolved: Name or service not known > 141216 21:56:28 [Warning] IP address '42.120.142.220' could not be resolved: Name or service not known > 141217 11:07:01 mysqld_safe Number of processes running now: 0 > 141217 11:07:01 mysqld_safe mysqld restarted > 141217 11:07:01 [Note] Plugin 'FEDERATED' is disabled. > 141217 11:07:01 InnoDB: The InnoDB memory heap is disabled > 141217 11:07:01 InnoDB: Mutexes and rw_locks use GCC atomic builtins > 141217 11:07:01 InnoDB: Compressed tables use zlib 1.2.3 > 141217 11:07:01 InnoDB: Using Linux native AIO > 141217 11:07:01 InnoDB: Initializing buffer pool, size = 128.0M > InnoDB: mmap(137363456 bytes) failed; errno 12 > 141217 11:07:01 InnoDB: Completed initialization of buffer pool > 141217 11:07:01 InnoDB: Fatal error: cannot allocate memory for the buffer pool > 141217 11:07:01 [ERROR] Plugin 'InnoDB' init function returned error. > 141217 11:07:01 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. > 141217 11:07:01 [ERROR] Unknown/unsupported storage engine: InnoDB > 141217 11:07:01 [ERROR] Aborting > > 141217 11:07:01 [Note] /alidata/server/mysql/bin/mysqld: Shutdown complete > > 141217 11:07:01 mysqld_safe mysqld from pid file /alidata/server/mysql/data/iZ280q00p7cZ.pid ended > 141217 11:09:15 mysqld_safe Starting mysqld daemon with databases from /alidata/server/mysql/data > 141217 11:09:15 [Note] Plugin 'FEDERATED' is disabled. > 141217 11:09:15 InnoDB: The InnoDB memory heap is disabled > 141217 11:09:15 InnoDB: Mutexes and rw_locks use GCC atomic builtins > 141217 11:09:15 InnoDB: Compressed tables use zlib 1.2.3 > 141217 11:09:15 InnoDB: Using Linux native AIO > 141217 11:09:15 InnoDB: Initializing buffer pool, size = 128.0M > InnoDB: mmap(137363456 bytes) failed; errno 12 > 141217 11:09:15 InnoDB: Completed initialization of buffer pool > 141217 11:09:15 InnoDB: Fatal error: cannot allocate memory for the buffer pool > 141217 11:09:15 [ERROR] Plugin 'InnoDB' init function returned error. > 141217 11:09:15 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. > 141217 11:09:15 [ERROR] Unknown/unsupported storage engine: InnoDB > 141217 11:09:15 [ERROR] Aborting > > 141217 11:09:15 [Note] /alidata/server/mysql/bin/mysqld: Shutdown complete > > 141217 11:09:15 mysqld_safe mysqld from pid file /alidata/server/mysql/data/iZ280q00p7cZ.pid ended
mysql频繁重新启动,大神帮忙看看
160831 16:32:10 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 160831 16:32:10 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead. 160831 16:32:10 InnoDB: Initializing buffer pool, size = 8.0M 160831 16:32:10 InnoDB: Completed initialization of buffer pool InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 35 row operations to undo InnoDB: Trx id counter is 0 112437760 160831 16:32:10 InnoDB: Started; log sequence number 1 255213035 InnoDB: Starting in background the rollback of uncommitted transactions InnoDB: Cleaning up trx with id 0 2496008 160831 16:32:10 InnoDB: Rollback of non-prepared transactions completed 160831 16:32:10 [Note] Event Scheduler: Loaded 0 events 160831 16:32:10 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.73-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution InnoDB: error in sec index entry update in InnoDB: index `history_uint_1` of table `zabbix`.`history_uint` InnoDB: tuple DATA TUPLE: 3 fields; 0: len 8; hex 0000000000005fd2; asc _ ;; 1: len 4; hex d771e21f; asc q ;; 2: len 6; hex 000000219c60; asc ! `;; InnoDB: record PHYSICAL RECORD: n_fields 3; compact format; info bits 32 0: len 8; hex 0000000000005fd2; asc _ ;; 1: len 4; hex d771e1e3; asc q ;; 2: len 6; hex 000000219a50; asc ! P;; TRANSACTION 0 112437763, ACTIVE 0 sec, process no 17925, OS thread id 140519254370064 updating or deleting, thread declared inside InnoDB 497 mysql tables in use 1, locked 1 5 lock struct(s), heap size 1216, 5 row lock(s), undo log entries 2 MySQL thread id 4, query id 11 localhost zabbix updating delete from history_uint where itemid=24530 and clock<1467095587 InnoDB: Submit a detailed bug report to http://bugs.mysql.com InnoDB: error in sec index entry update in InnoDB: index `history_uint_1` of table `zabbix`.`history_uint` InnoDB: tuple DATA TUPLE: 3 fields; 0: len 8; hex 0000000000005fd2; asc _ ;; 1: len 4; hex d771e25c; asc q \;; 2: len 6; hex 000000219e3e; asc ! >;; InnoDB: record PHYSICAL RECORD: n_fields 3; compact format; info bits 32 0: len 8; hex 0000000000005fd2; asc _ ;; 1: len 4; hex d771e1e3; asc q ;; 2: len 6; hex 000000219a50; asc ! P;; TRANSACTION 0 112437763, ACTIVE 0 sec, process no 17925, OS thread id 140519254370064 updating or deleting, thread declared inside InnoDB 495 mysql tables in use 1, locked 1 6 lock struct(s), heap size 1216, 7 row lock(s), undo log entries 3 MySQL thread id 4, query id 11 localhost zabbix updating delete from history_uint where itemid=24530 and clock<1467095587 InnoDB: Submit a detailed bug report to http://bugs.mysql.com InnoDB: error in sec index entry update in InnoDB: index `history_uint_1` of table `zabbix`.`history_uint` InnoDB: tuple DATA TUPLE: 3 fields; 0: len 8; hex 0000000000005fd2; asc _ ;; 1: len 4; hex d771e297; asc q ;; 2: len 6; hex 000000219f65; asc ! e;; InnoDB: record PHYSICAL RECORD: n_fields 3; compact format; info bits 32 0: len 8; hex 0000000000005fd2; asc _ ;; 1: len 4; hex d771e1e3; asc q ;; 2: len 6; hex 000000219a50; asc ! P;; TRANSACTION 0 112437763, ACTIVE 0 sec, process no 17925, OS thread id 140519254370064 updating or deleting, thread declared inside InnoDB 493 mysql tables in use 1, locked 1 6 lock struct(s), heap size 1216, 9 row lock(s), undo log entries 4 MySQL thread id 4, query id 11 localhost zabbix updating delete from history_uint where itemid=24530 and clock<1467095587 InnoDB: Submit a detailed bug report to http://bugs.mysql.com InnoDB: error in sec index entry update in InnoDB: index `history_uint_1` of table `zabbix`.`history_uint` InnoDB: tuple DATA TUPLE: 3 fields; 0: len 8; hex 0000000000005fd2; asc _ ;; 1: len 4; hex d771e2d3; asc q ;; 2: len 6; hex 00000021a125; asc ! %;; InnoDB: record PHYSICAL RECORD: n_fields 3; compact format; info bits 32 0: len 8; hex 0000000000005fd2; asc _ ;; 1: len 4; hex d771e1e3; asc q ;; 2: len 6; hex 000000219a50; asc ! P;; TRANSACTION 0 112437763, ACTIVE 0 sec, process no 17925, OS thread id 140519254370064 updating or deleting, thread declared inside InnoDB 491 mysql tables in use 1, locked 1 7 lock struct(s), heap size 1216, 11 row lock(s), undo log entries 5 MySQL thread id 4, query id 11 localhost zabbix updating delete from history_uint where itemid=24530 and clock<1467095587 InnoDB: Submit a detailed bug report to http://bugs.mysql.com InnoDB: error in sec index entry update in InnoDB: index `history_uint_1` of table `zabbix`.`history_uint` InnoDB: tuple DATA TUPLE: 3 fields; 0: len 8; hex 0000000000005fd2; asc _ ;; 1: len 4; hex d771e310; asc q ;; 2: len 6; hex 00000021a31a; asc ! ;; InnoDB: record PHYSICAL RECORD: n_fields 3; compact format; info bits 32 0: len 8; hex 0000000000005fd2; asc _ ;; 1: len 4; hex d771e1e3; asc q ;; 2: len 6; hex 000000219a50; asc ! P;;
MYSQL 在做查询表信息的时候数据库重启!!比较急,在线
如下是日志,麻烦哪位大神帮忙下,谢谢 150430 14:03:09 mysqld_safe Starting mysqld daemon with databases from /data/mongo_dev/mysqldb 150430 14:03:09 InnoDB: The InnoDB memory heap is disabled 150430 14:03:09 InnoDB: Mutexes and rw_locks use GCC atomic builtins 150430 14:03:09 InnoDB: Compressed tables use zlib 1.2.3 150430 14:03:09 InnoDB: CPU supports crc32 instructions 150430 14:03:09 InnoDB: Initializing buffer pool, size = 128.0M 150430 14:03:09 InnoDB: Completed initialization of buffer pool 150430 14:03:09 InnoDB: highest supported file format is Barracuda. InnoDB: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 150430 14:03:09 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... 150430 14:03:09 InnoDB: Operating system error number 5 in a file operation. InnoDB: Error number 5 means 'Input/output error'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html 150430 14:03:09 InnoDB: File name ./test/net_mac_log_bak#P#p0.MYI 150430 14:03:09 InnoDB: File operation call: 'stat'. InnoDB: Error: os_file_readdir_next_file() returned -1 in InnoDB: directory ./test InnoDB: Crash recovery may have failed for some .ibd files! 150430 14:03:09 InnoDB: Operating system error number 5 in a file operation. InnoDB: Error number 5 means 'Input/output error'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html 150430 14:03:09 InnoDB: File name ./mysql.sock 150430 14:03:09 InnoDB: File operation call: 'stat'. InnoDB: Error: os_file_readdir_next_file() returned -1 in InnoDB: directory . InnoDB: Crash recovery may have failed for some .ibd files! InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... 150430 14:03:10 InnoDB: 128 rollback segment(s) are active. 150430 14:03:10 InnoDB: Waiting for the background threads to start 150430 14:03:11 InnoDB: 1.2.4 started; log sequence number 109555758 Warning: World-writable config file './auto.cnf' is ignored 150430 14:03:11 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: 94d0a4e5-eefe-11e4-9ea2-40f2e9631adc. 150430 14:03:11 [Note] Event Scheduler: Loaded 0 events 150430 14:03:11 [Note] /usr/local/mysql/bin/mysqld: ready for connections. Version: '5.6.4-m7' socket: '/data/mongo_dev/mysql.sock' port: 3306 Source distribution 150430 14:04:05 [Note] /usr/local/mysql/bin/mysqld: Normal shutdown 150430 14:04:05 [Note] Giving client threads a chance to die gracefully 150430 14:04:05 [Note] Event Scheduler: Purging the queue. 0 events 150430 14:04:05 [Note] Shutting down slave threads 150430 14:04:05 [Note] Forcefully disconnecting remaining clients 150430 14:04:05 [Note] Binlog end 150430 14:04:05 [Note] Shutting down plugin 'partition' 150430 14:04:05 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA' 150430 14:04:05 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS' 150430 14:04:05 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN' 150430 14:04:05 [Note] Shutting down plugin 'INNODB_SYS_FIELDS' 150430 14:04:05 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS' 150430 14:04:05 [Note] Shutting down plugin 'INNODB_SYS_INDEXES' 150430 14:04:05 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS' 150430 14:04:05 [Note] Shutting down plugin 'INNODB_SYS_TABLES' 150430 14:04:05 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE' 150430 14:04:05 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE' 150430 14:04:05 [Note] Shutting down plugin 'INNODB_FT_CONFIG' 150430 14:04:05 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED' 150430 14:04:05 [Note] Shutting down plugin 'INNODB_FT_DELETED' 150430 14:04:05 [Note] Shutting down plugin 'INNODB_FT_INSERTED' 150430 14:04:05 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD' 150430 14:04:05 [Note] Shutting down plugin 'INNODB_METRICS' 150430 14:04:05 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS' 150430 14:04:05 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU' 150430 14:04:05 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE' 150430 14:04:05 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET' 150430 14:04:05 [Note] Shutting down plugin 'INNODB_CMPMEM' 150430 14:04:05 [Note] Shutting down plugin 'INNODB_CMP_RESET' 150430 14:04:05 [Note] Shutting down plugin 'INNODB_CMP' 150430 14:04:05 [Note] Shutting down plugin 'INNODB_LOCK_WAITS' 150430 14:04:05 [Note] Shutting down plugin 'INNODB_LOCKS' 150430 14:04:05 [Note] Shutting down plugin 'INNODB_TRX' 150430 14:04:05 [Note] Shutting down plugin 'InnoDB' 150430 14:04:05 InnoDB: FTS optimize thread exiting. 150430 14:04:05 InnoDB: Starting shutdown... 150430 14:04:05 InnoDB: Shutdown completed; log sequence number 109555768 150430 14:04:05 [Note] Shutting down plugin 'MEMORY' 150430 14:04:05 [Note] Shutting down plugin 'CSV' 150430 14:04:05 [Note] Shutting down plugin 'MyISAM' 150430 14:04:05 [Note] Shutting down plugin 'MRG_MYISAM' 150430 14:04:05 [Note] Shutting down plugin 'mysql_old_password' 150430 14:04:05 [Note] Shutting down plugin 'mysql_native_password' 150430 14:04:05 [Note] Shutting down plugin 'binlog' 150430 14:04:05 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete 150430 14:04:05 mysqld_safe mysqld from pid file /data/mongo_dev/mysqldb/log01.pid ended 150430 14:04:06 mysqld_safe Starting mysqld daemon with databases from /data/mongo_dev/mysqldb 150430 14:04:06 InnoDB: The InnoDB memory heap is disabled 150430 14:04:06 InnoDB: Mutexes and rw_locks use GCC atomic builtins 150430 14:04:06 InnoDB: Compressed tables use zlib 1.2.3 150430 14:04:06 InnoDB: CPU supports crc32 instructions 150430 14:04:06 InnoDB: Initializing buffer pool, size = 128.0M 150430 14:04:06 InnoDB: Completed initialization of buffer pool 150430 14:04:06 InnoDB: highest supported file format is Barracuda. 150430 14:04:06 InnoDB: 128 rollback segment(s) are active. 150430 14:04:06 InnoDB: 1.2.4 started; log sequence number 109555768 Warning: World-writable config file './auto.cnf' is ignored 150430 14:04:06 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: b5b184b2-eefe-11e4-9ea3-40f2e9631adc. 150430 14:04:06 [Note] Event Scheduler: Loaded 0 events 150430 14:04:06 [Note] /usr/local/mysql/bin/mysqld: ready for connections. Version: '5.6.4-m7' socket: '/data/mongo_dev/mysql.sock' port: 3306 Source distribution
centos虚拟机重启后,MySQL服务启动不了了,求解?
#MySQL版本5.1.73 贴出日志如下: 170808 23:02:18 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 170808 23:02:19 InnoDB: Initializing buffer pool, size = 8.0M 170808 23:02:19 InnoDB: Completed initialization of buffer pool InnoDB: The first specified data file ./ibdata1 did not exist: InnoDB: a new database to be created! 170808 23:02:19 InnoDB: Setting file ./ibdata1 size to 10 MB InnoDB: Database physically writes the file full: wait... 170808 23:02:19 InnoDB: Log file ./ib_logfile0 did not exist: new to be created InnoDB: Setting log file ./ib_logfile0 size to 5 MB InnoDB: Database physically writes the file full: wait... 170808 23:02:19 InnoDB: Log file ./ib_logfile1 did not exist: new to be created InnoDB: Setting log file ./ib_logfile1 size to 5 MB InnoDB: Database physically writes the file full: wait... InnoDB: Doublewrite buffer not found: creating new InnoDB: Doublewrite buffer created InnoDB: Creating foreign key constraint system tables InnoDB: Foreign key constraint system tables created 170808 23:02:19 InnoDB: Started; log sequence number 0 0 170808 23:02:19 [Note] Event Scheduler: Loaded 0 events 170808 23:02:19 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.73' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 170809 5:21:42 [Note] /usr/libexec/mysqld: Normal shutdown 170809 5:21:42 [Note] Event Scheduler: Purging the queue. 0 events 170809 5:21:42 InnoDB: Starting shutdown... 170809 5:21:45 InnoDB: Shutdown completed; log sequence number 0 89508 170809 5:21:45 [Note] /usr/libexec/mysqld: Shutdown complete 170809 05:21:45 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 170810 18:53:14 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 170810 18:53:14 [Warning] '--default-character-set' is deprecated and will be removed in a future release. Please use '--character-set-server' instead. /usr/libexec/mysqld: Character set 'utf-8' is not a compiled character set and is not specified in the '/usr/share/mysql/charsets/Index.xml' file 170810 18:53:14 [ERROR] Aborting 170810 18:53:14 [Note] /usr/libexec/mysqld: Shutdown complete 170810 18:53:14 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 170810 18:54:30 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 170810 18:54:30 [Warning] '--default-character-set' is deprecated and will be removed in a future release. Please use '--character-set-server' instead. /usr/libexec/mysqld: Character set 'utf-8' is not a compiled character set and is not specified in the '/usr/share/mysql/charsets/Index.xml' file 170810 18:54:30 [ERROR] Aborting 170810 18:54:30 [Note] /usr/libexec/mysqld: Shutdown complete 170810 18:54:30 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended ``` ```
centos6.5断电重启后,MySQL启动失败
MySQL启动的错误日志如下: 161213 16:07:39 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data 2016-12-13 16:07:40 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 2016-12-13 16:07:40 5243 [Note] Plugin 'FEDERATED' is disabled. 2016-12-13 16:07:40 5243 [Note] InnoDB: The InnoDB memory heap is disabled 2016-12-13 16:07:40 5243 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2016-12-13 16:07:40 5243 [Note] InnoDB: Compressed tables use zlib 1.2.3 2016-12-13 16:07:40 5243 [Note] InnoDB: Using Linux native AIO 2016-12-13 16:07:40 5243 [Note] InnoDB: Using CPU crc32 instructions 2016-12-13 16:07:40 5243 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2016-12-13 16:07:40 5243 [Note] InnoDB: Completed initialization of buffer pool 2016-12-13 16:07:40 5243 [Note] InnoDB: Highest supported file format is Barracuda. 2016-12-13 16:07:40 5243 [Note] InnoDB: Log scan progressed past the checkpoint lsn 6528157 2016-12-13 16:07:40 5243 [Note] InnoDB: Database was not shutdown normally! 2016-12-13 16:07:40 5243 [Note] InnoDB: Starting crash recovery. 2016-12-13 16:07:40 5243 [Note] InnoDB: Reading tablespace information from the .ibd files... 2016-12-13 16:07:40 5243 [Note] InnoDB: Restoring possible half-written data pages 2016-12-13 16:07:40 5243 [Note] InnoDB: from the doublewrite buffer... InnoDB: Doing recovery: scanned up to log sequence number 6528267 2016-12-13 16:07:40 5243 [Note] InnoDB: 128 rollback segment(s) are active. 2016-12-13 16:07:40 5243 [Note] InnoDB: Waiting for purge to start 2016-12-13 16:07:40 7f161458c700 InnoDB: Assertion failure in thread 139732807370496 in file trx0purge.cc line 699 InnoDB: Failing assertion: purge_sys->iter.trx_no <= purge_sys->rseg->last_trx_no InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 08:07:40 UTC - mysqld got signal 6 ; 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=268435456 read_buffer_size=1048576 max_used_connections=0 max_threads=151 thread_count=0 connection_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 728082 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 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... stack_bottom = 0 thread_stack 0x40000 /usr/local/mysql/bin/mysqld(my_print_stacktrace+0x35)[0x9024f5] /usr/local/mysql/bin/mysqld(handle_fatal_signal+0x3e8)[0x66f518] /lib64/libpthread.so.0[0x3030a0f710] /lib64/libc.so.6(gsignal+0x35)[0x3030632925] /lib64/libc.so.6(abort+0x175)[0x3030634105] /usr/local/mysql/bin/mysqld[0x9d8308] /usr/local/mysql/bin/mysqld[0x9d9936] /usr/local/mysql/bin/mysqld[0x9c82eb] /usr/local/mysql/bin/mysqld[0x9cc0b8] /lib64/libpthread.so.0[0x3030a079d1] /lib64/libc.so.6(clone+0x6d)[0x30306e8b6d] 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. 161213 16:07:40 mysqld_safe mysqld from pid file /usr/local/mysql/data/mysqld.pid ended
【mysql不能登陆root】
mysql无法登陆root: ``` ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES) ``` 查了一下,删掉data文件夹下和数据库无关的文件,在my-default.ini中加上'skip-grant-tables'选项,跳过密码登陆依然失败,加tmpdir路径也不可以; ``` PS C:\Program Files\MySQL\MySQL Server 5.6\bin> mysqld --skip-grant-tables 2019-10-21 14:48:07 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 2019-10-21 14:48:07 4416 [Warning] Can't create test file C:\Program Files\MySQL\MySQL Server 5.6\data\DESKTOP-FVGQVE8.lower-test 2019-10-21 14:48:07 4416 [Warning] Can't create test file C:\Program Files\MySQL\MySQL Server 5.6\data\DESKTOP-FVGQVE8.lower-test 2019-10-21 14:48:07 4416 [Note] Plugin 'FEDERATED' is disabled. 2019-10-21 14:48:07 4416 [Note] InnoDB: The InnoDB memory heap is disabled 2019-10-21 14:48:07 4416 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 2019-10-21 14:48:07 4416 [Note] InnoDB: Compressed tables use zlib 1.2.3 2019-10-21 14:48:07 4416 [Note] InnoDB: CPU does not support crc32 instructions 2019-10-21 14:48:07 4416 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2019-10-21 14:48:07 4416 [Note] InnoDB: Completed initialization of buffer pool 2019-10-21 14:48:07 32d4 InnoDB: Operating system error number 5 in a file operation. InnoDB: The error means mysqld does not have the access rights to InnoDB: the directory. It may also be you have created a subdirectory InnoDB: of the same name as a data file. 2019-10-21 14:48:07 32d4 InnoDB: File name .\ibdata1 2019-10-21 14:48:07 32d4 InnoDB: File operation call: 'create' returned OS error 105. 2019-10-21 14:48:07 32d4 InnoDB: Cannot continue operation. ``` 这是配置文件: ``` [mysqld] explicit_defaults_for_timestamp=true tmpdir="C:/Program Files/MySQL Server 5.6/temp/" skip-grant-tables old_passwords=0 # 设置3306端口 port=3306 # 设置mysql的安装目录 basedir="C:/Program Files/MySQL/MySQL Server 5.6 "# 设置mysql数据库的数据的存放目录 datadir="C:/Program Files/MySQL/MySQL Server 5.6/data "# 允许最大连接数 max_connections=200 # 允许连接失败的次数 max_connect_errors=10 # 服务端使用的字符集默认为UTF8 character-set-server=utf8 # 创建新表时将使用的默认存储引擎 default-storage-engine=MYISAM # 默认使用“mysql_native_password”插件认证 #mysql_native_password default_authentication_plugin=mysql_native_password [mysql] # 设置mysql客户端默认字符集 default-character-set=utf8 # 设置mysql客户端连接服务端时默认使用的端口 port=3306 default-character-set=utf8 innodb_buffer_pool_size=32M innodb_force_recovery = 1 ``` 请大神解答这是什么问题?
MySql服务启动不了,网上找不到类似的解决方法
错误日志如下: 151124 10:17:17 [Note] Plugin 'FEDERATED' is disabled. 151124 10:17:17 InnoDB: Initializing buffer pool, size = 107.0M 151124 10:17:17 InnoDB: Completed initialization of buffer pool 151124 10:17:17 InnoDB: Started; log sequence number 0 44556 151124 10:17:17 [ERROR] Aborting 151124 10:17:17 InnoDB: Starting shutdown... 151124 10:17:23 InnoDB: Shutdown completed; log sequence number 0 44556 151124 10:17:23 [Note] E:\MySQL\bin\mysqld: Shutdown complete
mysql安装The server quit without updating PID file?
折腾了一下午找不出原因 下面是日志内容 求大神带飞 2017-03-30 04:23:00 7295 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2017-03-30 04:23:00 7295 [Note] InnoDB: The InnoDB memory heap is disabled 2017-03-30 04:23:00 7295 [Note] InnoDB: Mutexes and rw_locks use InnoDB's own implementation 2017-03-30 04:23:00 7295 [Note] InnoDB: Memory barrier is not used 2017-03-30 04:23:00 7295 [Note] InnoDB: Compressed tables use zlib 1.2.3 2017-03-30 04:23:00 7295 [Note] InnoDB: Using Linux native AIO 2017-03-30 04:23:00 7295 [Note] InnoDB: Not using CPU crc32 instructions 2017-03-30 04:23:00 7295 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2017-03-30 04:23:00 7295 [Note] InnoDB: Completed initialization of buffer pool 2017-03-30 04:23:00 7295 [Note] InnoDB: Highest supported file format is Barracuda. 2017-03-30 04:23:00 7295 [Note] InnoDB: 128 rollback segment(s) are active. 2017-03-30 04:23:00 7295 [Note] InnoDB: Waiting for purge to start 2017-03-30 04:23:00 7295 [Note] InnoDB: 5.6.35 started; log sequence number 1626047 2017-03-30 04:23:01 7295 [Note] Binlog end 2017-03-30 04:23:01 7295 [Note] InnoDB: FTS optimize thread exiting. 2017-03-30 04:23:01 7295 [Note] InnoDB: Starting shutdown... 2017-03-30 04:23:02 7295 [Note] InnoDB: Shutdown completed; log sequence number 1626057 2017-03-30 04:23:02 7318 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2017-03-30 04:23:02 7318 [Note] InnoDB: The InnoDB memory heap is disabled 2017-03-30 04:23:02 7318 [Note] InnoDB: Mutexes and rw_locks use InnoDB's own implementatio
迁移数据库中遇到的问题
尝试了许多办法仍然无法解决数据库无法启动的错误,菜鸟盼望各位大婶能够指点迷津。。。。错误日志如下 140313 15:22:36 mysqld_safe Starting mysqld.bin daemon with databases from /opt/mediawiki-1.21.2-1/mysql/data 140313 15:22:36 [Note] Plugin 'FEDERATED' is disabled. /opt/mediawiki-1.21.2-1/mysql/bin/mysqld.bin: Can't find file: './mysql/plugin.frm' (errno: 13) 140313 15:22:36 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. 140313 15:22:36 InnoDB: The InnoDB memory heap is disabled 140313 15:22:36 InnoDB: Mutexes and rw_locks use InnoDB's own implementation 140313 15:22:36 InnoDB: Compressed tables use zlib 1.2.3 140313 15:22:36 InnoDB: Using Linux native AIO /opt/mediawiki-1.21.2-1/mysql/bin/mysqld.bin: Can't create/write to file '/opt/mediawiki-1.21.2-1/mysql/tmp/ibS1Nhnt' (Errcode: 13) 140313 15:22:36 InnoDB: Error: unable to create temporary file; errno: 13 140313 15:22:36 [ERROR] Plugin 'InnoDB' init function returned error. 140313 15:22:36 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 140313 15:22:36 [ERROR] Unknown/unsupported storage engine: InnoDB 140313 15:22:36 [ERROR] Aborting 140313 15:22:36 [Note] /opt/mediawiki-1.21.2-1/mysql/bin/mysqld.bin: Shutdown complete 140313 15:22:36 mysqld_safe mysqld from pid file /opt/mediawiki-1.21.2-1/mysql/data/mysqld.pid ended
130 个相见恨晚的超实用网站,一次性分享出来
文末没有公众号,只求 点赞 + 关注 搞学习 知乎:www.zhihu.com 大学资源网:http://www.dxzy163.com/ 简答题:http://www.jiandati.com/ 网易公开课:https://open.163.com/ted/ 网易云课堂:https://study.163.com/ 中国大学MOOC:www.icourse163.org 网易云课堂:stu
终于明白阿里百度这样的大公司,为什么面试经常拿ThreadLocal考验求职者了
点击上面↑「爱开发」关注我们每晚10点,捕获技术思考和创业资源洞察什么是ThreadLocalThreadLocal是一个本地线程副本变量工具类,各个线程都拥有一份线程私有的数
win10系统安装教程(U盘PE+UEFI安装)
一、准备工作 u盘,电脑一台,win10原版镜像(msdn官网) 二、下载wepe工具箱  极力推荐微pe(微pe官方下载) 下载64位的win10 pe,使用工具箱制作启动U盘打开软件,   选择安装到U盘(按照操作无需更改) 三、重启进入pe系统   1、关机后,将U盘插入电脑 2、按下电源后,按住F12进入启动项选择(技嘉主板是F12)     选择需要启
程序员必须掌握的核心算法有哪些?
由于我之前一直强调数据结构以及算法学习的重要性,所以就有一些读者经常问我,数据结构与算法应该要学习到哪个程度呢?,说实话,这个问题我不知道要怎么回答你,主要取决于你想学习到哪些程度,不过针对这个问题,我稍微总结一下我学过的算法知识点,以及我觉得值得学习的算法。这些算法与数据结构的学习大多数是零散的,并没有一本把他们全部覆盖的书籍。下面是我觉得值得学习的一些算法以及数据结构,当然,我也会整理一些看过
大学四年自学走来,这些私藏的实用工具/学习网站我贡献出来了
大学四年,看课本是不可能一直看课本的了,对于学习,特别是自学,善于搜索网上的一些资源来辅助,还是非常有必要的,下面我就把这几年私藏的各种资源,网站贡献出来给你们。主要有:电子书搜索、实用工具、在线视频学习网站、非视频学习网站、软件下载、面试/求职必备网站。 注意:文中提到的所有资源,文末我都给你整理好了,你们只管拿去,如果觉得不错,转发、分享就是最大的支持了。 一、PDF搜索网站推荐 对于大部
C语言魔塔游戏
很早就很想写这个,今天终于写完了。 游戏截图: 编译环境: VS2017 游戏需要一些图片,如果有想要的或者对游戏有什么看法的可以加我的QQ 2985486630 讨论,如果暂时没有回应,可以在博客下方留言,到时候我会看到。 下面我来介绍一下游戏的主要功能和实现方式 首先是玩家的定义,使用结构体,这个名字是可以自己改变的 struct gamerole { char n
java源码分析 Arrays.asList()与Collections.unmodifiableList()
举个栗子 本章示例代码来自java编程思想——17.4.1未获支持的操作——Unsupported类。 import java.util.*; public class Unsupported { static void test(String msg, List&lt;String&gt; list) { System.out.println("--- " + msg
究竟你适不适合买Mac?
我清晰的记得,刚买的macbook pro回到家,开机后第一件事情,就是上了淘宝网,花了500元钱,找了一个上门维修电脑的师傅,上门给我装了一个windows系统。。。。。。 表砍我。。。 当时买mac的初衷,只是想要个固态硬盘的笔记本,用来运行一些复杂的扑克软件。而看了当时所有的SSD笔记本后,最终决定,还是买个好(xiong)看(da)的。 已经有好几个朋友问我mba怎么样了,所以今天尽量客观
Python爬虫爬取淘宝,京东商品信息
小编是一个理科生,不善长说一些废话。简单介绍下原理然后直接上代码。 使用的工具(Python+pycharm2019.3+selenium+xpath+chromedriver)其中要使用pycharm也可以私聊我selenium是一个框架可以通过pip下载 pip install selenium -i https://pypi.tuna.tsinghua.edu.cn/simple/ 
Java学习笔记(七十二)—— Cookie
概述 会话技术: 会话:一次会话中包含多次请求和响应 一次会话:浏览器第一次给服务器发送资源请求,会话建立,直到有一方断开为止 功能:在一次会话的范围内的多次请求间,共享数据 方式: 客户端会话技术:Cookie,把数据存储到客户端 服务器端会话技术:Session,把数据存储到服务器端 Cookie 概念:客户端会话技术,将数据存储到客户端 快速入门: 使用步骤: 创建C
程序员写了一个新手都写不出的低级bug,被骂惨了。
你知道的越多,你不知道的越多 点赞再看,养成习惯 本文 GitHub https://github.com/JavaFamily 已收录,有一线大厂面试点思维导图,也整理了很多我的文档,欢迎Star和完善,大家面试可以参照考点复习,希望我们一起有点东西。 前前言 为啥今天有个前前言呢? 因为你们的丙丙啊,昨天有牌面了哟,直接被微信官方推荐,知乎推荐,也就仅仅是还行吧(心里乐开花)
Java工作4年来应聘要16K最后没要,细节如下。。。
前奏: 今天2B哥和大家分享一位前几天面试的一位应聘者,工作4年26岁,统招本科。 以下就是他的简历和面试情况。 基本情况: 专业技能: 1、&nbsp;熟悉Sping了解SpringMVC、SpringBoot、Mybatis等框架、了解SpringCloud微服务 2、&nbsp;熟悉常用项目管理工具:SVN、GIT、MAVEN、Jenkins 3、&nbsp;熟悉Nginx、tomca
2020年,冯唐49岁:我给20、30岁IT职场年轻人的建议
点击“技术领导力”关注∆  每天早上8:30推送 作者| Mr.K   编辑| Emma 来源| 技术领导力(ID:jishulingdaoli) 前天的推文《冯唐:职场人35岁以后,方法论比经验重要》,收到了不少读者的反馈,觉得挺受启发。其实,冯唐写了不少关于职场方面的文章,都挺不错的。可惜大家只记住了“春风十里不如你”、“如何避免成为油腻腻的中年人”等不那么正经的文章。 本文整理了冯
程序员该看的几部电影
##1、骇客帝国(1999) 概念:在线/离线,递归,循环,矩阵等 剧情简介: 不久的将来,网络黑客尼奥对这个看似正常的现实世界产生了怀疑。 他结识了黑客崔妮蒂,并见到了黑客组织的首领墨菲斯。 墨菲斯告诉他,现实世界其实是由一个名叫“母体”的计算机人工智能系统控制,人们就像他们饲养的动物,没有自由和思想,而尼奥就是能够拯救人类的救世主。 可是,救赎之路从来都不会一帆风顺,到底哪里才是真实的世界?
蓝桥杯知识点汇总:基础知识和常用算法
文章目录JAVA基础语法:算法竞赛常用的JAVA API:基础算法待更: 此系列包含蓝桥杯所考察的绝大部分知识点,一共有基础语法,常用API,基础算法和数据结构,和往年真题四部分,虽然语言以JAVA为主,但算法部分是相通的,C++组的小伙伴也可以看哦。所有文章的链接都会在此公布,还有很多没有更新,会持续更新,如果大佬发现文章有错误的地方请指正,我会十分感谢。另外,有什么问题可私信我~ JAVA基础
作为一个程序员,CPU的这些硬核知识你必须会!
CPU对每个程序员来说,是个既熟悉又陌生的东西? 如果你只知道CPU是中央处理器的话,那可能对你并没有什么用,那么作为程序员的我们,必须要搞懂的就是CPU这家伙是如何运行的,尤其要搞懂它里面的寄存器是怎么一回事,因为这将让你从底层明白程序的运行机制。 随我一起,来好好认识下CPU这货吧 把CPU掰开来看 对于CPU来说,我们首先就要搞明白它是怎么回事,也就是它的内部构造,当然,CPU那么牛的一个东
破14亿,Python分析我国存在哪些人口危机!
2020年1月17日,国家统计局发布了2019年国民经济报告,报告中指出我国人口突破14亿。 猪哥的朋友圈被14亿人口刷屏,但是很多人并没有看到我国复杂的人口问题:老龄化、男女比例失衡、生育率下降、人口红利下降等。 今天我们就来分析一下我们国家的人口数据吧! 一、背景 1.人口突破14亿 2020年1月17日,国家统计局发布了 2019年国民经济报告 ,报告中指出:年末中国大陆总人口(包括31个
实现简单的轮播图(单张图片、多张图片)
前言 刚学js没多久,这篇博客就当做记录了,以后还会完善的,希望大佬们多多指点。ps:下面出现的都是直接闪动,没有滑动效果的轮播图。 单张图片的替换 原理 1.将几张图片叠在一起,通过改变"display:block"和"display:none"这两个属性实现替换。 (前提:在css中给所有图片加上display:none属性) 2.不用将图片叠在一起,将一个div当做"窗口",通过"of
强烈推荐10本程序员在家读的书
很遗憾,这个鼠年春节注定是刻骨铭心的,新型冠状病毒让每个人的神经都是紧绷的。那些处在武汉的白衣天使们,尤其值得我们的尊敬。而我们这些窝在家里的程序员,能不外出就不外出,就是对社会做出的最大的贡献。 有些读者私下问我,窝了几天,有点颓丧,能否推荐几本书在家里看看。我花了一天的时间,挑选了 10 本我最喜欢的书,你可以挑选感兴趣的来读一读。读书不仅可以平复恐惧的压力,还可以对未来充满希望,毕竟苦难终
Linux自学篇——linux命令英文全称及解释
man: Manual 意思是手册,可以用这个命令查询其他命令的用法。 pwd:Print working directory 显示当前目录 su:Swith user 切换用户,切换到root用户 cd:Change directory 切换目录 ls:List files 列出目录下的文件 ps:Process Status 进程状态 mk
Python实战:抓肺炎疫情实时数据,画2019-nCoV疫情地图
文章目录1. 前言2. 数据下载3. 数据处理4. 数据可视化 1. 前言 今天,群里白垩老师问如何用python画武汉肺炎疫情地图。白垩老师是研究海洋生态与地球生物的学者,国家重点实验室成员,于不惑之年学习python,实为我等学习楷模。先前我并没有关注武汉肺炎的具体数据,也没有画过类似的数据分布图。于是就拿了两个小时,专门研究了一下,遂成此文。 2月6日追记:本文发布后,腾讯的数据源多次变更u
智力题(程序员面试经典)
NO.1  有20瓶药丸,其中19瓶装有1克/粒的药丸,余下一瓶装有1.1克/粒的药丸。给你一台称重精准的天平,怎么找出比较重的那瓶药丸?天平只能用一次。 解法 有时候,严格的限制条件有可能反倒是解题的线索。在这个问题中,限制条件是天平只能用一次。 因为天平只能用一次,我们也得以知道一个有趣的事实:一次必须同时称很多药丸,其实更准确地说,是必须从19瓶拿出药丸进行称重。否则,如果跳过两瓶或更多瓶药
Java与Python学习通法(1)和(2)序言和编程语言发展史怎么学
大家好,我是 jacky 朱元禄,很高兴跟大家一起学习 《Java与Python学习通法系列》。 首先,说一下,我为什么要录这个课; 我们都已经知道Java 和 Python的视频教程和书籍,可以说是非常非常多了,那我录制本系列课的意义是什么呢? (1)课程特色一:我想告诉大家学习编程语言是有捷径的,这个捷径就是 理解技术背后的“哲学逻辑”,或者说是“人文逻辑”,相信你听完 jack
在家远程办公效率低?那你一定要收好这个「在家办公」神器!
相信大家都已经收到国务院延长春节假期的消息,接下来,在家远程办公可能将会持续一段时间。 但是问题来了。远程办公不是人在电脑前就当坐班了,相反,对于沟通效率,文件协作,以及信息安全都有着极高的要求。有着非常多的挑战,比如: 1在异地互相不见面的会议上,如何提高沟通效率? 2文件之间的来往反馈如何做到及时性?如何保证信息安全? 3如何规划安排每天工作,以及如何进行成果验收? ......
作为一个程序员,内存和磁盘的这些事情,你不得不知道啊!!!
截止目前,我已经分享了如下几篇文章: 一个程序在计算机中是如何运行的?超级干货!!! 作为一个程序员,CPU的这些硬核知识你必须会! 作为一个程序员,内存的这些硬核知识你必须懂! 这些知识可以说是我们之前都不太重视的基础知识,可能大家在上大学的时候都学习过了,但是嘞,当时由于老师讲解的没那么有趣,又加上这些知识本身就比较枯燥,所以嘞,大家当初几乎等于没学。 再说啦,学习这些,也看不出来有什么用啊!
阿里架构师花近十年时间整理出来的Java核心知识pdf(Java岗)
由于细节内容实在太多啦,所以只把部分知识点截图出来粗略的介绍,每个小节点里面都有更细化的内容! 整理了一份Java核心知识点。覆盖了JVM、锁、并发、Java反射、Spring原理、微服务、Zookeeper、数据库、数据结构等大量知识点。       欢迎大家加入java学习交流社区  点击加入   可获取文中文档       小编推荐:     
Python基础知识点梳理
python基础知识点梳理 摘要: 本文主要介绍一些平时经常会用到的python基础知识点,用于加深印象,也算是对于学习这门语言的一个总结与回顾。python的详细语法介绍可以查看官方编程手册,也有一些在线网站对python语法进行了比较全面的介绍,比如菜鸟教程: python3 教程|菜鸟教程 为了方便聚焦知识点,本文涉及的操作实例并不多,想学好一门语言关键还得自己多编码多实践。 python语
2020年2月全国程序员工资统计,平均工资13716元
趋势 2020年2月,中国大陆程序员平均工资13716元,比上个月增加。具体趋势如图: 各主要程序员城市工资变化 城市 北京,上海,深圳,杭州,广州四地的工资最高。 city 平均工资 最低工资 中位数 最高工资 招聘人数 百分比 北京 18098 3750 15000 45000 20529 9.53% 深圳 16903 5750 15000 37500 30941 14
Java坑人面试题系列: 包装类(中级难度)
Java Magazine上面有一个专门坑人的面试题系列: https://blogs.oracle.com/javamagazine/quiz-2。 这些问题的设计宗旨,主要是测试面试者对Java语言的了解程度,而不是为了用弯弯绕绕的手段把面试者搞蒙。 如果你看过往期的问题,就会发现每一个都不简单。 这些试题模拟了认证考试中的一些难题。 而 “中级(intermediate)” 和 “高级(ad
为什么说程序员做外包没前途?
之前做过不到3个月的外包,2020的第一天就被释放了,2019年还剩1天,我从外包公司离职了。我就谈谈我个人的看法吧。首先我们定义一下什么是有前途 稳定的工作环境 不错的收入 能够在项目中不断提升自己的技能(ps:非技术上的认知也算) 找下家的时候能找到一份工资更高的工作 如果你目前还年轻,但高不成低不就,只有外包offer,那请往下看。 外包公司你应该
基于Python的人脸自动戴口罩系统
目录 1、项目背景 2、页面设计 3、器官识别 4、退出系统 1、项目背景 2019年新型冠状病毒感染的肺炎疫情发生以来,牵动人心,举国哀痛,口罩、酒精、消毒液奇货可居。 抢不到口罩,怎么办?作为技术人今天分享如何使用Python实现自动戴口罩系统,来安慰自己,系统效果如下所示: 本系统的实现原理是借助 Dlib模块的Landmark人脸68个关键点检测库轻松识别出人脸五官
相关热词 c# 为空 判断 委托 c#记事本颜色 c# 系统默认声音 js中调用c#方法参数 c#引入dll文件报错 c#根据名称实例化 c#从邮件服务器获取邮件 c# 保存文件夹 c#代码打包引用 c# 压缩效率
立即提问