When I surf to the OSSIM front page, I get the error message "Operation was not completed due to a database error". Things worked fine on Friday.
"service mysql restart" simply results in the message "failed".
I'm running version 4.7.
This is what's in the AlienVault database log:
140519 10:02:04 mysqld_safe Starting mysqld daemon with databases from /var/lib/
140519 10:02:04 [Warning] Using unique option prefix key_buffer instead of key_b
uffer_size is deprecated and will be removed in a future release. Please use the
full name instead.
140519 10:02:04 [Warning] option 'join_buffer_size': unsigned value 0 adjusted t
140519 10:02:04 [ERROR] An old style --language value with language specific part detected: /usr/share/mysql/english/
140519 10:02:04 [ERROR] Use --lc-messages-dir without language specific part instead.
140519 10:02:04 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
140519 10:02:04 [Note] Plugin 'FEDERATED' is disabled.
140519 10:02:04 InnoDB: The InnoDB memory heap is disabled
140519 10:02:04 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140519 10:02:04 InnoDB: Compressed tables use zlib 1.2.3
140519 10:02:04 InnoDB: Using Linux native AIO
140519 10:02:04 InnoDB: Initializing buffer pool, size = 512.0M
140519 10:02:04 InnoDB: Completed initialization of buffer pool
InnoDB: Note: The innodb_doublewrite_file option has been specified.
InnoDB: This option is for experts only. Don't use it unless you understand WELL what it is.
InnoDB: ### Don't specify a file older than the last checkpoint. ###
InnoDB: Otherwise, the older doublewrite buffer will break your data during recovery!
140519 10:02:04 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 754449439706
140519 10:02:04 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: doublewrite file '/var/lib/mysql/ib_doublewrite' is used.
InnoDB: Doing recovery: scanned up to log sequence number 754454349413
140519 10:02:05 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6
140519 10:02:05 InnoDB: Assertion failure in thread 140711269463808 in file ibuf0ibuf.c line 4571
InnoDB: Failing assertion: trx_doublewrite_must_reset_space_ids
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: about forcing recovery.
08:02:05 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 6787794 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
stack_bottom = 0 thread_stack 0x80000
You may download the Percona Server operations manual by visitinghttp://www.percona.com/software/percona-server/
. You may find information
in the manual which will help you identify the cause of the crash.
140519 10:02:05 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
Any ideas for solutions?