On Wed, 2021-03-03 at 14:14 +0100, Fabiano Fidêncio wrote:
Qian,
On Wed, Mar 3, 2021 at 1:54 PM Qian Cai <qcai@redhat.com> wrote:
On Wed, 2021-03-03 at 10:34 +0100, Christophe de Dinechin wrote:
On 2 Mar 2021, at 22:02, Qian Cai <qcai@redhat.com> wrote:
I am chasing a bug that "crictl rm" returns ESRCH which ends up tracking down in the rust agent code:
https://github.com/kata-containers/kata-containers/blob/a12772c6010f6886be7a...
I don't yet understand how to get some debugging messages outside of the agent, so I can see why it return ESRCH. I tried added things like,
info!(sl!(), "KKK in do_signal_process()");
Have you tried replacing that with a warn! ? I remember having a similar issue where info! was filtered by default.
Did you change the logging level, see https://github.com/kata-containers/kata-containers/blob/main/docs/Developer-... ?
Thanks Christophe, with those in place, I finally received the debug (and even info) output with "crio -l debug" even though previously I used "crio -l trace" which I thought it will override that log_level.
https://github.com/kata-containers/kata-containers/issues/1473#issuecomment-... may be of your interest.
Good catch! That definite looks like a silly piece of code.