#4969 (prod site does not write to lino.log after upgrade)
by Luc Saffre · in Developers · assigned to Luc Saffre
Résumé
Concepts sous-jacents
Commentaires
- 3 ans, 5 mois ago by Luc Saffre about #4969 (prod site does not write to lino.log after upgrade) : log/lino.log gets only two messages: 202305-09 07:46:51 INFO [consumers 4903 140368315881216] : Running log server 202305-09 07:46:52 INFO [consumers 4903 140368315881216] : Running system tasks
The remaining log messages go to /var/log/supervisor/prod_asgi0-stdout---supervisor-7n_ohm_s.log
And /va... - 3 ans, 5 mois ago by Luc Saffre about #4969 (prod site does not write to lino.log after upgrade) : I released to PyPI and pulled on newavanti.
- 3 ans, 5 mois ago by Luc Saffre about #4969 (prod site does not write to lino.log after upgrade) : I am wondering why we need two socket files ("worker" and "log")...
- 3 ans, 5 mois ago by Luc Saffre in reply to Luc Saffre about #4969 (prod site does not write to lino.log after upgrade) : And I had to call_command("runworker") from within the thread (i.e. where the call to super() had been before).
- 3 ans, 5 mois ago by Luc Saffre in reply to Luc Saffre about #4969 (prod site does not write to lino.log after upgrade) : The main problem was that I forgot to add runworker to the SKIP_COMMANDS
- 3 ans, 5 mois ago by Luc Saffre about #4969 (prod site does not write to lino.log after upgrade) (2 replies) : I still didn't figure out why my local changes don't work.
- 3 ans, 5 mois ago by Luc Saffre about #4969 (prod site does not write to lino.log after upgrade) : I am testing my changes locally in chatter demo, after having "mkdir settings/log". Right now, I had a ChannelFull exception and "ps aux | grep lino_run" shows 12 processes that seem to constantly re-spawn themselves (PID changes, so I cannot even kill them manually).
- 3 ans, 5 mois ago by Luc Saffre about #4969 (prod site does not write to lino.log after upgrade) (1 reply) : I am trying to fix this by having lino_runworker call call_command('runworker') and specifying LINOD as first argument instead of inheriting from the runworker Command.
- 3 ans, 5 mois ago by Luc Saffre about #4969 (prod site does not write to lino.log after upgrade) : IOW the lino_runworker command should not expect an argument but pass lino.modlib.linod.utils.LINOD to the BaseCommand.
- 3 ans, 5 mois ago by Luc Saffre about #4969 (prod site does not write to lino.log after upgrade) : Great! Yes, after saying say "linod_prod" instead of "foo", the logging now works. Thanks.
- 3 ans, 5 mois ago by Luc Saffre about #4969 (prod site does not write to lino.log after upgrade) : But when I say "pm status", the two messages "Started manage.py status (using lino_local.prod.settings) --> PID 1611201" and "Done manage.py status (PID 1611201)" are not being logged anywhere (except to the console).
- 3 ans, 5 mois ago by Luc Saffre about #4969 (prod site does not write to lino.log after upgrade) : Seems that the stdout of the daphne process (which should go to lino.log) goes instead to /var/log/supervisor/prod_asgi0-stdout---supervisor-77ghq18b.log
- 3 ans, 5 mois ago by Luc Saffre about #4969 (prod site does not write to lino.log after upgrade) (2 replies) : I added a channel name ("foo" because have no better idea) to the call to manage.py lino_runworker in the supervisor conf. Now there is no error message. But the lino.log is still not being touched,,,
Started manage.py lino_runworker foo (using lino_local.prod.settings) --> PID 1607136 Running worke... - 3 ans, 5 mois ago by Luc Saffre about #4969 (prod site does not write to lino.log after upgrade) : The supervisor log says:
Started manage.py lino_runworker (using lino_local.prod.settings) --> PID 1604991 usage: manage.py lino_runworker [-h] [--layer LAYER] [--version] [-v {0,1,2,3}] [--settings SETTINGS] [--pythonpath PYTHONPATH] [--... - 3 ans, 5 mois ago by Luc Saffre about #4969 (prod site does not write to lino.log after upgrade) : Both the log_sock and the lino.log file are last modified 2023-03-29 at 18:45:
luc@inin3:/usr/local/lino/lino_local/prod$ ll log/lino.log -rw-rw-r-- 1 root www-data 2046 29. märts 18:48 log/lino.log luc@inin3:/usr/local/lino/lino_local/prod$ ll ... srwxrwxr-x 1 root www-data 0 29. märts 18:4... - 3 ans, 5 mois ago by Luc Saffre about #4969 (prod site does not write to lino.log after upgrade) : The lino.log file of the prod site on newavanti has not been touched since end of March (i.e. the previous pull.sh). I guess that it has to do with the runworker or the log server. @8lurry do you have any idea what I can try?
- 3 ans, 5 mois ago by Luc Saffre about #4969 (prod site does not write to lino.log after upgrade) : Created new Ticket #4969 (prod site does not write to lino.log after upgrade).