Could not open DB for dynflow at '', will keep data in memory. Restart will drop all dynflow data

Hey guys ,

i had installed Foreman 3.1.2 with katello 4.3 plugin ,
after restarting Foreman services using “Foreman-maintain service restart” , service looks started normally but in when i looked in to smart proxy logs from Foreman dashboard i still can see warning as “Could not open DB for dynflow at ‘’, will keep data in memory. Restart will drop all dynflow data.”…

As i already checked my services are working fine , when i checked with command “Foreman-maintain service list | grep dynflow”, below are the logs.

[root@nwforeman ~]# foreman-maintain service status | grep dynflow
rh-redis5-redis, postgresql, pulpcore-api, pulpcore-content, pulpcore-worker@1.service, pulpcore-worker@2.service, pulpcore-worker@3.service, pulpcore-worker@4.service, pulpcore-worker@5.service, pulpcore-worker@6.service, pulpcore-worker@7.service, pulpcore-worker@8.service, tomcat, dynflow-sidekiq@orchestrator, foreman, httpd, dynflow-sidekiq@worker-1, dynflow-sidekiq@worker-hosts-queue-1, foreman-proxy
/ displaying dynflow-sidekiq@orchestrator
● dynflow-sidekiq@orchestrator.service - Foreman jobs daemon - orchestrator on sidekiq
Loaded: loaded (/usr/lib/systemd/system/dynflow-sidekiq@.service; enabled; vendor preset: disabled)
CGroup: /system.slice/system-dynflow\x2dsidekiq.slice/dynflow-sidekiq@orchestrator.service
Feb 27 01:09:18 nwforeman.auruspay.com dynflow-sidekiq@orchestrator[4307]: 2022-02-27T06:09:18.031Z 4307 TID-4lj INFO: GitLab reliable fetch activated!
Feb 27 01:09:18 nwforeman.auruspay.com dynflow-sidekiq@orchestrator[4307]: 2022-02-27T06:09:18.139Z 4307 TID-4kr INFO: Booting Sidekiq 5.2.7 with redis options {:id=>“Sidekiq-server-PID-4307”, :url=>“redis://localhost:6379/0”}
/ displaying dynflow-sidekiq@worker-1
● dynflow-sidekiq@worker-1.service - Foreman jobs daemon - worker-1 on sidekiq
Loaded: loaded (/usr/lib/systemd/system/dynflow-sidekiq@.service; enabled; vendor preset: disabled)
CGroup: /system.slice/system-dynflow\x2dsidekiq.slice/dynflow-sidekiq@worker-1.service
Feb 27 01:09:51 nwforeman.auruspay.com dynflow-sidekiq@worker-1[4884]: 2022-02-27T06:09:51.722Z 4884 TID-41s INFO: GitLab reliable fetch activated!
Feb 27 01:09:51 nwforeman.auruspay.com dynflow-sidekiq@worker-1[4884]: 2022-02-27T06:09:51.723Z 4884 TID-43g INFO: Booting Sidekiq 5.2.7 with redis options {:id=>“Sidekiq-server-PID-4884”, :url=>“redis://localhost:6379/0”}
/ displaying dynflow-sidekiq@worker-hosts-queue-1
● dynflow-sidekiq@worker-hosts-queue-1.service - Foreman jobs daemon - worker-hosts-queue-1 on sidekiq
Loaded: loaded (/usr/lib/systemd/system/dynflow-sidekiq@.service; enabled; vendor preset: disabled)
CGroup: /system.slice/system-dynflow\x2dsidekiq.slice/dynflow-sidekiq@worker-hosts-queue-1.service
Feb 27 01:09:51 nwforeman.auruspay.com dynflow-sidekiq@worker-hosts-queue-1[4883]: 2022-02-27T06:09:51.731Z 4883 TID-41z INFO: GitLab reliable fetch activated!
Feb 27 01:09:51 nwforeman.auruspay.com dynflow-sidekiq@worker-hosts-queue-1[4883]: 2022-02-27T06:09:51.732Z 4883 TID-43f INFO: Booting Sidekiq 5.2.7 with redis options {:id=>“Sidekiq-server-PID-4883”, :url=>“redis://localhost:6379/0”}

1 Like

This is completely normal. Dynflow on the smart proxy uses an in-memory database. It can be reconfigured to use a persistent database, but there’s no real reason to do that.

2 Likes

Noticed this warning as well on my new deployed proxy, Can perhaps the message level not be warning for this message for a proxy?
Would be nice to avoid seeing this on the proxy if all is good:
image

See this thread Dynflow database or not?

Opened redmine issue and created PR as now also others tend to see this as a problem. But the PR throws an error, I am not sure about.