by Luc Saffre · in Hosting (system administration) · assigned to Sharif Mehedi

Résumé

Concepts sous-jacents

• #4980 ('NoneType' object has no attribute 'default_color') (by Luc Saffre in Hosting (system administration) assigned to Luc Saffre)

Commentaires

• 4 ans, 2 mois ago by Sharif Mehedi in reply to Luc Saffre about #4595 (Multiple Lino processes logging to single file) : I replaced the use_websockets with use_linod. But I did NOT publish the changed in the book. I can publish them now. but since you (@luc ) have locally changed them, you can also publish them.
• 4 ans, 2 mois ago by Sharif Mehedi about #4595 (Multiple Lino processes logging to single file) : Linod consumer is ready to be tested on a production site.
• 4 ans, 2 mois ago by Sharif Mehedi about #4595 (Multiple Lino processes logging to single file) : I finally managed to get the logs send to the linod process. But I didn't write any rule for writing the logs. Something I need to discuss with @luc .
• 4 ans, 2 mois ago by Sharif Mehedi about #4595 (Multiple Lino processes logging to single file) : The handler for file logger never exists unless there's a child directory named "log" in the project directory!
• 4 ans, 2 mois ago by Sharif Mehedi about #4595 (Multiple Lino processes logging to single file) : I tried logging with a custom handler (attached to the root logger), which sends log records to a channel BUT there's a catch, which is when sending a record if an log message comes from the code that is sending the log record then it falls into an infinite loop. I am thinking about creating a filte...
• 4 ans, 2 mois ago by Sharif Mehedi about #4595 (Multiple Lino processes logging to single file) : I have separated the channels worker feature into lino.modlib.linod plugin. This plugin will be activated when any of the following feature is set to `True`: site.use_linod, notify.use_websockets, notify.use_push_api.
• 4 ans, 2 mois ago by Sharif Mehedi about #4595 (Multiple Lino processes logging to single file) : I checked my cosi5.com server logs. The django.request logs are put into the supervisor logging system, to be exact - the logs are put into the /var/log/supervisor/cosifive-uwsgi-stderr--supervisor-*.log. I am not sure whey they are going to the stderr instead of stdout.