# Log4r warning message

**URL:** <https://www.ruby-forum.com/t/log4r-warning-message/141722>\
**Category:** Rails\
**Created:** [June 30, 2008, 5:00am UTC](https://www.ruby-forum.com/t/log4r-warning-message/141722 "2008-06-30T05:00:07Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![nahabed](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/b77776/32.png) [@nahabed](https://www.ruby-forum.com/u/nahabed)\
**Post date:** [June 30, 2008, 5:00am UTC](https://www.ruby-forum.com/t/log4r-warning-message/141722/1 "2008-06-30T05:00:07Z")

</div>

I installed log4r as a gem on Max OS X Leopard. When I start the  
server locally, I have a warning that I’d like to get rid of. I think  
this is a side-effect of log4r? Other rails projects that I am working  
on, on the same machine that don’t generate this warning. this one is  
the only one using log4r.

=\> Booting Mongrel (use ‘script/server webrick’ to force WEBrick)  
=\> Rails application starting on [http://0.0.0.0:3000](http://0.0.0.0:3000)  
=\> Call with -d to detach  
=\> Ctrl-C to shutdown server  
\*\* Ruby version is up-to-date; cgi\_multipart\_eof\_fix was not loaded  
\*\* Starting Mongrel listening at 0.0.0.0:3000  
\*\* Starting Rails with development environment…  
/Users/roupen/RailsProjects/scoobydeal/config/logger.rb:16: warning:  
already initialized constant RAILS\_DEFAULT\_LOGGER  
\*\* Rails loaded.  
\*\* Loading any Rails specific GemPlugins  
\*\* Signals ready. TERM =\> stop. USR2 =\> restart. INT =\> stop (no  
restart).  
\*\* Rails signals registered. HUP =\> reload (without restart). It  
might not work well.  
\*\* Mongrel available at 0.0.0.0:3000  
\*\* Use CTRL-C to stop.