Yelp/dumb-init

Why everything as "error" in verbose mode?

christianinsert opened this issue · 5 comments

christianinsert commented

I am running dumb-init in Google Kubernetes Engine in verbose mode. It seems that everything dumb-init puts out is interpreted as error even seemingly harmless messages like Child spawned with PID ... Should this be an error? Is there anything I can or need to do?

asottile commented

in think you're confusing "stderr" with errors -- output is sent to stderr to not interfere with program output

  • 👍2
christianinsert commented

Well, it's actually not me "falling victim" to that confusion but Google Kubernetes Engine. Everything which dumb-init, puts out is marked as "error" in the GKE logs (because of stderr). And that's a little bit inconvenient to be honest.

asottile commented

I still think you're confused -- GKE produces a separate log for the stdout and the stderr -- they're not "errors"

christianinsert commented

Thanks for your answer!
I'm not a GKE expert to be honest, but this is what I see in my logs:

image

So, dumb-init logs are marked with severity "Error". And I cannot see a separate log for stderr.

asottile commented

ah you've probably configured GKE to treat stderr as [error] level logs

I can't really help you for free on fixing your kubernetes configuration but this is not a dumb-init problem