office386

https://www.microsoft.com/taiwan/modernization/shift/?wt.mc_id=AID757655-Paid-%E5%AA%92%E9%AB%94%E6%96%87%E7%AB%A0Affiliate-INSIDE-Win7-%E5%AE%A3%E5%82%B3%E6%96%87%E7%AB%A0&utm_source=Article&utm_medium=affiliates&utm_content=Paid_%E5%AA%92%E9%AB%94%E6%96%87%E7%AB%A0Affiliate_INSIDE_Win7-%E5%AE%A3%E5%82%B3%E6%96%87%E7%AB%A0&utm_campaign=eoscampaign

xp win7 input

http://download.bestdaylong.com/f28.htm

dlink

d-link des-1252

Depends on your version of Moodle and what you have in the settings at Site administration > Plugins > Media players >Manage media players.

screen

您好

該機型以VGA連接最佳解析度為1920*1080@60Hz

硬體連接時請依照： 先打開螢幕電源完成開機>  連接VGA線材 >  最後開啟筆電

如此筆電方能正確讀取螢幕上之EDID顯示設定資訊。

 

如有需服務歡迎您與客服中心聯繫，奇美客服專線0800-663-000。客服中心全年AM8:30~PM9:30服務 (除夕/春節初一暫停服務)，如忙線中無人接聽亦可於語音系統中留言。

http://benevo.pixnet.net/blog/post/32902948-%E5%9C%A8%E7%AD%86%E9%9B%BB%E8%A8%AD%E5%AE%9A%E9%80%A3%E6%8E%A5%E5%88%B0%E6%8A%95%E5%BD%B1%E6%A9%9F%E6%A8%A1%E5%BC%8F-%E9%9B%99%E8%9E%A2%E5%B9%95-%E4%B8%89%E8%9E%A2%E5%B9%95

mac - print screen

https://support.apple.com/zh-tw/HT201361

table

https://marketplace.atlassian.com/apps/1211609/table-enhancer-for-confluence?hosting=server&tab=overview

https://marketplace.atlassian.com/apps/1212855/csv-table-export?hosting=server&tab=overview


https://marketplace.atlassian.com/apps/1218222/word4teams-ms-word-attachments-editor?hosting=server&tab=overview

https://marketplace.atlassian.com/apps/1218080/xtables?hosting=server&tab=overview

macbook troubleshooting

https://support.apple.com/zh-tw/HT204267

http://letsoffice.tw/nvram-smc/

Bartender

72hr,使用
提供7-14試用,
可轉移4次

收據編號：Receipt NO.
經辦人：Clerk
統一編號: Business Associate No
本收據需加蓋經辦人收訖章始為有效：This receipt will be valid upon approval.
本證明未經核准不得擅自塗改: This receipt can't be changed without permission

apple patch

https://www.ithome.com.tw/news/127523?fbclid=IwAR0CHRxiENGeM0ZAoOEZlGBpeVm-4PxJUSdbtPEHPIlJxn3eGKz7c_oTRW0

光纖資訊

http://benevo.pixnet.net/blog/post/45152089-%E5%A4%9A%E6%A8%A1%E5%85%89%E7%BA%96%E8%88%87%E5%96%AE%E6%A8%A1%E5%85%89%E7%BA%96%E4%B9%8B%E8%AA%AA%E6%98%8E

outlook

https://support.microsoft.com/zh-tw/help/2462816

https://tlcheng.wordpress.com/2017/05/07/%E5%AE%89%E5%85%A8-outlook-%E9%A0%90%E8%A8%AD%E7%84%A1%E6%B3%95%E9%A1%AF%E7%A4%BA%E7%B6%B2%E8%B7%AF%E4%B8%8A%E7%9A%84%E5%9C%96%E7%89%87%E6%89%8D%E6%98%AF%E6%AD%A3%E5%B8%B8%E7%9A%84%E8%A8%AD%E8%A8%88/#comment-3219

https://tlcheng.wordpress.com/2010/09/06/vbnet-%E5%9C%A8-html-%E9%83%B5%E4%BB%B6%E5%85%A7%E5%8A%A0%E5%85%A5%E6%A8%A3%E5%BC%8F%E5%BA%AB/

https://support.office.com/zh-hk/article/%E6%96%B0%E5%A2%9E%E5%9C%96%E5%BD%A2%E8%87%B3%E9%83%B5%E4%BB%B6%E5%9C%A8-outlook-%E4%B8%AD-114bb251-861f-41cd-b20f-7e7289630c5b

https://support.office.com/zh-hk/article/%E6%96%B0%E5%A2%9E%E5%9C%96%E5%BD%A2%E8%87%B3%E9%83%B5%E4%BB%B6%E5%9C%A8-outlook-%E4%B8%AD-114bb251-861f-41cd-b20f-7e7289630c5b

https://support.office.com/zh-tw/article/%E5%9C%A8-outlook-%E9%9B%BB%E5%AD%90%E9%83%B5%E4%BB%B6%E8%A8%8A%E6%81%AF%E4%B8%AD%E9%99%84%E5%8A%A0%E6%AA%94%E6%A1%88%E6%88%96%E6%8F%92%E5%85%A5%E5%9C%96%E7%89%87-bdfafef5-792a-42b1-9a7b-84512d7de7fc#ID0EAADAAA=Office_2010

https://isvincent.pixnet.net/blog/post/35479299-outlook-%E6%8E%A7%E5%88%B6%E9%83%B5%E4%BB%B6%E4%B8%AD%E7%9A%84%E5%9C%96%E7%89%87%E4%B8%8B%E8%BC%89%E5%92%8C%E9%99%84%E4%BB%B6%E9%A0%90%E8%A6%BD

driver and reply

It'd be great if you can let us know if your problem is solved or not and see if any further needs to be taken to solve the problem. Thanks again for the feedback and sorry for the inconvenience this problem might have caused you.

Our business hours are 09:00 - 12:30, 13:20 - 18:00, (Pacific Standard Time,Taiwan)Monday through Friday.

https://support.hp.com/tw-zh/drivers/selfservice/hp-elitedesk-800-g4-tower-pc/21353703

d2comm

http://d2comm.paxar.com/

mac internet option

https://www.imore.com/how-view-websites-your-mac-require-internet-explorer-or-pc

sql port

netsh firewall set portopening protocol = TCP port = 1433 name = SQLPort mode = ENABLE scope = SUBNET profile = CURRENT

hp z8g4 win7 solu

how to install Windows 7 on the HP Z4 G4, HP Z6 G4, and HP Z8 G4 Workstations with Intel Skylake Processors.
http://h20195.www2.hp.com/v2/getpdf.aspx/4AA7-2325ENW.pdf

api-ms-win-crt-runtime

https://support.microsoft.com/zh-tw/help/2999226/update-for-universal-c-runtime-in-windows
https://blog.xuite.net/sugopili/computerblog/459059218-%E5%AE%89%E8%A3%9D+api-ms-win-crt-runtime-l1-1-0.dll%E6%AA%94%E6%A1%88

box permission

https://community.box.com/t5/Collaborate-By-Inviting-Others/Understanding-Collaborator-Permission-Levels/ta-p/144

https://community.box.com/t5/Using-Shared-Links/Creating-Shared-Links/ta-p/19523

moodle course restore and backup

https://docs.moodle.org/35/en/Course_restore

adobe language package

https://supportdownloads.adobe.com/product.jsp?platform=windows&product=10

1002

<Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs" prefix="conf_access_log" suffix=".log" pattern="%t %{X-AUSERNAME}o %{User-Agent}i %h %m %r %b %s %I" />



https://confluence.atlassian.com/doc/working-with-confluence-logs-108364721.html#WorkingwithConfluenceLogs-runtime

https://confluence.atlassian.com/doc/working-with-confluence-logs-108364721.html

https://confluence.atlassian.com/doc/enabling-detailed-sql-logging-179030.html

https://confluence.atlassian.com/doc/configuring-logging-181535215.html

https://confluence.atlassian.com/confkb/how-to-enable-user-access-logging-182943.html

https://confluence.atlassian.com/confkb/audit-confluence-using-the-tomcat-valve-component-223216846.html

permission check
https://confluence.atlassian.com/confkb/confluence-does-not-start-due-to-spring-application-context-has-not-been-set-218278311.html#ConfluencedoesnotstartduetoSpringApplicationcontexthasnotbeenset-Linux

hp

http://h30318.www3.hp.com/pub/softlib/software13/COL40842/ds-99376-19/upd-ps-x64-6.6.0.23029.exe

outlook

https://blog.miniasp.com/post/2013/02/27/Mark-items-as-read-when-viewed-in-the-Reading-Pane-Wait-n-seconds-before-marking-item-as-read-in-Outlook-2013.aspx

http://sysadm.ntpu.edu.tw/close_mailview.html

outlook index

https://www.question-defense.com/2010/12/03/windows-7-indexing-speed-up-windows-indexing-process

ppt

https://read01.com/zh-tw/ymRAn5.html#.W4QFc-gzbIU

http://artofslide.blogspot.com/2012/08/powerpoint-2010.html

excel

https://ithelp.ithome.com.tw/questions/10016263

http://isvincent.pixnet.net/blog/post/43936108-excel-%E5%84%B2%E5%AD%98%E6%A0%BC%E5%85%A7%E5%AE%B9%E9%80%A3%E7%B5%90%E7%89%B9%E5%AE%9A%E8%B7%AF%E5%BE%91%E4%B8%AD%E7%9A%84%E6%B4%BB%E9%A0%81%E7%B0%BF%E6%AA%94%E6%A1%88

投影機

亮度較低，也可能會隨時點不著

moodle fix

https://moodle.org/mod/forum/discuss.php?d=137212

https://moodle.org/mod/forum/discuss.php?d=261799

https://moodle.org/mod/forum/discuss.php?d=225768

ppt

https://www.evinco-software.com/chi/blog/make-powerpoint-file-smaller/

https://www.pook.com.tw/single-post/2017/02/15/%E5%BE%B9%E5%BA%95%E8%A7%A3%E6%B1%BAPPT%E6%AA%94%E6%A1%88%E5%A4%A7%E5%B0%8F%E7%9A%84%E5%95%8F%E9%A1%8C


https://support.office.com/zh-tw/article/%E5%A3%93%E7%B8%AE%E5%AA%92%E9%AB%94%E6%AA%94%E6%A1%88-a45c956a-f4a6-4d47-99ef-b408ac5a9a6b


https://support.office.com/zh-tw/article/powerpoint-%E4%B8%AD%E6%94%AF%E6%8F%B4%E7%9A%84%E8%A6%96%E8%A8%8A%E8%88%87%E9%9F%B3%E8%A8%8A%E6%AA%94%E6%A1%88%E6%A0%BC%E5%BC%8F-d8b12450-26db-4c7b-a5c1-593d3418fb59


https://support.apple.com/kb/DL837?locale=zh_TW&viewlocale=zh_TW

word copy and past

http://isvincent.pixnet.net/blog/post/39005659-word-2010-%E6%9B%B4%E6%94%B9%E5%89%AA%E4%B8%8B%E3%80%81%E8%A4%87%E8%A3%BD%E8%88%87%E8%B2%BC%E4%B8%8A%E7%9A%84%E9%A0%90%E8%A8%AD%E5%80%BC

https://support.symantec.com/en_US/article.TECH247833.html

https://support.symantec.com/en_US/article.TECH247833.html

form

https://www.blueshop.com.tw/board/FUM20041006152627A9N/BRD20090325162246GFD.html

https://www.blueshop.com.tw/board/FUM20041006152627A9N/BRD20090326154907BBR.html

https://www.blueshop.com.tw/board/FUM200410061525290EW/BRD20050809100752PL9.html

https://www.blueshop.com.tw/board/FUM200410061525290EW/BRD200508130102008AF.html

win10

https://www.reddit.com/r/Windows10/comments/6efo8w/all_text_is_missing_from_windows_10/
https://support.symantec.com/en_US/article.TECH220751.html

https

https://confluence.atlassian.com/doc/running-confluence-over-ssl-or-https-161203.html?_ga=2.79995415.1468186615.1533996650-1321040226.1507470095

https://confluence.atlassian.com/doc/running-confluence-over-ssl-or-https-161203.html

win2016 patch update

https://www.windowslatest.com/2017/03/15/direct-download-links-kb3213986-2/

cron job

https://ithelp.ithome.com.tw/questions/10184231

https://ithelp.ithome.com.tw/questions/10184135

https://ithelp.ithome.com.tw/questions/10176238

igs install

http://3d-viewers.com/license.html

pdf font

https://helpx.adobe.com/tw/acrobat/using/pdf-fonts.html

https://helpx.adobe.com/tw/acrobat/kb/error-no-available-system-font.html

靜態路由

http://blog.xuite.net/ganpin917/home/49852565-%E9%9B%BB%E8%85%A6%E5%8F%8AServer+%E6%89%8B%E5%8B%95%E5%A2%9E%E5%8A%A0%E8%B7%AF%E7%94%B1

win10 performance

https://support.microsoft.com/zh-tw/help/4002019/windows-10-improve-pc-performance

https://windowsreport.com/text-missing-windows-10-fix/

https://windowsreport.com/start-menu-disappears-windows-10/

https://answers.microsoft.com/en-us/windows/forum/windows_10-start-winpc/windows-10-start-menu-text-missing/e7caeb92-2da9-4aeb-9f6c-896c982475bf

https://support.microsoft.com/zh-tw/help/12374/windows-10-troubleshoot-screen-flickering

info

http://heavenchou.buddhason.org/node/261

outlook - setup

https://social.technet.microsoft.com/Forums/zh-TW/db962c26-447c-471c-8936-002480d33e41/outlook-2007?forum=officezhcht

https://academy.blueeyes.com.tw/Calculate3.php


https://confluence.atlassian.com/confkb/exceeds-max-allowed-packet-for-mysql-179443425.html?_ga=2.196085228.1148639263.1532520400-1321040226.1507470095

https://confluence.atlassian.com/confkb/confluence-will-not-update-or-install-add-ons-408453565.html

https://community.atlassian.com/t5/Confluence-questions/Unable-to-update-confluence-plugins-any-ideas/qaq-p/373774https://social.msdn.microsoft.com/Forums/zh-TW/a7ec6b3e-8e68-4fef-bbfd-f2c4f3b2b622/win10-log?forum=win10itprogeneralTW


https://social.technet.microsoft.com/Forums/windows/en-US/0100acd8-b7c8-416a-bd62-af92c92b259f/dns-client-server-event-8027-and-8033?forum=w8itprogeneral


https://social.technet.microsoft.com/Forums/windows/en-US/0100acd8-b7c8-416a-bd62-af92c92b259f/dns-client-server-event-8027-and-8033?forum=w8itprogeneral

info-dvr

https://www.security-camera-warehouse.com/knowledge-base/cif-vs-d1/

http://www.pcstore.com.tw/vion5588/M33635288.htm

php

https://pjchender.blogspot.com/2015/04/blog-post.html


http://www.blueshop.com.tw/board/FUM20041006152627A9N/BRD20090326135152QRQ.html
http://www.blueshop.com.tw/board/FUM20041006152627A9N/BRD20090325162246GFD.html

http://www.blueshop.com.tw/board/FUM20041006152627A9N/BRD20090326154907BBR.html


https://jira.atlassian.com/browse/CONFSERVER-25476?jql=project%20%3D%20CONFSERVER%20AND%20issuetype%20%3D%20Bug%20AND%20affectedVersion%20%3D%204.2.1

win10 text disappler

https://partnersupport.microsoft.com/zh-hant/par_clientsol/forum/par_win/win10微軟自動更/f528e1de-6b07-49e4-b5de-eb44f5a4dc0b

https://drive.google.com/drive/folders/1okpl7-D9PUroNp5AfQGpYeHDRLhhKzWG?usp=sharing

https://support.microsoft.com/en-us/help/299357/how-to-reset-tcp-ip-by-using-the-netshell-utility

calculator:

apple install windows

https://support.apple.com/zh-tw/ht205016

system fix

https://support.microsoft.com/en-us/help/2970908/how-to-use-microsoft-easy-fix-solutions

https://dotblogs.com.tw/chou/archive/2010/07/23/16714.aspx

traert

tracert.exe www.google.com >> d:\log.txt

ckeditor

http://blog.xuite.net/tolarku/blog/229329277-%5BAsp.net%5D+%E4%BD%BF%E7%94%A8+CKEditor+%2B+CKFinder+%E6%8F%90%E4%BE%9B+WYSIWYG+%E7%B6%B2%E9%A0%81%E5%85%A7%E5%AE%B9%E7%B7%A8%E8%BC%AF%E5%99%A8

https://drive.google.com/drive/folders/1Lr4M0RWXUkRGpOyaPKDHf67bgiJZl0aI?usp=sharing

win10 video format

https://www.winxdvd.com/windows-10/media-formats-supported-by-windows-10.htm

command

在開機時，按下F8進入
"帶命令提示符的安全"模式
輸入  NET USER USERID 123456
可把某使用者的密碼強行設置為123456

2.
知道Administrator的密碼的情況下
可用 net user USERID/add 增加一帳號
並用 net localgroup administrators USERID/add 將該帳號放入
Administrators的群組內，就可用該帳號作修改其他帳號密碼的工作  

方法二：使用電腦的本機電腦群組原則「啟動腳本」

編寫一個a.bat批次檔，內容為 net user USERID password

用CMD指令為

echo net user USERID password > a.bat

放到以下位址

X:\Windows\System32\GroupPolicy\Machine\Scripts\Startup

https://www.sevenforums.com/tutorials/181426-user-account-enable-disable.html

How to Enable or Disable a User Account in Windows 7 and Windows 8

   Information

This tutorial will show you how to enable (unlock) or disable (lock) a domain, local, or Microsoft user account in Windows 7 and Windows 8.

You must be logged in as an administrator to be able to do the steps in this tutorial.

   Note

When a user account is disabled, the user account will no longer be listed in User Accounts in the Control Panel, Parental Controls, log on screens, and can no longer be logged in to.

An administrator account will still be able to navigate to and access the contents of the C:\Users\(user-name) folder of a disabled user account using Windows Explorer.

 OPTION ONE 

Enable or Disable User Account in "Local Users and Groups"

1. Open Local Users and Groups, and click/tap on the Users folder in the left pane to open it. (see screenshot below)

2. In the middle pane of Users, double click/tap on the user account name (ex: Example-Account) that you want to enable or disable. (see screenshot above)

3. Do step 4 or 5 below depending on if you would like to enable or disable the user account.

4. To Enable and Unlock a User Account
NOTE: This is the default setting.

A) In the General tab, uncheck the Account is disabled box, click/tap on OK, and go to step 6 below. (see screenshot below)

5. To Disable and Lock a User Account

A) In the General tab, check the Account is disabled box, click/tap on OK, and go to step 6 below. (see screenshot above)

6. When finished, close the Local Users and Groups window.

 OPTION TWO 

Enable or Disable User Account in an "Elevated Command Prompt"

NOTE: This option will use the net user command to enable or disable a user account or domain account.

1. Open an elevated command prompt in Windows 7 or Windows 8.

2. To See if a User Account is Disabled or Enabled in a Command Prompt

A) In the elevated command prompt, type either command below and press Enter.
NOTE: This will give you a list of all users accounts either on your local computer or on the domain.

(Accounts on your computer) - Net user

(Accounts on domain) - Net user /domain

B) In the elevated command prompt, type either command below for the user account (ex: Example Account) that you want to see is enabled or disable, and press Enter.
NOTE: This will allow you to see the Account active details and more of the user account. Yes = enabled and No = disabled. Substitute User Name in the command below with the user name (ex: Example Account) of the user account (ex: Example Account) within quotes.

(Account on your computer) - Net user "User Name"

(Account on domain) - Net user "User Name" /domain

3. Do step 4 or 5 below depending on if you would like to enable or disable the user account.

4. To Enable a Local or Domain User Account
NOTE: This is the default setting.

A) In the elevated command prompt, type either command below for the user account (ex: Example Account) that you want to enable, and press Enter.
NOTE: Substitute User Name in the command below with the user name (ex: Example Account) of the user account (ex: Example Account) within quotes.

(Enable local account)
Net user "User Name" /active:yes

(Enable domain account)
Net user "User Name" /active:yes /domain

