I''m running Rails 1.2.3 with mongrel and Ruby 1.8.6 on Windows. I change the log_level in environment.rb from :debug to :warn (or :error) but still see gobs of output in the development.log file. The log_level setting seems to have no effect for me. I also tried putting in config.log_level = :warn in the environments/development.rb file to no avail. I did restart the server each time after making and saving the edits to the file. More than discovering a fix to my problem, I''d greatly appreciate any pointers as to how to go about debugging this issue. Thanks Vish --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Okay it looks like RAILS_DEFAULT_LOGGER is set so the log_level settings in the config files are ignored. Can''t seem to find who may be setting the RAILS_DEFAULT_LOGGER. Will appreciate any pointers. On Jul 31, 4:28 pm, Vish K <svko...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> I''m running Rails 1.2.3 with mongrel and Ruby 1.8.6 on Windows. > > I change the log_level in environment.rb from :debug to :warn > (or :error) but still see gobs of output in the development.log file. > The log_level setting seems to have no effect for me. I also tried > putting in config.log_level = :warn in the environments/development.rb > file to no avail. > > I did restart the server each time after making and saving the edits > to the file. > > More than discovering a fix to my problem, I''d greatly appreciate any > pointers as to how to go about debugging this issue. > > Thanks > Vish--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Vish K wrote:> Okay it looks like RAILS_DEFAULT_LOGGER is set so the log_level > settings in the config files are ignored. Can''t seem to find who may > be setting the RAILS_DEFAULT_LOGGER. Will appreciate any pointers. > > On Jul 31, 4:28 pm, Vish K <svko...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: >> I''m running Rails 1.2.3 with mongrel and Ruby 1.8.6 on Windows. >> >> I change the log_level in environment.rb from :debug to :warn >> (or :error) but still see gobs of output in the development.log file. >> The log_level setting seems to have no effect for me. I also tried >> putting in config.log_level = :warn in the environments/development.rb >> file to no avail. >> >> I did restart the server each time after making and saving the edits >> to the file. >> >> More than discovering a fix to my problem, I''d greatly appreciate any >> pointers as to how to go about debugging this issue. >> >> Thanks >> VishI believe there''s a bug in script/server when used with Mongrel related to this issue. Try searching the bugtracker at dev.rubyonrails.org for more information. -- Cheers, - Jacob Atzen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Jacob,
You''re right about the bug. I had to put this at the bottom of my
environment.rb to get what I wanted.
RAILS_DEFAULT_LOGGER.level = Logger::WARN
Hope this helps someone else.
Thanks
Vish
On Aug 1, 1:28 am, Jacob Atzen
<ja...-4U2y0bnePT5NzRJJ8cAMrg@public.gmane.org>
wrote:> Vish K wrote:
> > Okay it looks like RAILS_DEFAULT_LOGGER is set so thelog_level
> > settings in the config files are ignored. Can''t seem to find
who may
> > be setting the RAILS_DEFAULT_LOGGER. Will appreciate any pointers.
>
> > On Jul 31, 4:28 pm, Vish K
<svko...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> >> I''m running Rails 1.2.3 with mongrel and Ruby 1.8.6 on
Windows.
>
> >> I change thelog_levelin environment.rb from :debug to :warn
> >> (or :error) but still see gobs of output in the development.log
file.
> >> Thelog_levelsetting seems to have no effect for me. I also tried
> >> putting in config.log_level= :warn in the
environments/development.rb
> >> file to no avail.
>
> >> I did restart the server each time after making and saving the
edits
> >> to the file.
>
> >> More than discovering a fix to my problem, I''d greatly
appreciate any
> >> pointers as to how to go about debugging this issue.
>
> >> Thanks
> >> Vish
>
> I believe there''s a bug in script/server when used with Mongrel
related
> to this issue. Try searching the bugtracker at dev.rubyonrails.org for
> more information.
>
> --
> Cheers,
> - Jacob Atzen
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
It seems that the offending line (that causes the logging settings in the config files to be skipped) is Rails::Initializer.run(:initialize_logger) in rails-1.2.3/lib/commands/servers/mongrel.rb. This is line #50 for me. Due to this the RAILS_DEFAULT_LOGGER is set and you have to put a setting like this in the config file: RAILS_DEFAULT_LOGGER.level = Logger::WARN On Aug 1, 12:38 pm, Vish K <svko...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Jacob, > > You''re right about the bug. I had to put this at the bottom of my > environment.rb to get what I wanted. > > RAILS_DEFAULT_LOGGER.level = Logger::WARN > > Hope this helps someone else. > > Thanks > Vish > > On Aug 1, 1:28 am, Jacob Atzen <ja...-4U2y0bnePT5NzRJJ8cAMrg@public.gmane.org> wrote: > > > Vish K wrote: > > > Okay it looks like RAILS_DEFAULT_LOGGER is set so thelog_level > > > settings in the config files are ignored. Can''t seem to find who may > > > be setting the RAILS_DEFAULT_LOGGER. Will appreciate any pointers. > > > > On Jul 31, 4:28 pm, Vish K <svko...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > >> I''m running Rails 1.2.3 with mongrel and Ruby 1.8.6 on Windows. > > > >> I change thelog_levelin environment.rb from :debug to :warn > > >> (or :error) but still see gobs of output in the development.log file. > > >> Thelog_levelsetting seems to have no effect for me. I also tried > > >> putting in config.log_level= :warn in the environments/development.rb > > >> file to no avail. > > > >> I did restart the server each time after making and saving the edits > > >> to the file. > > > >> More than discovering a fix to my problem, I''d greatly appreciate any > > >> pointers as to how to go about debugging this issue. > > > >> Thanks > > >> Vish > > > I believe there''s a bug in script/server when used with Mongrel related > > to this issue. Try searching the bugtracker at dev.rubyonrails.org for > > more information. > > > -- > > Cheers, > > - Jacob Atzen--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Vish K wrote:> It seems that the offending line (that causes the logging settings in > the config files to be skipped) is > > Rails::Initializer.run(:initialize_logger) > > in rails-1.2.3/lib/commands/servers/mongrel.rb. This is line #50 for > me. Due to this the RAILS_DEFAULT_LOGGER is set and you have to put a > setting like this in the config file: > > RAILS_DEFAULT_LOGGER.level = Logger::WARN > > > On Aug 1, 12:38 pm, Vish K <svko...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: >> Jacob, >> >> You''re right about the bug. I had to put this at the bottom of my >> environment.rb to get what I wanted. >> >> RAILS_DEFAULT_LOGGER.level = Logger::WARN >> >> Hope this helps someone else. >> >> Thanks >> VishI seem to recall that you might be able to dodge the issue by using "mongrel_rails start" instead of script/server. My memory has been known to be corrupted though ;-) -- Cheers, - Jacob Atzen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---