An error occurred while starting up the preloader

From primerano@tonycode.com on June 27, 2013 19:41:48 What steps will reproduce the problem? Unknown, happens a few times a month. What is the expected output? What do you see instead? Successful s...

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

Comments

@FooBarWidget

From primerano@tonycode.com on June 27, 2013 19:41:48

What steps will reproduce the problem? Unknown, happens a few times a month. What is the expected output? What do you see instead? Successful spawn expected instead of failure. What version of Phusion Passenger are you using? Which version of Rails? On what operating system? * Passenger 4.0.1

  • Rails 3.2.11
  • Red Hat Enterprise Linux Server release 5.5 (Tikanga) Please provide any additional information below. Here is the error log. Let me know if there is additional debug information I should gather.

========= June 22nd ===============

013-06-22 02:35:07.0246 7557/433d7940 Pool2/Spawner.h:739 ]: [App 4855 stdout]

[ 2013-06-22 02:36:36.9501 7557/433d7940 Pool2/Implementation.cpp:762 ]: Could not spawn process for group /var/www/railsapps/app567/current#default: An error occurred while starting up the preloader: it did not write a startup response in time.
in ‘void Passenger::ApplicationPool2::SmartSpawner::throwPreloaderSpawnException(const std::string&, Passenger::SpawnException::ErrorKind, boost::shared_ptrPassenger::ApplicationPool2::Spawner::BackgroundIOCapturer&, const boost::shared_ptrPassenger::ApplicationPool2::Spawner::DebugDir&)’ (SmartSpawner.h:149)
in ‘std::string Passenger::ApplicationPool2::SmartSpawner::negotiatePreloaderStartup(Passenger::ApplicationPool2::SmartSpawner::StartupDetails&)’ (SmartSpawner.h:557)
in ‘void Passenger::ApplicationPool2::SmartSpawner::startPreloader()’ (SmartSpawner.h:205)
in ‘virtual Passenger::ApplicationPool2::ProcessPtr Passenger::ApplicationPool2::SmartSpawner::spawn(const Passenger::ApplicationPool2::Options&)’ (SmartSpawner.h:743)
in ‘void Passenger::ApplicationPool2::Group::spawnThreadRealMain(const Passenger::ApplicationPool2::SpawnerPtr&, const Passenger::ApplicationPool2::Options&, unsigned int)’ (Implementation.cpp:695)

[ 2013-06-22 02:36:37.0711 7557/42e39940 agents/HelperAgent/RequestHandler.h:1888 ]: [Client 61] Cannot checkout session. An error occurred while starting up the preloader: it did not write a startup response in time.
Error page:

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=914

@FooBarWidget

From aashish@plotwatt.com on July 03, 2013 03:53:36

Even i am facing the same issue, please update if you have found the solution for this.
Thanks.

@FooBarWidget

From cacao.sunrise29 on July 03, 2013 11:17:39

I have the same issue, need a fix ! :-)

[root@alarmpi logs]# tail -f error_log
[Wed Jul 03 17:12:26 2013] [notice] Apache/2.2.24 (Unix) mod_ssl/2.2.24 OpenSSL/1.0.1e DAV/2 Phusion_Passenger/4.0.5 configured — resuming normal operations
[ 2013-07-03 17:12:46.4255 26353/b5a5f450 Pool2/Spawner.h:739 ]: [App 26384 stdout]
[ 2013-07-03 17:14:16.4516 26353/b5a5f450 Pool2/Implementation.cpp:774 ]: Could not spawn process for group /srv/http/snorby#default: An error occurred while starting up the preloader : it did not write a startup response in time.
in ‘void Passenger::ApplicationPool2::SmartSpawner::throwPreloaderSpawnException(const string&, Passenger::SpawnException::ErrorKind, Passenger::ApplicationPool2::Spawner::Backgr oundIOCapturerPtr&, const DebugDirPtr&)’ (SmartSpawner.h:150)
in ‘std::string Passenger::ApplicationPool2::SmartSpawner::negotiatePreloaderStartup(Passenger::ApplicationPool2::SmartSpawner::StartupDetails&)’ (SmartSpawner.h:558)
in ‘void Passenger::ApplicationPool2::SmartSpawner::startPreloader()’ (SmartSpawner.h:206)
in ‘virtual Passenger::ApplicationPool2::ProcessPtr Passenger::ApplicationPool2::SmartSpawner::spawn(const Passenger::ApplicationPool2::Options&)’ (SmartSpawner.h:744)
in ‘void Passenger::ApplicationPool2::Group::spawnThreadRealMain(const SpawnerPtr&, const Passenger::ApplicationPool2::Options&, unsigned int)’ (Implementation.cpp:707)

[ 2013-07-03 17:14:16.4535 26353/b58ff450 agents/HelperAgent/RequestHandler.h:1885 ]: [Client 20] Cannot checkout session. An error occurred while starting up the preloader: it did no t write a startup response in time.

@FooBarWidget

From honglilai on July 04, 2013 14:42:10

Can you guys check for two things?

  1. Is there any code in the app which redirects STDOUT to a file?
  2. Is there any code in your bashrc or bash profile which may cause it to quit if there’s no terminal?

@FooBarWidget

From primerano@tonycode.com on July 05, 2013 14:03:54

I’ll dig into these questions next week. I’m out of the office this week.

@FooBarWidget

From Ashrafuzzaman.G2 on July 08, 2013 01:20:18

What steps will reproduce the problem?
Unknown, happens when I setup any new environment. But some how the older servers are ok.

What version of Phusion Passenger are you using? Which version of Rails? On
what operating system?

  • Passenger 4.0.5
  • Rails 3.2.13
  • Ubuntu 12.04

I searched with the STDOUT redirection. But there is nothing like so. Other servers like thin and puma is working fine.

@FooBarWidget

From omega842 on July 08, 2013 05:02:40

Same issue in my case but rails 4.0.0

What steps will reproduce the problem?
Starting passenger server on development mode.

What is the expected output? What do you see instead?
Successful spawn expected instead of failure.

What version of Phusion Passenger are you using? Which version of Rails? On
what operating system?

  • Passenger 4.0.7
  • Ruby ruby 2.0.0p250
  • Rails 4.0.0
  • Debian GNU/Linux 6.0.4 (squeeze)

Please provide any additional information below.

Output error:

[ 2013-07-08 13:41:07.3798 12054/7faf8ec18700 Pool2/Spawner.h:159 ]: [App 12091 stderr] stdin: is not a tty
[ 2013-07-08 13:41:07.3871 12054/7faf8ec59700 Pool2/Spawner.h:738 ]: [App 12091 stdout]
[ 2013-07-08 13:41:09.9229 12054/7faf8ec59700 Pool2/Implementation.cpp:774 ]: Could not spawn process for group /var/www/intra/applications/development/gestion_ticket_dev#default: An error occured while starting up the preloader.
in ‘void Passenger::ApplicationPool2::SmartSpawner::handleErrorResponse(Passenger::ApplicationPool2::SmartSpawner::StartupDetails&)’ (SmartSpawner.h:455)
in ‘std::string Passenger::ApplicationPool2::SmartSpawner::negotiatePreloaderStartup(Passenger::ApplicationPool2::SmartSpawner::StartupDetails&)’ (SmartSpawner.h:558)
in ‘void Passenger::ApplicationPool2::SmartSpawner::startPreloader()’ (SmartSpawner.h:206)
in ‘virtual Passenger::ApplicationPool2::ProcessPtr Passenger::ApplicationPool2::SmartSpawner::spawn(const Passenger::ApplicationPool2::Options&)’ (SmartSpawner.h:744)
in ‘void Passenger::ApplicationPool2::Group::spawnThreadRealMain(const Passenger::ApplicationPool2::SpawnerPtr&, const Passenger::ApplicationPool2::Options&, unsigned int)’ (Implementation.cpp:707)

[ 2013-07-08 13:41:09.9232 12054/7faf87fff700 agents/HelperAgent/RequestHandler.h:1892 ]: [Client 20] Cannot checkout session. An error occured while starting up the preloader.
Error page:
This application is a Rails 4 application, but it was wrongly detected as a Rails 1 or Rails 2 application. This is probably a bug in Phusion Passenger, so please report it.
!> Error
!>
exit (SystemExit)
/usr/local/rvm/gems/ruby-2.0.0-head@gesticket_dev/gems/passenger-4.0.7/helper-scripts/classic-rails-preloader.rb:79:in exit' /usr/local/rvm/gems/ruby-2.0.0-head@gesticket_dev/gems/passenger-4.0.7/helper-scripts/classic-rails-preloader.rb:79:inpreload_app’
/usr/local/rvm/gems/ruby-2.0.0-head@gesticket_dev/gems/passenger-4.0.7/helper-scripts/classic-rails-preloader.rb:156:in <module:App>' /usr/local/rvm/gems/ruby-2.0.0-head@gesticket_dev/gems/passenger-4.0.7/helper-scripts/classic-rails-preloader.rb:6:inmodule:PhusionPassenger’
/usr/local/rvm/gems/ruby-2.0.0-head@gesticket_dev/gems/passenger-4.0.7/helper-scripts/classic-rails-preloader.rb:5:in `

‘

Thanks in advance.

@FooBarWidget

From Ashrafuzzaman.G2 on July 08, 2013 05:04:21

Guys my application is working in passenger 3.0.12 but not in 4.0.x

@FooBarWidget

From honglilai on July 08, 2013 13:22:01

omega842, can you set passenger_log_level to 3 and send the logs?

@FooBarWidget

@FooBarWidget

From aashish@plotwatt.com on July 09, 2013 03:05:50

My ‘Passenger Spawn Server’ itself is down. When i restart Apache, passenger spawn server is not able to come up. Any comments on this ?

@FooBarWidget

From honglilai on July 09, 2013 03:09:42

aashish: does version 4.0.8 work for you? It was released 2 hours ago.

@FooBarWidget

From aashish@plotwatt.com on July 09, 2013 03:22:12

17373 216.1 MB 0.3 MB PassengerWatchdog
17378 489.6 MB 0.3 MB PassengerHelperAgent
17387 230.0 MB 1.0 MB PassengerLoggingAgent

Processes: 3

This are all processes which are started once i start apache. No spawn server :-(

@FooBarWidget

From honglilai on July 11, 2013 10:33:57

aashish, can you describe your problem in detail? What is not working? What error message do you see? What do you expect to happen, and what actually happens?

@FooBarWidget

From primerano@tonycode.com on July 12, 2013 14:01:18

In my case (the original post) I think my machine is having issues where the spawn is taking over 90s seconds.

I see the spawn and almost 80 seconds later I see a message from newrelic so I know it is finally starting up

This is the spawn start
[ 2013-07-07 03:02:36.5053 26740/41d4d940 Pool2/Spawner.h:739 ]: [App 15715 stdout]

I’m pretty sure this is newrelic
[ 2013-07-07 03:03:51.2345 26740/41d4d940 Pool2/Spawner.h:739 ]: [App 15715 stdout] Agent is configured to send raw SQL to the service

This is passenger punting at 90 seconds
[ 2013-07-07 03:04:06.4969 26740/41d4d940 Pool2/Implementation.cpp:762 ]: Could not spawn process for group

I need to figure out what is hanging up my machine but I’m wondering if this 90 seconds is configurable?

@FooBarWidget

@FooBarWidget

From aashish@plotwatt.com on July 15, 2013 00:04:22

honglilai:
Sure, I have posted list of processes running when i start my apache.
There is no Spawn server process running on. Now, when i try to hit my application url, it gives error as failure in spawning the application server.

Ideally it should spawn new application process and application should get started.
I checked in application, there is no redirection of logs to stdout.

Now, i am using Passengerv4.0.8

@FooBarWidget

From honglilai on July 15, 2013 03:10:54

But it could also be an application-level problem. Can you follow the tips at section «Application startup freeze»?

@FooBarWidget

From honglilai on September 05, 2013 03:47:23

Status: Stale

@FooBarWidget

From sandy@arenaflowers.com on September 05, 2013 04:23:17

I’m also getting : «An error occurred while starting up the preloader: it did not write a startup response in time.» since upgrading to passenger 4.x.

It only occurs when one of our apps starts on a small EC2 instance, but it’s ok on a medium. However, I don’t want to use a more expensive instance simply to satisfy a passenger 4.x startup constraint.

Can I have a configurable timeout to solve this problem, rather than being hardcoded at 90 seconds ?

@FooBarWidget

From honglilai on September 05, 2013 04:44:50

A configurable timeout was added last week and will be included in the next version of Phusion Passenger.

@FooBarWidget

@FooBarWidget

From honglilai on September 05, 2013 05:56:07

Either this week or next week. If you can’t wait, get the development source code from github.

@FooBarWidget

From primerano@tonycode.com on September 05, 2013 07:48:07

FYI.. I haven’t seen this issue in 2 months now. I suspect I was having network or hardware issues when it happened.

Thanks for making the timeout configurable.

@FooBarWidget

@FooBarWidget

From bartek.danek on September 25, 2013 04:46:37

For me it appeared again in version 4.0.19.
I have to say that passenger (especially enterprise edition) is ‘very stable’.

@FooBarWidget

From honglilai on September 25, 2013 05:39:36

bartek.danek, I’m sorry that you’re experiencing problems. Have you tried the suggestions at https://github.com/FooBarWidget/passenger/wiki/Debugging-application-startup-problems yet? That document should cover pretty much all possible failure scenarios. Last time we helped an Enterprise customer with this problem (about a month ago), it just turned out that his server is too busy with background processing, causing application startup to timeout. For him, increasing the timeout solved his problem.

@FooBarWidget

From bartek.danek on September 25, 2013 06:53:50

honglilai do you mean ‘passenger_start_timeout’ option?

@FooBarWidget

From honglilai on September 25, 2013 07:50:29

Yes.

@FooBarWidget

From bartek.danek on September 25, 2013 11:36:08

Cool, it fixed my problem.
Thanks honglilai!

@FooBarWidget

From almozavr on January 05, 2014 02:45:33

The only thing: doc says passenger_start_timeout uses seconds, but! in practice it seems to use millis.

@FooBarWidget

From honglilai on January 22, 2014 05:10:34

almozavr: It should be seconds. Which version are you using?

@danielquisbert

sorry,
openproject3 rvm install with 2.1, yet I chiliproject 3.8 with rvm 1.9.3. debian wheezy.
The question is: how do I setup apache to have passenger in running the two systems?
Thanks in advance

2 participants

@FooBarWidget

@danielquisbert

Источник

Содержание

  1. An error occurred while starting up the preloader #1164
  2. Comments
  3. Redmine
  4. [SOLVED] Redmine stopped working after updated and reboot
  5. Symptoms¶
  6. Tested¶
  7. An error occurred while starting up the preloader #1013
  8. Comments
  9. Passenger standalone not starting (ruby 2, OS X Mavericks) #1137
  10. Comments
  11. mkdir -p /var/folders/8y/phd10m5n6812q9x0nfsfth080000z8/T/passenger-standalone.39gr7p/locations.ini/buildout/ruby/ruby-2.0.0-x86_64-macosx
  12. Not a valid directory. Trying a different one.
  13. mkdir -p /Users/zhamman/.passenger/native_support/4.0.29/ruby-2.0.0-x86_64-macosx
  14. cd /Users/zhamman/.passenger/native_support/4.0.29/ruby-2.0.0-x86_64-macosx
  15. /Users/zhamman/.rvm/wrappers/ruby-2.0.0-p247/ruby ‘/usr/local/Cellar/passenger/4.0.29/libexec/ext/ruby/extconf.rb’
  16. Compilation failed.
  17. Passenger standalone not starting (ruby 2, OS X Mavericks) #1137
  18. Comments
  19. mkdir -p /var/folders/8y/phd10m5n6812q9x0nfsfth080000z8/T/passenger-standalone.39gr7p/locations.ini/buildout/ruby/ruby-2.0.0-x86_64-macosx
  20. Not a valid directory. Trying a different one.
  21. mkdir -p /Users/zhamman/.passenger/native_support/4.0.29/ruby-2.0.0-x86_64-macosx
  22. cd /Users/zhamman/.passenger/native_support/4.0.29/ruby-2.0.0-x86_64-macosx
  23. /Users/zhamman/.rvm/wrappers/ruby-2.0.0-p247/ruby ‘/usr/local/Cellar/passenger/4.0.29/libexec/ext/ruby/extconf.rb’
  24. Compilation failed.

An error occurred while starting up the preloader #1164

From vptcnt on March 04, 2014 23:57:13

What steps will reproduce the problem? 1. I am developping a Rails 4 application. Every morning, when I arrive at the office, and start working on the application, I have a Passenger Error :

An error occurred while starting up the preloader. It exited before signalling successful startup back to Phusion Passenger. Please read this article for more information about this problem.
Raw process output:

/home/vpt/.rvm/gems/ruby-2.1.0/gems/passenger-4.0.33/lib/phusion_passenger/preloader_shared_helpers.rb:99:in initialize’: No such file or directory — connect(2) for «/tmp/passenger.1.0.26371/generation-1/backends/preloader.8647» (Errno::ENOENT) from /home/vpt/.rvm/gems/ruby-2.1.0/gems/passenger-4.0.33/lib/phusion_passenger/preloader_shared_helpers.rb:99:in new’
from /home/vpt/.rvm/gems/ruby-2.1.0/gems/passenger-4.0.33/lib/phusion_passenger/preloader_shared_helpers.rb:99:in run_main_loop’ from /home/vpt/.rvm/gems/ruby-2.1.0/gems/passenger-4.0.33/helper-scripts/rack-preloader.rb:153:in module:App’
from /home/vpt/.rvm/gems/ruby-2.1.0/gems/passenger-4.0.33/helper-scripts/rack-preloader.rb:29:in ‘ from /home/vpt/.rvm/gems/ruby-2.1.0/gems/passenger-4.0.33/helper-scripts/rack-preloader.rb:28:in

  1. To resolve the problem, I have to restart the Apache Server..
  2. Everything is fine.
  3. And if I stop working on the application for a while (few hours), the error appears again

What version of Phusion Passenger are you using?
4.0.33

Which version of Rails?
4.0.2 with ruby 2.1 via RVM

On what operating system?
OpenSuse 13.1

The text was updated successfully, but these errors were encountered:

Источник

Redmine

[SOLVED] Redmine stopped working after updated and reboot

I’m having some problems with our Redmine installation and would greatly appreciate any help!

Symptoms¶

I recently updated Redmine to 3.2 from 3.1, which worked fine. However, when I did some server maintenance the other day I rebooted the server for the first time since the upgrade (I believe). It will now not start (preloader times out). I’m redirected to a Passenger error page, but it does not output any real error (the raw output is (empty) ). The output in the Apache log is the following.

The server works for the rest of what its being used for (Mercurial repository and file server).

Tested¶

I followed the Passenger debugging page, but either I didn’t understand it properly or those were not the issue.

I also tried hosting the pre-update instance of Redmine, which did not work either.

I have triple verified permissions (which I believe would have given an other error anyway).

Any help in debugging this would be greatly appreciated! I’m not very familiar with Ruby or Passenger, so I’m having a hard time finding what is actually causing it to not start up.

I have attached the HTML page that is displayed, which contains most variables. The more general are listed here.

OS Ubuntu Server 14.04 LTS
Web Apache2
Redmine 3.2
Ruby 1.9.1

HTML_Error_output.html — HTML error page (17,477 КБ)

Источник

An error occurred while starting up the preloader #1013

What steps will reproduce the problem? Unknown, happens a few times a month. What is the expected output? What do you see instead? Successful spawn expected instead of failure. What version of Phusion Passenger are you using? Which version of Rails? On what operating system? * Passenger 4.0.1

  • Rails 3.2.11
  • Red Hat Enterprise Linux Server release 5.5 (Tikanga) Please provide any additional information below. Here is the error log. Let me know if there is additional debug information I should gather.

013-06-22 02:35:07.0246 7557/433d7940 Pool2/Spawner.h:739 ]: [App 4855 stdout]

[ 2013-06-22 02:36:36.9501 7557/433d7940 Pool2/Implementation.cpp:762 ]: Could not spawn process for group /var/www/railsapps/app567/current#default: An error occurred while starting up the preloader: it did not write a startup response in time.
in ‘void Passenger::ApplicationPool2::SmartSpawner::throwPreloaderSpawnException(const std::string&, Passenger::SpawnException::ErrorKind, boost::shared_ptrPassenger::ApplicationPool2::Spawner::BackgroundIOCapturer&, const boost::shared_ptrPassenger::ApplicationPool2::Spawner::DebugDir&)’ (SmartSpawner.h:149)
in ‘std::string Passenger::ApplicationPool2::SmartSpawner::negotiatePreloaderStartup(Passenger::ApplicationPool2::SmartSpawner::StartupDetails&)’ (SmartSpawner.h:557)
in ‘void Passenger::ApplicationPool2::SmartSpawner::startPreloader()’ (SmartSpawner.h:205)
in ‘virtual Passenger::ApplicationPool2::ProcessPtr Passenger::ApplicationPool2::SmartSpawner::spawn(const Passenger::ApplicationPool2::Options&)’ (SmartSpawner.h:743)
in ‘void Passenger::ApplicationPool2::Group::spawnThreadRealMain(const Passenger::ApplicationPool2::SpawnerPtr&, const Passenger::ApplicationPool2::Options&, unsigned int)’ (Implementation.cpp:695)

[ 2013-06-22 02:36:37.0711 7557/42e39940 agents/HelperAgent/RequestHandler.h:1888 ]: [Client 61] Cannot checkout session. An error occurred while starting up the preloader: it did not write a startup response in time.
Error page:

The text was updated successfully, but these errors were encountered:

Even i am facing the same issue, please update if you have found the solution for this.
Thanks.

From cacao.sunrise29 on July 03, 2013 11:17:39

I have the same issue, need a fix ! 🙂

[root@alarmpi logs]# tail -f error_log
[Wed Jul 03 17:12:26 2013] [notice] Apache/2.2.24 (Unix) mod_ssl/2.2.24 OpenSSL/1.0.1e DAV/2 Phusion_Passenger/4.0.5 configured — resuming normal operations
[ 2013-07-03 17:12:46.4255 26353/b5a5f450 Pool2/Spawner.h:739 ]: [App 26384 stdout]
[ 2013-07-03 17:14:16.4516 26353/b5a5f450 Pool2/Implementation.cpp:774 ]: Could not spawn process for group /srv/http/snorby#default: An error occurred while starting up the preloader : it did not write a startup response in time.
in ‘void Passenger::ApplicationPool2::SmartSpawner::throwPreloaderSpawnException(const string&, Passenger::SpawnException::ErrorKind, Passenger::ApplicationPool2::Spawner::Backgr oundIOCapturerPtr&, const DebugDirPtr&)’ (SmartSpawner.h:150)
in ‘std::string Passenger::ApplicationPool2::SmartSpawner::negotiatePreloaderStartup(Passenger::ApplicationPool2::SmartSpawner::StartupDetails&)’ (SmartSpawner.h:558)
in ‘void Passenger::ApplicationPool2::SmartSpawner::startPreloader()’ (SmartSpawner.h:206)
in ‘virtual Passenger::ApplicationPool2::ProcessPtr Passenger::ApplicationPool2::SmartSpawner::spawn(const Passenger::ApplicationPool2::Options&)’ (SmartSpawner.h:744)
in ‘void Passenger::ApplicationPool2::Group::spawnThreadRealMain(const SpawnerPtr&, const Passenger::ApplicationPool2::Options&, unsigned int)’ (Implementation.cpp:707)

[ 2013-07-03 17:14:16.4535 26353/b58ff450 agents/HelperAgent/RequestHandler.h:1885 ]: [Client 20] Cannot checkout session. An error occurred while starting up the preloader: it did no t write a startup response in time.

From honglilai on July 04, 2013 14:42:10

Can you guys check for two things?

  1. Is there any code in the app which redirects STDOUT to a file?
  2. Is there any code in your bashrc or bash profile which may cause it to quit if there’s no terminal?

I’ll dig into these questions next week. I’m out of the office this week.

What steps will reproduce the problem?
Unknown, happens when I setup any new environment. But some how the older servers are ok.

What version of Phusion Passenger are you using? Which version of Rails? On
what operating system?

I searched with the STDOUT redirection. But there is nothing like so. Other servers like thin and puma is working fine.

From omega842 on July 08, 2013 05:02:40

Same issue in my case but rails 4.0.0

What steps will reproduce the problem?
Starting passenger server on development mode.

What is the expected output? What do you see instead?
Successful spawn expected instead of failure.

What version of Phusion Passenger are you using? Which version of Rails? On
what operating system?

  • Passenger 4.0.7
  • Ruby ruby 2.0.0p250
  • Rails 4.0.0
  • Debian GNU/Linux 6.0.4 (squeeze)

Please provide any additional information below.

Источник

Passenger standalone not starting (ruby 2, OS X Mavericks) #1137

From z.hamman on December 30, 2013 22:37:23

What steps will reproduce the problem? 1. brew install passenger
2. run passenger start from Rails.root
3. web server fails to start What is the expected output? What do you see instead? Expected: webapp to start

See: web application could not be started.

An error occurred while starting up the preloader. It sent an unknown response type «n».
Raw process output:

*** Phusion Passenger: no passenger_native_support.bundle found for the current Ruby interpreter. Downloading precompiled binary from the Phusion server (set PASSENGER_DOWNLOAD_NATIVE_SUPPORT_BINARY=0 to disable).
Attempting to download https://oss-binaries.phusionpassenger.com/binaries/passenger/by_release/4.0.29/rubyext-ruby-2.0.0-x86_64-macosx.tar.gz into /var/folders/8y/phd10m5n6812q9x0nfsfth080000z8/T/passenger-native-support-a40zbz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 —:—:— —:—:— —:—:— 0
0 0 0 0 0 0 0 0 —:—:— —:—:— —:—:— 0
0 0 0 0 0 0 0 0 —:—:— —:—:— —:—:— 0
curl: (22) The requested URL returned error: 404 Not Found
*** Phusion Passenger: no passenger_native_support.bundle found for the current Ruby interpreter. Compiling one (set PASSENGER_COMPILE_NATIVE_SUPPORT_BINARY=0 to disable).

mkdir -p /var/folders/8y/phd10m5n6812q9x0nfsfth080000z8/T/passenger-standalone.39gr7p/locations.ini/buildout/ruby/ruby-2.0.0-x86_64-macosx

Not a valid directory. Trying a different one.

mkdir -p /Users/zhamman/.passenger/native_support/4.0.29/ruby-2.0.0-x86_64-macosx

cd /Users/zhamman/.passenger/native_support/4.0.29/ruby-2.0.0-x86_64-macosx

/Users/zhamman/.rvm/wrappers/ruby-2.0.0-p247/ruby ‘/usr/local/Cellar/passenger/4.0.29/libexec/ext/ruby/extconf.rb’

*** /usr/local/Cellar/passenger/4.0.29/libexec/ext/ruby/extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers. Check the mkmf.log file for more details. You may
need configuration options.

Provided configuration options:
—with-opt-dir
—with-opt-include
—without-opt-include=$/include
—with-opt-lib
—without-opt-lib=$/lib
—with-make-prog
—without-make-prog
—srcdir=/usr/local/Cellar/passenger/4.0.29/libexec/ext/ruby
—curdir
—ruby=/Users/zhamman/.rvm/rubies/ruby-2.0.0-p247/bin/ruby
/Users/zhamman/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/mkmf.rb:434:in try_do’: The compiler failed to generate an executable file. (RuntimeError) You have to install development tools first. from /Users/zhamman/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/mkmf.rb:565:in try_cpp’
from /Users/zhamman/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/mkmf.rb:1044:in block in have_header’ from /Users/zhamman/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/mkmf.rb:895:in block in checking_for’
from /Users/zhamman/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/mkmf.rb:340:in block (2 levels) in postpone’ from /Users/zhamman/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/mkmf.rb:310:in open’
from /Users/zhamman/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/mkmf.rb:340:in block in postpone’ from /Users/zhamman/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/mkmf.rb:310:in open’
from /Users/zhamman/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/mkmf.rb:336:in postpone’ from /Users/zhamman/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/mkmf.rb:894:in checking_for’
from /Users/zhamman/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/mkmf.rb:1043:in have_header’ from /usr/local/Cellar/passenger/4.0.29/libexec/ext/ruby/extconf.rb:37:in

Compilation failed.

Ruby native_support extension not loaded. Continuing without native_support.
checking for alloca.h. !> Error What version of Phusion Passenger are you using? Which version of Rails? On what operating system? 4.0.29, 4.0.1, OS X Mavericks Please provide any additional information below. Ruby 2.0, RVM

Also tried with gem installation through bundler using 4.0.30. Same result.

The text was updated successfully, but these errors were encountered:

Источник

Passenger standalone not starting (ruby 2, OS X Mavericks) #1137

From z.hamman on December 30, 2013 22:37:23

What steps will reproduce the problem? 1. brew install passenger
2. run passenger start from Rails.root
3. web server fails to start What is the expected output? What do you see instead? Expected: webapp to start

See: web application could not be started.

An error occurred while starting up the preloader. It sent an unknown response type «n».
Raw process output:

*** Phusion Passenger: no passenger_native_support.bundle found for the current Ruby interpreter. Downloading precompiled binary from the Phusion server (set PASSENGER_DOWNLOAD_NATIVE_SUPPORT_BINARY=0 to disable).
Attempting to download https://oss-binaries.phusionpassenger.com/binaries/passenger/by_release/4.0.29/rubyext-ruby-2.0.0-x86_64-macosx.tar.gz into /var/folders/8y/phd10m5n6812q9x0nfsfth080000z8/T/passenger-native-support-a40zbz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 —:—:— —:—:— —:—:— 0
0 0 0 0 0 0 0 0 —:—:— —:—:— —:—:— 0
0 0 0 0 0 0 0 0 —:—:— —:—:— —:—:— 0
curl: (22) The requested URL returned error: 404 Not Found
*** Phusion Passenger: no passenger_native_support.bundle found for the current Ruby interpreter. Compiling one (set PASSENGER_COMPILE_NATIVE_SUPPORT_BINARY=0 to disable).

mkdir -p /var/folders/8y/phd10m5n6812q9x0nfsfth080000z8/T/passenger-standalone.39gr7p/locations.ini/buildout/ruby/ruby-2.0.0-x86_64-macosx

Not a valid directory. Trying a different one.

mkdir -p /Users/zhamman/.passenger/native_support/4.0.29/ruby-2.0.0-x86_64-macosx

cd /Users/zhamman/.passenger/native_support/4.0.29/ruby-2.0.0-x86_64-macosx

/Users/zhamman/.rvm/wrappers/ruby-2.0.0-p247/ruby ‘/usr/local/Cellar/passenger/4.0.29/libexec/ext/ruby/extconf.rb’

*** /usr/local/Cellar/passenger/4.0.29/libexec/ext/ruby/extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers. Check the mkmf.log file for more details. You may
need configuration options.

Provided configuration options:
—with-opt-dir
—with-opt-include
—without-opt-include=$/include
—with-opt-lib
—without-opt-lib=$/lib
—with-make-prog
—without-make-prog
—srcdir=/usr/local/Cellar/passenger/4.0.29/libexec/ext/ruby
—curdir
—ruby=/Users/zhamman/.rvm/rubies/ruby-2.0.0-p247/bin/ruby
/Users/zhamman/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/mkmf.rb:434:in try_do’: The compiler failed to generate an executable file. (RuntimeError) You have to install development tools first. from /Users/zhamman/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/mkmf.rb:565:in try_cpp’
from /Users/zhamman/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/mkmf.rb:1044:in block in have_header’ from /Users/zhamman/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/mkmf.rb:895:in block in checking_for’
from /Users/zhamman/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/mkmf.rb:340:in block (2 levels) in postpone’ from /Users/zhamman/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/mkmf.rb:310:in open’
from /Users/zhamman/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/mkmf.rb:340:in block in postpone’ from /Users/zhamman/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/mkmf.rb:310:in open’
from /Users/zhamman/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/mkmf.rb:336:in postpone’ from /Users/zhamman/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/mkmf.rb:894:in checking_for’
from /Users/zhamman/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/mkmf.rb:1043:in have_header’ from /usr/local/Cellar/passenger/4.0.29/libexec/ext/ruby/extconf.rb:37:in

Compilation failed.

Ruby native_support extension not loaded. Continuing without native_support.
checking for alloca.h. !> Error What version of Phusion Passenger are you using? Which version of Rails? On what operating system? 4.0.29, 4.0.1, OS X Mavericks Please provide any additional information below. Ruby 2.0, RVM

Also tried with gem installation through bundler using 4.0.30. Same result.

The text was updated successfully, but these errors were encountered:

Источник

Источник

I’ve tried what was recommended here: Passenger: internal server error , but found no references to STDOUT in config.ru

I’m on ruby-2.0.0-p247 and passenger (4.0.17)

Console output after attempting to load page:

[ 2013-09-16 14:34:07.3648 4197/b72beb40 Pool2/Spawner.h:738 ]: [App 4435 stdout]
Connecting to database specified by database.yml
[ 2013-09-16 14:35:37.4570 4197/b72beb40 Pool2/Implementation.cpp:849 ]: Could not spawn process for group /media/sf_John/product#default: An error occurred while starting up the preloader: it did not write a startup response in time.
in ‘void Passenger::ApplicationPool2::SmartSpawner::throwPreloaderSpawnException(const std::string&, Passenger::SpawnException::ErrorKind, boost::shared_ptr&, const boost::shared_ptr&)’ (SmartSpawner.h:150)
in ‘std::string Passenger::ApplicationPool2::SmartSpawner::negotiatePreloaderStartup(Passenger::ApplicationPool2::SmartSpawner::StartupDetails&)’ (SmartSpawner.h:558)
in ‘void Passenger::ApplicationPool2::SmartSpawner::startPreloader()’ (SmartSpawner.h:206)
in ‘virtual Passenger::ApplicationPool2::ProcessPtr Passenger::ApplicationPool2::SmartSpawner::spawn(const Passenger::ApplicationPool2::Options&)’ (SmartSpawner.h:744)
in ‘void Passenger::ApplicationPool2::Group::spawnThreadRealMain(const Passenger::ApplicationPool2::SpawnerPtr&, const Passenger::ApplicationPool2::Options&, unsigned int)’ (Implementation.cpp:782)

[ 2013-09-16 14:35:37.4578 4197/b60fdb40 agents/HelperAgent/RequestHandler.h:1952 ]: [Client 20] Cannot checkout session. An error occurred while starting up the preloader: it did not write a startup response in time.

Gem list:

actionmailer (3.2.14, 3.2.13)
actionpack (3.2.14, 3.2.13)
active_hash (1.0.1, 0.9.14)
activemodel (3.2.14, 3.2.13)
activerecord (3.2.14, 3.2.13)
activeresource (3.2.14, 3.2.13)
activesupport (3.2.14, 3.2.13)
acts_as_paranoid (0.4.2)
addressable (2.3.5, 2.3.4)
american_date (1.1.0)
arbre (1.0.1)
arel (3.0.2)
attr_required (0.0.5)
bcrypt-ruby (3.1.2, 3.1.1, 3.0.1)
better_errors (0.9.0)
binding_of_caller (0.7.2)
bourbon (3.1.8)
builder (3.0.4)
bundler (1.3.5)
bundler-unload (1.0.1)
cancan (1.6.10)
capybara (2.1.0)
childprocess (0.3.9)
chronic (0.10.0, 0.9.1)
chunky_png (1.2.8)
cliver (0.2.1)
coderay (1.0.9)
coffee-rails (3.2.2)
coffee-rails-source-maps (1.3.6, 1.3.5)
coffee-script (2.2.0)
coffee-script-source (1.6.3, 1.6.2)
compass (0.12.2)
compass-rails (1.0.3)
crack (0.4.1, 0.4.0)
daemon_controller (1.1.4)
daemons (1.1.9)
dalli (2.6.4)
database_cleaner (1.1.1, 0.9.1)
debug_inspector (0.0.2)
devise (3.0.3, 3.0.2, 3.0.1, 2.2.4)
devise_oauth2_providable (1.1.2)
diff-lcs (1.2.4)
dotenv (0.8.0)
dragonfly (0.9.15)
draper (1.2.1)
erubis (2.7.0)
ethon (0.6.1, 0.6.0, 0.5.12)
eventmachine (1.0.3)
excon (0.25.3, 0.23.0)
execjs (2.0.1, 1.4.0)
factory_girl (4.2.0)
factory_girl_rails (4.2.1)
faraday (0.8.8)
faraday_middleware (0.9.0)
fastercsv (1.5.5)
ffaker (1.18.0, 1.16.1)
ffi (1.9.0)
fog (1.15.0, 1.14.0, 1.12.1)
foreman (0.63.0)
formatador (0.2.4)
formtastic (2.2.1)
forward (0.3.2)
fssm (0.2.10)
fuubar (1.2.1, 1.1.1)
gherkin (2.12.1, 2.12.0)
guard (1.8.2, 1.8.1)
guard-rspec (3.0.2)
guard-spork (1.5.1, 1.5.0)
haml (4.0.3)
haml-rails (0.4)
has_scope (0.6.0.rc, 0.5.1)
highline (1.6.19)
hike (1.2.3)
httpclient (2.3.4.1, 2.3.3)
i18n (0.6.5, 0.6.4, 0.6.1)
inherited_resources (1.4.1, 1.4.0)
journey (1.0.4)
jquery-rails (2.3.0)
jquery-ui-rails (4.0.4, 4.0.3)
json (1.7.7)
jwt (0.1.8)
kaminari (0.14.1)
kgio (2.8.0)
kramdown (1.1.0, 1.0.2)
launchy (2.3.0)
listen (1.3.0, 1.2.2)
lumberjack (1.0.4)
mail (2.5.4)
mail_view (1.0.3)
meta_search (1.1.3)
method_source (0.8.2, 0.8.1)
mime-types (1.24, 1.23)
mini_magick (3.6.0)
mini_portile (0.5.1)
mock_redis (0.9.0, 0.8.2, 0.7.0)
modernizr-rails (2.6.2.3)
modular-scale (1.0.6)
mono_logger (1.1.0)
multi_json (1.7.9, 1.7.8, 1.7.7)
multipart-post (1.2.0)
mysql2 (0.3.13, 0.3.11)
net-scp (1.1.2, 1.1.1)
net-ssh (2.6.8, 2.6.7)
newrelic_rpm (3.6.6.147, 3.6.3.111)
nokogiri (1.6.0, 1.5.10)
oily_png (1.1.0)
orm_adapter (0.4.0)
paper_trail (2.7.2)
passenger (4.0.17)
polyamorous (0.5.0)
polyglot (0.3.3)
pry (0.9.12.2)
quiet_assets (1.0.2)
rack (1.5.2, 1.4.5)
rack-cache (1.2)
rack-oauth2 (0.11.0)
rack-protection (1.5.0)
rack-ssl (1.3.3)
rack-test (0.6.2)
rails (3.2.14, 3.2.13)
railties (3.2.14, 3.2.13)
raindrops (0.11.0)
rake (10.1.0)
rb-fsevent (0.9.3)
rb-inotify (0.9.1, 0.9.0)
rb-kqueue (0.2.0)
rdoc (3.12.2)
redcarpet (3.0.0, 2.3.0)
redis (3.0.4)
redis-namespace (1.3.1, 1.3.0)
request_store (1.0.5)
responders (1.0.0.rc, 0.9.3)
resque (1.24.1)
resque_mailer (2.2.4)
rspec (2.14.1)
rspec-core (2.14.5, 2.14.4, 2.14.3)
rspec-expectations (2.14.2, 2.14.0)
rspec-instafail (0.2.4)
rspec-mocks (2.14.3, 2.14.2, 2.14.1)
rspec-rails (2.14.0)
ruby-hmac (0.4.0)
ruby-progressbar (1.2.0, 1.1.1)
rubygems-bundler (1.2.2)
rvm (1.11.3.8)
safe_yaml (0.9.5, 0.9.4, 0.9.3)
sass (3.2.10, 3.2.9)
sass-rails (3.2.6)
sassy-math (1.5)
shoulda-matchers (2.3.0, 2.2.0)
simple_form (2.1.0)
simplecov (0.7.1)
simplecov-html (0.7.1)
sinatra (1.4.3)
slop (3.4.6, 3.4.5)
spork-rails (3.2.1)
sprockets (2.2.2)
stamp (0.5.0)
state_machine (1.2.0)
subexec (0.2.3)
thin (1.5.1)
thor (0.18.1)
tilt (1.4.1)
travis-artifacts (0.1.0)
treetop (1.4.15, 1.4.14)
turnip (1.1.0)
twilio-ruby (3.10.1, 3.9.0)
typhoeus (0.6.5, 0.6.4, 0.6.3)
tzinfo (0.3.37)
uglifier (2.2.0, 2.1.2, 2.1.1)
unicorn (4.6.3, 4.6.2)
valid_attribute (1.3.1)
vcr (2.5.0)
vegas (0.1.11)
verbs (2.1.3)
warden (1.2.3, 1.2.1)
webmock (1.11.0)
websocket-driver (0.2.3, 0.2.1)
whenever (0.8.4, 0.8.2)
xpath (2.0.0)

Источник

em_larionov

0 / 0 / 0

Регистрация: 25.09.2012

Сообщений: 46

1

16.08.2014, 21:09. Показов 2065. Ответов 4

Метки нет (Все метки)

Здравствуйте, в логах ошибка «An error occurred while starting up the preloader: it did not write a startup response in time»

вот дидагер для этой проблемы https://github.com/phusion/pas… p-problems

но как его использовать не пойму, зупускаю

Bash 
1
2

bash -l -c '/path-to/SpawnPreparer /path-to-loader-or-preloader'
bash: /path-to/SpawnPreparer: No such file or directory

нашел SpawnPreparer запускаю

Bash 
1

/usr/local/lib/ruby/gems/1.9/gems/passenger-4.0.48/buildout/agents/SpawnPreparer /path-to-loader-or-preloader

получаю

Bash 
1

Too few arguments.

Может кто силен в этом вопросе и подскажет как подцепить этот дебагер.
Спасибо

__________________
Помощь в написании контрольных, курсовых и дипломных работ, диссертаций здесь



0

227 / 225 / 23

Регистрация: 30.01.2013

Сообщений: 720

17.08.2014, 12:05

2

а попробуйте само приложение запустить, может в нем самом ошибки, а не в Passenger



0

0 / 0 / 0

Регистрация: 25.09.2012

Сообщений: 46

17.08.2014, 12:27

 [ТС]

3

Уже методом втыка вычислил что ошибка в самом приложении я не ас в ruby а как приложение пускануть без Passenger-а ?



0

MpaKus

227 / 225 / 23

Регистрация: 30.01.2013

Сообщений: 720

17.08.2014, 12:41

4
Bash 
1

RAILS_ENV=production bundle exec rails console

— чтобы зайти и проверить в консоле

Bash 
1

RAILS_ENV=production bundle exec rails server

— чтобы запустить сервер и посмотреть логи, они будут обычно в log/production.log файле или прям в консоль вывалятся



1

0 / 0 / 0

Регистрация: 25.09.2012

Сообщений: 46

17.08.2014, 14:26

 [ТС]

5

Спасибо, не много не так сделал — но на путь ты меня направил у меня просто sinatra а не rails и в нем есть отладчик консольный



0
Источник

You are on this page means, there is not much information on Error ID – c51399ee on google. Hope this post on how to solve phusion passenger preloader error might save your day. Well the LoadError comes from a failure by Ruby to load the phusion passenger.so module.  

Contents

  • 1 The Secret of Error ID: c51399ee
  • 2 Lets Start Digging More
  • 3 Here is quick way to solve preloader error
    • 3.1 To install Phusion Passenger(R) against this specific Apache version:
    • 3.2 re-install phusion passenger
    • 3.3 Install nodejs to latest version
    • 3.4 Share this:
    • 3.5 Like this:
    • 3.6 Related

The Secret of Error ID: c51399ee

I am using – ruby 2.7.0p0 (2019-12-25 revision 647ee6f091) [aarch64-linux] , this issue appears on ARM – aarch64 based system and it works well with ruby 2.7.0p0 (2019-12-25 revision 647ee6f091) [x86_64-linux-gnu].

You can check apache error log from your /var/log/apach2 directory. 

$ tail -100 /var/log/apache2/error.log
App 2001 stderr: /usr/bin/passenger-config:27:in `require': cannot load such file -- phusion_passenger (LoadError)
App 2001 stderr:        from /usr/bin/passenger-config:27:in `<main>'
App 2001 stdout:
[ 2021-09-30 07:27:30.0924 1907/ffff957fa190 age/Cor/App/Implementation.cpp:304 ]: Could not spawn process for application /var/www/<app>/current: An error occurred while starting up the preloader.
Error ID: c51399ee
Error details saved to: /tmp/passenger-error-3xV1ZX.html
Cannot checkout session because a spawning error occurred. The identifier of the error is c51399ee. Please see earlier logs for details about the error.
App 2158 stdout:

Good thing is you do not have error like “stack smashing detected” yet.

Lets Start Digging More

Confirm which version of Passenger is currently installed. 

$ dpkg -l | grep passenger
ii  libapache2-mod-passenger          5.0.30-1+deb9u1build0.18.04.1       arm64        Rails and Rack support for Apache2
ii  passenger                         5.0.30-1+deb9u1build0.18.04.1       arm64        Rails and Rack support

Now confirm passenger installation path and number of installation on your system using following command

$ passenger-config validate-install
What would you like to validate?
Use <space> to select.
If the menu doesn't display correctly, press '!'
⬢  Passenger itself
‣ ⬡  Apache
-------------------------------------------------------------------------
* Checking whether this Passenger install is in PATH... (!)
Please add /home/ubuntu/.rvm/gems/ruby-2.7.0/gems/passenger-6.0.10/bin to PATH.
Otherwise you will get "command not found" errors upon running
any Passenger commands.
Learn more at about PATH at:
https://www.phusionpassenger.com/library/indepth/environment_variables.html#the-path-environment-variable
* Checking whether there are no other Passenger installations... (!)
You are currently validating against Phusion Passenger(R) 6.0.10, located in:
/home/ubuntu/.rvm/gems/ruby-2.7.0/gems/passenger-6.0.10/bin/passenger
Besides this Passenger installation, the following other
Passenger installations have also been detected:
/home/ubuntu/.rvm/gems/ruby-2.7.0/bin/passenger
/usr/local/bin/passenger
Please uninstall these other Passenger installations to avoid
confusion or conflicts.
Detected 0 error(s), 2 warning(s).

Though it gives warnings, you should correct the installation and use proper path.

If everything looks good then you should get following message

$ passenger-config validate-install
What would you like to validate?
Use <space> to select.
If the menu doesn't display correctly, press '!'
‣ ⬢  Passenger itself
⬡  Apache
-------------------------------------------------------------------------
* Checking whether this Passenger install is in PATH... ✓
* Checking whether there are no other Passenger installations... ✓
Everything looks good. :-)
What would you like to validate?
Use <space> to select.
If the menu doesn't display correctly, press '!'
⬢  Passenger itself
‣ ⬡  Apache
-------------------------------------------------------------------------
* Checking whether this Passenger install is in PATH... ✓
* Checking whether there are no other Passenger installations... ✓
Everything looks good. :-)
$ passenger-config list-instances
Name                       PID      Description
--------------------------------------------------------------------------
kWPoouHW                   12164    Apache/2.4.29 (Ubuntu) Phusion_Passenger/6.0.11

passenger-config list-instances will show you phusion passenger version along with PID.

install libpcre3-dev to check “passenger-config install-standalone-runtime” 

$sudo apt-get install libpcre3-dev

Here is quick way to solve preloader error

Following are quick fixes,

To install Phusion Passenger(R) against this specific Apache version:

/home/ubuntu/.rvm/gems/ruby-2.7.0/wrappers/ruby /home/ubuntu/.rvm/gems/ruby-2.7.0/gems/passenger-6.0.10/bin/passenger-install-apache2-module --apxs2-path='/usr/bin/apxs'

On ARM-arch64-linux system this issue happens to be there, but as per the online forum, it appears to happen on VM or docker. I am using AWS S2, so this issue should not have popped up. Are you also facing stack Smashed on AWS cloud server? If yes, do share your solution.

I was lucky to have development environment running on this server and it was easy for me to migrate from ARM – arch64 to x86_64. ARM support at the libv8-node repo is still under development and its recommended to manually cross compile to aarch64 on x86_64 [libv8-node host=x86_64/target=aarch64 ].

gem install libv8 host=x86_64/target=aarch64

Once this is done, verify if passenger is running. 

$ passenger-status
Version : 6.0.11
Date    : 2021-10-07 07:40:34 +0530
Instance: kWPoouHW (Apache/2.4.29 (Ubuntu) Phusion_Passenger/6.0.11)
----------- General information -----------
Max pool size : 4
App groups    : 1
Processes     : 2
Requests in top-level queue : 0
----------- Application groups -----------
/var/www/vtpbook/current (development):
App root: /var/www/vtpbook/current
Requests in queue: 0
* PID: 12423   Sessions: 0       Processed: 181     Uptime: 23h 43m 21s
CPU: 0%      Memory  : 386M    Last used: 57s ago
* PID: 12446   Sessions: 0       Processed: 1       Uptime: 23h 43m 20s
CPU: 0%      Memory  : 177M    Last used: 8h 8m 9

re-install phusion passenger

If you are not getting above output for passenger status, then uninstall passenger and re-install it. 

$ sudo apt-get remove -y passenger libapache2-mod-passenger
$ sudo apt-get remove libapache2-mod-passenger
$ gem install passenger --no-document
$ passenger-install-apache2-module

Install nodejs to latest version

This worked for me, as I was running older version of node 

$ node --version
v8.10.0

I had updated node and npm as follows. 

$ cd ~
$ curl -fsSL https://deb.nodesource.com/setup_16.x | sudo -E bash -
$ sudo apt-get install -y nodejs
$ node --version
v16.10.0
$ npm --version
7.24.0

Источник

Scott Sauber

Software Developer – Full Stack – ASP.NET Core, JavaScript, and DevOps

How to troubleshoot: “An error occurred while starting the application” in ASP.NET Core on IIS

The Problem

If you’ve ever seen this message when hitting your ASP.NET Core app:

“An error occurred while starting the application. .NET Framework | Microsoft.AspNetCore.Hosting version | Microsoft Windows ”

It looks a little something like this:

What Happened?

It basically means something really bad happened with your app. Some things that might have gone wrong:

  1. You might not have the correct .NET Core version installed on the server.
  2. You might be missing DLL’s
  3. Something went wrong in your Program.cs or Startup.cs before any exception handling kicked in

Event Viewer (probably) won’t show you anything

If you’re running on Windows and behind IIS, you might immediately go to the Event Viewer to see what happened based on your previous ASP.NET knowledge. You’ll notice that the error is not there. This is because Event Logging must be wired up explicitly and you’ll need to use the Microsoft.Extensions.Logging.EventLog package, and depending on the error, you might not have a chance to even catch it to log to the Event Viewer.

How to figure what happened (if running on IIS)

Instead of the Event Viewer, if you’re running behind IIS, we can log the request out to a file. To do that:

  1. Open your web.config
  2. Change stdoutLogEnabled=true
  3. Create a logs folder
    1. Unfortunately, the AspNetCoreModule doesn’t create the folder for you by default
      1. If you forget to create the logs folder, an error will be logged to the Event Viewer that says: Warning: Could not create stdoutLogFile \?YourPathlogsstdout_timestamp.log, ErrorCode = -2147024893.
    2. The “stdout” part of the value “.logsstdout” actually references the filename not the folder. Which is a bit confusing.
  4. Run your request again, then open the logsstdout_*.log file


Note – you will want to turn this off after you’re done troubleshooting, as it is a performance hit.

So your web.config’s aspNetCore element should look something like this

Doing this will log all the requests out to this file and when the exception occurs, it will give you the full stack trace of what happened in the logsstdout_*.log file

Hope this helps. This happened to me a friend of mine. A friend. Yep. Definitely not me. My apps would never bomb.

Источник

Redmine Web application could not be started (Raw process output: (empty)). Как исправить?

После очередного обновления на сервере перестал работать Redmine.
Какое обновление именно повлияло непонятно.
При попытке открыть страничку с Redmine вижу след-ее:

Web application could not be started
An error occurred while starting up the preloader. It exited before signalling successful startup back to Phusion Passenger. Please read this article for more information about this problem.
Raw process output:

(empty)
Error ID
90d30484

Error ID всегда разный.
Пробовал переставлять Ruby, Gems, сам Redmine, даже Apache и тот.
Толку 0.
Постоянно 1 и та же ошибка.

Если попытаться запустить без passenger (с помощью webrick), то вижу след-ее:

root@vld-bsd-1:/usr/local/www/redmine # bundle exec rails s -e production
=> Booting WEBrick
=> Rails 3.2.19 application starting in production on 0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server
Illegal instruction (core dumped)

Логи Apache и самого Redmine не блещут информативностью.
Куда копать?

  • Вопрос задан более трёх лет назад
  • 3514 просмотров

Глядел. И не только в него. Там только лишь записи о том что произошло подключение к БД.

В общем итог следующий. Я в очередной раз все удалил и переставил по новой. Заменил потом из бэкапа не всю папку с рэдмайном а только конфигурационные файлы и он заработал. Видимо что-то мешало в строй копии бэкапа.

Источник

An error occurred while starting up the preloader #1013

Comments

FooBarWidget commented May 29, 2014

What steps will reproduce the problem? Unknown, happens a few times a month. What is the expected output? What do you see instead? Successful spawn expected instead of failure. What version of Phusion Passenger are you using? Which version of Rails? On what operating system? * Passenger 4.0.1

  • Rails 3.2.11
  • Red Hat Enterprise Linux Server release 5.5 (Tikanga) Please provide any additional information below. Here is the error log. Let me know if there is additional debug information I should gather.

013-06-22 02:35:07.0246 7557/433d7940 Pool2/Spawner.h:739 ]: [App 4855 stdout]

[ 2013-06-22 02:36:36.9501 7557/433d7940 Pool2/Implementation.cpp:762 ]: Could not spawn process for group /var/www/railsapps/app567/current#default: An error occurred while starting up the preloader: it did not write a startup response in time.
in ‘void Passenger::ApplicationPool2::SmartSpawner::throwPreloaderSpawnException(const std::string&, Passenger::SpawnException::ErrorKind, boost::shared_ptrPassenger::ApplicationPool2::Spawner::BackgroundIOCapturer&, const boost::shared_ptrPassenger::ApplicationPool2::Spawner::DebugDir&)’ (SmartSpawner.h:149)
in ‘std::string Passenger::ApplicationPool2::SmartSpawner::negotiatePreloaderStartup(Passenger::ApplicationPool2::SmartSpawner::StartupDetails&)’ (SmartSpawner.h:557)
in ‘void Passenger::ApplicationPool2::SmartSpawner::startPreloader()’ (SmartSpawner.h:205)
in ‘virtual Passenger::ApplicationPool2::ProcessPtr Passenger::ApplicationPool2::SmartSpawner::spawn(const Passenger::ApplicationPool2::Options&)’ (SmartSpawner.h:743)
in ‘void Passenger::ApplicationPool2::Group::spawnThreadRealMain(const Passenger::ApplicationPool2::SpawnerPtr&, const Passenger::ApplicationPool2::Options&, unsigned int)’ (Implementation.cpp:695)

[ 2013-06-22 02:36:37.0711 7557/42e39940 agents/HelperAgent/RequestHandler.h:1888 ]: [Client 61] Cannot checkout session. An error occurred while starting up the preloader: it did not write a startup response in time.
Error page:

The text was updated successfully, but these errors were encountered:

FooBarWidget commented May 29, 2014

Even i am facing the same issue, please update if you have found the solution for this.
Thanks.

FooBarWidget commented May 29, 2014

From cacao.sunrise29 on July 03, 2013 11:17:39

I have the same issue, need a fix ! 🙂

[root@alarmpi logs]# tail -f error_log
[Wed Jul 03 17:12:26 2013] [notice] Apache/2.2.24 (Unix) mod_ssl/2.2.24 OpenSSL/1.0.1e DAV/2 Phusion_Passenger/4.0.5 configured — resuming normal operations
[ 2013-07-03 17:12:46.4255 26353/b5a5f450 Pool2/Spawner.h:739 ]: [App 26384 stdout]
[ 2013-07-03 17:14:16.4516 26353/b5a5f450 Pool2/Implementation.cpp:774 ]: Could not spawn process for group /srv/http/snorby#default: An error occurred while starting up the preloader : it did not write a startup response in time.
in ‘void Passenger::ApplicationPool2::SmartSpawner::throwPreloaderSpawnException(const string&, Passenger::SpawnException::ErrorKind, Passenger::ApplicationPool2::Spawner::Backgr oundIOCapturerPtr&, const DebugDirPtr&)’ (SmartSpawner.h:150)
in ‘std::string Passenger::ApplicationPool2::SmartSpawner::negotiatePreloaderStartup(Passenger::ApplicationPool2::SmartSpawner::StartupDetails&)’ (SmartSpawner.h:558)
in ‘void Passenger::ApplicationPool2::SmartSpawner::startPreloader()’ (SmartSpawner.h:206)
in ‘virtual Passenger::ApplicationPool2::ProcessPtr Passenger::ApplicationPool2::SmartSpawner::spawn(const Passenger::ApplicationPool2::Options&)’ (SmartSpawner.h:744)
in ‘void Passenger::ApplicationPool2::Group::spawnThreadRealMain(const SpawnerPtr&, const Passenger::ApplicationPool2::Options&, unsigned int)’ (Implementation.cpp:707)

[ 2013-07-03 17:14:16.4535 26353/b58ff450 agents/HelperAgent/RequestHandler.h:1885 ]: [Client 20] Cannot checkout session. An error occurred while starting up the preloader: it did no t write a startup response in time.

FooBarWidget commented May 29, 2014

From honglilai on July 04, 2013 14:42:10

Can you guys check for two things?

  1. Is there any code in the app which redirects STDOUT to a file?
  2. Is there any code in your bashrc or bash profile which may cause it to quit if there’s no terminal?

FooBarWidget commented May 29, 2014

I’ll dig into these questions next week. I’m out of the office this week.

FooBarWidget commented May 29, 2014

What steps will reproduce the problem?
Unknown, happens when I setup any new environment. But some how the older servers are ok.

What version of Phusion Passenger are you using? Which version of Rails? On
what operating system?

I searched with the STDOUT redirection. But there is nothing like so. Other servers like thin and puma is working fine.

FooBarWidget commented May 29, 2014

From omega842 on July 08, 2013 05:02:40

Same issue in my case but rails 4.0.0

What steps will reproduce the problem?
Starting passenger server on development mode.

What is the expected output? What do you see instead?
Successful spawn expected instead of failure.

What version of Phusion Passenger are you using? Which version of Rails? On
what operating system?

  • Passenger 4.0.7
  • Ruby ruby 2.0.0p250
  • Rails 4.0.0
  • Debian GNU/Linux 6.0.4 (squeeze)

Please provide any additional information below.

Источник

[restartedMain] ERROR o.s.boot.SpringApplication — Application startup failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name #11

Comments

liuduojia commented Apr 27, 2017

2017-04-27 12:35:38 [restartedMain] ERROR o.s.boot.SpringApplication — Application startup failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘flywayInitializer’ defined in class path resource [org/springframework/boot/autoconfigure/flyway/FlywayAutoConfiguration$FlywayConfiguration.class]: Invocation of init method failed; nested exception is org.flywaydb.core.api.FlywayException: Found non-empty schema excord without metadata table! Use baseline() or set baselineOnMigrate to true to initialize the metadata table.
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1578)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:545)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:482)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:296)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1054)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:829)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:538)
at org.springframework.boot.context.embedded.EmbeddedWebApplicationContext.refresh(EmbeddedWebApplicationContext.java:118)
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:766)
at org.springframework.boot.SpringApplication.createAndRefreshContext(SpringApplication.java:361)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:307)
at com.deem.excord.Main.main(Main.java:19)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.springframework.boot.devtools.restart.RestartLauncher.run(RestartLauncher.java:49)
Caused by: org.flywaydb.core.api.FlywayException: Found non-empty schema excord without metadata table! Use baseline() or set baselineOnMigrate to true to initialize the metadata table.
at org.flywaydb.core.Flyway$1.execute(Flyway.java:1035)
at org.flywaydb.core.Flyway$1.execute(Flyway.java:1006)
at org.flywaydb.core.Flyway.execute(Flyway.java:1418)
at org.flywaydb.core.Flyway.migrate(Flyway.java:1006)
at org.springframework.boot.autoconfigure.flyway.FlywayMigrationInitializer.afterPropertiesSet(FlywayMigrationInitializer.java:66)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1637)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1574)
. 21 common frames omitted
2017-04-27 12:35:38 [restartedMain] INFO o.s.b.l.ClasspathLoggingApplicationListener — Application failed to start with classpath: [file:/D:/git.jd/excord/target/classes/]

The text was updated successfully, but these errors were encountered:

gitorko commented Jul 7, 2017

Looks like issue with DB initialization. Were the setup steps followed correctly?

liuduojia commented Aug 17, 2017

shivanandacss commented Aug 17, 2017

@liuduojia Got stuck with the same error. Kindly let me know how u fixed it?

liuduojia commented Aug 24, 2017

nehadba commented Feb 7, 2018

How did u solve the issue I am also getting this error when running «mvn spring-boot:run» command from terminal

sorny commented Feb 7, 2018

@nehadba application.properties setup correctly and DB-init executed?

nehadba commented Feb 7, 2018

Can you provide an example of application.properties file and how to do DB-init?

sorny commented Feb 7, 2018

@nehadba See the README.md of this repo, DB-init is explained there.
Sample application.properties file: https://github.com/DeemOpen/excord/blob/master/application.properties

LuckyKidXiao commented Jan 11, 2019

Would you mind telling me how to solve this? I have met the same problem.

Источник

Источник

Я хочу установить redmine на свой компьютер. Я работал с учебниками из http://redmine.org/, чтобы развернуть redmine на моем ПК. После установки ruby, дополнительных пакетов и redmine, я хочу настроить apache2 для redmine. Но есть проблема после доступа к приложению:

Message from application: incompatible library version — /opt/redmine/.rvm/gems/ruby-2.3.3/gems/nokogiri-1.7.2/lib/nokogiri/nokogiri.so

Я установил ruby ​​on rails через rvm:

oleg@oleg-VirtualBox ~ $ ruby -v
ruby 2.3.1p112 (2016-04-26) [x86_64-linux-gnu]
oleg@oleg-VirtualBox ~ $ rails -v
Rails 4.2.8

установлен libapache2-mode-passenger с /etc/apache2/mods-available/passenger.conf config:

<IfModule mod_passenger.c>
PassengerUserSwitching on
PassengerUser redmine
PassengerGroup redmine
PassengerRoot /usr/lib/ruby/vendor_ruby/phusion_passenger/locations.ini
PassengerDefaultRuby /usr/bin/ruby
</IfModule>

и config для redmine:

<VirtualHost *:80>
DocumentRoot /var/www/html/redmine/
ServerName redmine.local

<Directory /var/www/html/redmine/>
PassengerResolveSymlinksInDocumentRoot on
AllowOverride all
Options -MultiViews
Options FollowSymLinks
RailsBaseURI /redmine
</Directory>
</VirtualHost>

Журнал ошибок Apache:

[ 2017-07-04 13:53:21.9413 1661/7f51d8495700 age/Cor/App/Implementation.cpp:304 ]: Could not spawn process for application /opt/redmine/redmine: An error occurred while starting up the preloader.
Error ID: 28c6ac21
Error details saved to: /tmp/passenger-error-GYyEzF.html
Message from application: incompatible library version - /opt/redmine/.rvm/gems/ruby-2.3.3/gems/nokogiri-1.7.2/lib/nokogiri/nokogiri.so (LoadError)
/opt/redmine/.rvm/gems/ruby-2.3.3/gems/nokogiri-1.7.2/lib/nokogiri.rb:32:in `require'
/opt/redmine/.rvm/gems/ruby-2.3.3/gems/nokogiri-1.7.2/lib/nokogiri.rb:32:in `rescue in <top (required)>'
/opt/redmine/.rvm/gems/ruby-2.3.3/gems/nokogiri-1.7.2/lib/nokogiri.rb:28:in `<top (required)>'
/opt/redmine/.rvm/gems/ruby-2.3.3/gems/roadie-3.2.2/lib/roadie/inliner.rb:2:in `require'
/opt/redmine/.rvm/gems/ruby-2.3.3/gems/roadie-3.2.2/lib/roadie/inliner.rb:2:in `<top (required)>'
/opt/redmine/.rvm/gems/ruby-2.3.3/gems/roadie-3.2.2/lib/roadie.rb:29:in `require'
/opt/redmine/.rvm/gems/ruby-2.3.3/gems/roadie-3.2.2/lib/roadie.rb:29:in `<top (required)>'
/opt/redmine/.rvm/gems/ruby-2.3.3/gems/roadie-rails-1.1.1/lib/roadie/rails.rb:6:in `require'
/opt/redmine/.rvm/gems/ruby-2.3.3/gems/roadie-rails-1.1.1/lib/roadie/rails.rb:6:in `<top (required)>'
/opt/redmine/.rvm/gems/ruby-2.3.3/gems/roadie-rails-1.1.1/lib/roadie-rails.rb:1:in `require'
/opt/redmine/.rvm/gems/ruby-2.3.3/gems/roadie-rails-1.1.1/lib/roadie-rails.rb:1:in `<top (required)>'
/opt/redmine/.rvm/gems/ruby-2.3.3/gems/bundler-1.15.1/lib/bundler/runtime.rb:82:in `require'
/opt/redmine/.rvm/gems/ruby-2.3.3/gems/bundler-1.15.1/lib/bundler/runtime.rb:82:in `block (2 levels) in require'
/opt/redmine/.rvm/gems/ruby-2.3.3/gems/bundler-1.15.1/lib/bundler/runtime.rb:77:in `each'
/opt/redmine/.rvm/gems/ruby-2.3.3/gems/bundler-1.15.1/lib/bundler/runtime.rb:77:in `block in require'
/opt/redmine/.rvm/gems/ruby-2.3.3/gems/bundler-1.15.1/lib/bundler/runtime.rb:66:in `each'
/opt/redmine/.rvm/gems/ruby-2.3.3/gems/bundler-1.15.1/lib/bundler/runtime.rb:66:in `require'
/opt/redmine/.rvm/gems/ruby-2.3.3/gems/bundler-1.15.1/lib/bundler.rb:108:in `require'
/opt/redmine/redmine-3.3.4/config/application.rb:5:in `<top (required)>'
/opt/redmine/redmine-3.3.4/config/environment.rb:2:in `require'
/opt/redmine/redmine-3.3.4/config/environment.rb:2:in `<top (required)>'
config.ru:3:in `require'
config.ru:3:in `block in <main>'
/opt/redmine/.rvm/gems/ruby-2.3.3/gems/rack-1.6.8/lib/rack/builder.rb:55:in `instance_eval'
/opt/redmine/.rvm/gems/ruby-2.3.3/gems/rack-1.6.8/lib/rack/builder.rb:55:in `initialize'
config.ru:1:in `new'
config.ru:1:in `<main>'
/usr/share/passenger/helper-scripts/rack-preloader.rb:110:in `eval'
/usr/share/passenger/helper-scripts/rack-preloader.rb:110:in `preload_app'
/usr/share/passenger/helper-scripts/rack-preloader.rb:156:in `<module:App>'
/usr/share/passenger/helper-scripts/rack-preloader.rb:30:in `<module:PhusionPassenger>'
/usr/share/passenger/helper-scripts/rack-preloader.rb:29:in `<main>'

[ 2017-07-04 13:53:21.9466 1661/7f51d3fff700 age/Cor/Con/CheckoutSession.cpp:285 ]: [Client 1-1] Cannot checkout session because a spawning error occurred. The identifier of the error is 28c6ac21. Please see earlier logs for details about the error.

Файл nokogiri.so присутствует в папке.

Если вы запускаете сервер rails, redmine запускается и работает хорошо.

Кто-нибудь знает, как исправить проблему?

задан
4 July 2017 в 14:10

поделиться

4 ответа

Я не вижу, какая версия Ruby запускается Passenger, но я подозрюю, что у вас есть конфликт между системой Ruby (v2.3.1) и RVM Ruby (v2.3.3).

Если вы смотрите на выход ruby -v, вы получаете ruby 2.3.1p112. Но файл журнала, который вы опубликовали, имеет следующий путь: …/.rvm/gems/ruby-2.3.3/. Поэтому я думаю, что запуск rails напрямую работает, потому что вы используете системные драгоценные камни, но когда вы запускаете Passenger, он использует систему Ruby (per PassengerDefaultRuby), но каким-то образом пытается загрузить несовместимые драгоценные камни. Я рекомендую отменить шаги и выбрать между системой Ruby и RVM. Если вы выполнили какое-либо руководство по установке, добавьте его в свой вопрос.

Если вы хотите использовать систему Ruby, попробуйте удалить /opt/rubymine/.rvm. Если у вас есть проблемы с зависимостями, вы можете установить их с помощью bundle install —deployment, поэтому он будет содержаться в каталоге Rubymine (см. Режим развертывания). Убедитесь, что учетная запись пользователя, под которой находится Пассажир, имеет доступ для чтения ко всем файлам в /opt/redmine.

В качестве альтернативы вы можете поручить Пассажиру использовать другой Ruby с Redmine с использованием опции конфигурации PasengerRuby, см. [D3] режим развертывания

ответ дан jnv
18 July 2018 в 10:44

поделиться

Считаете ли вы использование Docker? Я вижу, что вы запускаете виртуальную машину, и если вы можете рассмотреть Docker, я думаю, что вы могли бы очень выиграть.

Что такое docker

Docker — это ведущая в мире программная контейнерная платформа , Разработчики используют Docker для устранения проблем «работы на моей машине» при сотрудничестве с кодом с коллегами. Операторы используют Docker для запуска и управления приложениями бок о бок в изолированных контейнерах для повышения плотности вычислений. Предприятия используют Docker для создания гибких программных конвейеров для доставки новых функций быстрее, безопаснее и с уверенностью для приложений Linux и Windows Server.

Зачем вы его используете?

Кажется, что вам сложно войти, но это довольно просто, как только вы получите его. Это в основном дизайн зданий и архитектуры изображений / контейнеров и сервисов, которые трудно получить сразу, но если вы просто используете фондовые изображения, предоставленные сообществами вокруг Docker, вы можете получить довольно далеко.

Недавно я попробовал Redmine самостоятельно, используя только Docker, потому что легче поддерживать чистую ОС при возникновении таких проблем. Я запускаю Arch Linux на своих основных ноутбуках, и я часто сталкиваюсь с проблемами, когда старые версии выходят из строя и не доступны из AUR.

Идея состоит в том, что вы извлекаете AUR (или создаете свои собственные), настраиваете docker-compose.yml OR run two commands: сначала запустите свой SQL-сервер, в зависимости от того, быть, а другой — запустить сервер, на котором работает Redmine (docker run -d —name some-redmine redmine). Эти действия задокументированы на странице для изображения.

Следует обратить внимание на то, как вы обрабатываете постоянные данные, такие как база данных, которая зависит от вашей настройки. Я не уверен, где мои файлы настройки находятся в данный момент, но если я их найду, я добавлю их здесь.

ответ дан Simon
18 July 2018 в 10:44

поделиться

Я не вижу, какая версия Ruby запускается Passenger, но я подозрюю, что у вас есть конфликт между системой Ruby (v2.3.1) и RVM Ruby (v2.3.3).

Если вы смотрите на выход ruby -v, вы получаете ruby 2.3.1p112. Но файл журнала, который вы опубликовали, имеет следующий путь: …/.rvm/gems/ruby-2.3.3/. Поэтому я думаю, что запуск rails напрямую работает, потому что вы используете системные драгоценные камни, но когда вы запускаете Passenger, он использует систему Ruby (per PassengerDefaultRuby), но каким-то образом пытается загрузить несовместимые драгоценные камни. Я рекомендую отменить шаги и выбрать между системой Ruby и RVM. Если вы выполнили какое-либо руководство по установке, добавьте его в свой вопрос.

Если вы хотите использовать систему Ruby, попробуйте удалить /opt/rubymine/.rvm. Если у вас есть проблемы с зависимостями, вы можете установить их с помощью bundle install —deployment, поэтому он будет содержаться в каталоге Rubymine (см. Режим развертывания). Убедитесь, что учетная запись пользователя, под которой находится Пассажир, имеет доступ для чтения ко всем файлам в /opt/redmine.

В качестве альтернативы вы можете поручить Пассажиру использовать другой Ruby с Redmine с использованием опции конфигурации PasengerRuby, см. [D3] режим развертывания

ответ дан jnv
24 July 2018 в 19:38

поделиться

Считаете ли вы использование Docker? Я вижу, что вы запускаете виртуальную машину, и если вы можете рассмотреть Docker, я думаю, что вы могли бы очень выиграть.

Что такое docker

Docker — это ведущая в мире программная контейнерная платформа , Разработчики используют Docker для устранения проблем «работы на моей машине» при сотрудничестве с кодом с коллегами. Операторы используют Docker для запуска и управления приложениями бок о бок в изолированных контейнерах для повышения плотности вычислений. Предприятия используют Docker для создания гибких программных конвейеров для доставки новых функций быстрее, безопаснее и с уверенностью для приложений Linux и Windows Server.

Зачем вы его используете?

Кажется, что вам сложно войти, но это довольно просто, как только вы получите его. Это в основном дизайн зданий и архитектуры изображений / контейнеров и сервисов, которые трудно получить сразу, но если вы просто используете фондовые изображения, предоставленные сообществами вокруг Docker, вы можете получить довольно далеко.

Недавно я попробовал Redmine самостоятельно, используя только Docker, потому что легче поддерживать чистую ОС при возникновении таких проблем. Я запускаю Arch Linux на своих основных ноутбуках, и я часто сталкиваюсь с проблемами, когда старые версии выходят из строя и не доступны из AUR.

Идея состоит в том, что вы извлекаете AUR (или создаете свои собственные), настраиваете docker-compose.yml OR run two commands: сначала запустите свой SQL-сервер, в зависимости от того, быть, а другой — запустить сервер, на котором работает Redmine (docker run -d —name some-redmine redmine). Эти действия задокументированы на странице для изображения.

Следует обратить внимание на то, как вы обрабатываете постоянные данные, такие как база данных, которая зависит от вашей настройки. Я не уверен, где мои файлы настройки находятся в данный момент, но если я их найду, я добавлю их здесь.

ответ дан Simon
24 July 2018 в 19:38

поделиться

Другие вопросы по тегам:

Похожие вопросы:

Источник

Forums » Help »

Hi,

I’m having some problems with our Redmine installation and would greatly appreciate any help!

Symptoms¶

I recently updated Redmine to 3.2 from 3.1, which worked fine. However, when I did some server maintenance the other day I rebooted the server for the first time since the upgrade (I believe). It will now not start (preloader times out). I’m redirected to a Passenger error page, but it does not output any real error (the raw output is (empty)). The output in the Apache log is the following.

[ 2016-02-24 08:25:17.8434 6628/7efdf3c1e700 age/Cor/App/Implementation.cpp:304 ]: Could not spawn process for application /usr/share/redmine: An error occurred while starting up the preloader: it did not write a startup response in time.
  Error ID: 1e8099d5
  Error details saved to: /tmp/passenger-error-xkR3xU.html
  Message from application: An error occurred while starting up the preloader: it did not write a startup response in time. Please read <a href="https://github.com/phusion/passenger/wiki/Debugging-application-startup-problems">this article</a> for more information about this problem.<br>
<h2>Raw process output:</h2>
(empty)

[ 2016-02-24 08:25:17.8558 6628/7efdedc25700 age/Cor/Con/CheckoutSession.cpp:277 ]: [Client 1-1] Cannot checkout session because a spawning error occurred. The identifier of the error is 1e8099d5. Please see earlier logs for details about the error.
[ 2016-02-24 08:25:17.8558 6628/7efded424700 age/Cor/Con/CheckoutSession.cpp:277 ]: [Client 2-1] Cannot checkout session because a spawning error occurred. The identifier of the error is 1e8099d5. Please see earlier logs for details about the error.
App 7318 stdout:

The server works for the rest of what its being used for (Mercurial repository and file server).

Tested¶

I followed the Passenger debugging page, but either I didn’t understand it properly or those were not the issue.

I also tried hosting the pre-update instance of Redmine, which did not work either.

I have triple verified permissions (which I believe would have given an other error anyway).

Any help in debugging this would be greatly appreciated! I’m not very familiar with Ruby or Passenger, so I’m having a hard time finding what is actually causing it to not start up.

Info¶

I have attached the HTML page that is displayed, which contains most variables. The more general are listed here.

OS Ubuntu Server 14.04 LTS
Web  Apache2
Redmine 3.2
Ruby 1.9.1


RE: Redmine stopped working after updated and reboot
—
Added by Oscar Edvardsson almost 7 years ago

Thanks for your reply!

The production.log does not actually log any messages since the issue started to appear.

I didn’t know there was a WEBrick server — neat! Thanks.
However, I can’t make much sense of the output. I can not access the server on the specified IP and port. And it wonders if it is running on host «masked.com» with an IP that I bet is external. I would assume that port 5453 is blocked from outside, but I’m on the same (local) network. I do am running a DNS server as well on the server. I get the following. It takes quite a while before Exiting (and the rest) appears.

I’m using Postgresql and I can access the database from the terminal and it appears to contain all tables (55 or so of them).

sudo bin/rails server -e production -b 192.168.1.100
=> Booting WEBrick
=> Rails 4.2.3 application starting in production on http://192.168.1.100:3000
=> Run `rails server -h` for more startup options
=> Ctrl-C to shutdown server
Exiting
/var/lib/gems/1.9.1/gems/activerecord-4.2.3/lib/active_record/connection_adapters/postgresql_adapter.rb:655:in `initialize': could not connect to server: Connection timed out (PG::ConnectionBad)
    Is the server running on host "masked.com" (XX.XXX.XXX.XXX) and accepting
    TCP/IP connections on port 5432?
    from /var/lib/gems/1.9.1/gems/activerecord-4.2.3/lib/active_record/connection_adapters/postgresql_adapter.rb:655:in `new'
    from /var/lib/gems/1.9.1/gems/activerecord-4.2.3/lib/active_record/connection_adapters/postgresql_adapter.rb:655:in `connect'
    from /var/lib/gems/1.9.1/gems/activerecord-4.2.3/lib/active_record/connection_adapters/postgresql_adapter.rb:242:in `initialize'
    from /var/lib/gems/1.9.1/gems/activerecord-4.2.3/lib/active_record/connection_adapters/postgresql_adapter.rb:44:in `new'
    from /var/lib/gems/1.9.1/gems/activerecord-4.2.3/lib/active_record/connection_adapters/postgresql_adapter.rb:44:in `postgresql_connection'
    from /var/lib/gems/1.9.1/gems/activerecord-4.2.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:438:in `new_connection'
    from /var/lib/gems/1.9.1/gems/activerecord-4.2.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:448:in `checkout_new_connection'
    from /var/lib/gems/1.9.1/gems/activerecord-4.2.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:422:in `acquire_connection'
    from /var/lib/gems/1.9.1/gems/activerecord-4.2.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:349:in `block in checkout'
    from /usr/lib/ruby/1.9.1/monitor.rb:211:in `mon_synchronize'
    from /var/lib/gems/1.9.1/gems/activerecord-4.2.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:348:in `checkout'
    from /var/lib/gems/1.9.1/gems/activerecord-4.2.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:263:in `block in connection'
    from /usr/lib/ruby/1.9.1/monitor.rb:211:in `mon_synchronize'
    from /var/lib/gems/1.9.1/gems/activerecord-4.2.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:262:in `connection'
    from /var/lib/gems/1.9.1/gems/activerecord-4.2.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:571:in `retrieve_connection'
    from /var/lib/gems/1.9.1/gems/activerecord-4.2.3/lib/active_record/connection_handling.rb:113:in `retrieve_connection'
    from /var/lib/gems/1.9.1/gems/activerecord-4.2.3/lib/active_record/connection_handling.rb:87:in `connection'
    from /var/lib/gems/1.9.1/gems/activerecord-4.2.3/lib/active_record/model_schema.rb:230:in `table_exists?'
    from /var/lib/gems/1.9.1/gems/activerecord-4.2.3/lib/active_record/attribute_methods/primary_key.rb:97:in `get_primary_key'
    from /var/lib/gems/1.9.1/gems/activerecord-4.2.3/lib/active_record/attribute_methods/primary_key.rb:85:in `reset_primary_key'
    from /var/lib/gems/1.9.1/gems/activerecord-4.2.3/lib/active_record/attribute_methods/primary_key.rb:73:in `primary_key'
    from /var/lib/gems/1.9.1/gems/protected_attributes-1.1.3/lib/active_record/mass_assignment_security/attribute_assignment.rb:15:in `attributes_protected_by_default'
    from /var/lib/gems/1.9.1/gems/protected_attributes-1.1.3/lib/active_model/mass_assignment_security.rb:337:in `block in protected_attributes_configs'
    from /var/lib/gems/1.9.1/gems/protected_attributes-1.1.3/lib/active_model/mass_assignment_security.rb:222:in `yield'
    from /var/lib/gems/1.9.1/gems/protected_attributes-1.1.3/lib/active_model/mass_assignment_security.rb:222:in `default'
    from /var/lib/gems/1.9.1/gems/protected_attributes-1.1.3/lib/active_model/mass_assignment_security.rb:222:in `protected_attributes'
    from /var/lib/gems/1.9.1/gems/protected_attributes-1.1.3/lib/active_model/mass_assignment_security.rb:126:in `block in attr_protected'
    from /var/lib/gems/1.9.1/gems/protected_attributes-1.1.3/lib/active_model/mass_assignment_security.rb:125:in `each'
    from /var/lib/gems/1.9.1/gems/protected_attributes-1.1.3/lib/active_model/mass_assignment_security.rb:125:in `attr_protected'
    from /usr/share/redmine-3.1.0/app/models/custom_field.rb:32:in `<class:CustomField>'
    from /usr/share/redmine-3.1.0/app/models/custom_field.rb:18:in `<top (required)>'
    from /var/lib/gems/1.9.1/gems/activesupport-4.2.3/lib/active_support/dependencies.rb:274:in `require'
    from /var/lib/gems/1.9.1/gems/activesupport-4.2.3/lib/active_support/dependencies.rb:274:in `block in require'
    from /var/lib/gems/1.9.1/gems/activesupport-4.2.3/lib/active_support/dependencies.rb:240:in `load_dependency'
    from /var/lib/gems/1.9.1/gems/activesupport-4.2.3/lib/active_support/dependencies.rb:274:in `require'
    from /var/lib/gems/1.9.1/gems/activesupport-4.2.3/lib/active_support/dependencies.rb:360:in `require_or_load'
    from /var/lib/gems/1.9.1/gems/activesupport-4.2.3/lib/active_support/dependencies.rb:494:in `load_missing_constant'
    from /var/lib/gems/1.9.1/gems/activesupport-4.2.3/lib/active_support/dependencies.rb:184:in `const_missing'
    from /var/lib/gems/1.9.1/gems/activesupport-4.2.3/lib/active_support/dependencies.rb:526:in `load_missing_constant'
    from /var/lib/gems/1.9.1/gems/activesupport-4.2.3/lib/active_support/dependencies.rb:184:in `const_missing'
    from /var/lib/gems/1.9.1/gems/activesupport-4.2.3/lib/active_support/dependencies.rb:526:in `load_missing_constant'
    from /var/lib/gems/1.9.1/gems/activesupport-4.2.3/lib/active_support/dependencies.rb:184:in `const_missing'
    from /var/lib/gems/1.9.1/gems/activesupport-4.2.3/lib/active_support/dependencies.rb:526:in `load_missing_constant'
    from /var/lib/gems/1.9.1/gems/activesupport-4.2.3/lib/active_support/dependencies.rb:184:in `const_missing'
    from /usr/share/redmine-3.1.0/lib/redmine/field_format.rb:83:in `field_attributes'
    from /usr/share/redmine-3.1.0/lib/redmine/field_format.rb:86:in `<class:Base>'
    from /usr/share/redmine-3.1.0/lib/redmine/field_format.rb:48:in `<module:FieldFormat>'
    from /usr/share/redmine-3.1.0/lib/redmine/field_format.rb:19:in `<module:Redmine>'
    from /usr/share/redmine-3.1.0/lib/redmine/field_format.rb:18:in `<top (required)>'
    from /var/lib/gems/1.9.1/gems/activesupport-4.2.3/lib/active_support/dependencies.rb:274:in `require'
    from /var/lib/gems/1.9.1/gems/activesupport-4.2.3/lib/active_support/dependencies.rb:274:in `block in require'
    from /var/lib/gems/1.9.1/gems/activesupport-4.2.3/lib/active_support/dependencies.rb:240:in `load_dependency'
    from /var/lib/gems/1.9.1/gems/activesupport-4.2.3/lib/active_support/dependencies.rb:274:in `require'
    from /usr/share/redmine-3.1.0/lib/redmine.rb:38:in `<top (required)>'
    from /var/lib/gems/1.9.1/gems/activesupport-4.2.3/lib/active_support/dependencies.rb:274:in `require'
    from /var/lib/gems/1.9.1/gems/activesupport-4.2.3/lib/active_support/dependencies.rb:274:in `block in require'
    from /var/lib/gems/1.9.1/gems/activesupport-4.2.3/lib/active_support/dependencies.rb:240:in `load_dependency'
    from /var/lib/gems/1.9.1/gems/activesupport-4.2.3/lib/active_support/dependencies.rb:274:in `require'
    from /usr/share/redmine-3.1.0/config/initializers/30-redmine.rb:6:in `<top (required)>'
    from /var/lib/gems/1.9.1/gems/activesupport-4.2.3/lib/active_support/dependencies.rb:268:in `load'
    from /var/lib/gems/1.9.1/gems/activesupport-4.2.3/lib/active_support/dependencies.rb:268:in `block in load'
    from /var/lib/gems/1.9.1/gems/activesupport-4.2.3/lib/active_support/dependencies.rb:240:in `load_dependency'
    from /var/lib/gems/1.9.1/gems/activesupport-4.2.3/lib/active_support/dependencies.rb:268:in `load'
    from /var/lib/gems/1.9.1/gems/railties-4.2.3/lib/rails/engine.rb:652:in `block in load_config_initializer'
    from /var/lib/gems/1.9.1/gems/activesupport-4.2.3/lib/active_support/notifications.rb:166:in `instrument'
    from /var/lib/gems/1.9.1/gems/railties-4.2.3/lib/rails/engine.rb:651:in `load_config_initializer'
    from /var/lib/gems/1.9.1/gems/railties-4.2.3/lib/rails/engine.rb:616:in `block (2 levels) in <class:Engine>'
    from /var/lib/gems/1.9.1/gems/railties-4.2.3/lib/rails/engine.rb:615:in `each'
    from /var/lib/gems/1.9.1/gems/railties-4.2.3/lib/rails/engine.rb:615:in `block in <class:Engine>'
    from /var/lib/gems/1.9.1/gems/railties-4.2.3/lib/rails/initializable.rb:30:in `instance_exec'
    from /var/lib/gems/1.9.1/gems/railties-4.2.3/lib/rails/initializable.rb:30:in `run'
    from /var/lib/gems/1.9.1/gems/railties-4.2.3/lib/rails/initializable.rb:55:in `block in run_initializers'
    from /usr/lib/ruby/1.9.1/tsort.rb:150:in `block in tsort_each'
    from /usr/lib/ruby/1.9.1/tsort.rb:183:in `block (2 levels) in each_strongly_connected_component'
    from /usr/lib/ruby/1.9.1/tsort.rb:210:in `block (2 levels) in each_strongly_connected_component_from'
    from /usr/lib/ruby/1.9.1/tsort.rb:219:in `each_strongly_connected_component_from'
    from /usr/lib/ruby/1.9.1/tsort.rb:209:in `block in each_strongly_connected_component_from'
    from /var/lib/gems/1.9.1/gems/railties-4.2.3/lib/rails/initializable.rb:44:in `each'
    from /var/lib/gems/1.9.1/gems/railties-4.2.3/lib/rails/initializable.rb:44:in `tsort_each_child'
    from /usr/lib/ruby/1.9.1/tsort.rb:203:in `each_strongly_connected_component_from'
    from /usr/lib/ruby/1.9.1/tsort.rb:182:in `block in each_strongly_connected_component'
    from /usr/lib/ruby/1.9.1/tsort.rb:180:in `each'
    from /usr/lib/ruby/1.9.1/tsort.rb:180:in `each_strongly_connected_component'
    from /usr/lib/ruby/1.9.1/tsort.rb:148:in `tsort_each'
    from /var/lib/gems/1.9.1/gems/railties-4.2.3/lib/rails/initializable.rb:54:in `run_initializers'
    from /var/lib/gems/1.9.1/gems/railties-4.2.3/lib/rails/application.rb:352:in `initialize!'
    from /usr/share/redmine-3.1.0/config/environment.rb:14:in `<top (required)>'
    from /var/lib/gems/1.9.1/gems/activesupport-4.2.3/lib/active_support/dependencies.rb:274:in `require'
    from /var/lib/gems/1.9.1/gems/activesupport-4.2.3/lib/active_support/dependencies.rb:274:in `block in require'
    from /var/lib/gems/1.9.1/gems/activesupport-4.2.3/lib/active_support/dependencies.rb:240:in `load_dependency'
    from /var/lib/gems/1.9.1/gems/activesupport-4.2.3/lib/active_support/dependencies.rb:274:in `require'
    from /usr/share/redmine-3.1.0/config.ru:3:in `block in <main>'
    from /var/lib/gems/1.9.1/gems/rack-1.6.4/lib/rack/builder.rb:55:in `instance_eval'
    from /var/lib/gems/1.9.1/gems/rack-1.6.4/lib/rack/builder.rb:55:in `initialize'
    from /usr/share/redmine-3.1.0/config.ru:in `new'
    from /usr/share/redmine-3.1.0/config.ru:in `<main>'
    from /var/lib/gems/1.9.1/gems/rack-1.6.4/lib/rack/builder.rb:49:in `eval'
    from /var/lib/gems/1.9.1/gems/rack-1.6.4/lib/rack/builder.rb:49:in `new_from_string'
    from /var/lib/gems/1.9.1/gems/rack-1.6.4/lib/rack/builder.rb:40:in `parse_file'
    from /var/lib/gems/1.9.1/gems/rack-1.6.4/lib/rack/server.rb:299:in `build_app_and_options_from_config'
    from /var/lib/gems/1.9.1/gems/rack-1.6.4/lib/rack/server.rb:208:in `app'
    from /var/lib/gems/1.9.1/gems/railties-4.2.3/lib/rails/commands/server.rb:61:in `app'
    from /var/lib/gems/1.9.1/gems/rack-1.6.4/lib/rack/server.rb:336:in `wrapped_app'
    from /var/lib/gems/1.9.1/gems/rack-1.6.4/lib/rack/server.rb:272:in `start'
    from /var/lib/gems/1.9.1/gems/railties-4.2.3/lib/rails/commands/server.rb:80:in `start'
    from /var/lib/gems/1.9.1/gems/railties-4.2.3/lib/rails/commands/commands_tasks.rb:80:in `block in server'
    from /var/lib/gems/1.9.1/gems/railties-4.2.3/lib/rails/commands/commands_tasks.rb:75:in `tap'
    from /var/lib/gems/1.9.1/gems/railties-4.2.3/lib/rails/commands/commands_tasks.rb:75:in `server'
    from /var/lib/gems/1.9.1/gems/railties-4.2.3/lib/rails/commands/commands_tasks.rb:39:in `run_command!'
    from /var/lib/gems/1.9.1/gems/railties-4.2.3/lib/rails/commands.rb:17:in `<top (required)>'
    from bin/rails:4:in `require'
    from bin/rails:4:in `<main>'


RE: Redmine stopped working after updated and reboot
—
Added by Pavel Potcheptsov almost 7 years ago

So redmine and database are on different servers and you can connect to database but redmine host can’t.
Do you have a static IP configuration on redmine?
Maybe after reboot redmine got a new IP and there is restriction in database to accept specific user from specific IP for redmine database?
Try to telnet to host that specified in database.yml from redmine server:

telnet database_IP 5432

You can also might want to disable firewalls on redmine and on database hosts and maybe on gateways between them just for testing connectivity.


RE: Redmine stopped working after updated and reboot
—
Added by Oscar Edvardsson almost 7 years ago

Ah, its so obvious now.

The database actually runs on the same machine, but (I don’t really remember why) the database configuration was set to use masked.com, instead of localhost. For some reason, it would not resolve masked.com to the IP it was assigned to (not sure why though, since it works on all other machines on the network), but would try to reach a server outside of the network. That’s obviously a bad idea. Now I just need to figure out why the server don’t resolve the IP to itself. Man I’m dumb.

Sorry about that! A ton of thanks!

Источник

Понравилась статья? Поделить с друзьями:
  • An error occurred while gathering user information lenovo system update
  • An error occurred while fulfilling the request перевод
  • An error occurred while finding kernel data structures
  • An error occurred while fetching folder content
  • An error occurred while extracting files перевод