Restarting app hangs on supervisor install

[ntdb]

This seems to be a rehash of a couple of old issues... I have the same node app running on two different DO droplets. On one I was able to install dokku-logging-supervisord without issues and it worked after restarting my app. On the other installation was also simple... but I cannot restart my app. It consistently hangs after these lines:

admin@SERVER:~$ dokku ps:restart APP
-----> Releasing APP (dokku/APP:latest)...
-----> Injecting Logging Supervisor ...
supervisor is not installed (will install via apt-get)

Here are the Docker logs from the (exited) container:

Get:1 http://apt.postgresql.org trusty-pgdg InRelease [30.2 kB]
Ign http://archive.ubuntu.com trusty InRelease
Get:2 http://archive.ubuntu.com trusty-security InRelease [64.4 kB]
Get:3 http://apt.postgresql.org trusty-pgdg/main amd64 Packages [65.8 kB]
Get:4 http://archive.ubuntu.com trusty-updates InRelease [64.4 kB]
Get:5 http://archive.ubuntu.com trusty Release.gpg [933 B]
Get:6 http://archive.ubuntu.com trusty-security/main amd64 Packages [477 kB]
Get:7 http://archive.ubuntu.com trusty-updates/main amd64 Packages [836 kB]
Get:8 http://archive.ubuntu.com trusty Release [58.5 kB]
Get:9 http://archive.ubuntu.com trusty/main amd64 Packages [1743 kB]
Get:10 http://archive.ubuntu.com trusty/universe amd64 Packages [7589 kB]
Fetched 10.9 MB in 4s (2568 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
The following extra packages will be installed:
  python-meld3 python-pkg-resources
Suggested packages:
  python-distribute python-distribute-doc
The following NEW packages will be installed:
  python-meld3 python-pkg-resources supervisor
0 upgraded, 3 newly installed, 0 to remove and 73 not upgraded.
Need to get 415 kB of archives.
After this operation, 1878 kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu/ trusty-updates/main python-pkg-resources all 3.3-1ubuntu2 [61.9 kB]
Get:2 http://archive.ubuntu.com/ubuntu/ trusty/universe python-meld3 amd64 0.6.10-1 [39.0 kB]
Get:3 http://archive.ubuntu.com/ubuntu/ trusty/universe supervisor all 3.0b2-1 [314 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 415 kB in 2s (163 kB/s)
Selecting previously unselected package python-pkg-resources.
(Reading database ... 48495 files and directories currently installed.)
Preparing to unpack .../python-pkg-resources_3.3-1ubuntu2_all.deb ...
Unpacking python-pkg-resources (3.3-1ubuntu2) ...
Selecting previously unselected package python-meld3.
Preparing to unpack .../python-meld3_0.6.10-1_amd64.deb ...
Unpacking python-meld3 (0.6.10-1) ...
Selecting previously unselected package supervisor.
Preparing to unpack .../supervisor_3.0b2-1_all.deb ...
Unpacking supervisor (3.0b2-1) ...
Setting up python-pkg-resources (3.3-1ubuntu2) ...
Setting up python-meld3 (0.6.10-1) ...
Setting up supervisor (3.0b2-1) ...
invoke-rc.d: policy-rc.d denied execution of start.

I don't recall any significant different in the way I set up the droplets or Dokku. How is policy-rc.d defined and do I need to adjust it for dokku-logging-supervisord to run properly? Thanks!

[jgeurts]

Seeing this same problem.. any suggestions?

[peerbolte]

having the same problem.. did anyone solve this?

[jwigley]

Using #33 appears to have solved the issue for me. There's more discussion in issue #32, but not entirely sure if they are related.

[dblock]

Anyone has a good handle on this? I tried using this plugin and ran into this problem. Should #33 be merged? Are people using forks?

[jgeurts]

@dblock I'm using @rsteckler's fork with the fix from #33 successfully. Sounds like it's a temporary fix until the docker bug gets patched

[jeffrafter]

Not sure if this is helpful but my app was running completely fine, then I started scaling processes and ran into this issue. At the time of this comment there are two ways to scale dokku scale worker=2 and dokku ps:scale worker=2. I am not sure which one... but one of these messed everything up. I went in via ssh and manually killed DOKKU_SCALE and SCALE files. Then I did a dokku ps:rebuildall and now it works (albeit slowly). So it is possible that if you are running into this issue and don't want to patch you can get back to working.

If you want to apply the patch above without working from #33 you can apply it manually on your server:

sudo vim /var/lib/dokku/plugins/enabled/logging-supervisord/lib/helpers