5. To Disable a Local or Domain User Account

A) In the elevated command prompt, type either command below for the user account (ex: Example Account) that you want to disable, and press Enter.
NOTE: Substitute User Name in the command below with the user name (ex: Example Account) of the user account (ex: Example Account) within quotes.

(Disable local account)
Net user "User Name" /active:no

(Disable domain account)
Net user "User Name" /active:no /domain

synmatec

https://support.symantec.com/en_US/article.TECH91587.html

https://support.symantec.com/en_US/article.TECH191617.html

titanFTP

titanFTP

bulk insert account

https://moodle.org/mod/forum/discuss.php?d=330150#p1328560

share drive link add

http://benjr.tw/98858

pdf to excel

http://www.pdfmate.com/3-ways-to-convert-pdf-to-excel.html

ping

https://www.mobile01.com/topicdetail.php?f=507&t=3343420

http://smalleaf.blogspot.com/2011/12/ttl.html

http://www.ublink.org/index.php/news/313-ping-lose

win10 close

https://blog.3bro.info/archives/windows-event-viewer/

https://www.ptt.cc/bbs/Windows/M.1270604160.A.648.html

http://catchtest.pixnet.net/blog/post/17674551-%E6%9F%A5%E8%A9%A2%E9%96%8B%E9%97%9C%E6%A9%9F%E6%99%82%E9%96%93%E5%90%A7

https://kknews.cc/zh-tw/digital/n5o84q8.html

https://www.mobile01.com/topicdetail.php?f=300&t=4484777

scanap

https://drive.google.com/file/d/11M-bjz9IGZ7_m6bOh05ESpeuZOmmfiwR/view?usp=sharing

outlook

http://blog.xuite.net/ppopp33/blog/45372160-%E4%B8%8D%E8%A3%9Doutlook%EF%BC%8C%E4%B9%9F%E5%8F%AF%E9%96%8B%E5%95%9F%E6%9F%A5%E7%9C%8Bpst%E6%AA%94%28pst%E4%B8%8D%E6%98%AF%E5%80%8B%E4%BA%BA%E8%B3%87%E6%96%99%E5%A4%BE%E6%AA%94%E6%A1%88%29

moodle login form

Hi Anderson,
Given the date you posted this question, you might have already figured out the solution. But I hope it will be helpful to other users.
For the cursor to focus on the 'username' field on the login page, 'loginpageautofocus' option should be enabled.
To locate the page to modify this option, you can either search 'loginpageautofocus' in the global administration search field, or you can navigate to:
Site administration >> Plugins >> Authentication >> Manage authentication

and scroll down to "Autofocus login page form" section. By default, it is set to "No".
Thank you,
Gehendra

firefox

https://support.mozilla.org/zh-TW/get-involved

https://voice.mozilla.org/zh-TW

https://www.mozilla.org/zh-TW/contribute/signup/

https://testpilot.firefox.com/?utm_source=www.mozilla.org&utm_medium=referral&utm_campaign=fx-content-hub

viewsonic

https://www.viewsonic.com/hk/products/lcd/va2265smh.php#pSpecs

wifi

https://walker-a.com/archives/4631

https://zi.media/@walker-a/post/awCBks


http://www.lovemytool.com/blog/2010/05/wifi-diagnostics-from-windows-7-or-vista-command-prompt-by-tony-fortunato.html

http://techgenix.com/newnetshwlancommandsinwindows7andserver2008r2/

check 5/29
http://3c.ltn.com.tw/news/27752

https://www.intel.com.tw/content/www/tw/zh/support/detect.html

https://www.intel.com.tw/content/www/tw/zh/support/articles/000005879/network-and-i-o/wireless-networking.html

https://www.intel.com.tw/content/www/tw/zh/support/articles/000005875/network-and-i-o/wireless-networking.html

https://www.intel.com.tw/content/www/tw/zh/support/detect.html

hp

https://support.hp.com/us-en/contact-hp

https://mycrm.support.hp.com/en-US/SignIn?ReturnUrl=%2Fen-US%2Fcreate-case%2F%3Fainfo%3DCND8K5T8HR

win10

https://drive.google.com/file/d/1f5UOmUqWQZTNzV9ZonC6RYxJ_2uFkZuH/view?usp=sharing

https://social.technet.microsoft.com/Forums/windows/en-US/18667011-c034-43bc-ab2e-0e87bf811e5e/windows-7-increase-the-limit-of-concurrent-tcp-connections-not-related-to-eula-file-sharing?forum=w7itpronetworking
https://forum.gamer.com.tw/C.php?bsn=27943&snA=754

https://social.technet.microsoft.com/Forums/zh-TW/b66c9506-0283-4e28-b1ff-6ed119c5bf1c/win10-?forum=win10itprogeneralTW

https://www.sony.com.tw/zh/electronics/support/articles/00051695

https://windowsreport.com/windows-10-internet-connection-issues/

https://windowsreport.com/windows-10-kb3201845-bugs/

https://downloadcenter.intel.com/zh-tw/download/25016/Intel-Network-Adapter-Driver-for-Windows-10

https://windowsreport.com/connect-hidden-wi-fi-network-windows-10/

https://www.coolutils.com/MSG-to-Outlook

https://www.coolutils.com/MSG-to-PST

shutdown find
https://www.tenforums.com/tutorials/78335-read-shutdown-logs-event-viewer-windows.html

https://www.maketecheasier.com/see-pc-startup-and-shutdown-history-in-windows/

box app

https://developer.box.com/reference#get-embed-link

https://community.box.com/t5/custom/page/page-id/BoxViewTicketDetail?ticket_id=1660330

centos

Hello,

You can find all the license information in the installation itself.

CentOS Linux is a redistribution of many thousands of software packages that are governed by their own licenses.

The permission you look for is covered by those licenses.

CentOS Linux does have an end user license agreement (EULA) included that you can view here:

http://mirror.centos.org/centos/7/os/x86_64/EULA

The GPLv2 license referred there is this license:

https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html

I hope this answers your questions.

Best regards,

- Karsten

oxps

https://drive.google.com/open?id=0BxriXuT0xeaFeUJJZ0hETF92bHM

box

https://drive.google.com/drive/folders/14em4jwz4tvhTCV2xPBHqB5GSrggDrlrp?usp=sharing

https://community.box.com/t5/Using-Box-Edit/Opening-and-Editing-Files-with-Box-Edit/ta-p/19160

https://community.box.com/t5/How-to-Guides-for-Integrations/Box-for-Office-Integrations/ta-p/324

https://community.box.com/t5/Box-API-Guides-for-Admins/Box-API-Recipes-for-Box-Admins/ta-p/37489

https://community.box.com/t5/custom/page/page-id/BoxViewTicketDetail?ticket_id=1655256


http://mirror.centos.org/centos/7/os/x86_64/EULA

https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html


https://community.box.com/t5/custom/page/page-id/BoxViewTicketDetail?ticket_id=1655259

https://community.box.com/t5/How-to-Guides-for-Account/Configuring-A-Firewall-For-Box-Applications/ta-p/12

 https://community.box.com/t5/custom/page/page-id/BoxViewTicketDetail?ticket_id=1656738

cisco

您好！欢迎致信思科售后技术支持中心。

由于我们是思科前端的客服人员，没有任何技术背景，所以不能直接解答您的问题。如果您需要得到思科公司的直接技术支持，请您提供以下相关信息。

CASE 类型：故障诊断/备件更换
用户名 (CCO)：
产品序列号(SN)：(如果您是为软件产品申请故障诊断的case，请忽略此项)
售后服务合同号：
故障描述：
最终用户信息：
联系人&电话&邮件地址：

届时，我们会核实您所提供的信息并及时与您取得联系。

language

https://briian.com/6296/

https://www.mobile01.com/topicdetail.php?f=300&t=1237377

https://support.hp.com/vn-en/document/c01409647#AbT1

http://aries.dyu.edu.tw/~tarng/dyu_c.c/Win10_Safe.htm

HDMI 3D: 用於HDMI-1.4a,禎封裝格式或上下格式的720/1080P，並非格式的1080i 

php redirect

http://s90304a123.pixnet.net/blog/post/39295907-php%E8%B7%B3%E8%BD%89%E9%A0%81%E9%9D%A2

m

https://drive.google.com/file/d/1li8Lo4d9JhP-HJzb7-nbXsHNkpwCaHnK/view?usp=sharing

https://drive.google.com/file/d/1jdnrximSGcWRZuuGA4KTSUp-zULYp6sg/view?usp=sharing

http://www.px.com.tw/

english learn

The following table shows the relative performance as the load increases for each Confluence instance configuration: Confluence Server, two node Confluence Data Center, and four node Confluence Data Center. The table shows the response time relative to the baseline response time which we determined to be Confluence Server with sixteen browsers. 

Today’s Friday Favorite is a helpful solution for my fellow Jira admins who have struggled to achieve a streamlined, standardized practice to escalate support requests to development. This dynamic duo of apps can automate a cumbersome and easily fumbled process, and, in turn, help you achieve those always important SLAs and time-to-resolution goals.

The very useful CallCenter for Jira Service Desk app allows customers to easily initiate new service requests over the phone, either by talking to an agent directly or through guided voice prompts. These requests are filled in with the same fields, issue types, and SLAs as standard web-based tickets, and placed into the same Service Desk queue.

Then, when a support ticket with a “bug” issue type enters a queue, Create on Transition for Jira can be triggered to automatically create a linked issue in the relevant project, pre-populate the fields, and add labels, assignees, watchers, attachments, comments, and more. Countless hours and valuable resources saved! :)

To bring this process full circle, because both the service ticket and development issue are linked from the start, the service desk agent can quickly navigate between issues to stay informed on the status of the bug fix. Plus, after configuring a simple Jira setting, agents can be automatically notified when a developer resolves a linked issue as “fixed,” and then follow up with the customer. As a result, communication between support and development teams improves, and nothing gets lost in the shuffle.

So, if your admins, engineers, and service desk agents are spending valuable time creating and linking issues and checking on bug fix statuses, then it may be time to take a look at these two handy apps on the Atlassian Marketplace.

Now, go have a great weekend! :)

confluence3

https://confluence.atlassian.com/confkb/confluence-admin-permission-levels-explained-604209420.html

https://confluence.atlassian.com/doc/page-restrictions-139414.html

adobe

https://forums.adobe.com/message/10318256#10318256

https://forums.adobe.com/thread/1452292?tstart=0

https://helpx.adobe.com/download-install/using/download-creative-cloud-apps.html

box ticket

https://community.box.com/t5/custom/page/page-id/submit_unauthenticated

Confluence disk check

os

http://download.microsoft.com/download/3/A/A/3AAD8D67-E23C-426F-9D0B-2BC3552BC9EA/InputMethodEditor%20x86%20zh-tw.exe

https://social.technet.microsoft.com/Forums/windows/zh-TW/b66c9506-0283-4e28-b1ff-6ed119c5bf1c/win10-?forum=win10itprogeneralTW

http://www.windinin.com/2016/03/windows-10.html

mysql3

linux3

https://serverfault.com/questions/742209/how-can-the-hostname-go-missing-on-linux

https://serverfault.com/questions/742209/how-can-the-hostname-go-missing-on-linux


https://scottlinux.com/2012/06/09/cant-ping-localhost-in-linux/

mysql

180406 22:02:19  InnoDB: Waiting for the background threads to start
180406 22:02:20 InnoDB: 5.5.42 started; log sequence number 2447407723
180406 22:02:20 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
180406 22:02:20 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
180406 22:02:20 [Note] Server socket created on IP: '0.0.0.0'.
180406 22:02:20  InnoDB: Error: page 1634 log sequence number 2448111769
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:20  InnoDB: Error: page 11748 log sequence number 2453014172
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:20  InnoDB: Error: page 997 log sequence number 2448111763
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:20  InnoDB: Error: page 10009 log sequence number 2454137883
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:20  InnoDB: Error: page 10011 log sequence number 2454164920
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:20  InnoDB: Error: page 11511 log sequence number 2451636431
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:20 InnoDB: Unable to allocate memory of size 18446744073709545496.
180406 22:02:20  InnoDB: Assertion failure in thread 140481254418176 in file mem0mem.c line 361
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
14:02:20 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=8388608
read_buffer_size=131072
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 = 338508 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
180406 22:02:20 [ERROR] Missing system table mysql.proxies_priv; please run mysql_upgrade to create it
180406 22:02:20 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure
180406 22:02:20 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure
180406 22:02:20 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure
180406 22:02:20 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure
180406 22:02:20 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure
180406 22:02:20 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure
180406 22:02:20 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure
180406 22:02:20 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure
180406 22:02:20 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
180406 22:02:20 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
180406 22:02:20 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
180406 22:02:20 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
180406 22:02:20 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
180406 22:02:20 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
180406 22:02:20 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
180406 22:02:20 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
180406 22:02:20 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
180406 22:02:20 [Note] Event Scheduler: Loaded 0 events
180406 22:02:20 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.42'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Server (GPL) by Remi
/usr/libexec/mysqld(my_print_stacktrace+0x2e)[0x78c92e]
/usr/libexec/mysqld(handle_fatal_signal+0x493)[0x675473]
/lib64/libpthread.so.0[0x34ca00f710]
/lib64/libc.so.6(gsignal+0x35)[0x34c9c32625]
/lib64/libc.so.6(abort+0x175)[0x34c9c33e05]
/usr/libexec/mysqld[0x8cf7a0]
/usr/libexec/mysqld[0x8cf7f0]
/usr/libexec/mysqld[0x8cf9fd]
/usr/libexec/mysqld[0x838ff4]
/usr/libexec/mysqld[0x83906c]
/usr/libexec/mysqld[0x83e294]
/usr/libexec/mysqld[0x82730a]
/usr/libexec/mysqld[0x8f50b2]
/usr/libexec/mysqld[0x860ee6]
/usr/libexec/mysqld[0x819e06]
/usr/libexec/mysqld[0x8f5260]
/usr/libexec/mysqld[0x8f57ee]
/usr/libexec/mysqld[0x8f5f90]
/usr/libexec/mysqld[0x8ebfb5]
/usr/libexec/mysqld[0x8366a5]
/usr/libexec/mysqld[0x82982c]
/usr/libexec/mysqld[0x82da23]
/lib64/libpthread.so.0[0x34ca0079d1]
/lib64/libc.so.6(clone+0x6d)[0x34c9ce88fd]
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.
180406 22:02:20 mysqld_safe Number of processes running now: 0
180406 22:02:20 mysqld_safe mysqld restarted
180406 22:02:21 [Note] Plugin 'FEDERATED' is disabled.
180406 22:02:21 InnoDB: The InnoDB memory heap is disabled
180406 22:02:21 InnoDB: Mutexes and rw_locks use GCC atomic builtins
180406 22:02:21 InnoDB: Compressed tables use zlib 1.2.3
180406 22:02:21 InnoDB: Using Linux native AIO
180406 22:02:21 InnoDB: Initializing buffer pool, size = 128.0M
180406 22:02:21 InnoDB: Completed initialization of buffer pool
180406 22:02:21 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!
180406 22:02:21  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...
180406 22:02:21  InnoDB: Error: page 12002 log sequence number 2453750257
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 12007 log sequence number 2453750000
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 11999 log sequence number 2453751788
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 710 log sequence number 2447778739
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 11459 log sequence number 2452727152
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 1434 log sequence number 2447779955
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 11983 log sequence number 2451637965
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 2358 log sequence number 2447780536
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 2974 log sequence number 2453046618
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 2978 log sequence number 2453046355
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 1439 log sequence number 2447780729
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 1440 log sequence number 2447780942
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 1441 log sequence number 2447781115
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 742 log sequence number 2447781682
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 850 log sequence number 2447781869
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 855 log sequence number 2447782078
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 1442 log sequence number 2447782275
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 1443 log sequence number 2447782663
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 1830 log sequence number 2447782852
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 1444 log sequence number 2447783061
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 1837 log sequence number 2447783229
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 10177 log sequence number 2454123240
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 1848 log sequence number 2447783631
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 1445 log sequence number 2447783826
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 10181 log sequence number 2454123811
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 892 log sequence number 2447784399
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 900 log sequence number 2447784774
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 1446 log sequence number 2447784977
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 1448 log sequence number 2447785548
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 10191 log sequence number 2454125608
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 1449 log sequence number 2447785938
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 11458 log sequence number 2450939970
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 2305 log sequence number 2447786141
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 10199 log sequence number 2454126348
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 10203 log sequence number 2454126744
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 1450 log sequence number 2447787108
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 10208 log sequence number 2454127138
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 10215 log sequence number 2454127329
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 11876 log sequence number 2454127518
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 12430 log sequence number 2449201262
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 1451 log sequence number 2447787838
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 11525 log sequence number 2448816743
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 1022 log sequence number 2447787990
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 10221 log sequence number 2454128090
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 10225 log sequence number 2454128297
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 11476 log sequence number 2450227049
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 11506 log sequence number 2450226411
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 1452 log sequence number 2447788788
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 11535 log sequence number 2454128892
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 11906 log sequence number 2454129065
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 1453 log sequence number 2447789364
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 10232 log sequence number 2454129440
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 10235 log sequence number 2454129627
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 11914 log sequence number 2454129834
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 10238 log sequence number 2454130009
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 11917 log sequence number 2454130214
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 1840 log sequence number 2447790465
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 1843 log sequence number 2447790672
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 1844 log sequence number 2447766677
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 1454 log sequence number 2447766836
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 11516 log sequence number 2448110270
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 11521 log sequence number 2448109643
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 1321 log sequence number 2447767234
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 11928 log sequence number 2454131774
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 12106 log sequence number 2448111701
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 812 log sequence number 2447767819
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 11524 log sequence number 2449521962
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 11532 log sequence number 2449521699
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 11935 log sequence number 2454132504
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 12060 log sequence number 2449523394
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 11943 log sequence number 2454133267
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 647 log sequence number 2447769143
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 3460 log sequence number 2454133645
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 1628 log sequence number 2447769535
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 11953 log sequence number 2454134030
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 841 log sequence number 2447769908
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 660 log sequence number 2447770061
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 663 log sequence number 2447770266
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 666 log sequence number 2447770459
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 670 log sequence number 2447770672
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 673 log sequence number 2447770842
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 12058 log sequence number 2454135338
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 1576 log sequence number 2447771217
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 1346 log sequence number 2447771408
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 11393 log sequence number 2454111528
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 704 log sequence number 2447771921
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 11855 log sequence number 2454449051
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 11863 log sequence number 2454448788
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 1903 log sequence number 2447772102
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 722 log sequence number 2447772315
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 729 log sequence number 2447772496
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 738 log sequence number 2447772705
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 748 log sequence number 2447772882
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 12103 log sequence number 2447413755
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 751 log sequence number 2447773057
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 756 log sequence number 2447773264
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 761 log sequence number 2447773457
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 764 log sequence number 2447773634
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 770 log sequence number 2447773827
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 774 log sequence number 2447774012
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 980 log sequence number 2447774191
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 1384 log sequence number 2447774374
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 3518 log sequence number 2454114409
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 988 log sequence number 2447774774
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 786 log sequence number 2447774934
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 990 log sequence number 2447775131
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 981 log sequence number 2447775318
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 789 log sequence number 2447775507
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 794 log sequence number 2447775680
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 3011 log sequence number 2452726859
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 3019 log sequence number 2452338925
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 989 log sequence number 2447775891
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
180406 22:02:21  InnoDB: Error: page 991 log sequence number 2447776088
InnoDB: is in the future! Current system log sequence number 2447407723.
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.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
InnoDB: 7 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 11303 row operations to undo
InnoDB: Trx id counter is 5ADD00
InnoDB: Cleaning up trx with id 5B1BFD
InnoDB: Cleaning up trx with id 5B159E
InnoDB: Cleaning up trx with id 5B0F3E
InnoDB: Cleaning up trx with id 5B08AD
InnoDB: Cleaning up trx with id 5AF58D
InnoDB: Cleaning up trx with id 5AEF2C
InnoDB: Cleaning up trx with id 5AE239
180406 22:02:21  InnoDB: Error: page 1075 log sequence number 2448111775
InnoDB: is in the future! Current system log sequence number 2447407723.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See