sometimes, another table has the same error.
When I click login link on top of my local oxwall website, it open a popup to login. I input username and password, then submit.
But I can not login and this error show on Even Viewer/Windows Logs / Application as below:
If u see it before and have a solution, pls help me.
Thanks
Leader
go to your db section and click on repair db, then click on check db and see if there are any errors. If no errors try again and let us know please.
@dave: thank for your answer. I repaired the table 'ow_base_site_statistic' and the error has gone away.
After that, my website worked well but sometimes that error happen again.I don't know why.
I check mysql_error.log everytime that error occurs and see this log:
2016-08-10 11:42:16 135c InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2016-08-10 11:42:16 4956 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2016-08-10 11:42:16 4956 [Note] InnoDB: The InnoDB memory heap is disabled
2016-08-10 11:42:16 4956 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2016-08-10 11:42:16 4956 [Note] InnoDB: Memory barrier is not used
2016-08-10 11:42:16 4956 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-08-10 11:42:16 4956 [Note] InnoDB: Using generic crc32 instructions
2016-08-10 11:42:16 4956 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2016-08-10 11:42:16 4956 [Note] InnoDB: Completed initialization of buffer pool
2016-08-10 11:42:16 4956 [Note] InnoDB: Highest supported file format is Barracuda.
2016-08-10 11:42:16 4956 [Note] InnoDB: The log sequence numbers 15020409 and 15020409 in ibdata files do not match the log sequence number 15020419 in the ib_logfiles!
2016-08-10 11:42:16 4956 [Note] InnoDB: Database was not shutdown normally!
2016-08-10 11:42:16 4956 [Note] InnoDB: Starting crash recovery.
2016-08-10 11:42:16 4956 [Note] InnoDB: Reading tablespace information from the .ibd files...
2016-08-10 11:42:17 4956 [Note] InnoDB: Restoring possible half-written data pages
2016-08-10 11:42:17 4956 [Note] InnoDB: from the doublewrite buffer...
2016-08-10 11:42:17 4956 [Note] InnoDB: 128 rollback segment(s) are active.
2016-08-10 11:42:17 4956 [Note] InnoDB: Waiting for purge to start
2016-08-10 11:42:18 4956 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.28-76.1 started; log sequence number 15020419
2016-08-10 11:42:18 4840 [Note] InnoDB: Dumping buffer pool(s) not yet started
2016-08-10 11:42:18 4956 [Note] Plugin 'FEEDBACK' is disabled.
2016-08-10 11:42:18 4956 [Note] Server socket created on IP: '::'.
2016-08-10 11:42:18 4956 [Note] d:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.13-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
2016-08-10 11:59:05 4600 [ERROR] mysqld.exe: Table '.\fsndb\ow_base_user' is marked as crashed and should be repaired
2016-08-10 11:59:05 4600 [Warning] Checking table: '.\fsndb\ow_base_user'
2016-08-10 11:59:05 6424 [ERROR] mysqld.exe: Table '.\fsndb\ow_base_user_online' is marked as crashed and should be repaired
2016-08-10 11:59:05 6424 [Warning] Checking table: '.\fsndb\ow_base_user_online'
2016-08-10 11:59:05 6424 [ERROR] mysqld.exe: Table '.\fsndb\ow_newsfeed_action' is marked as crashed and should be repaired
2016-08-10 11:59:05 6424 [Warning] Checking table: '.\fsndb\ow_newsfeed_action'
2016-08-10 11:59:05 6424 [ERROR] mysqld.exe: Table '.\fsndb\ow_newsfeed_activity' is marked as crashed and should be repaired
2016-08-10 11:59:05 6424 [Warning] Checking table: '.\fsndb\ow_newsfeed_activity'
2016-08-10 12:16:02 4392 [ERROR] mysqld.exe: Table '.\fsndb\ow_base_site_statistic' is marked as crashed and should be repaired
Leader
If i had to take a stab in the dark i would say your running out of resources at times or there may be a conflict which is causing the table to get wacked.
It looks like you may need to contact your host or the mariadb help forum. You are using mariadb correct?I'm using mySQL in XAMPP 3.2.2, no more DB. I don't know why these log has things related to mariaDB. I run only one website at time.
If i had to take a stab in the dark i would say your running out of resources at times or there may be a conflict which is causing the table to get wacked.
OK, i will investigate the resources and some other service.
Thank u.
Leader
Team
