Haywood, Do you mean the remote logging like rsyslog? We did not try since syslog does not emit at all. Is it worth to try though? Anyway thanks for the advice, I will try to do anything to fix it. 2020년 2월 11일 (화) 오후 9:03, G.W. Haywood <ged@xxxxxxxxxxxxxxxxxx>님이 작성: > > Hi there, > > On Tue, 11 Feb 2020, 양유석 wrote: > > > From today, we even does not know what makes crush since there was no > > any log (literally kernel, application or something) Only that we > > encounter is when linux bridge agent in openstack restarted, server > > reboot without any log. After reboot, we see strange null string (@) > > in syslog. ... > > I cannot help you with the kernel crash but I suggest that you try > remote logging to another server, it might help provide more log info. > > -- > > 73, > Ged.
