[closed] Redmine- Intermittent 503 service temporarily unavailable error/Thin services

Same error with the newest version...

Upgrading the ruby event machine gem to -v1.0.0.rc.4 resolved the 503 error for us in a Windows environment.

It is strange. The Thin log files are into the apps/redmine/htdocs/log folder. Could you try to start it manually instead of using the services?

Open the "Use Redmine" console from the shorcuts

> cd C:\\Program Files\\BitNami Redmine Stack\\apps\\redmine\\htdocs
> bundle exec thin start -e production -p 3001 --prefix /redmine

Check if you see any error in the output. Did you install any plugin?

Hi, we have updated the eventmachine gem to 1.0.0.rc.1 version for windows in a development version. This should fix the timeout issue. Could you help us testing this issue? You can download this Stack version at:

http://bitnami.org/files/download/bitnami-redmine-2.0.3-dev-windows-installer.exe

Please post if you find any issue or if that fixes the timeout issue.

Beltran, I'm also experiencing problems with this. I'm running the bitnami-redmine-2.0.3-dev2-windows-installer.exe version on a Windows Server 2008 R2. The Redmine instance hangs multiple times an hour, and we're just a few persons using it. Restarting the thin instances fixes the problem. The apache2 log file contains a lot of these lines

[Thu Jun 28 13:58:31 2012] [error] (OS 10061)No connection could be made because the target machine actively refused it. : proxy: HTTP: attempt to connect to 127.0.0.1:3002 (127.0.0.1) failed [Thu Jun 28 13:58:31 2012] [error] ap_proxy_connect_backend disabling worker for (127.0.0.1)

When the Redmine instance is non responsive, I can't manually connect to 127.0.0.1:3001/127.0.0.1:3002.

Here is what we are seeing:

We recently installed the Redmine 2.0.3-1 native setup on a machine, Windows 2008. This was actually an upgrade from redmine 1.0.1, but we did a fresh install, then moved over our DB and did the upgrade.

But daily, and non stop, we keep getting both:

• '503 Service Temporarily Unavailable - The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later'
• 'Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET /redmine/login. Reason: Error reading from remote server"

This has gotten very bad. It seems that if its not used for an hour, it does this.

Even though this is an upgrade, that was just our data. This upgrade made everything much slower, and we have these issues continuously.

Looking at production.log, I don't see any type of error. Basically I saw this:

Started GET "/redmine/issues/5390" for 127.0.0.1 at Thu Jun 28 09:18:11 -0400 2012
Processing by IssuesController#show as HTML
  Parameters: {"id"=>"5390"}
  Rendered issues/_action_menu.html.erb (93.8ms)
DEPRECATION WARNING: :confirm option is deprecated and will be removed from Rails 4.0. Use ':data => { :confirm => 'Text' }' instead. (called from _app_views_attachments__links_html_erb___701086988_56257836 at C:/Program Files/BitNami Redmine Stack/apps/redmine/htdocs/app/views/attachments/_links.html.erb:11)
  Rendered attachments/_links.html.erb (437.5ms)
  Rendered issue_relations/_form.html.erb (0.0ms)
  Rendered issues/_relations.html.erb (15.6ms)
  Rendered issues/_history.html.erb (93.8ms)
  Rendered issues/_action_menu.html.erb (0.0ms)
  Rendered issues/_form_custom_fields.html.erb (0.0ms)
  Rendered issues/_attributes.html.erb (343.8ms)
  Rendered issues/_form.html.erb (359.4ms)
  Rendered attachments/_form.html.erb (0.0ms)
  Rendered issues/_edit.html.erb (375.0ms)
  Rendered issues/_sidebar.html.erb (0.0ms)
  Rendered watchers/_watchers.html.erb (31.3ms)
  Rendered issues/show.html.erb within layouts/base (1421.9ms)
Completed 200 OK in 2125ms (Views: 984.4ms | ActiveRecord: 1015.7ms)
Connecting to database specified by database.yml
Connecting to database specified by database.yml
OpenIdAuthentication.store is nil. Using in-memory store.
OpenIdAuthentication.store is nil. Using in-memory store.
Creating scope :open. Overwriting existing method Version.open.
Creating scope :open. Overwriting existing method Version.open.
Creating scope :active. Overwriting existing method User.active.
Creating scope :active. Overwriting existing method User.active.
DEPRECATION WARNING: The InstanceMethods module inside ActiveSupport::Concern will be no longer included automatically. Please define instance methods directly in CollectiveIdea::Acts::NestedSet::Model instead. (called from include at C:/Program Files/BitNami Redmine Stack/apps/redmine/htdocs/lib/plugins/awesome_nested_set/lib/awesome_nested_set/awesome_nested_set.rb:58)
DEPRECATION WARNING: The InstanceMethods module inside ActiveSupport::Concern will be no longer included automatically. Please define instance methods directly in CollectiveIdea::Acts::NestedSet::Model instead. (called from include at C:/Program Files/BitNami Redmine Stack/apps/redmine/htdocs/lib/plugins/awesome_nested_set/lib/awesome_nested_set/awesome_nested_set.rb:58)
DEPRECATION WARNING: The InstanceMethods module inside ActiveSupport::Concern will be no longer included automatically. Please define instance methods directly in CollectiveIdea::Acts::NestedSet::Model instead. (called from include at C:/Program Files/BitNami Redmine Stack/apps/redmine/htdocs/lib/plugins/awesome_nested_set/lib/awesome_nested_set/awesome_nested_set.rb:58)
DEPRECATION WARNING: The InstanceMethods module inside ActiveSupport::Concern will be no longer included automatically. Please define instance methods directly in CollectiveIdea::Acts::NestedSet::Model instead. (called from include at C:/Program Files/BitNami Redmine Stack/apps/redmine/htdocs/lib/plugins/awesome_nested_set/lib/awesome_nested_set/awesome_nested_set.rb:58)
Creating scope :open. Overwriting existing method Issue.open.
Creating scope :open. Overwriting existing method Issue.open.

and then this:

Started GET "/redmine/" for 127.0.0.1 at Thu Jun 28 10:48:42 -0400 2012

Processing by WelcomeController#index as HTML Rendered welcome/index.html.erb within layouts/base (2484.4ms) Completed 200 OK in 4359ms (Views: 3000.0ms | ActiveRecord: 890.6ms)

Looking in access.log, around this time, we are getting a lot of 502 errors.

And then in error.log, we see this:

Thu Jun 28 10:34:52 2012] [error] (OS 10061)No connection could be made because the target machine actively refused it.  : proxy: HTTP: attempt to connect to 127.0.0.1:3002 (127.0.0.1) failed
[Thu Jun 28 10:34:52 2012] [error] ap_proxy_connect_backend disabling worker for (127.0.0.1)
[Thu Jun 28 10:39:23 2012] [error] [client 10.7.5.2] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : proxy: error reading status line from remote server 127.0.0.1:3001
[Thu Jun 28 10:39:23 2012] [error] [client 10.7.5.2] proxy: Error reading from remote server returned by /redmine/

It looks like thin keeps dying, but why? Nothing is changing on the server - no user is going in and turning a service off. But after an hour or so, it just falls over, and then causes some issues for usage. Do we really have to poke it every hour to keep it awake?

To start, by reading some of the other issues similar, I decided to tell the thin services to start automatically again if they fail, but we really want to track down the issue.

We have just released a new version of BitNami Redmine 2.0 and 1.4 with the latest eventmachine gem 1.0.0.rc.4. We have tested on several Windows versions. Could you try this new version and post if you find any issue?

http://bitnami.org/files/stacks/redmine/2.0.3-1/bitnami-redmine-2.0.3-1-windows-installer-r01.exe

Unfortunately, the problem remains on latest release. I'm using:

• bitnami-redmine-2.1.2-1-module on Bitnami-RubyStack-1.8.7-0
• Windows 2008 Server R2 (x64) Standard.

htdocs\\log\\production.log shows nothing about the crash. However, Windows Event Viewer shows

Faulting application name: ruby.exe, version: 1.8.7.370 Faulting module name: msvcrt-ruby18.dll, version: 1.8.7.370 Exception code: 0x40000015

which, of course, isn't very helpful.

"gem q" reports "eventmachine (1.0.0.rc.4 x86-mingw32)" installed

Running the service from command-line (with the following command, extracted from \apps\redmine\scripts\serviceinstall.bat)

"D:\Bitnami-RubyStack-1.8.7-0\ruby\bin\ruby.exe" "D:\Bitnami-RubyStack-1.8.7-0/apps/redmine\htdocs\bin\thin" start -p 3001 -e production -c "D:\Bitnami-RubyStack-1.8.7-0/apps/redmine/htdocs" --prefix /redmine

shows me the following error (on a popup window) several times

"The procedure entry point svn_mergeinfor__remove2 could not be located in the dynamic link library libsvn_subr-1.dll"

but I just click on "Ok" and the server keeps running.

Maybe this is what's causing the crash? Anyone knows how I could fix this error? Maybe some gem update?