-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MySQL problem I guess #50
Comments
Hi Gleve, I had the same problem recently, just enable mysql query log a look for the create table syslog_data.syslogs_index_1 query. In my case I had to leave mysql data dir in /var/lib/mysql because in mysql 5.5 you cannot have DATA DIRECTORY in create table statement pointing to the same directory as datadir defined in my.cnf. Double check that you have apparmor disabled (not sure if it is installed by default on debian, too) |
Hi PVi1, Thank you for your reply. I did this commands as root : It solved the mysql problem and the buffer is now ok. I think I'm done with this project, I'll try another one. |
I was seeing the same issue with the exact same error messages. After creating syslogs_index_1 (with the above create statement by 'gleve') syslogs_archive_1 was missing. After creating syslogs_archive_1 and restarting all services, old logs could be searched, but new logs were not available to the web interface. Apparmor wasn't enabled. I looked at SHOW FULL COLUMNS of those two new tables and two of the older ones and noted that the old ones were utf8 instead of latin. After changing the charset of the two new tables to utf8 and restarting services, I am able to see new logs. Hope this helps. |
Hi,
Is the project still alive ? (No commit for the last 6 months)
I installed a new server under Debian 8.7.1 64 bits, then I tried to install Elsa but that didn't work. The web interface works properly but I can't see any logs on it.
After some researches, I understood that syslog-ng gets the logs from the network, then redirect them to /usr/local/elsa/node/elsa.pl which store them in /data/elsa/tmp/buffers/. But after, the perl script /usr/local/elsa/web/cron.pl launched every minutes by cron shows errors like this :
DBD::mysql::st execute failed: Duplicate entry 'syslog_data.syslogs_index_1' for key 'table_name' at /usr/local/elsa/web/../node/Indexer.pm line 1636.
DBD::mysql::st execute failed: Table 'syslog_data.syslogs_index_1' doesn't exist at /usr/local/elsa/web/../node/Indexer.pm line 1342.
And logs are just accumulating into the buffer.
Any help would be greatly appreciated :-)
Thanks in advance !
The text was updated successfully, but these errors were encountered: