Kernel Panic on foreman start? #73
Comments
|
This should be fixed in foreman 0.22.0 (latest). Are you still seeing it? |
|
I also experience a kernel panic when I start up Foreman (0.22.0). Crash report: Procfile: I also had Spork and Guard initializers in the Procfile but I removed them because I thought they were the trouble makers, but even with only Resque, it still crashes. I don't know if it could have something to do with Mac OS X Lion? - I'm running 10.7.1 (11B26) |
|
I also experience kernel panic when I start up Foreman 0.22.0. I'm running Mac OS X Lion 10.7.1 too. My Procfile: With Foreman 0.20.0 I received SIGTERM to all process: 14:59:20 rake.1 | process terminated 14:59:20 system | sending SIGTERM to all processes 14:59:20 redis.1 | [1347] 28 Sep 14:59:20 # Received SIGTERM, scheduling shutdown... 14:59:20 redis.1 | [1347] 28 Sep 14:59:20 # User requested shutdown... 14:59:20 redis.1 | [1347] 28 Sep 14:59:20 * Saving the final RDB snapshot before exiting. 14:59:20 redis.1 | [1347] 28 Sep 14:59:20 * DB saved on disk 14:59:20 redis.1 | [1347] 28 Sep 14:59:20 # Redis is now ready to exit, bye bye... |
|
My Procfile format was deprecated: redis: redis-server Last line doesn't have a name and a colon. I fix it and foreman is working fine. But... Kernel Panic because Procfile? |
|
Could anyone else getting kernel panics try updating to the latest version of foreman and pasting your Procfile here? |
|
My Procfile with error was: I fix it with: Foreman 0.22.0 is working fine now. But kernel panic because Procfile is weird. |
|
I issued two Kernel Panic on Mac OS X Lion 10.7.1 while starting Foreman 0.24.0 with the following Procfile: Any idea? |
|
Are you running inside |
|
Nope, just in my Terminal. |
|
What version of Ruby are you using? |
|
Oups sorry, forgotten than one! It's Ruby 1.9.2. |
|
Could you give me the full output of Thanks! |
|
ruby 1.9.2p180 (2011-02-18 revision 30909) [x86_64-darwin10.7.0] |
|
I assume you are using rvm? If so, could you try updating rvm to latest and recompiling that version of ruby? |
|
Hi! It finally works after updating all the stuff I can update.
I'm glad to use Foreman again! :) |
|
Hey, I'm getting the kernel panic also in OS X 10.7.1. Here's my info... I installed Ruby with ruby-build. Let me know what other info I can provide. Oh, using foreman-0.24.0. Thanks for the help. |
|
also getting kernel panics on Mac OS X Lion 10.7.1 (11B26) using TotalTerminal + oh-my-zsh and ruby |
|
Im getting the same with But it was giving me a error when the last one wasn't installed in the system once i install the openerp-web start to work again. |
|
Anyone seeing this issue please try the following:
If you do all of that and are still seeing kernel panics, please report here and include the following:
Thanks, |
|
Im working from a brand new macbook 11" with lion i installed all 2 days ago. My issue just happend when the last work on the Procfile wasn't installed in the system. |
|
Ok at least in my case i found that the problem it based in PTY.spawn when the command doesn't exists give me a kernel panic. Can any of you try something like require 'pty'
PTY.spawn('unexisting_command')Thanks |
|
Ok more news!!! It gives error just with 1.9.2 from p180 to HEAD but its works again with 1.9.3 in Head but need a small patch, because give a uncontrolled error. issue #83 is a pull request with the patch |
|
i create a issue in redmine so u can track this http://redmine.ruby-lang.org/issues/5433 |
|
Updating news, the error has been closed and mark as a Kernel BUG. But it just happend in 1.9.2 and not 1.9.3. As a workaround u can be sure that your command doesn't give any error, or use 1.9.3, 1.8.6. |
|
Also experience kernel panics, but with one specific change to my Procfile. Here's my Procfile: I've starred out the queue/worker names as they are business sensitive. This works fine. Adding VVERBOSE=1 to one of my resque workers causes the kernel panic. This appears to be repeatable. I'm running OSX 10.7.2 (GM). Version info: Gem env: Which foreman: OSX Crash report: |
|
@lukeredpath one question, if you execute the command in the console what happen?? |
|
Worked fine executed from the console. It also worked if I moved the VVERBOSE=1 to the end so it's as if it's interpreting that as a command rather than an environment variable declaration. |
|
I have reported this on the official Mac developer forums. As mentioned about by @argami, details can also be found on the ruby tracker: |
|
Link to the bug report at Apple: https://bugreport.apple.com/cgi-bin/WebObjects/RadarWeb.woa/43/wo/Pq8zrB5X24wNMaKDNqKUs0/12.66 |
|
FYI at least for us it seemed to happen only with redis tasks, and when we upgraded to a new redis version and installed it system-wide, rather than locally, it went away. I don't know if this helps figure it out. |
|
I got Foreman to work by installing it with the pkg package - I don't get any segfaults anymore! Yay! |
|
+1 on michenriksen solution |
|
The difference is probably that you are using system Ruby when using the .pkg installer. |
|
since the debugging of this issue is cumbersome (crashes my machine each time) i didn't get into depth why it worked. anyway here are my env details after installing the pkg. ~ rvm -v rvm 1.9.2 by Wayne E. Seguin (wayneeseguin@gmail.com) [https://rvm.beginrescueend.com/] ~ ruby -v
10x |
|
Since which foreman is still returning the gem, I doubt the package installation did anything for you. The crash occurs when you try to run a nonexistent command in the Procfile, perhaps something about the environment is different. |
|
thanks for the info i'll keep you posted |
|
I'm also having this issue with foreman-0.26.0 on 10.7.2. My Procfile is just: |
|
I was running into this problem (I think it's the same one) and solved it by changing my Procfile from to I figured this out by exporting to Bluepill (I couldn't get foreman start to work, so I was trying via Bluepill) and then looking at the log files for the individual processes, in which I saw After moving QUEUE=* to the end, I tried foreman start and it worked! |
|
I have been able to produce a kernel panic consistently. This doesn't appear to be quite the same as what others are experiencing but figured I'd share it here. My Procfile looks like this: The cause was operator error on my own part: turns out I did not have coffee-script installed on this machine. Everything started normally once I removed the coffee-script line from the Procfile and likewise once I installed coffee-script. |
|
Can you try the latest foreman prerelease? |
|
I was receiving a SIGTERM error and was just able to resolve it. Figured I would share in case it helps anyone else. I got the idea from hundredwatt above. Thank you, by the way! My Procfile looked like this: Upon trying to start foreman, I received the following: The only thing I did differently was to move the environment variable to the end, as hundredwatt suggested. Smooth sailing since... My environment: |
|
No problem anymore here with Foreman 0.28.0.pre2 with Ruby 1.9.2-p290 and RubyGems 1.8.11 on Mac OS 10.7.2. Thanks! ;) |
|
I am no longer experiencing an error with foreman 0.30.1. Thanks. |
|
This was fixed by moving away from the |
I got twice a kernel panic right after running
foreman start.This is my Procfile:
and if I run them separately they all work great.
After the
foreman startI see te colored output and then it crashes the entire system, so I must restart. This is the crash log I get after the reboot:The text was updated successfully, but these errors were encountered: