Unit log not showing up

[Andrew Liaw]

When running `juju debug-log` log for a unit is not showing up.

Controller juju version: 2.9.32
CLI juju version: 2.9.38-ubuntu-amd64

logging-config is set to <root>=INFO;unit=DEBUG, and have tried using --include on the unit

The unit is producing logs and the logs can be found on the machine.

See the juju channel thread for details:
https://chat.charmhub.io/charmhub/pl/mkju6q4k5jyqzxbqepxhn8ha6y

[Joseph Phillips (manadart)]

I notice that the local log file had these lines following the Juju uniter preamble:

2023-02-14 14:46:40 DEBUG unit.runner/11.juju-log server.go:319 Operator Framework 1.5.4 up and running.
2023-02-14 14:46:40 DEBUG unit.runner/11.juju-log server.go:319 Emitting Juju event reconcile_runners.
2023-02-14 14:46:40 DEBUG unit.runner/11.juju-log server.go:319 http://localhost:None "GET /1.0 HTTP/1.1" 200 None

Is it possible that the charm logic is using the juju exec/run trick to dispatch a custom hook, and that a misapplication of said trick is wedging the charm?

[Andrew Liaw (aliaw)]

I deployed the same version of charm on a different juju controller hosted on an openstack instance.

The `juju debug-log` was showing the unit logs, for example:

unit-runner-0: 12:37:57 INFO unit.runner/0.juju-log Download of runner binary from https://github.com/actions/runner/releases/download/v2.301.1/actions-runner-linux-x64-2.301.1.tar.gz return status code: 200

It seems this only happens on that controller/server, I have redeployed multiple times, but the unit log never shows up there.

I have also started up a tiny-bash charm on that controller/server, and that units log is not showing up in `juju debug-log` either. The unit log are present on the machine as well.

I think we can focus on using the tiny-bash charm as the charm for testing this bug as the other charm is in active development.