I uploaded my website to the server but my log files are not being written to anymore. I don''t think it has anything to do with permission because even when I set the permission to the log files to 777 they are still not being written to. I am running my site on lighttpd but I am proxypassing to it through apache... would that have anything to do with it? Do I need to have a specific line in lighttpd so for my logs to be written? Thanks for your insight :-) Your Friend, John
Which mode are you running it in? I believe that rails doesn''t log anything when it is set to production. Although I may be wrong seeing as I am new to rails. --- Oliver Legg On 21 Jun 2005, at 19:13, John Kopanas wrote:> I uploaded my website to the server but my log files are not being > written to anymore. I don''t think it has anything to do with > permission because even when I set the permission to the log files > to 777 they are still not being written to. > > I am running my site on lighttpd but I am proxypassing to it > through apache... would that have anything to do with it? Do I > need to have a specific line in lighttpd so for my logs to be written? > > Thanks for your insight :-) > > Your Friend, > > John > _______________________________________________ > 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
> Which mode are you running it in? > > I believe that rails doesn''t log anything when it is set to production. > Although I may be wrong seeing as I am new to rails.No, Rails will log in production mode (see log/production.log). Make sure all the directories leading up to the log file are world executable. If you log is empty, it probably means: 1) Permission error. Check your apache error log. An error message telling you it can''t open the log file should appear right after an apache restart (this is most likely). 2) If you''ve modify the logger information in config/environment.rb. I did this once, as I didn''t finish an install of Rails Log Analyzer, which required me to edit the Logger parameters. Your best bet is probably to examine your apache error log. Matt
there is nothing being written to my apache error log file either... absolutely nothing... that is probably a separate problem but I think I will need to fix that as well... Thanks for your help. On 21-Jun-05, at 3:46 PM, Belorion wrote:>> Which mode are you running it in? >> >> I believe that rails doesn''t log anything when it is set to >> production. >> Although I may be wrong seeing as I am new to rails. >> > > No, Rails will log in production mode (see log/production.log). Make > sure all the directories leading up to the log file are world > executable. > > If you log is empty, it probably means: > > 1) Permission error. Check your apache error log. An error message > telling you it can''t open the log file should appear right after an > apache restart (this is most likely). > 2) If you''ve modify the logger information in config/environment.rb. I > did this once, as I didn''t finish an install of Rails Log Analyzer, > which required me to edit the Logger parameters. > > Your best bet is probably to examine your apache error log. > > Matt > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >
Even if I am using lighttpd the error message would be in apache and not the lighthttpd error log? On 21-Jun-05, at 5:49 PM, John Kopanas wrote:> there is nothing being written to my apache error log file > either... absolutely nothing... that is probably a separate problem > but I think I will need to fix that as well... > > Thanks for your help. > > On 21-Jun-05, at 3:46 PM, Belorion wrote: > > >>> Which mode are you running it in? >>> >>> I believe that rails doesn''t log anything when it is set to >>> production. >>> Although I may be wrong seeing as I am new to rails. >>> >>> >> >> No, Rails will log in production mode (see log/production.log). Make >> sure all the directories leading up to the log file are world >> executable. >> >> If you log is empty, it probably means: >> >> 1) Permission error. Check your apache error log. An error message >> telling you it can''t open the log file should appear right after an >> apache restart (this is most likely). >> 2) If you''ve modify the logger information in config/ >> environment.rb. I >> did this once, as I didn''t finish an install of Rails Log Analyzer, >> which required me to edit the Logger parameters. >> >> Your best bet is probably to examine your apache error log. >> >> Matt >> _______________________________________________ >> 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 >
On 6/21/05, John Kopanas <john.kopanas-O1KSuMybMhqBUy7/sJONFg@public.gmane.org> wrote:> Even if I am using lighttpd the error message would be in apache and > not the lighthttpd error log?Gah, I''m sorry, I meant your lighttpd log. Or, to simplify things, your webserver error log :P. Though, in the last week I''ve been using lighttpd and have not been impressed by its error logs.