Skip to content
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

Closed
PNRxA opened this issue Jun 7, 2018 · 4 comments
Closed

Error 1406: Data too long for column 'msg' #75

PNRxA opened this issue Jun 7, 2018 · 4 comments

Comments

@PNRxA
Copy link

PNRxA commented Jun 7, 2018

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"

2018-06-07T14:07:54+10:00 ERR  Error 1406: Data too long for column 'msg' at row 3
2018-06-07T14:07:56+10:00 ERR  Error 1406: Data too long for column 'msg' at row 56
2018-06-07T14:07:59+10:00 ERR  Error 1406: Data too long for column 'msg' at row 39
2018-06-07T14:08:08+10:00 ERR  Error 1406: Data too long for column 'msg' at row 9
2018-06-07T14:08:08+10:00 ERR  Error 1406: Data too long for column 'msg' at row 47
2018-06-07T14:08:08+10:00 ERR  Error 1406: Data too long for column 'msg' at row 25
2018-06-07T14:08:10+10:00 ERR  Error 1406: Data too long for column 'msg' at row 79
2018-06-07T14:08:12+10:00 ERR  Error 1406: Data too long for column 'msg' at row 1
2018-06-07T14:08:12+10:00 ERR  Error 1406: Data too long for column 'msg' at row 10
2018-06-07T14:08:12+10:00 ERR  Error 1406: Data too long for column 'msg' at row 95
2018-06-07T14:08:12+10:00 ERR  Error 1406: Data too long for column 'msg' at row 26
2018-06-07T14:08:14+10:00 ERR  Error 1406: Data too long for column 'msg' at row 4
2018-06-07T14:08:14+10:00 ERR  Error 1406: Data too long for column 'msg' at row 117
2018-06-07T14:08:17+10:00 ERR  Error 1406: Data too long for column 'msg' at row 21
2018-06-07T14:08:17+10:00 ERR  Error 1406: Data too long for column 'msg' at row 21
2018-06-07T14:08:17+10:00 ERR  Error 1406: Data too long for column 'msg' at row 5
2018-06-07T14:08:20+10:00 ERR  Error 1406: Data too long for column 'msg' at row 18
2018-06-07T14:08:20+10:00 ERR  Error 1406: Data too long for column 'msg' at row 6
2018-06-07T14:08:26+10:00 ERR  Error 1406: Data too long for column 'msg' at row 2
2018-06-07T14:08:26+10:00 ERR  Error 1406: Data too long for column 'msg' at row 13
2018-06-07T14:08:26+10:00 ERR  Error 1406: Data too long for column 'msg' at row 16
2018-06-07T14:08:29+10:00 ERR  Error 1406: Data too long for column 'msg' at row 20
2018-06-07T14:08:29+10:00 ERR  Error 1406: Data too long for column 'msg' at row 13
2018-06-07T14:08:29+10:00 ERR  Error 1406: Data too long for column 'msg' at row 9
2018-06-07T14:08:35+10:00 ERR  Error 1406: Data too long for column 'msg' at row 2
2018-06-07T14:08:44+10:00 ERR  Error 1406: Data too long for column 'msg' at row 53
2018-06-07T14:09:11+10:00 ERR  Error 1406: Data too long for column 'msg' at row 96
2018-06-07T14:09:17+10:00 ERR  Error 1406: Data too long for column 'msg' at row 7
2018-06-07T14:09:35+10:00 ERR  Error 1406: Data too long for column 'msg' at row 36
2018-06-07T14:09:47+10:00 ERR  Error 1406: Data too long for column 'msg' at row 1
2018-06-07T14:09:53+10:00 ERR  Error 1406: Data too long for column 'msg' at row 22
2018-06-07T14:10:08+10:00 ERR  Error 1406: Data too long for column 'msg' at row 11
2018-06-07T14:10:11+10:00 ERR  Error 1406: Data too long for column 'msg' at row 100
2018-06-07T14:10:14+10:00 ERR  Error 1406: Data too long for column 'msg' at row 5
2018-06-07T14:10:14+10:00 ERR  Error 1406: Data too long for column 'msg' at row 13
2018-06-07T14:10:17+10:00 ERR  Error 1406: Data too long for column 'msg' at row 38
2018-06-07T14:10:20+10:00 ERR  Error 1406: Data too long for column 'msg' at row 8
2018-06-07T14:10:20+10:00 ERR  Error 1406: Data too long for column 'msg' at row 28
2018-06-07T14:10:20+10:00 ERR  Error 1406: Data too long for column 'msg' at row 1
2018-06-07T14:10:26+10:00 ERR  Error 1406: Data too long for column 'msg' at row 12
2018-06-07T14:10:26+10:00 ERR  Error 1406: Data too long for column 'msg' at row 19
2018-06-07T14:10:29+10:00 ERR  Error 1406: Data too long for column 'msg' at row 13
2018-06-07T14:10:29+10:00 ERR  Error 1406: Data too long for column 'msg' at row 10
2018-06-07T14:10:35+10:00 ERR  Error 1406: Data too long for column 'msg' at row 6
2018-06-07T14:10:41+10:00 ERR  Error 1406: Data too long for column 'msg' at row 4
2018-06-07T14:10:47+10:00 ERR  Error 1406: Data too long for column 'msg' at row 12
2018-06-07T14:10:47+10:00 ERR  Error 1406: Data too long for column 'msg' at row 15
2018-06-07T14:10:50+10:00 ERR  Error 1406: Data too long for column 'msg' at row 8
2018-06-07T14:10:50+10:00 ERR  Error 1406: Data too long for column 'msg' at row 1
2018-06-07T14:10:53+10:00 ERR  Error 1406: Data too long for column 'msg' at row 17
2018-06-07T14:11:08+10:00 ERR  Error 1406: Data too long for column 'msg' at row 5
2018-06-07T14:11:11+10:00 ERR  Error 1406: Data too long for column 'msg' at row 92
@negbie
Copy link
Member

negbie commented Jun 7, 2018

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.

@PNRxA
Copy link
Author

PNRxA commented Jun 7, 2018

Killing the tables and letting heplify-server generate them fixed the issue :)

Thanks, I'll close this

@PNRxA PNRxA closed this as completed Jun 7, 2018
@negbie
Copy link
Member

negbie commented Jun 7, 2018

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

@PNRxA
Copy link
Author

PNRxA commented Jun 7, 2018

Done. I had it set at 0 so thanks for that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants