2023-05-19T03:23:11.464631Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.464639Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.464647Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.464655Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.464663Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.464671Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.464678Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.464687Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.464694Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.464702Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.464710Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.464718Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.464726Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.464734Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.464741Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.464750Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.464757Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.464765Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.464773Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.464781Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.464788Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.464796Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.464809Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.464818Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.464826Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.464835Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.464842Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.464851Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.464858Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.464867Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.464874Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.464882Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.464890Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.464898Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.464906Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.464914Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.464922Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.464930Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.464937Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.464946Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.464953Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.464961Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.464969Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.464977Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.464985Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.464993Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465000Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465013Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465022Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465031Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465038Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465046Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465054Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465063Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465070Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465079Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465086Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465095Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465102Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465111Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465118Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465126Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465134Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465142Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465150Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465158Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465166Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465174Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465182Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465190Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465198Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465206Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465218Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465228Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465236Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465244Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465252Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465260Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465268Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465276Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465284Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465292Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465300Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465308Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465316Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465338Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465351Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465360Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465368Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465377Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465384Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465393Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465400Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465409Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465417Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465426Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465433Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465447Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465456Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465464Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465472Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465480Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465488Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465496Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465503Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465512Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465519Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465527Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465535Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465543Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465551Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465559Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465567Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465575Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465582Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465591Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465598Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465606Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465614Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465622Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465630Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465638Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465651Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465660Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465668Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465677Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465684Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465692Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465700Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465708Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465716Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465724Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465732Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465740Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465748Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465757Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465764Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465773Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465780Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465789Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465796Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465804Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465812Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465820Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465828Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465836Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465844Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465857Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465866Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465874Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465882Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465890Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465898Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465906Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465914Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465922Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465930Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465938Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465946Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465954Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465962Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465970Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465978Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.465986Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.465994Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.466002Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.466010Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.466018Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.466026Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.466034Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.466042Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.466051Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.466063Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.466072Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.466080Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.466088Z 0 [ERROR] InnoDB: Trying to do I/O to a tablespace which does not exist. I/O type: read, page: [page id: space=473, page number=3], I/O length: 16384 bytes
2023-05-19T03:23:11.466096Z 0 [ERROR] InnoDB: trying to read page [page id: space=473, page number=3] in nonexisting or being-dropped tablespace
2023-05-19T03:23:11.466105Z 0 [ERROR] [FATAL] InnoDB: Unable to read page [page id: space=473, page number=3] into the buffer pool after 100 attempts. The most probable cause of this error may be that the table has been corrupted. Or, the table was compressed with with an algorithm that is not supported by this instance. If it is not a decompress failure, you can try to fix this problem by using innodb_force_recovery. Please see http://dev.mysql.com/doc/refman/5.7/en/ for more details. Aborting...
2023-05-19 11:23:11 0x2ad8ae90d700  InnoDB: Assertion failure in thread 47110130030336 in file ut0ut.cc line 921
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.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
03:23:11 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=536870912
read_buffer_size=8388608
max_used_connections=15
max_threads=500
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 = 8722983 K  bytes of memory
Hope thats 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
/www/server/mysql/bin/mysqld(my_print_stacktrace+0x2c)[0xed32cc]
/www/server/mysql/bin/mysqld(handle_fatal_signal+0x476)[0x79d656]
/lib64/libpthread.so.0(+0xf630)[0x2ad7cbddc630]
/lib64/libc.so.6(gsignal+0x37)[0x2ad7cd759387]
/lib64/libc.so.6(abort+0x148)[0x2ad7cd75aa78]
/www/server/mysql/bin/mysqld[0x76dea2]
/www/server/mysql/bin/mysqld(_ZN2ib5fatalD1Ev+0xee)[0x10a01ee]
/www/server/mysql/bin/mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x6d2)[0x10df812]
/www/server/mysql/bin/mysqld(_Z27btr_cur_search_to_nth_levelP12dict_index_tmPK8dtuple_t15page_cur_mode_tmP9btr_cur_tmPKcmP5mtr_t+0x661)[0x10bf0b1]
/www/server/mysql/bin/mysqld[0x100d6a5]
/www/server/mysql/bin/mysqld[0x1011ea0]
/www/server/mysql/bin/mysqld(_Z12row_sel_stepP9que_thr_t+0x3b)[0x101416b]
/www/server/mysql/bin/mysqld(_Z15que_run_threadsP9que_thr_t+0x6d1)[0xfb7b51]
/www/server/mysql/bin/mysqld(_Z12fts_eval_sqlP5trx_tP10que_fork_t+0x2d)[0x11b0d9d]
/www/server/mysql/bin/mysqld[0x119027b]
/www/server/mysql/bin/mysqld[0x119049a]
/www/server/mysql/bin/mysqld(_Z14fts_sync_tableP12dict_table_tbbb+0x584)[0x1190f44]
/www/server/mysql/bin/mysqld(_Z23fts_optimize_sync_tablem+0x3f)[0x11a331f]
/www/server/mysql/bin/mysqld(_Z19fts_optimize_threadPv+0x259)[0x11a3599]
/lib64/libpthread.so.0(+0x7ea5)[0x2ad7cbdd4ea5]
/lib64/libc.so.6(clone+0x6d)[0x2ad7cd821b0d]
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.
2023-05-19T03:23:25.446235Z 0 [Warning] option max_allowed_packet: unsigned value 107374182400 adjusted to 1073741824
2023-05-19T03:23:25.446423Z 0 [Warning] NO_ZERO_DATE, NO_ZERO_IN_DATE and ERROR_FOR_DIVISION_BY_ZERO sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2023-05-19T03:23:25.446433Z 0 [Warning] NO_AUTO_CREATE_USER sql mode was not set.
2023-05-19T03:23:25.446465Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2023-05-19T03:23:25.446517Z 0 [Note] /www/server/mysql/bin/mysqld (mysqld 5.7.40-log) starting as process 36348 ...
2023-05-19T03:23:25.495666Z 0 [Note] InnoDB: PUNCH HOLE support available
2023-05-19T03:23:25.495730Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2023-05-19T03:23:25.495737Z 0 [Note] InnoDB: Uses event mutexes
2023-05-19T03:23:25.495743Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2023-05-19T03:23:25.495749Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
2023-05-19T03:23:25.495757Z 0 [Note] InnoDB: Using Linux native AIO
2023-05-19T03:23:25.496349Z 0 [Note] InnoDB: Number of pools: 1
2023-05-19T03:23:25.496503Z 0 [Note] InnoDB: Using CPU crc32 instructions
2023-05-19T03:23:25.504759Z 0 [Note] InnoDB: Initializing buffer pool, total size = 2G, instances = 8, chunk size = 128M
2023-05-19T03:23:25.679067Z 0 [Note] InnoDB: Completed initialization of buffer pool
2023-05-19T03:23:25.706512Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2023-05-19T03:23:25.718779Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2023-05-19T03:23:25.732343Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 6582012208494
2023-05-19T03:23:25.732371Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 6582012208761
2023-05-19T03:23:25.732816Z 0 [Note] InnoDB: Database was not shutdown normally!
2023-05-19T03:23:25.732825Z 0 [Note] InnoDB: Starting crash recovery.
2023-05-19T03:23:25.765244Z 0 [Note] InnoDB: Last MySQL binlog file position 0 21493, file name mysql-bin.000310
2023-05-19T03:23:25.881137Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.881159Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.881166Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.881174Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/FTS_000000000000014b_000000000000036e_INDEX_1.ibd OS error: 71
2023-05-19T03:23:25.881180Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.881186Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.881191Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.881201Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/FTS_000000000000014b_000000000000036e_INDEX_1`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.881212Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/FTS_000000000000014b_000000000000036e_INDEX_1` because it could not be opened.
2023-05-19T03:23:25.881237Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.881244Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.881265Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.881271Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/FTS_000000000000014b_000000000000036e_INDEX_2.ibd OS error: 71
2023-05-19T03:23:25.881277Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.881282Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.881287Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.881293Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/FTS_000000000000014b_000000000000036e_INDEX_2`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.881300Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/FTS_000000000000014b_000000000000036e_INDEX_2` because it could not be opened.
2023-05-19T03:23:25.881329Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.881341Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.881347Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.881353Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/FTS_000000000000014b_000000000000036e_INDEX_3.ibd OS error: 71
2023-05-19T03:23:25.881358Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.881363Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.881368Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.881374Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/FTS_000000000000014b_000000000000036e_INDEX_3`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.881381Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/FTS_000000000000014b_000000000000036e_INDEX_3` because it could not be opened.
2023-05-19T03:23:25.881403Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.881410Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.881415Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.881421Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/FTS_000000000000014b_000000000000036e_INDEX_4.ibd OS error: 71
2023-05-19T03:23:25.881426Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.881431Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.881436Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.881442Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/FTS_000000000000014b_000000000000036e_INDEX_4`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.881449Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/FTS_000000000000014b_000000000000036e_INDEX_4` because it could not be opened.
2023-05-19T03:23:25.881469Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.881476Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.881481Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.881493Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/FTS_000000000000014b_000000000000036e_INDEX_5.ibd OS error: 71
2023-05-19T03:23:25.881499Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.881504Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.881509Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.881514Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/FTS_000000000000014b_000000000000036e_INDEX_5`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.881522Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/FTS_000000000000014b_000000000000036e_INDEX_5` because it could not be opened.
2023-05-19T03:23:25.881543Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.881549Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.881555Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.881560Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/FTS_000000000000014b_000000000000036e_INDEX_6.ibd OS error: 71
2023-05-19T03:23:25.881566Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.881571Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.881576Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.881582Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/FTS_000000000000014b_000000000000036e_INDEX_6`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.881589Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/FTS_000000000000014b_000000000000036e_INDEX_6` because it could not be opened.
2023-05-19T03:23:25.881610Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.881616Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.881622Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.881627Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/FTS_000000000000014b_0000000000000375_INDEX_1.ibd OS error: 71
2023-05-19T03:23:25.881633Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.881638Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.881643Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.881648Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/FTS_000000000000014b_0000000000000375_INDEX_1`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.881656Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/FTS_000000000000014b_0000000000000375_INDEX_1` because it could not be opened.
2023-05-19T03:23:25.881676Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.881682Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.881687Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.881693Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/FTS_000000000000014b_0000000000000375_INDEX_2.ibd OS error: 71
2023-05-19T03:23:25.881704Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.881709Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.881714Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.881720Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/FTS_000000000000014b_0000000000000375_INDEX_2`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.881728Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/FTS_000000000000014b_0000000000000375_INDEX_2` because it could not be opened.
2023-05-19T03:23:25.881749Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.881755Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.881761Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.881766Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/FTS_000000000000014b_0000000000000375_INDEX_3.ibd OS error: 71
2023-05-19T03:23:25.881772Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.881777Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.881782Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.881787Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/FTS_000000000000014b_0000000000000375_INDEX_3`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.881795Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/FTS_000000000000014b_0000000000000375_INDEX_3` because it could not be opened.
2023-05-19T03:23:25.881814Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.881821Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.881826Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.881832Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/FTS_000000000000014b_0000000000000375_INDEX_4.ibd OS error: 71
2023-05-19T03:23:25.881838Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.881842Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.881847Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.881853Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/FTS_000000000000014b_0000000000000375_INDEX_4`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.881860Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/FTS_000000000000014b_0000000000000375_INDEX_4` because it could not be opened.
2023-05-19T03:23:25.881879Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.881886Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.881891Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.881897Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/FTS_000000000000014b_0000000000000375_INDEX_5.ibd OS error: 71
2023-05-19T03:23:25.881908Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.881913Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.881918Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.881924Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/FTS_000000000000014b_0000000000000375_INDEX_5`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.881931Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/FTS_000000000000014b_0000000000000375_INDEX_5` because it could not be opened.
2023-05-19T03:23:25.881952Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.881959Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.881964Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.881970Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/FTS_000000000000014b_0000000000000375_INDEX_6.ibd OS error: 71
2023-05-19T03:23:25.881975Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.881980Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.881985Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.881990Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/FTS_000000000000014b_0000000000000375_INDEX_6`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.881998Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/FTS_000000000000014b_0000000000000375_INDEX_6` because it could not be opened.
2023-05-19T03:23:25.882018Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.882025Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.882030Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.882036Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/FTS_000000000000014b_BEING_DELETED.ibd OS error: 71
2023-05-19T03:23:25.882041Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.882046Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.882051Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.882057Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/FTS_000000000000014b_BEING_DELETED`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.882064Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/FTS_000000000000014b_BEING_DELETED` because it could not be opened.
2023-05-19T03:23:25.882084Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.882091Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.882096Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.882101Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/FTS_000000000000014b_BEING_DELETED_CACHE.ibd OS error: 71
2023-05-19T03:23:25.882107Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.882112Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.882122Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.882128Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/FTS_000000000000014b_BEING_DELETED_CACHE`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.882136Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/FTS_000000000000014b_BEING_DELETED_CACHE` because it could not be opened.
2023-05-19T03:23:25.882156Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.882163Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.882168Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.882174Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/FTS_000000000000014b_CONFIG.ibd OS error: 71
2023-05-19T03:23:25.882180Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.882185Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.882190Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.882195Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/FTS_000000000000014b_CONFIG`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.882202Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/FTS_000000000000014b_CONFIG` because it could not be opened.
2023-05-19T03:23:25.882222Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.882229Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.882234Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.882240Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/FTS_000000000000014b_DELETED.ibd OS error: 71
2023-05-19T03:23:25.882245Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.882250Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.882255Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.882261Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/FTS_000000000000014b_DELETED`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.882268Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/FTS_000000000000014b_DELETED` because it could not be opened.
2023-05-19T03:23:25.882288Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.882295Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.882300Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.882305Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/FTS_000000000000014b_DELETED_CACHE.ibd OS error: 71
2023-05-19T03:23:25.882311Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.882316Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.882326Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.882342Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/FTS_000000000000014b_DELETED_CACHE`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.882350Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/FTS_000000000000014b_DELETED_CACHE` because it could not be opened.
2023-05-19T03:23:25.882373Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.882380Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.882385Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.882391Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/ylrc_b2_circle_related.ibd OS error: 71
2023-05-19T03:23:25.882396Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.882401Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.882406Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.882412Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/ylrc_b2_circle_related`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.882419Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/ylrc_b2_circle_related` because it could not be opened.
2023-05-19T03:23:25.882440Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.882447Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.882452Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.882458Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/ylrc_b2_coupon.ibd OS error: 71
2023-05-19T03:23:25.882464Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.882468Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.882473Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.882479Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/ylrc_b2_coupon`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.882486Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/ylrc_b2_coupon` because it could not be opened.
2023-05-19T03:23:25.882507Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.882514Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.882519Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.882524Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/ylrc_b2_gold.ibd OS error: 71
2023-05-19T03:23:25.882530Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.882535Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.882540Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.882545Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/ylrc_b2_gold`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.882552Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/ylrc_b2_gold` because it could not be opened.
2023-05-19T03:23:25.882579Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.882587Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.882592Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.882598Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/ylrc_b2_msg.ibd OS error: 71
2023-05-19T03:23:25.882603Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.882608Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.882613Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.882619Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/ylrc_b2_msg`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.882625Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/ylrc_b2_msg` because it could not be opened.
2023-05-19T03:23:25.882646Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.882653Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.882658Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.882664Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/ylrc_b2_post_relationships.ibd OS error: 71
2023-05-19T03:23:25.882669Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.882674Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.882679Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.882685Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/ylrc_b2_post_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.882692Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/ylrc_b2_post_relationships` because it could not be opened.
2023-05-19T03:23:25.882712Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.882719Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.882724Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.882730Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/ylrc_b2_verify.ibd OS error: 71
2023-05-19T03:23:25.882735Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.882740Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.882745Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.882751Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/ylrc_b2_verify`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.882757Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/ylrc_b2_verify` because it could not be opened.
2023-05-19T03:23:25.882777Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.882784Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.882789Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.882801Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/ylrc_commentmeta.ibd OS error: 71
2023-05-19T03:23:25.882807Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.882812Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.882817Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.882823Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/ylrc_commentmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.882829Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/ylrc_commentmeta` because it could not be opened.
2023-05-19T03:23:25.882850Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.882857Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.882862Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.882867Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/ylrc_comments.ibd OS error: 71
2023-05-19T03:23:25.882873Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.882878Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.882883Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.882888Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/ylrc_comments`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.882895Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/ylrc_comments` because it could not be opened.
2023-05-19T03:23:25.882914Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.882921Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.882926Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.882932Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/ylrc_links.ibd OS error: 71
2023-05-19T03:23:25.882938Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.882942Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.882947Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.882953Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/ylrc_links`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.882959Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/ylrc_links` because it could not be opened.
2023-05-19T03:23:25.882979Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.882985Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.882990Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.882996Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/ylrc_options.ibd OS error: 71
2023-05-19T03:23:25.883001Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.883006Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.883018Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.883025Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/ylrc_options`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.883031Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/ylrc_options` because it could not be opened.
2023-05-19T03:23:25.883052Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.883058Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.883064Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.883069Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/ylrc_postmeta.ibd OS error: 71
2023-05-19T03:23:25.883075Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.883080Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.883084Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.883090Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/ylrc_postmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.883096Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/ylrc_postmeta` because it could not be opened.
2023-05-19T03:23:25.883116Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.883123Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.883128Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.883133Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/ylrc_posts.ibd OS error: 71
2023-05-19T03:23:25.883139Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.883144Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.883149Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.883154Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/ylrc_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.883161Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/ylrc_posts` because it could not be opened.
2023-05-19T03:23:25.883181Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.883188Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.883193Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.883199Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/ylrc_term_relationships.ibd OS error: 71
2023-05-19T03:23:25.883204Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.883209Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.883214Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.883219Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/ylrc_term_relationships`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.883232Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/ylrc_term_relationships` because it could not be opened.
2023-05-19T03:23:25.883254Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.883261Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.883266Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.883271Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/ylrc_term_taxonomy.ibd OS error: 71
2023-05-19T03:23:25.883277Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.883282Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.883287Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.883292Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/ylrc_term_taxonomy`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.883299Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/ylrc_term_taxonomy` because it could not be opened.
2023-05-19T03:23:25.883319Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.883335Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.883341Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.883347Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/ylrc_termmeta.ibd OS error: 71
2023-05-19T03:23:25.883352Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.883357Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.883362Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.883368Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/ylrc_termmeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.883374Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/ylrc_termmeta` because it could not be opened.
2023-05-19T03:23:25.883396Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.883403Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.883408Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.883413Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/ylrc_terms.ibd OS error: 71
2023-05-19T03:23:25.883419Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.883424Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.883442Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.883447Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/ylrc_terms`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.883454Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/ylrc_terms` because it could not be opened.
2023-05-19T03:23:25.883472Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.883478Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.883483Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.883494Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/ylrc_usermeta.ibd OS error: 71
2023-05-19T03:23:25.883499Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.883504Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.883508Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.883513Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/ylrc_usermeta`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.883519Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/ylrc_usermeta` because it could not be opened.
2023-05-19T03:23:25.883538Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.883544Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.883549Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.883554Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/ylrc_users.ibd OS error: 71
2023-05-19T03:23:25.883559Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.883563Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.883568Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.883573Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/ylrc_users`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.883579Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/ylrc_users` because it could not be opened.
2023-05-19T03:23:25.883597Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.883604Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.883609Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.883614Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/ylrc_wb_bsl_day.ibd OS error: 71
2023-05-19T03:23:25.883619Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.883623Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.883628Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.883633Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/ylrc_wb_bsl_day`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.883639Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/ylrc_wb_bsl_day` because it could not be opened.
2023-05-19T03:23:25.883657Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.883663Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.883668Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.883673Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/ylrc_wb_bsl_log.ibd OS error: 71
2023-05-19T03:23:25.883678Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.883683Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.883692Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.883698Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/ylrc_wb_bsl_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.883704Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/ylrc_wb_bsl_log` because it could not be opened.
2023-05-19T03:23:25.883738Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.883744Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.883750Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.883755Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/ylrc_wb_bsl_stats.ibd OS error: 71
2023-05-19T03:23:25.883761Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.883766Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.883770Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.883776Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/ylrc_wb_bsl_stats`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.883783Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/ylrc_wb_bsl_stats` because it could not be opened.
2023-05-19T03:23:25.883803Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.883809Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.883815Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.883820Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/ylrc_wb_spider.ibd OS error: 71
2023-05-19T03:23:25.883826Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.883830Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.883835Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.883841Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/ylrc_wb_spider`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.883848Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/ylrc_wb_spider` because it could not be opened.
2023-05-19T03:23:25.883867Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.883874Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.883879Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.883885Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/ylrc_wb_spider_ip.ibd OS error: 71
2023-05-19T03:23:25.883890Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.883895Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.883900Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.883906Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/ylrc_wb_spider_ip`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.883918Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/ylrc_wb_spider_ip` because it could not be opened.
2023-05-19T03:23:25.883938Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.883945Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.883951Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.883956Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/ylrc_wb_spider_log.ibd OS error: 71
2023-05-19T03:23:25.883962Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.883967Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.883972Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.883977Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/ylrc_wb_spider_log`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.883984Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/ylrc_wb_spider_log` because it could not be opened.
2023-05-19T03:23:25.884004Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.884010Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.884015Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.884021Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/ylrc_wb_spider_post.ibd OS error: 71
2023-05-19T03:23:25.884027Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.884032Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.884036Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.884042Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/ylrc_wb_spider_post`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.884049Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/ylrc_wb_spider_post` because it could not be opened.
2023-05-19T03:23:25.884068Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.884075Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.884080Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.884086Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/ylrc_wb_spider_post_link.ibd OS error: 71
2023-05-19T03:23:25.884091Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.884096Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.884101Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.884107Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/ylrc_wb_spider_post_link`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.884114Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/ylrc_wb_spider_post_link` because it could not be opened.
2023-05-19T03:23:25.884140Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.884152Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.884158Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.884164Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/ylrc_wb_spider_sum.ibd OS error: 71
2023-05-19T03:23:25.884169Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.884174Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.884179Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.884185Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/ylrc_wb_spider_sum`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.884192Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/ylrc_wb_spider_sum` because it could not be opened.
2023-05-19T03:23:25.884212Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.884219Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.884224Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.884230Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/ylrc_wb_spider_visit.ibd OS error: 71
2023-05-19T03:23:25.884236Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.884241Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.884245Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.884251Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/ylrc_wb_spider_visit`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.884258Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/ylrc_wb_spider_visit` because it could not be opened.
2023-05-19T03:23:25.884277Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.884284Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.884289Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.884295Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/ylrc_wb_sst_broken_url.ibd OS error: 71
2023-05-19T03:23:25.884301Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.884306Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.884311Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.884316Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/ylrc_wb_sst_broken_url`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.884330Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/ylrc_wb_sst_broken_url` because it could not be opened.
2023-05-19T03:23:25.884355Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.884363Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.884368Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.884374Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/ylrc_wb_sst_redirection_url.ibd OS error: 71
2023-05-19T03:23:25.884385Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.884390Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.884395Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.884401Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/ylrc_wb_sst_redirection_url`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.884408Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/ylrc_wb_sst_redirection_url` because it could not be opened.
2023-05-19T03:23:25.884429Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.884436Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.884441Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.884447Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/ylrc_yarpp_related_cache.ibd OS error: 71
2023-05-19T03:23:25.884452Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.884457Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.884462Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.884468Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/ylrc_yarpp_related_cache`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.884474Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/ylrc_yarpp_related_cache` because it could not be opened.
2023-05-19T03:23:25.884495Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.884502Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.884507Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.884513Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/ylrc_zrz_card.ibd OS error: 71
2023-05-19T03:23:25.884518Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.884523Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.884528Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.884534Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/ylrc_zrz_card`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.884540Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/ylrc_zrz_card` because it could not be opened.
2023-05-19T03:23:25.884560Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.884567Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.884572Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.884578Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/ylrc_zrz_directmessage.ibd OS error: 71
2023-05-19T03:23:25.884584Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.884589Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.884593Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.884605Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/ylrc_zrz_directmessage`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.884612Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/ylrc_zrz_directmessage` because it could not be opened.
2023-05-19T03:23:25.884633Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.884640Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.884646Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.884651Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/ylrc_zrz_invitation.ibd OS error: 71
2023-05-19T03:23:25.884657Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.884662Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.884667Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.884672Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/ylrc_zrz_invitation`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.884679Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/ylrc_zrz_invitation` because it could not be opened.
2023-05-19T03:23:25.884699Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.884705Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.884711Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.884716Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/ylrc_zrz_message.ibd OS error: 71
2023-05-19T03:23:25.884722Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.884727Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.884732Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.884738Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/ylrc_zrz_message`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.884744Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/ylrc_zrz_message` because it could not be opened.
2023-05-19T03:23:25.884764Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.884771Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.884776Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.884781Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/ylrc_zrz_order.ibd OS error: 71
2023-05-19T03:23:25.884787Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.884792Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.884797Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.884803Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/ylrc_zrz_order`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.884815Z 0 [Warning] InnoDB: Ignoring tablespace `www_yuanlairuci_/ylrc_zrz_order` because it could not be opened.
2023-05-19T03:23:25.889945Z 0 [ERROR] InnoDB: Failed to find tablespace for table `www_yuanlairuci_`.`FTS_000000000000014b_000000000000036e_INDEX_1` in the cache. Attempting to load the tablespace with space id 476
2023-05-19T03:23:25.889976Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.889984Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.889989Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.889995Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/FTS_000000000000014b_000000000000036e_INDEX_1.ibd OS error: 71
2023-05-19T03:23:25.890001Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.890006Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.890010Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.890016Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/FTS_000000000000014b_000000000000036e_INDEX_1`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.890110Z 0 [ERROR] InnoDB: Failed to find tablespace for table `www_yuanlairuci_`.`ylrc_posts` in the cache. Attempting to load the tablespace with space id 470
2023-05-19T03:23:25.890130Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.890136Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.890142Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.890147Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/ylrc_posts.ibd OS error: 71
2023-05-19T03:23:25.890152Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.890157Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.890162Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.890167Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/ylrc_posts`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.890297Z 0 [ERROR] InnoDB: Failed to find tablespace for table `www_yuanlairuci_`.`FTS_000000000000014b_000000000000036e_INDEX_2` in the cache. Attempting to load the tablespace with space id 477
2023-05-19T03:23:25.890316Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.890328Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.890338Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.890344Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/FTS_000000000000014b_000000000000036e_INDEX_2.ibd OS error: 71
2023-05-19T03:23:25.890349Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.890354Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.890359Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.890364Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/FTS_000000000000014b_000000000000036e_INDEX_2`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.890436Z 0 [ERROR] InnoDB: Failed to find tablespace for table `www_yuanlairuci_`.`FTS_000000000000014b_000000000000036e_INDEX_3` in the cache. Attempting to load the tablespace with space id 478
2023-05-19T03:23:25.890456Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.890461Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.890466Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.890472Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/FTS_000000000000014b_000000000000036e_INDEX_3.ibd OS error: 71
2023-05-19T03:23:25.890477Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.890481Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.890486Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.890491Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/FTS_000000000000014b_000000000000036e_INDEX_3`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.890545Z 0 [ERROR] InnoDB: Failed to find tablespace for table `www_yuanlairuci_`.`FTS_000000000000014b_000000000000036e_INDEX_4` in the cache. Attempting to load the tablespace with space id 479
2023-05-19T03:23:25.890561Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.890567Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.890572Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.890577Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/FTS_000000000000014b_000000000000036e_INDEX_4.ibd OS error: 71
2023-05-19T03:23:25.890582Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.890587Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.890591Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.890597Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/FTS_000000000000014b_000000000000036e_INDEX_4`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.890642Z 0 [ERROR] InnoDB: Failed to find tablespace for table `www_yuanlairuci_`.`FTS_000000000000014b_000000000000036e_INDEX_5` in the cache. Attempting to load the tablespace with space id 480
2023-05-19T03:23:25.890659Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.890664Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.890669Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.890674Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/FTS_000000000000014b_000000000000036e_INDEX_5.ibd OS error: 71
2023-05-19T03:23:25.890679Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.890684Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.890688Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.890694Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/FTS_000000000000014b_000000000000036e_INDEX_5`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.890768Z 0 [ERROR] InnoDB: Failed to find tablespace for table `www_yuanlairuci_`.`FTS_000000000000014b_000000000000036e_INDEX_6` in the cache. Attempting to load the tablespace with space id 481
2023-05-19T03:23:25.890786Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.890792Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.890797Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.890802Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/FTS_000000000000014b_000000000000036e_INDEX_6.ibd OS error: 71
2023-05-19T03:23:25.890808Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.890813Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.890818Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.890823Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/FTS_000000000000014b_000000000000036e_INDEX_6`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.890874Z 0 [ERROR] InnoDB: Failed to find tablespace for table `www_yuanlairuci_`.`FTS_000000000000014b_0000000000000375_INDEX_1` in the cache. Attempting to load the tablespace with space id 482
2023-05-19T03:23:25.890893Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.890899Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.890904Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.890909Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/FTS_000000000000014b_0000000000000375_INDEX_1.ibd OS error: 71
2023-05-19T03:23:25.890915Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.890920Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.890925Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.890931Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/FTS_000000000000014b_0000000000000375_INDEX_1`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.890979Z 0 [ERROR] InnoDB: Failed to find tablespace for table `www_yuanlairuci_`.`FTS_000000000000014b_0000000000000375_INDEX_2` in the cache. Attempting to load the tablespace with space id 483
2023-05-19T03:23:25.890997Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.891003Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.891008Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.891014Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/FTS_000000000000014b_0000000000000375_INDEX_2.ibd OS error: 71
2023-05-19T03:23:25.891019Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.891024Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.891029Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.891034Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/FTS_000000000000014b_0000000000000375_INDEX_2`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.891086Z 0 [ERROR] InnoDB: Failed to find tablespace for table `www_yuanlairuci_`.`FTS_000000000000014b_0000000000000375_INDEX_3` in the cache. Attempting to load the tablespace with space id 484
2023-05-19T03:23:25.891104Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.891110Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.891115Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.891121Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/FTS_000000000000014b_0000000000000375_INDEX_3.ibd OS error: 71
2023-05-19T03:23:25.891126Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.891131Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.891136Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.891141Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/FTS_000000000000014b_0000000000000375_INDEX_3`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.891187Z 0 [ERROR] InnoDB: Failed to find tablespace for table `www_yuanlairuci_`.`FTS_000000000000014b_0000000000000375_INDEX_4` in the cache. Attempting to load the tablespace with space id 485
2023-05-19T03:23:25.891205Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.891212Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.891217Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.891222Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/FTS_000000000000014b_0000000000000375_INDEX_4.ibd OS error: 71
2023-05-19T03:23:25.891228Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.891233Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.891237Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.891243Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/FTS_000000000000014b_0000000000000375_INDEX_4`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.891292Z 0 [ERROR] InnoDB: Failed to find tablespace for table `www_yuanlairuci_`.`FTS_000000000000014b_0000000000000375_INDEX_5` in the cache. Attempting to load the tablespace with space id 486
2023-05-19T03:23:25.891309Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.891315Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.891327Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.891337Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/FTS_000000000000014b_0000000000000375_INDEX_5.ibd OS error: 71
2023-05-19T03:23:25.891343Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.891349Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.891353Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.891359Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/FTS_000000000000014b_0000000000000375_INDEX_5`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.891412Z 0 [ERROR] InnoDB: Failed to find tablespace for table `www_yuanlairuci_`.`FTS_000000000000014b_0000000000000375_INDEX_6` in the cache. Attempting to load the tablespace with space id 487
2023-05-19T03:23:25.891430Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.891436Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.891441Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.891447Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/FTS_000000000000014b_0000000000000375_INDEX_6.ibd OS error: 71
2023-05-19T03:23:25.891452Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.891457Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.891462Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.891467Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/FTS_000000000000014b_0000000000000375_INDEX_6`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.891516Z 0 [ERROR] InnoDB: Failed to find tablespace for table `www_yuanlairuci_`.`FTS_000000000000014b_BEING_DELETED` in the cache. Attempting to load the tablespace with space id 471
2023-05-19T03:23:25.891533Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.891539Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.891544Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.891550Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/FTS_000000000000014b_BEING_DELETED.ibd OS error: 71
2023-05-19T03:23:25.891555Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.891560Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.891565Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.891570Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/FTS_000000000000014b_BEING_DELETED`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.891617Z 0 [ERROR] InnoDB: Failed to find tablespace for table `www_yuanlairuci_`.`FTS_000000000000014b_BEING_DELETED_CACHE` in the cache. Attempting to load the tablespace with space id 472
2023-05-19T03:23:25.891634Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.891640Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.891645Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.891651Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/FTS_000000000000014b_BEING_DELETED_CACHE.ibd OS error: 71
2023-05-19T03:23:25.891656Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.891661Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.891666Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.891671Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/FTS_000000000000014b_BEING_DELETED_CACHE`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.891720Z 0 [ERROR] InnoDB: Failed to find tablespace for table `www_yuanlairuci_`.`FTS_000000000000014b_CONFIG` in the cache. Attempting to load the tablespace with space id 473
2023-05-19T03:23:25.891741Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.891747Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.891753Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.891758Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/FTS_000000000000014b_CONFIG.ibd OS error: 71
2023-05-19T03:23:25.891763Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.891768Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.891773Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.891778Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/FTS_000000000000014b_CONFIG`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.891826Z 0 [ERROR] InnoDB: Failed to find tablespace for table `www_yuanlairuci_`.`FTS_000000000000014b_DELETED` in the cache. Attempting to load the tablespace with space id 474
2023-05-19T03:23:25.891844Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.891850Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.891855Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.891860Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/FTS_000000000000014b_DELETED.ibd OS error: 71
2023-05-19T03:23:25.891865Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.891870Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.891875Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.891880Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/FTS_000000000000014b_DELETED`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.891924Z 0 [ERROR] InnoDB: Failed to find tablespace for table `www_yuanlairuci_`.`FTS_000000000000014b_DELETED_CACHE` in the cache. Attempting to load the tablespace with space id 475
2023-05-19T03:23:25.891942Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.891948Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.891953Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.891959Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ./www_yuanlairuci_/FTS_000000000000014b_DELETED_CACHE.ibd OS error: 71
2023-05-19T03:23:25.891964Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-05-19T03:23:25.891969Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-05-19T03:23:25.891973Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-05-19T03:23:25.891979Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `www_yuanlairuci_/FTS_000000000000014b_DELETED_CACHE`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2023-05-19T03:23:25.895508Z 0 [Note] InnoDB: Removed temporary tablespace data file: ibtmp1
2023-05-19T03:23:25.895523Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2023-05-19T03:23:25.895585Z 0 [Note] InnoDB: Setting file /www/server/data/ibtmp1 size to 12 MB. Physically writing the file full; Please wait ...
2023-05-19T03:23:25.937664Z 0 [Note] InnoDB: File /www/server/data/ibtmp1 size is now 12 MB.
2023-05-19T03:23:25.938584Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2023-05-19T03:23:25.938598Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2023-05-19T03:23:25.938898Z 0 [Note] InnoDB: Waiting for purge to start
2023-05-19T03:23:25.989012Z 0 [Note] InnoDB: 5.7.40 started; log sequence number 6582012208761
2023-05-19T03:23:25.989211Z 0 [Note] InnoDB: Loading buffer pool(s) from /www/server/data/ib_buffer_pool
2023-05-19T03:23:25.989441Z 0 [Note] Plugin FEDERATED is disabled.
mysqld: File ./mysql-bin.000279 not found (Errcode: 2 - No such file or directory)
2023-05-19T03:23:25.994171Z 0 [ERROR] Failed to open log (file ./mysql-bin.000279, errno 2)
2023-05-19T03:23:25.994177Z 0 [ERROR] Could not open log file
mysqld: File ./mysql-bin.000280 not found (Errcode: 2 - No such file or directory)
2023-05-19T03:23:25.994187Z 0 [ERROR] Failed to open log (file ./mysql-bin.000280, errno 2)
2023-05-19T03:23:25.994189Z 0 [ERROR] Could not open log file
mysqld: File ./mysql-bin.000281 not found (Errcode: 2 - No such file or directory)
2023-05-19T03:23:25.994197Z 0 [ERROR] Failed to open log (file ./mysql-bin.000281, errno 2)
2023-05-19T03:23:25.994200Z 0 [ERROR] Could not open log file
mysqld: File ./mysql-bin.000282 not found (Errcode: 2 - No such file or directory)
2023-05-19T03:23:25.994208Z 0 [ERROR] Failed to open log (file ./mysql-bin.000282, errno 2)
2023-05-19T03:23:25.994210Z 0 [ERROR] Could not open log file
mysqld: File ./mysql-bin.000283 not found (Errcode: 2 - No such file or directory)
2023-05-19T03:23:25.994217Z 0 [ERROR] Failed to open log (file ./mysql-bin.000283, errno 2)
2023-05-19T03:23:25.994219Z 0 [ERROR] Could not open log file
mysqld: File ./mysql-bin.000284 not found (Errcode: 2 - No such file or directory)
2023-05-19T03:23:25.994227Z 0 [ERROR] Failed to open log (file ./mysql-bin.000284, errno 2)
2023-05-19T03:23:25.994229Z 0 [ERROR] Could not open log file
mysqld: File ./mysql-bin.000285 not found (Errcode: 2 - No such file or directory)
2023-05-19T03:23:25.994236Z 0 [ERROR] Failed to open log (file ./mysql-bin.000285, errno 2)
2023-05-19T03:23:25.994238Z 0 [ERROR] Could not open log file
mysqld: File ./mysql-bin.000286 not found (Errcode: 2 - No such file or directory)
2023-05-19T03:23:25.994246Z 0 [ERROR] Failed to open log (file ./mysql-bin.000286, errno 2)
2023-05-19T03:23:25.994248Z 0 [ERROR] Could not open log file
mysqld: File ./mysql-bin.000287 not found (Errcode: 2 - No such file or directory)
2023-05-19T03:23:25.994255Z 0 [ERROR] Failed to open log (file ./mysql-bin.000287, errno 2)
2023-05-19T03:23:25.994257Z 0 [ERROR] Could not open log file
mysqld: File ./mysql-bin.000288 not found (Errcode: 2 - No such file or directory)
2023-05-19T03:23:25.994264Z 0 [ERROR] Failed to open log (file ./mysql-bin.000288, errno 2)
2023-05-19T03:23:25.994267Z 0 [ERROR] Could not open log file
mysqld: File ./mysql-bin.000289 not found (Errcode: 2 - No such file or directory)
2023-05-19T03:23:25.994274Z 0 [ERROR] Failed to open log (file ./mysql-bin.000289, errno 2)
2023-05-19T03:23:25.994276Z 0 [ERROR] Could not open log file
mysqld: File ./mysql-bin.000290 not found (Errcode: 2 - No such file or directory)
2023-05-19T03:23:25.994283Z 0 [ERROR] Failed to open log (file ./mysql-bin.000290, errno 2)
2023-05-19T03:23:25.994285Z 0 [ERROR] Could not open log file
mysqld: File ./mysql-bin.000291 not found (Errcode: 2 - No such file or directory)
2023-05-19T03:23:25.994297Z 0 [ERROR] Failed to open log (file ./mysql-bin.000291, errno 2)
2023-05-19T03:23:25.994299Z 0 [ERROR] Could not open log file
mysqld: File ./mysql-bin.000292 not found (Errcode: 2 - No such file or directory)
2023-05-19T03:23:25.994307Z 0 [ERROR] Failed to open log (file ./mysql-bin.000292, errno 2)
2023-05-19T03:23:25.994310Z 0 [ERROR] Could not open log file
mysqld: File ./mysql-bin.000293 not found (Errcode: 2 - No such file or directory)
2023-05-19T03:23:25.994317Z 0 [ERROR] Failed to open log (file ./mysql-bin.000293, errno 2)
2023-05-19T03:23:25.994319Z 0 [ERROR] Could not open log file
mysqld: File ./mysql-bin.000294 not found (Errcode: 2 - No such file or directory)
2023-05-19T03:23:25.994335Z 0 [ERROR] Failed to open log (file ./mysql-bin.000294, errno 2)
2023-05-19T03:23:25.994337Z 0 [ERROR] Could not open log file
mysqld: File ./mysql-bin.000295 not found (Errcode: 2 - No such file or directory)
2023-05-19T03:23:25.994345Z 0 [ERROR] Failed to open log (file ./mysql-bin.000295, errno 2)
2023-05-19T03:23:25.994347Z 0 [ERROR] Could not open log file
mysqld: File ./mysql-bin.000296 not found (Errcode: 2 - No such file or directory)
2023-05-19T03:23:25.994354Z 0 [ERROR] Failed to open log (file ./mysql-bin.000296, errno 2)
2023-05-19T03:23:25.994357Z 0 [ERROR] Could not open log file
2023-05-19T03:23:25.996334Z 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them.
2023-05-19T03:23:25.996347Z 0 [Note] Skipping generation of SSL certificates as certificate files are present in data directory.
2023-05-19T03:23:25.996351Z 0 [Warning] A deprecated TLS version TLSv1 is enabled. Please use TLSv1.2 or higher.
2023-05-19T03:23:25.996353Z 0 [Warning] A deprecated TLS version TLSv1.1 is enabled. Please use TLSv1.2 or higher.
2023-05-19T03:23:25.997034Z 0 [Warning] CA certificate ca.pem is self signed.
2023-05-19T03:23:25.997082Z 0 [Note] Skipping generation of RSA key pair as key files are present in data directory.
2023-05-19T03:23:25.997186Z 0 [Note] Server hostname (bind-address): *; port: 3306
2023-05-19T03:23:25.997230Z 0 [Note] IPv6 is available.
2023-05-19T03:23:25.997242Z 0 [Note]   - :: resolves to ::;
2023-05-19T03:23:25.997256Z 0 [Note] Server socket created on IP: ::.
2023-05-19T03:23:26.001502Z 0 [Note] Failed to start slave threads for channel 
2023-05-19T03:23:26.007568Z 0 [Note] Event Scheduler: Loaded 0 events
2023-05-19T03:23:26.007719Z 0 [Note] /www/server/mysql/bin/mysqld: ready for connections.
Version: 5.7.40-log  socket: /tmp/mysql.sock  port: 3306  Source distribution
2023-05-19T03:23:26.389102Z 0 [Note] InnoDB: Buffer pool(s) load completed at 230519 11:23:26
2023-05-19T03:24:11.390097Z 233 [Note] Aborted connection 233 to db: paayoo_com user: paayoo_com host: localhost (Got an error writing communication packets)
2023-05-19T03:25:11.583283Z 557 [Note] Aborted connection 557 to db: paayoo_com user: paayoo_com host: localhost (Got an error writing communication packets)
2023-05-19T03:26:12.513709Z 907 [Note] Aborted connection 907 to db: paayoo_com user: paayoo_com host: localhost (Got an error writing communication packets)
2023-05-19T03:27:13.477337Z 1256 [Note] Aborted connection 1256 to db: paayoo_com user: paayoo_com host: localhost (Got an error writing communication packets)
2023-05-19T03:28:16.618279Z 1633 [Note] Aborted connection 1633 to db: paayoo_com user: paayoo_com host: localhost (Got an error writing communication packets)
2023-05-19T03:29:21.215000Z 2016 [Note] Aborted connection 2016 to db: paayoo_com user: paayoo_com host: localhost (Got an error writing communication packets)
2023-05-19T03:30:23.297449Z 2328 [Note] Aborted connection 2328 to db: paayoo_com user: paayoo_com host: localhost (Got an error writing communication packets)
2023-05-19T03:31:24.339411Z 2656 [Note] Aborted connection 2656 to db: paayoo_com user: paayoo_com host: localhost (Got an error writing communication packets)
2023-05-19T03:32:24.763186Z 3013 [Note] Aborted connection 3013 to db: paayoo_com user: paayoo_com host: localhost (Got an error writing communication packets)
2023-05-19T03:33:25.489543Z 3323 [Note] Aborted connection 3323 to db: paayoo_com user: paayoo_com host: localhost (Got an error writing communication packets)
2023-05-19T03:34:27.522041Z 3633 [Note] Aborted connection 3633 to db: paayoo_com user: paayoo_com host: localhost (Got an error writing communication packets)
2023-05-19T03:34:47.258707Z 0 [Note] InnoDB: page_cleaner: 1000ms intended loop took 6495ms. The settings might not be optimal. (flushed=8 and evicted=0, during the time.)
2023-05-19T03:35:29.852104Z 3984 [Note] Aborted connection 3984 to db: paayoo_com user: paayoo_com host: localhost (Got an error writing communication packets)
2023-05-19T03:37:33.503415Z 4641 [Note] Aborted connection 4641 to db: paayoo_com user: paayoo_com host: localhost (Got an error writing communication packets)
2023-05-19T03:38:37.570045Z 4964 [Note] Aborted connection 4964 to db: paayoo_com user: paayoo_com host: localhost (Got an error writing communication packets)
2023-05-19T03:39:40.063058Z 5212 [Note] Aborted connection 5212 to db: paayoo_com user: paayoo_com host: localhost (Got an error writing communication packets)
2023-05-19T03:40:40.706231Z 5497 [Note] Aborted connection 5497 to db: paayoo_com user: paayoo_com host: localhost (Got an error writing communication packets)
2023-05-19T03:41:41.973587Z 5841 [Note] Aborted connection 5841 to db: paayoo_com user: paayoo_com host: localhost (Got an error writing communication packets)
2023-05-19T03:42:43.250107Z 6118 [Note] Aborted connection 6118 to db: paayoo_com user: paayoo_com host: localhost (Got an error writing communication packets)
2023-05-19T03:43:43.754155Z 6491 [Note] Aborted connection 6491 to db: paayoo_com user: paayoo_com host: localhost (Got an error writing communication packets)
2023-05-19T03:44:46.188206Z 6844 [Note] Aborted connection 6844 to db: paayoo_com user: paayoo_com host: localhost (Got an error writing communication packets)
2023-05-19T03:44:53.828641Z 0 [Note] InnoDB: page_cleaner: 1000ms intended loop took 4596ms. The settings might not be optimal. (flushed=308 and evicted=0, during the time.)
2023-05-19T03:45:46.744518Z 7156 [Note] Aborted connection 7156 to db: paayoo_com user: paayoo_com host: localhost (Got an error writing communication packets)
2023-05-19T03:46:47.505557Z 7442 [Note] Aborted connection 7442 to db: paayoo_com user: paayoo_com host: localhost (Got an error writing communication packets)
2023-05-19T03:47:24.790342Z 7652 [Note] Aborted connection 7652 to db: wuzhaoguo_siwei user: wuzhaoguo_siwei host: localhost (Got an error reading communication packets)
2023-05-19T03:47:50.998189Z 7816 [Note] Aborted connection 7816 to db: paayoo_com user: paayoo_com host: localhost (Got an error writing communication packets)
2023-05-19T03:48:51.530792Z 8126 [Note] Aborted connection 8126 to db: paayoo_com user: paayoo_com host: localhost (Got an error writing communication packets)