-
-
Notifications
You must be signed in to change notification settings - Fork 86
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
Error 1406: Data too long for column 'msg' #75
Comments
I guess this is because this table was created by the old rotation script with a msg column length < 3000. You can alter the table and set the msg column length to 3000 or delete the table and let heplify-server create it. If heplify-server would have created this table this error cannot occur. |
Killing the tables and letting heplify-server generate them fixed the issue :) Thanks, I'll close this |
Nice. Keep in mind for mysql the tables will be created every day with a new suffix. If you let heplify-server do this, don't forget to set DBDropDays > 0. Otherwise no old data will be deleted |
Done. I had it set at 0 so thanks for that |
I have set up heplify-server to send data to a separate homer server, it works for the most part but is missing some calls when searching sip records
E.g a call occurred at 1308 which was from extension 140 and after exporting a pcap from homer with the time range 0900 - 1400, the call is missing, however, other calls and information exist for that extension before and after 1308 so it's partially working
This is pretty consistent and there are quite a lot of missing calls
When looking into the heplify-server logs, there are lots of error messages saying "Data too long for column"
The text was updated successfully, but these errors were encountered: