Re: [ossec-list] OSSEC upgrade from 2.8.3 to 2.9 RC5 DBD error

On Mon, Apr 10, 2017 at 2:34 PM, Dayne Jordan wrote: > DISREGARD - major faux pas on my part from previous... its' alert not alerts > table.(singular) > > Alert table does exist, however the column "level" does not, i will create > it manually. > > MariaDB [ossec]> describe

Re: [ossec-list] OSSEC upgrade from 2.8.3 to 2.9 RC5 DBD error

DISREGARD - major faux pas on my part from previous... its' alert not alerts table.(singular) Alert table does exist, however the column "level" does not, i will create it manually. MariaDB [ossec]> describe alert; +-+---+--+-+-+---+ | Field

Re: [ossec-list] OSSEC upgrade from 2.8.3 to 2.9 RC5 DBD error

MariaDB [(none)]> use ossec Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Database changed MariaDB [ossec]> describe alerts; ERROR 1146 (42S02): Table 'ossec.alerts' doesn't exist MariaDB [ossec]> the mysql

Re: [ossec-list] OSSEC upgrade from 2.8.3 to 2.9 RC5 DBD error

Looking at the database schema here: https://github.com/ossec/ossec-hids/blob/master/src/os_dbd/mysql.schema There is a column in the alerts table called level. I would do a describe on your alerts table and make sure that it has all of the expected columns. MySQL> use ossec; -- this should be

[ossec-list] OSSEC upgrade from 2.8.3 to 2.9 RC5 DBD error

All has been running fine with 2.8.3 since mid 2016 - no issues at all. Decided to update to 2.9 for some JSON functionality and after updating the server we are encountering this error: ossec-dbd(5203): ERROR: Error executing query 'INSERT INTO >