For completeness, I''ll cross post my answer, which I posted in the
Deploying Rails group:
I''ve solved my problem. Thanks to everyone who read these ramblings -
sorry for bugging you all. Right up front, I did not share all of the
right information because frankly I did not know I had it.
For instance, I did not share that I had redefined the Logger''s
format_message method to improve my logger output. My definition was
as follows:
class Logger
def format_message(severity, timestamp, msg, progname)
"#{severity} #{timestamp} (#{$$})\n #{msg}\n"
end
end
It took me quite a while to figure out what was wrong with the above.
I tried some other folks'' format_message definitions with no luck:
http://michaelmarth.blogspot.com/2006/07/rubys-classes-are-dynamic.html
http://dev.rubyonrails.org/ticket/2245
Then I found that Ruby 1.8.3 had transposed the msg and progname
arguments:
http://devblog.famundo.com/articles/2006/09/22/improving-the-rails-logger
Making the format look like what is depicted at the Wiki:
http://wiki.rubyonrails.com/rails/pages/HowtoConfigureLogging
Certainly this problem occurred because I went to a new Ruby version
on my new MacBook and coincidentally Dreamhost upgraded Ruby
recently. So the new format_message method is simply:
class Logger
def format_message(severity, timestamp, progname, msg)
"#{severity} #{timestamp} (#{$$})\n #{msg}\n"
end
end
-Barry
On Feb 8, 6:01 am, "bjhess"
<bjh...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:> Anyone have thoughts on this?
>
> Thanks!
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---