action #29481
[openqa-monitoring] DBI Exception: DBD::Pg::st execute failed: ERROR: invalid input syntax for integer: "127),"
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Concrete Bugs
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Difficulty:
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
Related issues
History
#1
Updated by okurz over 5 years ago
Updated by - Copied from action #18048: [tools][openqa-monitoring] AMQP connection closed added
#2
Updated by okurz over 5 years ago
https://github.com/os-autoinst/openqa-logwarn/pull/10 to ignore in logfiles
#3
Updated by okurz almost 5 years ago
- Copied to action #40007: [openqa-monitoring] [warn] A message received from unknown worker connection added
#4
Updated by okurz about 3 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