Take the 2-minute tour ×
Stack Overflow is a question and answer site for professional and enthusiast programmers. It's 100% free, no registration required.

Assets are timing out for my Rails app served locally through Pow. When I visit an asset's url directly (eg. '/assets/home.css') I'm presented with this error:

{
    "name":"IOError",
    "message":"closed stream",
    "stack":"/Users/XXX/Library/Application/ Support/Pow/Versions/0.4.0/node_modules/nack/lib/nack/server.rb:158:in `close'
    /Users/XXX/Library/Application Support/Pow/Versions/0.4.0/node_modules/nack/lib/nack/server.rb:158:in `ensure in handle'
    /Users/XXX/Library/Application Support/Pow/Versions/0.4.0/node_modules/nack/lib/nack/server.rb:158:in `handle'
    /Users/XXX/Library/Application Support/Pow/Versions/0.4.0/node_modules/nack/lib/nack/server.rb:99:in `rescue in block (2 levels) in start'
    /Users/XXX/Library/Application Support/Pow/Versions/0.4.0/node_modules/nack/lib/nack/server.rb:96:in `block (2 levels) in start'
    /Users/XXX/Library/Application Support/Pow/Versions/0.4.0/node_modules/nack/lib/nack/server.rb:86:in `each'
    /Users/XXX/Library/Application Support/Pow/Versions/0.4.0/node_modules/nack/lib/nack/server.rb:86:in `block in start'
    /Users/XXX/Library/Application Support/Pow/Versions/0.4.0/node_modules/nack/lib/nack/server.rb:66:in `loop'
    /Users/XXX/Library/Application Support/Pow/Versions/0.4.0/node_modules/nack/lib/nack/server.rb:66:in `start'
    /Users/XXX/Library/Application Support/Pow/Versions/0.4.0/node_modules/nack/lib/nack/server.rb:13:in `run'
    /Users/XXX/Library/Application Support/Pow/Versions/0.4.0/node_modules/nack/bin/nack_worker:4:in `<main>'"
}

I'm using Pow 0.4.0, Rack 1.4.5 and Rails 3.2.12.

I've tried restarting the Pow site, restarting Pow, uninstalling and reinstalling Pow, and restarting my machine.

share|improve this question
    
reformat the error, it's one long line –  RadBrad Feb 20 '13 at 20:51
    
any luck with this? –  Ben Apr 9 '13 at 14:39
    
I fixed it, but I'm not sure how or when. Sorry. –  Zane Shannon Apr 9 '13 at 20:16
    
did you try upgrading node? –  codenamev Sep 16 '13 at 16:04

1 Answer 1

Looks like you might need to update node.js. If you installed via Homebrew, you can use:

brew update
brew upgrade node
npm update npm -g

This will update Homebrew and Node Package Manager.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.