Debian Bug report logs - #846052 passenger-config/status cannot find instance registry Package: passenger; Maintainer for passenger is Debian Ruby Extras Maintainers ; Source for passenger is src:passenger (PTS, buildd, popcon). Reported by: Matijs van Zuijlen Date: Mon, 28 Nov 2016 08:15:02 UTC Severity: normal Found in version passenger/5.0.30-1 Reply or subscribe to this bug. Toggle useless messages View this report as an mbox folder, status mbox, maintainer mbox Message #5 received at
[email protected] (full text, mbox, reply):
From: Matijs van Zuijlen To: Debian Bug Tracking System Subject: passenger-config/status cannot find instance registry Date: Mon, 28 Nov 2016 07:40:10 +0000 Package: passenger Version: 5.0.30-1 Severity: normal Dear Maintainer, I have just upgraded to passenger 5, and now I want to restart my application the 'new' way by using passenger-config. I have tried this both through capistrano, and on the command line, and I get the following error message: *** ERROR: Phusion Passenger doesn't seem to be running. If you are sure that it is running, then the causes of this problem could be one of: 1. You customized the instance registry directory using Apache's PassengerInstanceRegistryDir option, Nginx's passenger_instance_registry_dir option, or Phusion Passenger Standalone's --instance-registry-dir command line argument. If so, please set the environment variable PASSENGER_INSTANCE_REGISTRY_DIR to that directory and run this command again. 2. The instance directory has been removed by an operating system background service. Please set a different instance registry directory using Apache's PassengerInstanceRegistryDir option, Nginx's passenger_instance_registry_dir option, or Phusion Passenger Standalone's --instance-registry-dir command line argument. I have tried both with and without sudo. I can confirm that passenger is indeed running, and throught lsof I can see that it has open files in a directory in /tmp that I cannot not in fact see listed there. So to me it looks like option 2 is in fact the case, but I have not tried the instructions there and I would have expected them not be needed. -- System Information: Distributor ID: Ubuntu Description: Ubuntu GNU/Linux 8.6 (jessie) Release: 8.6 Codename: jessie Architecture: i386 (i686) Kernel: Linux 4.4.32-rh33-20161115070633.xenU.i386 (SMP w/2 CPU cores) Locale: LANG=en_IE.utf8, LC_CTYPE=en_IE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages passenger depends on: ii libc6 2.19-18+deb8u6 ii libcurl3 7.38.0-4+deb8u4 ii libgcc1 1:4.9.2-10 ii libgmp10 2:6.0.0+dfsg-6 ii libruby2.3 2.3.1-6 ii libstdc++6 6.2.0-13 ii libuv1 1.9.1-3 ii ruby 1:2.3.0+4 ii ruby-rack 1.6.4-4 ii zlib1g 1:1.2.8.dfsg-2+b1 passenger recommends no packages. Versions of packages passenger suggests: ii nodejs 0.10.29~dfsg-2 pn passenger-doc ii python 2.7.9-1 pn rails -- no debconf information
Message #10 received at
[email protected] (full text, mbox, reply):
From: Martin von Wittich To:
[email protected] Cc:
[email protected] Subject: Re: passenger-config/status cannot find instance registry Date: Tue, 15 Aug 2017 19:28:24 +0200 On Mon, 28 Nov 2016 07:40:10 +0000 Matijs van Zuijlen wrote: > I have just upgraded to passenger 5, and now I want to restart my > application the 'new' way by using passenger-config. I have tried this > both through capistrano, and on the command line, and I get the > following error message: > > *** ERROR: Phusion Passenger doesn't seem to be running. If you are sure that it > is running, then the causes of this problem could be one of: I just upgraded our Redmine installation to Debian stretch, and I have the same issue. I believe this is caused by the PrivateTmp feature of systemd (PrivateTmp=true is set in /lib/systemd/system/apache2.service), because while passenger-status is looking in /tmp, Apache is storing the instance registry dir in /tmp/systemd-private-...: redmine.iserv.eu ~ # ll /tmp/systemd-private-df0217594fc94127b16c17b45a99716c-apache2.service-Q1WevN/tmp total 72K drwxr-xr-x 3 www-data www-data 4.0K Aug 15 18:49 bundler/ drwxr-xr-x 4 root root 4.0K Aug 15 18:49 passenger.U9uCrRI/ -rw------- 1 www-data www-data 0 Aug 15 18:52 RackMultipart20170815-1192-8063mg -rw------- 1 www-data www-data 0 Aug 15 18:56 RackMultipart20170815-1192-8qsxi -rw------- 1 www-data www-data 0 Aug 15 18:53 RackMultipart20170815-1192-v5lfb6 -rw------- 1 root root 30K Aug 15 18:56 passenger-error-24wMBJ.html -rw------- 1 root root 30K Aug 15 18:49 passenger-error-GwQoka.html I have resolved this as follows: 1) Create /etc/systemd/system/apache2.service.d/passenger-instance-reg.conf with the following contents: [Service] ExecStartPre=/bin/mkdir -p /run/passenger ExecStopPost=/bin/rmdir --ignore-fail-on-non-empty /run/passenger 2) systemctl daemon-reload 3) Add the following to your Apache configuration: # https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846052 PassengerInstanceRegistryDir /run/passenger 4) Add the following to your /etc/environment: # https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846052 PASSENGER_INSTANCE_REGISTRY_DIR=/run/passenger 5) restart Apache and reconnect (SSH) or re-login (local). Opening a new shell is not enough, because /etc/environment is only read by PAM. passenger-status should work now. -- Mit freundlichen Grüßen Martin v. Wittich IServ GmbH Bültenweg 73 38106 Braunschweig Telefon: 0531-2243666-0 Fax: 0531-2243666-9 E-Mail:
[email protected] Internet: iserv.eu USt-IdNr. DE265149425 | Amtsgericht Braunschweig | HRB 201822 Geschäftsführer: Benjamin Heindl, Jörg Ludwig
Send a report that this bug log contains spam.
Debian bug tracking system administrator . Last modified: Fri Mar 9 03:20:54 2018; Machine Name: beach Debian Bug tracking system Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/. Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.