Hi all, Suddenly my production logs happen to have empty lines. I mean lines get added to them, but they are empty. I did an apt-get upgrade earlier that updated a bunch of things and I fear this is related somehow, since I restarted Lighttpd a little while after the upgrade. Nothing else changed. I am using Debian testing and Rails from Debian package. Did any of you experienced that? Jos
Oops, might be related to ticket #2263. So beware before you update. I will post a solution if I find one. Jos wrote:> Hi all, > > Suddenly my production logs happen to have empty lines. I mean lines > get added to them, but they are empty. I did an apt-get upgrade > earlier that updated a bunch of things and I fear this is related > somehow, since I restarted Lighttpd a little while after the upgrade. > Nothing else changed. > > I am using Debian testing and Rails from Debian package. > > Did any of you experienced that? > > Jos > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails
On Oct 15, 2005, at 7:09 PM, Jos wrote:> Hi all, > > Suddenly my production logs happen to have empty lines. I mean > lines get added to them, but they are empty. I did an apt-get > upgrade earlier that updated a bunch of things and I fear this is > related somehow, since I restarted Lighttpd a little while after > the upgrade. Nothing else changed. > > I am using Debian testing and Rails from Debian package. > > Did any of you experienced that? > > Jos > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails > >Do a ruby -v from the command line. I bet when you did an apt-get update && apt-get upgrade. You probably ended up with ruby 1.8.3. The new version of ruby has some conflicts with the Logger class and the way that rails uses it. This is fixed in beta gems I think but the . 13.1 gems have problems with the Logger class and ruby 1.8.3. I''m sticking with 1.8.2 until the fix is added to rails stable. Cheers- -Ezra Zygmuntowicz WebMaster Yakima Herald-Republic Newspaper ezra-gdxLOakOTQ9oetBuM9ipNAC/G2K4zDHf@public.gmane.org 509-577-7732
Yeah, thanks. Actually I upgraded to 1.8.3 a while ago, but never restarted my FCGI so didn''t notice... Guess I will downgrade to 1.8.2 for the time being. Ezra Zygmuntowicz wrote:> > On Oct 15, 2005, at 7:09 PM, Jos wrote: > >> Hi all, >> >> Suddenly my production logs happen to have empty lines. I mean lines >> get added to them, but they are empty. I did an apt-get upgrade >> earlier that updated a bunch of things and I fear this is related >> somehow, since I restarted Lighttpd a little while after the >> upgrade. Nothing else changed. >> >> I am using Debian testing and Rails from Debian package. >> >> Did any of you experienced that? >> >> Jos >> _______________________________________________ >> Rails mailing list >> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org >> http://lists.rubyonrails.org/mailman/listinfo/rails >> >> > > > Do a ruby -v from the command line. I bet when you did an apt-get > update && apt-get upgrade. You probably ended up with ruby 1.8.3. The > new version of ruby has some conflicts with the Logger class and the > way that rails uses it. This is fixed in beta gems I think but the . > 13.1 gems have problems with the Logger class and ruby 1.8.3. I''m > sticking with 1.8.2 until the fix is added to rails stable. > > Cheers- > -Ezra Zygmuntowicz > WebMaster > Yakima Herald-Republic Newspaper > ezra-gdxLOakOTQ9oetBuM9ipNAC/G2K4zDHf@public.gmane.org > 509-577-7732 > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails
Just to conclude with this thing. I still do not know exactly what caused the issue to appear, but is is because my Ruby reports 1.8.3 while including the old Logger. So this is related to ticket #2263. To correct I commented the 1.8.3 test in clean_logger.rb to force the old style parameters. Hopefully this will be fixed either in the Ruby (proper Logger) or in the Rails packages (proper detection). Jos wrote:> Oops, might be related to ticket #2263. So beware before you update. I > will post a solution if I find one. > > Jos wrote: > >> Hi all, >> >> Suddenly my production logs happen to have empty lines. I mean lines >> get added to them, but they are empty. I did an apt-get upgrade >> earlier that updated a bunch of things and I fear this is related >> somehow, since I restarted Lighttpd a little while after the upgrade. >> Nothing else changed. >> >> I am using Debian testing and Rails from Debian package. >> >> Did any of you experienced that? >> >> Jos >> _______________________________________________ >> Rails mailing list >> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org >> http://lists.rubyonrails.org/mailman/listinfo/rails > > > > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails
For what it''s worth, I upgraded my Rails installation with gems last night and it corrected the problem. On 10/17/05, Jos <jos-opYYzZorcyRWk0Htik3J/w@public.gmane.org> wrote:> Just to conclude with this thing. I still do not know exactly what > caused the issue to appear, but is is because my Ruby reports 1.8.3 > while including the old Logger. So this is related to ticket #2263. > > To correct I commented the 1.8.3 test in clean_logger.rb to force the > old style parameters. Hopefully this will be fixed either in the Ruby > (proper Logger) or in the Rails packages (proper detection). > > Jos wrote: > > > Oops, might be related to ticket #2263. So beware before you update. I > > will post a solution if I find one. > > > > Jos wrote: > > > >> Hi all, > >> > >> Suddenly my production logs happen to have empty lines. I mean lines > >> get added to them, but they are empty. I did an apt-get upgrade > >> earlier that updated a bunch of things and I fear this is related > >> somehow, since I restarted Lighttpd a little while after the upgrade. > >> Nothing else changed. > >> > >> I am using Debian testing and Rails from Debian package. > >> > >> Did any of you experienced that? > >> > >> Jos > >> _______________________________________________ > >> Rails mailing list > >> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > >> http://lists.rubyonrails.org/mailman/listinfo/rails > > > > > > > > _______________________________________________ > > Rails mailing list > > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > > http://lists.rubyonrails.org/mailman/listinfo/rails > > > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >