to the monkey and the frog.for an eternity of ten thousand tales.什么意思？

Posted 2023-04-13

来自弗雷德里克 巴克曼的外婆的道歉信 ，有道和百度翻译很不满意 求专业解答

to the monkey and the frog.for an eternity of ten thousand tales的意思是：给猴子和青蛙，一万个故事的永恒。

重点词汇

monkey

英 [ˈmʌŋki]  美 [ˈmʌŋki]  

n : 猴子；顽皮的孩子；调皮鬼；捣蛋鬼；500英镑；

vt : 胡闹；捣蛋嘲弄；

第三人称单数： monkeys 复数： monkeys 现在分词： monkeying 过去式： monkeyed 过去分词： monkeyed

eternity 英 [ɪˈtɜːnəti]   美 [ɪˈtɜːrnəti] 

永恒; 永生; 不朽; 无穷无尽的一段时间

ten thousand 英 [ten ˈθaʊznd]   美 [ten ˈθaʊznd] 

万; 一万; 万卍

tales 英 ['teɪliːz] 

故事; 历险记； 讲述；叙述；tale的复数；

扩展资料

eternity

noun：[U] (formal) 永恒；永生；不朽 

例句

There will be rich and poor for all eternity.

贫富将永远存在。

an eternity

[sing.] (informal) （似乎）无穷无尽的一段时间。

例句

After what seemed like an eternity the nurse returned with the results of the test.

过了漫长的一段时间后护士才拿着检验结果回来。

参考技术A The Monkey and the Frog 指的是两种不同性格的人，这里应该是代指的外婆和艾莎，然后两人是最好的朋友好像出自The Monkey and the Frog 这本故事书里有这么一句话The Monkey and the Frog is about two different characters who meet and become fast friends when the frog ventures away from his pond to see what it is like beyond. The monkey then visits the pond, spending the day with the frog. 参考技术B to the monkey and the frog.for an eternity of ten thousand tales.
这个不是一个完整的句子，没有上下文不好翻译。
供参考：给猴子和青蛙一万个故事的永恒。

mysql报错：Ignoring the redo log due to missing MLOG_CHECKPOINT between the checkpoint 63593957 and the

mysql报错：Ignoring the redo log due to missing MLOG_CHECKPOINT between the checkpoint 63593957 and the end 63593472.

 

mysql版本：5.7.19

系统版本：centos7.3

 

由于公司断电，跑在vmware虚拟机上的mysql挂掉，无法重启

innodb_force_recovery=6
2017-11-15T12:07:25.235397+08:00 0 [Warning] ‘db‘ entry ‘sys [email protected]‘ ignored in --skip-name-resolve mode.
2017-11-15T12:07:25.235408+08:00 0 [Warning] ‘proxies_priv‘ entry ‘@ [email protected]‘ ignored in --skip-name-resolve mode.
2017-11-15T12:07:25.235540+08:00 0 [ERROR] InnoDB: Failed to find tablespace for table `mysql`.`time_zone_leap_second` in the cache. Attempting to load the tablespace with space id 46
2017-11-15T12:07:25.256456+08:00 0 [ERROR] InnoDB: Failed to find tablespace for table `mysql`.`time_zone_name` in the cache. Attempting to load the tablespace with space id 47
2017-11-15T12:07:25.258414+08:00 0 [ERROR] InnoDB: Failed to find tablespace for table `mysql`.`time_zone` in the cache. Attempting to load the tablespace with space id 45
2017-11-15T12:07:25.263576+08:00 0 [ERROR] InnoDB: Failed to find tablespace for table `mysql`.`time_zone_transition_type` in the cache. Attempting to load the tablespace with space id 49
2017-11-15T12:07:25.267569+08:00 0 [ERROR] InnoDB: Failed to find tablespace for table `mysql`.`time_zone_transition` in the cache. Attempting to load the tablespace with space id 48
2017-11-15T12:07:25.272648+08:00 0 [ERROR] InnoDB: Failed to find tablespace for table `mysql`.`servers` in the cache. Attempting to load the tablespace with space id 41
2017-11-15T12:07:25.276466+08:00 0 [ERROR] InnoDB: Failed to find tablespace for table `mysql`.`slave_master_info` in the cache. Attempting to load the tablespace with space id 42
2017-11-15T12:07:25.280225+08:00 0 [ERROR] InnoDB: Failed to find tablespace for table `mysql`.`slave_relay_log_info` in the cache. Attempting to load the tablespace with space id 43
2017-11-15T12:07:25.286619+08:00 0 [ERROR] InnoDB: Failed to find tablespace for table `mysql`.`slave_worker_info` in the cache. Attempting to load the tablespace with space id 44
2017-11-15T12:07:25.292450+08:00 0 [ERROR] Error writing master configuration.
2017-11-15T12:07:25.292468+08:00 0 [ERROR] Error reading master configuration.
2017-11-15T12:07:25.294535+08:00 0 [Warning] Recovery from master pos 1065 and file mysql-bin.000003 for channel ‘‘. Previous relay log pos and relay log file had been set to 4, /data/mysql/mysql3306/logs/mysql-relay.000003 respectively.
2017-11-15T12:07:25.294643+08:00 0 [ERROR] Error writing relay log configuration.
2017-11-15T12:07:25.294656+08:00 0 [ERROR] Error reading relay log configuration.
2017-11-15T12:07:25.294983+08:00 0 [ERROR] Slave: Failed to initialize the master info structure for channel ‘‘; its record may still be present in ‘mysql.slave_master_info‘ table, consider deleting it.
2017-11-15T12:07:25.294996+08:00 0 [ERROR] Failed to create or recover replication info repositories.
2017-11-15T12:07:25.295000+08:00 0 [Note] Some of the channels are not created/initialized properly. Check for additional messages above. You will not be able to start replication on those channels until the issue is resolved and the server restarted.

---

http://blog.csdn.net/weiwangsisoftstone/article/details/52954228

 

-15T11:44:46.406153+08:00 0 [Note] InnoDB: Using CPU crc32 instructions
2017-11-15T11:44:46.453775+08:00 0 [Note] InnoDB: Initializing buffer pool, total size = 5M, instances = 1, chunk size = 5M
2017-11-15T11:44:46.454888+08:00 0 [Note] InnoDB: Completed initialization of buffer pool
2017-11-15T11:44:46.456582+08:00 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2017-11-15T11:44:46.546548+08:00 0 [Note] InnoDB: Opened 8 undo tablespaces
2017-11-15T11:44:46.546575+08:00 0 [Note] InnoDB: 8 undo tablespaces made active
2017-11-15T11:44:46.546960+08:00 0 [Note] InnoDB: Highest supported file format is Barracuda.
2017-11-15T11:44:46.562061+08:00 0 [ERROR] InnoDB: Ignoring the redo log due to missing MLOG_CHECKPOINT between the checkpoint 63593957 and the end 63593472.
2017-11-15T11:44:46.562090+08:00 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2017-11-15T11:44:47.062885+08:00 0 [ERROR] Plugin ‘InnoDB‘ init function returned error.
2017-11-15T11:44:47.062936+08:00 0 [ERROR] Plugin ‘InnoDB‘ registration as a STORAGE ENGINE failed.
2017-11-15T11:44:47.062945+08:00 0 [ERROR] Failed to initialize plugins.
2017-11-15T11:44:47.062951+08:00 0 [ERROR] Aborting

2017-11-15T11:44:47.062962+08:00 0 [Note] Binlog end
2017-11-15T11:44:47.063067+08:00 0 [Note] Shutting down plugin ‘MyISAM‘
2017-11-15T11:44:47.063097+08:00 0 [Note] Shutting down plugin ‘CSV‘
2017-11-15T11:44:47.063622+08:00 0 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete


丢失数据
2017-11-15T11:54:17.694175+08:00 0 [Note] Server socket created on IP: ‘::‘.
2017-11-15T11:54:17.696000+08:00 0 [ERROR] InnoDB: Page [page id: space=40, page number=3] log sequence number 3725922 is in the future! Current system log sequence number 2440232.
2017-11-15T11:54:17.696018+08:00 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2017-11-15T11:54:17.696287+08:00 0 [ERROR] InnoDB: Page [page id: space=40, page number=1] log sequence number 3720522 is in the future! Current system log sequence number 2440232.
2017-11-15T11:54:17.696300+08:00 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2017-11-15T11:54:17.696535+08:00 0 [ERROR] InnoDB: Page [page id: space=40, page number=2] log sequence number 3724576 is in the future! Current system log sequence number 2440232.
2017-11-15T11:54:17.696551+08:00 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2017-11-15T11:54:17.697469+08:00 0 [ERROR] InnoDB: Page [page id: space=32, page number=3] log sequence number 2483079 is in the future! Current system log sequence number 2440232.
2017-11-15T11:54:17.697485+08:00 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2017-11-15T11:54:17.697809+08:00 0 [ERROR] InnoDB: Page [page id: space=32, page number=1] log sequence number 2479069 is in the future! Current system log sequence number 2440232.
2017-11-15T11:54:17.697821+08:00 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2017-11-15T11:54:17.698049+08:00 0 [ERROR] InnoDB: Page [page id: space=32, page number=2] log sequence number 2482784 is in the future! Current system log sequence number 2440232.
2017-11-15T11:54:17.698061+08:00 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2017-11-15T11:54:17.700092+08:00 0 [Warning] ‘user‘ entry ‘[email protected]‘ ignored in --skip-name-resolve mode.
2017-11-15T11:54:17.700140+08:00 0 [Warning] ‘user‘ entry ‘[email protected]‘ ignored in --skip-name-resolve mode.
2017-11-15T11:54:17.700153+08:00 0 [Warning] ‘user‘ entry ‘[email protected]‘ ignored in --skip-name-resolve mode.
2017-11-15T11:54:17.701714+08:00 0 [Warning] ‘db‘ entry ‘performance_schema [email protected]‘ ignored in --skip-name-resolve mode.
2017-11-15T11:54:17.701727+08:00 0 [Warning] ‘db‘ entry ‘sys [email protected]‘ ignored in --skip-name-resolve mode.
2017-11-15T11:54:17.701881+08:00 0 [Warning] ‘proxies_priv‘ entry ‘@ [email protected]‘ ignored in --skip-name-resolve mode.
2017-11-15T11:54:17.702485+08:00 0 [ERROR] InnoDB: Page [page id: space=46, page number=3] log sequence number 3754946 is in the future! Current system log sequence number 2440232.
2017-11-15T11:54:17.702502+08:00 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2017-11-15T11:54:17.702718+08:00 0 [ERROR] InnoDB: Page [page id: space=46, page number=1] log sequence number 3751039 is in the future! Current system log sequence number 2440232.
2017-11-15T11:54:17.702741+08:00 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2017-11-15T11:54:17.702962+08:00 0 [ERROR] InnoDB: Page [page id: space=46, page number=2] log sequence number 3754946 is in the future! Current system log sequence number 2440232.
2017-11-15T11:54:17.702974+08:00 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.