Project

General

Profile

Actions

Bug #20388

closed

Fails to open database, which one?

Added by Guido Günther over 7 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Foreman plugin
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

Installing the nighlty debs including foreman_ansible on Debian Stretch gives me lots of

2017-07-23T23:09:30 [app] [D] Registering 5 assets for plugin foreman-tasks precompilation
2017-07-23T23:09:30 [app] [D] Registering 3 assets for plugin foreman_ansible precompilation
2017-07-23T23:09:34 [app] [W] Failed running foreman-tasks daemon | Sequel::DatabaseConnectionError: SQLite3::CantOpenException: unable to open database file | /usr/share/foreman/vendor/ruby/2.3.0/gems/sequel-4.37.0/lib/sequel/adapters/sqlite.rb:109:in `initialize' | /usr/share/foreman/vendor/ruby/2.3.0/gems/sequel-4.37.0/lib/sequel/adapters/sqlite.rb:109:in `new' | /usr/share/foreman/vendor/ruby/2.3.0/gems/sequel-4.37.0/lib/sequel/adapters/sqlite.rb:109:in `connect' | /usr/share/foreman/vendor/ruby/2.3.0/gems/sequel-4.37.0/lib/sequel/connection_pool.rb:116:in `make_new'

in the logs. Now it would be totally great if it would tell me which database it can't open. The foreman database looks writeable (can create users, ...) and dynflow-production does change timestamp too

rw-r--r- 1 foreman foreman 110592 Jul 23 23:00 dynflow-production.sqlite3
rw-r--r- 1 foreman foreman 2408448 Jul 23 23:12 production.sqlite3

Actions #1

Updated by Adam Ruzicka over 3 years ago

  • Status changed from New to Closed

Dynflow on Foreman no longer uses sqlite, database configuration is "inehrited" from Foreman itself. Closing.

Actions

Also available in: Atom PDF