On Wednesday, May 4, 2016 at 6:09:58 PM UTC-7, Dave S wrote: > > On Wednesday, May 4, 2016 at 5:32:47 PM UTC-7, Chris Guest wrote: >> >> Not seeing logging.error in nginx error_log >> >> >> I have a mostly successful install of web2py application with uwsgi and >> nginx on centos using setup-web2py-nginx-uwsgi-centos70.sh . >> >> But I can't figure out how to configure nginx, uwsgi and wsgihandler.py >> so that logging.error messages appear in the error_log file. >> I have been able to configure it so that nginx [notice] and [info] >> messages appear but these are generated by nginx itself and are not coming >> from logging.notice or logging.info calls in the web2py application. >> >> Can someone post a recipe as to how this is done? >> >> Thanks, >> Chris >> > > > Doesn't this also involve configuring web2py's logging? The default > logging.conf uses either the web2py directory or web2py/logs (depending on > version, IIRC), and writes the logging messages to a file therein. >
The part above is fine, the part below is a late-afternoon moment of misreading. > Most logging messages, though, aren't really intended to be seen by users, > and some of them reveal internal details that shouldn't be seen by > [hostile] users. > > Even the ticket system is intended to just say "oops, we broke something. > Tell our webmaster to check it out." > > HTML error codes are intended to be returned to the user (e.g., HTML 404). > > Ooops, you didn't say "to the user", you were just trying to consolidate logs. /dps -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
