Closed januszm closed 11 months ago
Solved! it's the -d
option, if you want to run shoryuken via Procfile, -d
cannot be used, also -r
is problematic if used with relative path, e.g. -r app/jobs
bundler: failed to load command: shoryuken (/opt/elasticbeanstalk/.rbenv/versions/3.0.6/bin/shoryuken)
gems/bootsnap-1.16.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:29:in `require':
cannot load such file -- app/jobs/my_job.rb (LoadError)
Maybe -r
requires absolute paths, but anyway, I think it's redundant when I use Rails with -R
as the whole app
will be preloaded anyway
This issue is now marked as stale because it hasn't seen activity for a while. Add a comment or it will be closed soon.
This issue was closed because it hasn't seen activity for a while.
I have an application that uses Shoryuken on AWS Elastic Beanstalk, I even added instructions here on how to configure it. It worked OK until about early 2023 but I see it stopped for some reason. The instructions from the wiki are a bit out of date, the process does not start. I've now tried changing this to run via Procfile, which seems more appropriate at the moment.
But the process is constantly restarted, receives the TERM signal and then starts over and over again. I'm wondering if there's something wrong with my config or the gem just doesn't work with Procfile?
Currently the only way to run it side by side with puma webserver on Elastic Beanstalk is by SSH and manually executing the script I described on Wiki, it doesn't work as an Elastic Beanstalk hook, only works when started from interactive shell.