Ruby on Rails: "no such file or directory" with logger.rb

Question

I'm attempting to run a RoR app locally for the first time. I've started the server and I get the following error (after WEBrick starts):

C:/Ruby/lib/ruby/1.9.1/logger.rb:599:in `initialize': No such file or directory - /dev/null (Errno::ENOENT)

I try to run rake db:migrate and I get the same error:

    ** Execute environment
    rake aborted!
    No such file or directory - /dev/null
    C:/Ruby/lib/ruby/1.9.1/logger.rb:599:in `initialize'
    C:/Ruby/lib/ruby/1.9.1/logger.rb:599:in `open'
    C:/Ruby/lib/ruby/1.9.1/logger.rb:599:in `create_logfile'
    C:/Ruby/lib/ruby/1.9.1/logger.rb:594:in `open_logfile'
    C:/Ruby/lib/ruby/1.9.1/logger.rb:549:in `initialize'
    C:/Ruby/lib/ruby/1.9.1/logger.rb:314:in `new'
    C:/Ruby/lib/ruby/1.9.1/logger.rb:314:in `initialize'
    C:/Ruby/lib/ruby/gems/1.9.1/gems/activesupport-3.2.0/lib/active_support/core_ext/logger.rb:72:in `initialize'

I'm running on a Windows machine, in case it helps. Does anyone have any idea what's going on here?

> ruby -v
ruby 1.9.3p0 (2011-10-30) [i386-mingw32]

> rails -v
Rails 3.2.0

I installed it with an exe from rubyinstaller.org – JakeP Feb 17 '12 at 20:06 — JakeP, Feb 17 '12 at 20:06

score 2 · Accepted Answer · answered Feb 17 '12 at 19:28

2

/dev/null file is specific to unix, there's no such file on Windows.

answered Feb 17 '12 at 19:28

farnoy

7,356
2
20
30

So the real question is, why is it trying to open /dev/null ? – DGM Feb 17 '12 at 19:43
to fix this you need to find where in code is the `Logger` instance constructed and change the first parameter to some real file on your system. Beware, that if something pointed out to `/dev/null`, the developer wanted it to dissapear, so be sure to clear that file you set to log on windows from time to time. – farnoy Feb 17 '12 at 19:44
Thanks so much, this fixed it :). The project was developed on a *nix machine so I should have looked for that in the config files. – JakeP Feb 17 '12 at 20:13

score 0 · Answer 2 · answered Sep 07 '14 at 06:10

To add to @farnoy 's answer.

although from the trace it looks like that it might be thrown from rails framework stack or ruby stack. usually it is caused by application developer making wrong assumptions about the environment.

in my case, it is some of the App script file specify '/dev/null' as log file causing the cross platform break.

just grep 'dev/null' in your application folder and modify accordingly.

Ruby on Rails: "no such file or directory" with logger.rb

2 Answers2

Linked