You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just installed ELSA on Ubuntu server 16.04.1 and it appears to be up and running (I can get to the web interface just fine). When I point my devices at this new server to send their syslogs over, I'm getting the following error in /data/elsa/log/node.log: Error: DBD::mysql::st execute failed: Table 'syslog.buffers' doesn't exist at /usr/local/elsa/web/../node/Indexer.pm line 945. TRACE [2017/02/07 12:14:03] /usr/local/elsa/web/cron.pl (99) main:: 64445 [undef] cron.pl finished.
Sure enough, when I log into MySQL, it appears that the table referenced was not created. This is all I have in that database: +--------------------+ | Tables_in_syslog | +--------------------+ | class_program_map | | classes | | fields | | fields_classes_map | | programs | | table_types | +--------------------+
Is there an extra step to be taken to initialize this database to store syslogs correctly? Thank you!
-Dennis
The text was updated successfully, but these errors were encountered:
Hello,
I just installed ELSA on Ubuntu server 16.04.1 and it appears to be up and running (I can get to the web interface just fine). When I point my devices at this new server to send their syslogs over, I'm getting the following error in /data/elsa/log/node.log:
Error: DBD::mysql::st execute failed: Table 'syslog.buffers' doesn't exist at /usr/local/elsa/web/../node/Indexer.pm line 945. TRACE [2017/02/07 12:14:03] /usr/local/elsa/web/cron.pl (99) main:: 64445 [undef] cron.pl finished.
Sure enough, when I log into MySQL, it appears that the table referenced was not created. This is all I have in that database:
+--------------------+ | Tables_in_syslog | +--------------------+ | class_program_map | | classes | | fields | | fields_classes_map | | programs | | table_types | +--------------------+
Is there an extra step to be taken to initialize this database to store syslogs correctly? Thank you!
-Dennis
The text was updated successfully, but these errors were encountered: