In addition, I found that after 15:32:26, the journalctl -b 0 logs won't
generate until thesession can be connected again.
Because of my server being attacked all the time, the log used to be continuous.
--
You received this bug notification because you are a member of Desktop
Packages, which
Thanks for your suggestion, I have test ping in 15:32:26 using 'journalctl -b
0' without related return.
I have point this in the file. Do you need complete file?
** Attachment added: "journalctl-log.txt"
Sorry for that I haven't received logs. I have tested the session with
ping and the session dropped down,then I used "journalctl _PID=25564"
command in root with no related logs return.("lsof -i" was used for
checking the session number)
--
You received this bug notification because you are a
3 matches
Mail list logo
