Actions
action #29481
open[openqa-monitoring] DBI Exception: DBD::Pg::st execute failed: ERROR: invalid input syntax for integer: "127),"
Start date:
Due date:
% Done:
0%
Estimated time:
Description
observation¶
[Fri Dec 15 17:27:25 2017] [23481:error] DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::Pg::st execute failed: ERROR: invalid input syntax for integer: "127)," [for Statement "SELECT me.id, me.name, me.parent_id, me.size_limit_gb, me.exclusively_kept_asset_size, me.keep_logs_in_days, me.keep_important_logs_in_days, me.keep_results_in_days, me.keep_important_results_in_days, me.default_priority, me.sort_order, me.description, me.build_version_sort, me.t_created, me.t_updated FROM job_groups me WHERE ( id = ? )" with ParamValues: 1='127),'] at /usr/share/openqa/script/../lib/OpenQA/WebAPI/Controller/Test.pm line 501
suggestion¶
wrong api use should not cause a database exception but be handled on a higher level or the error silently ignored
Updated by okurz over 7 years ago
- Copied from action #18048: [tools][openqa-monitoring] AMQP connection closed added
Updated by okurz over 7 years ago
https://github.com/os-autoinst/openqa-logwarn/pull/10 to ignore in logfiles
Updated by okurz over 6 years ago
- Copied to action #40007: [openqa-monitoring] [warn] A message received from unknown worker connection added
Updated by okurz almost 5 years ago
- Status changed from New to Resolved
Might be fixed by our recent better parameter validations. Other than this we probably do not need to care that much
Updated by tinita over 1 year ago
- Status changed from Resolved to Workable
We still have this ticket referenced here: https://github.com/os-autoinst/openqa-logwarn/blob/master/logwarn_openqa#L59C8-L59C50
I say we shouldn't resolve tickets when we ignore DBI errors.
Actions