Application freezes when run with docker-compose since v0.9.9 about active_workflow HOT 5 CLOSED

Hi Markus, thanks for the notice!

This is a tough one to solve quickly, still working on it. As a temporary solution, I have released a point version v0.9.9.1 that runs docker-compose without SINGLE_DYNO=1 (three separate containers).

After the latest refactoring scheduler was extracted out into a separate component and all parts of ActiveWorkflow (web, scheduler, and worker/-s) now run independently. SINGLE_DYNO mode was added specifically as a workaround to let everything run in a single container. Apparently it doesn't work correctly and we will resolve it as soon as possible.

Thank you!
Vidas

from active_workflow.

Hi Vidas,
the 0.9.9.1 fix does not seem to work. Checking out the repository from scratch an starting with docker-compose up first complains about formatting of the docker-compose.yml (environment values' lines must not begin with "-"). After resolving that, the database does not get initialized correctly, I guess from the logs:

active_workflow_scheduler_1  | { 47216107507720 rufus-scheduler intercepted an error:
active_workflow_scheduler_1  |   47216107507720   job:
active_workflow_scheduler_1  |   47216107507720     Rufus::Scheduler::EveryJob "0.5s" {:tag=>"scheduler"}
active_workflow_scheduler_1  |   47216107507720   error:
active_workflow_scheduler_1  |   47216107507720     47216107507720
active_workflow_scheduler_1  |   47216107507720     ActiveRecord::StatementInvalid
active_workflow_scheduler_1  |   47216107507720     PG::UndefinedTable: ERROR:  relation "delayed_jobs" does not exist
active_workflow_scheduler_1  | LINE 8:  WHERE a.attrelid = '"delayed_jobs"'::regclass
active_workflow_scheduler_1  |                             ^
active_workflow_scheduler_1  |   47216107507720       /app/vendor/bundle/ruby/2.6.0/gems/activerecord-6.0.3.2/lib/active_record/connection_adapters/postgresql/database_statements.rb:65:in `exec'
(...)
postgres_1                   | ERROR:  relation "delayed_jobs" does not exist at character 454
postgres_1                   | STATEMENT:  SELECT a.attname, format_type(a.atttypid, a.atttypmod),
postgres_1                   | 	       pg_get_expr(d.adbin, d.adrelid), a.attnotnull, a.atttypid, a.atttypmod,
postgres_1                   | 	       c.collname, col_description(a.attrelid, a.attnum) AS comment
postgres_1                   | 	  FROM pg_attribute a
postgres_1                   | 	  LEFT JOIN pg_attrdef d ON a.attrelid = d.adrelid AND a.attnum = d.adnum
postgres_1                   | 	  LEFT JOIN pg_type t ON a.atttypid = t.oid
postgres_1                   | 	  LEFT JOIN pg_collation c ON a.attcollation = c.oid AND a.attcollation <> t.typcollation

No need to rush though, my main system still works and there's no urgent reason to upgrade that instance at the moment.

Best,
Markus

from active_workflow.

Fixed the fix: v0.9.9.2 fixes broken docker-compose syntax and database initialization issues (that is where errors came from). Rushing things is never an answer...

from active_workflow.

Release v0.9.10 fixes the single-dyno mode (simply by getting rid of foreman and replacing it with a simple shell script). This should not affect anyone running ActiveWorkflow in multi-container mode (which is recommended for production anyway, but was not properly communicated...)

Default docker-compose.yml started using prebuilt docker image (from the docker hub), so if you have any source code modifications you may need to edit it (or use the one in docker/docker-compose.local.yml that still builds images locally).

Thanks!

from active_workflow.

Finally got around to testing v0.9.10 and it works. I consider this issue resolved, thank you!

from active_workflow.