Project

General

Profile

Bug #1318

Application Error: Rails application failed to start properly

Added by dcshoes23 over 6 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
03/05/2014
Due date:
% Done:

0%


Description

All of a sudden, when trying to access the dashboard, an error is displayed:

/var/log/httpd/error_log contains the following error:
[Wed Mar 05 15:48:47.836019 2014] [passenger:error] [pid 19286] *** Passenger could not be initialized because of this error: Unable to start the Phusion Passenger watchdog because its executable (/usr/share/gems/gems/passenger-4.0.18/buildout/agents/PassengerWatchdog) does not exist. This probably means that your Phusion Passenger installation is broken or incomplete, or that your 'PassengerRoot' directive is set to the wrong value. Please reinstall Phusion Passenger or fix your 'PassengerRoot' directive, whichever is applicable.

The directory "/usr/share/gems/gems/passenger-4.0.18/" exists, the subdirectory "buildout" does not.

/var/log/messages shows the following each time you try to access the dashboard:
Mar 5 15:51:56 localhost avahi-daemon337: Invalid response packet from host 192.168.0.4.

Platform version info:
[root@localhost ~]# yum info hda-ctl hda-platform
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile * fedora: less.cogeco.net * rpmfusion-free: mirror.us.leaseweb.net * rpmfusion-free-updates: mirror.us.leaseweb.net * rpmfusion-nonfree: mirror.us.leaseweb.net * rpmfusion-nonfree-updates: mirror.us.leaseweb.net * updates: less.cogeco.net
Installed Packages
Name : hda-ctl
Arch : x86_64
Version : 5.1.4
Release : 1
Size : 306 k
Repo : installed
From repo : amahi
Summary : hda-ctl is the Amahi HDA daemon.
License : GPL
Description : hda-ctl is the Amahi HDA daemon process.

Name : hda-platform
Arch : x86_64
Version : 7.1.1
Release : 1
Size : 84 M
Repo : installed
From repo : amahi
Summary : hda-platform is the Amahi web interface platform.
License : AGPL
Description : hda-platform is the Amahi web platform.


Other info:
This may have started after doing a "yum update"

History

#1 Updated by bigfoot65 over 6 years ago

  • Assignee set to dcshoes23

Is this still a problem?

#2 Updated by bigfoot65 over 6 years ago

  • Status changed from New to Feedback

#3 Updated by dcshoes23 over 6 years ago

bigfoot65 wrote:

Is this still a problem?

Yes, I still have this issue.

#4 Updated by cpg over 6 years ago

  • Assignee changed from dcshoes23 to cpg

#5 Updated by bigfoot65 over 6 years ago

  • Assignee changed from cpg to dcshoes23
  • Target version set to amahi-7-2

Please try the following as root user:

yum clean all
yum update hda-platform

Reboot the server and verify if the dashboard issue is resolved.

#6 Updated by dcshoes23 over 6 years ago

I have performed the steps that you have provided and still have the issue.

#7 Updated by cpg over 6 years ago

your installation is corrupted somehow. you did not say how this started to happen. or how long the machine was on and operating before this happened. or if there was a power failure. or if the root directory fill up.

let's start at the top: how exacly did you install your amahi system?

#8 Updated by bigfoot65 over 6 years ago

You indicated this happened when you did yum update. Are you running Fedora 19?

Please provide the output of this command:
cat /etc/fedora-release

#9 Updated by dcshoes23 over 6 years ago

I have Fedora 19

I noticed the following in the /var/hda/platform/logs/error_log whenever I try to access the dashboard:

[Tue Apr 01 16:19:17.426069 2014] [core:error] [pid 15631] [client 192.168.0.5:29163] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.

How do I set 'LogLevel debug'?

I set the LogLevel to debug and this is what I see now in error_log:

[Tue Apr 01 16:35:29.026124 2014] [authz_core:debug] [pid 13756] mod_authz_core.c(802): [client 192.168.0.5:29396] AH01626: authorization result of Require all granted: granted
[Tue Apr 01 16:35:29.026218 2014] [authz_core:debug] [pid 13756] mod_authz_core.c(802): [client 192.168.0.5:29396] AH01626: authorization result of <RequireAny>: granted
[Tue Apr 01 16:35:29.026324 2014] [authz_core:debug] [pid 13756] mod_authz_core.c(802): [client 192.168.0.5:29396] AH01626: authorization result of Require all granted: granted
[Tue Apr 01 16:35:29.026337 2014] [authz_core:debug] [pid 13756] mod_authz_core.c(802): [client 192.168.0.5:29396] AH01626: authorization result of <RequireAny>: granted
[Tue Apr 01 16:35:29.026399 2014] [authz_core:debug] [pid 13756] mod_authz_core.c(802): [client 192.168.0.5:29396] AH01626: authorization result of Require all granted: granted
[Tue Apr 01 16:35:29.026408 2014] [authz_core:debug] [pid 13756] mod_authz_core.c(802): [client 192.168.0.5:29396] AH01626: authorization result of <RequireAny>: granted
[Tue Apr 01 16:35:29.026489 2014] [authz_core:debug] [pid 13756] mod_authz_core.c(802): [client 192.168.0.5:29396] AH01626: authorization result of Require all granted: granted
[Tue Apr 01 16:35:29.026498 2014] [authz_core:debug] [pid 13756] mod_authz_core.c(802): [client 192.168.0.5:29396] AH01626: authorization result of <RequireAny>: granted
[Tue Apr 01 16:35:29.026556 2014] [authz_core:debug] [pid 13756] mod_authz_core.c(802): [client 192.168.0.5:29396] AH01626: authorization result of Require all granted: granted
[Tue Apr 01 16:35:29.026564 2014] [authz_core:debug] [pid 13756] mod_authz_core.c(802): [client 192.168.0.5:29396] AH01626: authorization result of <RequireAny>: granted
[Tue Apr 01 16:35:29.026626 2014] [authz_core:debug] [pid 13756] mod_authz_core.c(802): [client 192.168.0.5:29396] AH01626: authorization result of Require all granted: granted
[Tue Apr 01 16:35:29.026635 2014] [authz_core:debug] [pid 13756] mod_authz_core.c(802): [client 192.168.0.5:29396] AH01626: authorization result of <RequireAny>: granted
[Tue Apr 01 16:35:29.026698 2014] [authz_core:debug] [pid 13756] mod_authz_core.c(802): [client 192.168.0.5:29396] AH01626: authorization result of Require all granted: granted
[Tue Apr 01 16:35:29.026706 2014] [authz_core:debug] [pid 13756] mod_authz_core.c(802): [client 192.168.0.5:29396] AH01626: authorization result of <RequireAny>: granted
[Tue Apr 01 16:35:29.026774 2014] [authz_core:debug] [pid 13756] mod_authz_core.c(802): [client 192.168.0.5:29396] AH01626: authorization result of Require all granted: granted
[Tue Apr 01 16:35:29.026783 2014] [authz_core:debug] [pid 13756] mod_authz_core.c(802): [client 192.168.0.5:29396] AH01626: authorization result of <RequireAny>: granted
[Tue Apr 01 16:35:29.026853 2014] [authz_core:debug] [pid 13756] mod_authz_core.c(802): [client 192.168.0.5:29396] AH01626: authorization result of Require all granted: granted
[Tue Apr 01 16:35:29.026862 2014] [authz_core:debug] [pid 13756] mod_authz_core.c(802): [client 192.168.0.5:29396] AH01626: authorization result of <RequireAny>: granted
[Tue Apr 01 16:35:29.026942 2014] [authz_core:debug] [pid 13756] mod_authz_core.c(802): [client 192.168.0.5:29396] AH01626: authorization result of Require all granted: granted
[Tue Apr 01 16:35:29.026953 2014] [authz_core:debug] [pid 13756] mod_authz_core.c(802): [client 192.168.0.5:29396] AH01626: authorization result of <RequireAny>: granted
[Tue Apr 01 16:35:29.027032 2014] [authz_core:debug] [pid 13756] mod_authz_core.c(802): [client 192.168.0.5:29396] AH01626: authorization result of Require all granted: granted
[Tue Apr 01 16:35:29.027040 2014] [authz_core:debug] [pid 13756] mod_authz_core.c(802): [client 192.168.0.5:29396] AH01626: authorization result of <RequireAny>: granted
[Tue Apr 01 16:35:29.027128 2014] [authz_core:debug] [pid 13756] mod_authz_core.c(802): [client 192.168.0.5:29396] AH01626: authorization result of Require all granted: granted
[Tue Apr 01 16:35:29.027143 2014] [authz_core:debug] [pid 13756] mod_authz_core.c(802): [client 192.168.0.5:29396] AH01626: authorization result of <RequireAny>: granted
[Tue Apr 01 16:35:29.027257 2014] [authz_core:debug] [pid 13756] mod_authz_core.c(802): [client 192.168.0.5:29396] AH01626: authorization result of Require all granted: granted
[Tue Apr 01 16:35:29.027267 2014] [authz_core:debug] [pid 13756] mod_authz_core.c(802): [client 192.168.0.5:29396] AH01626: authorization result of <RequireAny>: granted
[Tue Apr 01 16:35:29.027287 2014] [core:error] [pid 13756] [client 192.168.0.5:29396] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
[Tue Apr 01 16:35:29.027299 2014] [core:debug] [pid 13756] core.c(3517): [client 192.168.0.5:29396] AH00121: r->uri = /dispatch.fcgi
[Tue Apr 01 16:35:29.027306 2014] [core:debug] [pid 13756] core.c(3524): [client 192.168.0.5:29396] AH00122: redirected from r->uri = /dispatch.fcgi
[Tue Apr 01 16:35:29.027314 2014] [core:debug] [pid 13756] core.c(3524): [client 192.168.0.5:29396] AH00122: redirected from r->uri = /dispatch.fcgi
[Tue Apr 01 16:35:29.027320 2014] [core:debug] [pid 13756] core.c(3524): [client 192.168.0.5:29396] AH00122: redirected from r->uri = /dispatch.fcgi
[Tue Apr 01 16:35:29.027325 2014] [core:debug] [pid 13756] core.c(3524): [client 192.168.0.5:29396] AH00122: redirected from r->uri = /dispatch.fcgi
[Tue Apr 01 16:35:29.027330 2014] [core:debug] [pid 13756] core.c(3524): [client 192.168.0.5:29396] AH00122: redirected from r->uri = /dispatch.fcgi
[Tue Apr 01 16:35:29.027336 2014] [core:debug] [pid 13756] core.c(3524): [client 192.168.0.5:29396] AH00122: redirected from r->uri = /dispatch.fcgi
[Tue Apr 01 16:35:29.027341 2014] [core:debug] [pid 13756] core.c(3524): [client 192.168.0.5:29396] AH00122: redirected from r->uri = /dispatch.fcgi
[Tue Apr 01 16:35:29.027346 2014] [core:debug] [pid 13756] core.c(3524): [client 192.168.0.5:29396] AH00122: redirected from r->uri = /dispatch.fcgi
[Tue Apr 01 16:35:29.027352 2014] [core:debug] [pid 13756] core.c(3524): [client 192.168.0.5:29396] AH00122: redirected from r->uri = /dispatch.fcgi
[Tue Apr 01 16:35:29.027357 2014] [core:debug] [pid 13756] core.c(3524): [client 192.168.0.5:29396] AH00122: redirected from r->uri = /

#10 Updated by bigfoot65 over 6 years ago

Please post the result of this command as root user:
yum list rubygem-passenger

#11 Updated by dcshoes23 over 6 years ago

rubygem-passenger.x86_64          4.0.18-2.fc19          @repos.fedorapeople.org_repos_axilleas_gitlab_fedora-19_x86_64_

Now that I think about it, I may have messed up my ruby installation while trying to get another ruby app to work.

#12 Updated by bigfoot65 over 6 years ago

I would say that's the issue. There is no rubygem-passenger in the Fedora stable repo with that version.

You can try downgrading the package, but you will most likely have to reinstall. Not much we can do to help you here.

#13 Updated by cpg over 6 years ago

  • Status changed from Feedback to Closed

gitlab can be installed with the current existing ruby in amahi 7.1 but it's not an easy app to deploy.

closing as user error.

#14 Updated by dcshoes23 over 6 years ago

Fixed with "yum downgrade rubygem-passenger* mod_passenger*"

Thanks everyone for your help!

Also available in: Atom