Skip to content

Prevent stale journalctl instances #14

@alberanid

Description

@alberanid

In some unknown circumstances multiple instances of journalctl for the the same LXC are run, over prolonged periods of time.

E.g., a ps faux | grep journalctl inside one of the containers will show:

root       21717  0.0  0.8 251392 17024 ?        S    Dec15   0:00 journalctl --lines 0 --follow --output json
root        6153  0.0  0.8 256340 18560 ?        S    Dec12   0:00 journalctl --lines 0 --follow --output json
root         317  0.0  0.8 257608 17152 ?        S    Dec10   0:00 journalctl --lines 0 --follow --output json

Those are killed if pve2otelcol is restarted; some logs seem, in fact, to be duplicated (to be validated).

We must identify the possible source of the problem.

Metadata

Metadata

Assignees

Labels

bugSomething isn't workinghelp wantedExtra attention is needed

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions