ERROR: open /var/lib/dokku/plugins/available/shoreman/plugin.toml: no such file or directory about dokku-shoreman

[sman591]

Same issue here on 0.4.x. Would love to get this working!

[Xiangshen-Meng]

I created a plugin.toml and rebuild my app still not work.
But the error disappeared.

[plugin]
description = "dokku shoreman service plugin"
version = "0.2.0"
[plugin.config]

Now I am using logging-supervisord instead.

[statianzo]

Looks like dokku-shoreman isn't compatible with 0.4.x at the moment. Thanks for filing the issue.

[Xiangshen-Meng]

😃

[hako]

+1 Same issue here too, can't run more than 1 worker without this plugin. Tried supervisord but runs only 1 worker.

[letalumil]

Same issue here.

[Corstiaan84]

Noob question: how do I remove shoreman from dokku in this scenario? "dokku plugin uninstall shoreman" is not working... Thanks :-)

[statianzo]

Most likely rm -r /var/lib/dokku/plugins/dokku-shoreman, assuming that's where your plugin folder is, and then redeploy.

[Corstiaan84]

Thanks. Ran

rm -r /var/lib/dokku/plugins/available/shoreman

and now 'dokku plugin' shows a nice clean list again. However, when I want to deploy I get this warning:

remote: 2015/11/23 17:08:24 open /var/lib/dokku/plugins/available/shoreman/plugin.toml: no such file or directory

and the deploy fails with this message:

remote: Error response from daemon: Cannot kill container a1ef2537264fe871d97faa8741b77e4fbfe97fc12a76f727910f665c3d1dbb40: notrunning: Container a1ef2537264fe871d97faa8741b77e4fbfe97fc12a76f727910f665c3d1dbb40 is not running
remote: Error: failed to kill containers: [a1ef2537264fe871d97faa8741b77e4fbfe97fc12a76f727910f665c3d1dbb40]

Ideas? :-)

Thanks for your time!

[pmvieira]

Hi @Corstiaan84

have you checked if there is a symlink on /var/lib/dokku/plugins/enabled ?

Thanks

[Corstiaan84]

Hi @pmvieira :-). Noob alert! How do I check that and why is it important? I would like to learn more about this.

[pmvieira]

@Corstiaan84 do an ls -lha /var/lib/dokku/plugins/enabled

There are two directories inside /var/lib/dokku/plugins/ : available and enabled.

"available" contains every plugin that was installed and not yet uninstalled;
"enabled" contains all plugins that are being used. Each plugin that is being used is actually just a "shortcut" pointing to a another directory.

So, if you manually uninstalled shoreman, chances are that there is a symlink (AKA a shortcut) pointing somewhere else, and dokku is looking for it but finding nothing.

Have a look and if there is a shoreman symlink there, delete it.

[Corstiaan84]

Thanks. Worked :-).

[riccardoio]

@pmvieira I've noticed that you've done a fork of the branch...works with dokku 0.4.x ? I've tried but seems not load correctly the workers...

[pmvieira]

@riccardoa i just had a quick shot at it, but found the same issue and didn't have time to work on it.
If I manage to get it working on my fork I'll submit a PR

[Corstiaan84]

+1

[riccardoio]

@pmvieira Honestly I've then tried to run the worker like it's explain here: http://progrium.viewdocs.io/dokku/process-management/ and it works perfectly! so it's a bit useless use something like shoreman! (at least in my case where I've only web and worker)

[Corstiaan84]

@riccardoa Could you provide some insights into the steps/config/code you used to get it working? Perhaps create a gist?

[pmvieira]

@riccardoa I agree with you, if that's your scenario then what you mentioned is the best approach IMHO and me/we are using it in some projects.
However, if you want to run non-standard process types, shoreman is indeed handy.

Anyway, I just submited a PR since I believe I was able to fix it for Dokku V4 CC: @statianzo

[riccardoio]

👍