Seeing multiple error messages like this in our production instance: (psycopg2.errors.StringDataRightTruncation) value too long for type character varying(255)

[portante]

2023-03-30T11:47:03.121168 WARNING 8309 140708314549120 pbench-index sync error 207 -- INDEX fio__2023.03.28T03.58.19 'error' (9) error updating message: (psycopg2.errors.StringDataRightTruncation) value too long for type character varying(255)

[SQL: UPDATE dataset_operations SET state=%(state)s, message=%(message)s WHERE dataset_operations.id = %(dataset_operations_id)s]
[parameters: {'state': 'FAILED', 'message': "Could not fetch tar ball size for /srv/pbench/archive/fs-version-001/virtlab722.virt.lab.xxx.xxx.xxxxxx.com/fio__2023.03.28T03.58.19.tar.xz: [Errno 2] No such file or directory: '/srv/pbench/archive/fs-version-001/virtlab722.virt.lab.xxx.xxx.xxxxxx.com/fio__2023.03.28T03.58.19.tar.xz'", 'dataset_operations_id': 1823}]
(Background on this error at: https://sqlalche.me/e/14/9h9h)

[dbutenhof]

Interesting. So either we should make a short summary of the "operational" status messages (they should all be in the log anyway) or we should make the column unlimited. More importantly, why is the indexer looking for a tarball that doesn't exist?

…

On Thu, Mar 30, 2023 at 7:54 AM Peter Portante ***@***.***> wrote: 2023-03-30T11:47:03.121168 WARNING 8309 140708314549120 pbench-index sync error 207 -- INDEX fio__2023.03.28T03.58.19 'error' (9) error updating message: (psycopg2.errors.StringDataRightTruncation) value too long for type character varying(255) [SQL: UPDATE dataset_operations SET state=%(state)s, message=%(message)s WHERE dataset_operations.id = %(dataset_operations_id)s] [parameters: {'state': 'FAILED', 'message': "Could not fetch tar ball size for /srv/pbench/archive/fs-version-001/virtlab722.virt.lab.xxx.xxx.xxxxxx.com/fio__2023.03.28T03.58.19.tar.xz: [Errno 2] No such file or directory: '/srv/pbench/archive/fs-version-001/virtlab722.virt.lab.xxx.xxx.xxxxxx.com/fio__2023.03.28T03.58.19.tar.xz'", 'dataset_operations_id': 1823}] (Background on this error at: https://sqlalche.me/e/14/9h9h) — Reply to this email directly, view it on GitHub <#3366>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOXGP6NVHRJ6ZLQN42U6P7LW6VX7FANCNFSM6AAAAAAWNF3I5A> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>