Is there another log I should be checking? or are my fastcgi.crash.log settings not verbose enough
Log locations?
- Milmarn
- Posts: 4
- Starts: 2
- Wiki Edits: 0
I'm getting the "Application Error - Rails application failed to start properly" message. I know exactly what is causing it, I'm just having trouble diagnosing why. Obviously, nothing is in production.log since the application doesn't start. There's nothing useful in fastcgi.crash.log.
Is there another log I should be checking? or are my fastcgi.crash.log settings not verbose enough
Is there another log I should be checking? or are my fastcgi.crash.log settings not verbose enough
- Varun
- Posts: 410
- Starts: 0
- Wiki Edits: 0
Hi Milmarn,
Looking into Apache logs would make you wiser. You can view up to the last 300 error log Apache error log entries for your site in the "Error Log" section of your cPanel control panel. If that didn't make more sense, please contact support with the URL where you see this error when accessing.
Looking into Apache logs would make you wiser. You can view up to the last 300 error log Apache error log entries for your site in the "Error Log" section of your cPanel control panel. If that didn't make more sense, please contact support with the URL where you see this error when accessing.
2007-10-14 11:30 PM
- Milmarn
- Posts: 4
- Starts: 2
- Wiki Edits: 0
That log doesn't contain any useful information. All it contains is stuff like
[03/Oct/2007:23:50:22 :: 8204] starting
[03/Oct/2007:23:55:59 :: 8178] asked to terminate immediately
[03/Oct/2007:23:55:59 :: 8178] terminated by explicit exit
[04/Oct/2007:00:03:38 :: 29777] asked to terminate immediately
And is exactly the same as the afore mentioned fastcgi.crash.log
[03/Oct/2007:23:50:22 :: 8204] starting
[03/Oct/2007:23:55:59 :: 8178] asked to terminate immediately
[03/Oct/2007:23:55:59 :: 8178] terminated by explicit exit
[04/Oct/2007:00:03:38 :: 29777] asked to terminate immediately
And is exactly the same as the afore mentioned fastcgi.crash.log
2007-10-15 11:50 AM
- Rahul
- Posts: 496
- Starts: 0
- Wiki Edits: 1
Hello,
Can you check it out now. Also can you confirm us the URL that you are testing to check and confirm the issue from our end.
Can you check it out now. Also can you confirm us the URL that you are testing to check and confirm the issue from our end.
2007-10-15 02:04 PM
Regards,Rahul
- Milmarn
- Posts: 4
- Starts: 2
- Wiki Edits: 0
Still not very useful. I have deployed the code that breaks my app. The problem is exception notifier. Adding this line to production.rb causes the app not to start
ExceptionNotifier.exception_recipients = %w(myemail@somehwere.com)
[Mon Oct 15 21:08:13 2007] [notice] mod_fcgid: process /home/***/public_html/dispatch.fcgi(2091) exit(communication error), terminated by calling exit(), return code: 1
[Mon Oct 15 21:08:07 2007] [info] mod_fcgid: server /home/***/public_html/dispatch.fcgi(2091) started
[Mon Oct 15 20:22:05 2007] [info] mod_fcgid: server /home/***/public_html/dispatch.fcgi(27260) started
[Mon Oct 15 19:27:58 2007] [notice] mod_fcgid: process /home/***/public_html/dispatch.fcgi(1848) exit(shutting down), get stop signal 9
ExceptionNotifier.exception_recipients = %w(myemail@somehwere.com)
[Mon Oct 15 21:08:13 2007] [notice] mod_fcgid: process /home/***/public_html/dispatch.fcgi(2091) exit(communication error), terminated by calling exit(), return code: 1
[Mon Oct 15 21:08:07 2007] [info] mod_fcgid: server /home/***/public_html/dispatch.fcgi(2091) started
[Mon Oct 15 20:22:05 2007] [info] mod_fcgid: server /home/***/public_html/dispatch.fcgi(27260) started
[Mon Oct 15 19:27:58 2007] [notice] mod_fcgid: process /home/***/public_html/dispatch.fcgi(1848) exit(shutting down), get stop signal 9
2007-10-15 09:12 PM
- Varun
- Posts: 410
- Starts: 0
- Wiki Edits: 0
Milmarn -
Could you try adding the lines below to your environment.rb instead of the setting in production.rb
========
ExceptionNotifier.exception_recipients = %w(your@emailaddress.com)
=======
You need to pkill your dispatch.fcgi process after making changes in your environment.rb and production.rb
You may also take a look at the link below for more information regarding this.
http://soakedandsoaped.com/articles/read/exception-notifier-ruby-on-rails-plugin
Could you try adding the lines below to your environment.rb instead of the setting in production.rb
========
ExceptionNotifier.exception_recipients = %w(your@emailaddress.com)
=======
You need to pkill your dispatch.fcgi process after making changes in your environment.rb and production.rb
You may also take a look at the link below for more information regarding this.
http://soakedandsoaped.com/articles/read/exception-notifier-ruby-on-rails-plugin
2007-10-16 04:50 AM
- Milmarn
- Posts: 4
- Starts: 2
- Wiki Edits: 0
forgive me, I'm not too savvy. Where does this line go: before, in, or after the Rails::Initializer.run block? The server will only start if it goes after the block, but it doesn't seem to be working
2007-10-16 08:33 PM
- Milmarn
- Posts: 4
- Starts: 2
- Wiki Edits: 0
forgive me again, its working. consider the issue closed
2007-10-16 11:16 PM
- Grains
- Posts: 3
- Starts: 2
- Wiki Edits: 0
- Location: Chelmsford, MA
I'm having the same problem as above - I get an application error when I have the line
========
ExceptionNotifier.exception_recipients = %w(your@emailaddress.com)
=======
in my environment.rb file, but not when it isn't there. However, I don't get the emails that I need without that line in the file.
========
ExceptionNotifier.exception_recipients = %w(your@emailaddress.com)
=======
in my environment.rb file, but not when it isn't there. However, I don't get the emails that I need without that line in the file.
2008-01-26 07:08 PM
- Rahul
- Posts: 496
- Starts: 0
- Wiki Edits: 1
Have you tried the turn round which is mentioned above? If the problem still persists, please contact the support team with the required details. So that we can look into it.
2008-01-26 11:09 PM
Regards,Rahul