Project

General

Profile

action #18950

OpenQA "internal server failure", possibly after upgrade in TW

Added by mwolcendorf over 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Support
Target version:
-
Start date:
2017-05-04
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

After latest (2017-05-04) upgrade in TW, the OpenQA stopped working with the "internal server error" in web interface.

systemctl status openqa-webui.service
● openqa-webui.service - The openQA web UI
Loaded: loaded (/usr/lib/systemd/system/openqa-webui.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2017-05-04 17:38:57 CEST; 8min ago
Main PID: 4343 (openqa)
Tasks: 11 (limit: 4915)
CGroup: /system.slice/openqa-webui.service
├─4343 /usr/bin/perl /usr/share/openqa/script/openqa prefork -m production --proxy -i 100 -H 400 -w 10 -a 100 -G 1000 -r 20
├─5925 /usr/bin/perl /usr/share/openqa/script/openqa prefork -m production --proxy -i 100 -H 400 -w 10 -a 100 -G 1000 -r 20
├─5926 /usr/bin/perl /usr/share/openqa/script/openqa prefork -m production --proxy -i 100 -H 400 -w 10 -a 100 -G 1000 -r 20
├─5933 /usr/bin/perl /usr/share/openqa/script/openqa prefork -m production --proxy -i 100 -H 400 -w 10 -a 100 -G 1000 -r 20
├─5935 /usr/bin/perl /usr/share/openqa/script/openqa prefork -m production --proxy -i 100 -H 400 -w 10 -a 100 -G 1000 -r 20
├─5938 /usr/bin/perl /usr/share/openqa/script/openqa prefork -m production --proxy -i 100 -H 400 -w 10 -a 100 -G 1000 -r 20
├─5939 /usr/bin/perl /usr/share/openqa/script/openqa prefork -m production --proxy -i 100 -H 400 -w 10 -a 100 -G 1000 -r 20
├─5943 /usr/bin/perl /usr/share/openqa/script/openqa prefork -m production --proxy -i 100 -H 400 -w 10 -a 100 -G 1000 -r 20
├─5944 /usr/bin/perl /usr/share/openqa/script/openqa prefork -m production --proxy -i 100 -H 400 -w 10 -a 100 -G 1000 -r 20
├─5945 /usr/bin/perl /usr/share/openqa/script/openqa prefork -m production --proxy -i 100 -H 400 -w 10 -a 100 -G 1000 -r 20
└─5946 /usr/bin/perl /usr/share/openqa/script/openqa prefork -m production --proxy -i 100 -H 400 -w 10 -a 100 -G 1000 -r 20

May 04 17:38:57 linux-2dan.suse systemd[1]: Started The openQA web UI.
May 04 17:38:59 linux-2dan.suse openqa[4343]: [Thu May 4 17:38:59 2017] [4343:info] Listening at "http://localhost:9526/"
May 04 17:38:59 linux-2dan.suse openqa[4343]: [Thu May 4 17:38:59 2017] [4343:info] Manager 4343 started
May 04 17:38:59 linux-2dan.suse openqa[4343]: Server available at http://localhost:9526/
May 04 17:38:59 linux-2dan.suse openqa[4343]: [Thu May 4 17:38:59 2017] [4343:info] Creating process id file "/tmp/prefork.pid"
May 04 17:39:42 linux-2dan.suse openqa[4343]: [Thu May 4 17:39:42 2017] [5943:error] DBIx::Class::Storage::DBI::_prepare_sth(): DBI Exception: DBD::SQLite::db prepare_cached failed: too many SQL variables at /usr/share/openqa/script/../lib/OpenQA/BuildResults.pm line 186
May 04 17:43:00 linux-2dan.suse openqa[4343]: [Thu May 4 17:43:00 2017] [5939:error] DBIx::Class::Storage::DBI::_prepare_sth(): DBI Exception: DBD::SQLite::db prepare_cached failed: too many SQL variables at /usr/share/openqa/script/../lib/OpenQA/BuildResults.pm line 186
May 04 17:45:13 linux-2dan.suse openqa[4343]: [Thu May 4 17:45:13 2017] [5946:error] DBIx::Class::Storage::DBI::_prepare_sth(): DBI Exception: DBD::SQLite::db prepare_cached failed: too many SQL variables at /usr/share/openqa/script/../lib/OpenQA/BuildResults.pm line 186
May 04 17:45:16 linux-2dan.suse openqa[4343]: [Thu May 4 17:45:16 2017] [5944:error] DBIx::Class::Storage::DBI::_prepare_sth(): DBI Exception: DBD::SQLite::db prepare_cached failed: too many SQL variables at /usr/share/openqa/script/../lib/OpenQA/BuildResults.pm line 186

History

#1 Updated by mwolcendorf over 4 years ago

The old, broken database.

#3 Updated by coolo about 4 years ago

you have too many jobs for sqlite. Switch to postgresql in your instance or reset

#4 Updated by mwolcendorf about 4 years ago

Deleting the database did the trick.

#5 Updated by mwolcendorf about 4 years ago

  • Status changed from New to Closed

Closing - the workaround worked.

#6 Updated by okurz about 4 years ago

  • Category set to Support
  • Status changed from Closed to Resolved
  • Assignee set to okurz

please use "Resolved" normally to close tickets. coolo already gave the right answer of what we also discussed.

Also available in: Atom PDF