Data too long for column 'message

[Petros Abajyan]

We are getting error message Data too long for column 'message_id' at row 1* (errno: 1406)’. Can you please help us to troubleshooting this issue?

May 28 13:53:14 piler piler[16950]: 400000005b0c4214110c8274006e6c641711: mysql_stmt_execute error: Data too long for column 'message_id' at row 1 (errno: 1406) May 28 13:53:14 piler piler[16950]: 400000005b0c4214110c8274006e6c641711: discarding: duplicate message, id: 0, message-id: xserial.s56e5Yzf+VxDGa6ZDeqHq0+fTGV9cr14py+S7SSgCroS7BnO4DYXgj2k+8X2SA5KdIYH4eL/rRj8C1GfDRx3MEEUtBY3wEZB+vxRkzBpps0kkBjoff4D8IwFtQ==@legendarymarketing.net May 28 13:53:14 piler piler[16950]: 400000005b0c4214110c8274006e6c641711: from=[e-mail], size=38317/10312, attachments=0, reference=, message-id=xserial.s56e5Yzf+VxDGa6ZDeqHq0+fTGV9cr14py+S7SSgCroS7BnO4DYXgj2k+8X2SA5KdIYH4eL/rRj8C1GfDRx3MEEUtBY3wEZB+vxRkzBpps0kkBjoff4D8IwFtQ==@legendarymarketing.net, retention=3652, folder=0, delay=0.02, delays=0.01/0.00/0.00/0.00/0.00/0.00, status=duplicate

Thank you

[Janos SUTO]

Make the message_id column in metadata to "varchar(255) not null"

[Petros Abajyan]

Thank you very much . I modify the metadata table as you suggested. Can you please advise on how to reprocess this failure message?

[Janos SUTO]

reindex it, just as with the other issue.

[Petros Abajyan]

Can you tell me how to get ID number since metadata table does not have the entry.

[Janos SUTO]

Run describe metadata, and you'll see the 'id' column as it's the primary key.

[Petros Abajyan]

MariaDB [piler]> select * from metadata where piler_id='400000005b0c4214110c8274006e6c641711'; Empty set (0.00 sec)

MariaDB [piler]> desc metadata -> ; +-------------+---------------------+------+-----+---------+----------------+ | Field | Type | Null | Key | Default | Extra | +-------------+---------------------+------+-----+---------+----------------+ | id | bigint(20) unsigned | NO | PRI | NULL | auto_increment | | from | varchar(128) | NO | MUL | NULL | | | fromdomain | varchar(64) | NO | MUL | NULL | | | subject | text | YES | | NULL | | | spam | tinyint(1) | YES | | 0 | | | arrived | int(10) unsigned | NO | MUL | NULL | | | sent | int(10) unsigned | NO | MUL | NULL | | | retained | int(10) unsigned | NO | MUL | NULL | | | deleted | tinyint(1) | YES | MUL | 0 | | | size | int(11) | YES | | 0 | | | hlen | int(11) | YES | | 0 | | | direction | int(11) | YES | | 0 | | | attachments | int(11) | YES | | 0 | | | piler_id | char(36) | NO | MUL | NULL | | | message_id | varchar(255) | NO | MUL | NULL | | | reference | char(64) | NO | MUL | NULL | | | digest | char(64) | NO | | NULL | | | bodydigest | char(64) | NO | MUL | NULL | | | vcode | char(64) | YES | | NULL | | +-------------+---------------------+------+-----+---------+----------------+ 19 rows in set (0.08 sec)

Can you please advice?

[Janos SUTO]

Unfortunately this message was not archived, because piler thought it was a duplicate. Extending the message_id column will prevent such issues in the future. If you think this specific message is important, then you have to get this message from the mailbox of the given user, and send it to piler again.