Skip to content
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

Fire.app won't launch after changing webserver port #14

Closed
VinSpee opened this issue May 3, 2012 · 2 comments
Closed

Fire.app won't launch after changing webserver port #14

VinSpee opened this issue May 3, 2012 · 2 comments

Comments

@VinSpee
Copy link

VinSpee commented May 3, 2012

I've been using fire.app (precompiled, purchased) successfully for the last week. I changed my webserver port number, now it won't run. I see the "Loading Modules" dialog, but after that appears to complete, the app crashes.

Any Ideas?

log:

5/3/12 9:09:39.658 AM   com.apple.launchd.peruser.2078700921    ([0x0-0x7b07b].Fire[8234]) Tried to setup shared memory more than once
5/3/12 9:09:45.206 AM   [0x0-0x7b07b].Fire  [LaunchRunner Error] org.rubyforge.rawr.Main.main(String[]) threw an exception:
5/3/12 9:09:45.209 AM   [0x0-0x7b07b].Fire  org.jruby.exceptions.RaiseException: (NoMethodError) undefined method `[]' for false:FalseClass
5/3/12 9:09:45.210 AM   [0x0-0x7b07b].Fire      at app.get_config(src/app.rb:61)
5/3/12 9:09:45.210 AM   [0x0-0x7b07b].Fire      at app.App(src/app.rb:85)
5/3/12 9:09:45.210 AM   [0x0-0x7b07b].Fire      at app.(root)(src/app.rb:3)
5/3/12 9:09:45.210 AM   [0x0-0x7b07b].Fire      at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:1033)
5/3/12 9:09:45.210 AM   [0x0-0x7b07b].Fire      at require_patch.require(src/require_patch.rb:6)
5/3/12 9:09:45.210 AM   [0x0-0x7b07b].Fire      at main.(root)(src/main.rb:26)
5/3/12 9:09:45.210 AM   [0x0-0x7b07b].Fire      at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:1033)
5/3/12 9:09:45.210 AM   [0x0-0x7b07b].Fire      at (Anonymous).(root)(<script>:1)
@VinSpee
Copy link
Author

VinSpee commented May 3, 2012

The issue was with the ~/.fire-app/config file. It was somehow blank. Deleting the file caused it to be regenerated with defaults.

I think it may have something to do with changing the port while the webserver is still enabled?

@hlb
Copy link
Contributor

hlb commented Jun 22, 2012

We have better error handing for these text fields now.

@hlb hlb closed this as completed Jun 22, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants