Skip to content

podman logs: error resolving symbol "sd_journal_xxx": libsystemd-journal.so.0: cannot open shared object file: ENOENT #20569

@edsantiago

Description

@edsantiago

Two in the last week and a half. Both under vfs, which may be coincidence but I think it isn't Never mind, it's not a vfs thing:

<+073ms> # # podman logs 68fee835c41fcfbab5a673ec3457204394563e38857e979747d8ca457ef72608
<+086ms> # Error: error resolving symbol "sd_journal_open": libsystemd-journal.so.0: cannot open shared object file: No such file or directory

and:

# podman-remote [options] logs testPod-init-test
time="2023-11-02T06:49:37-05:00" level=error msg="Failed to get journal entry: failed to move journal cursor to next entry: error resolving symbol \"sd_journal_next\": libsystemd-journal.so.0: cannot open shared object file: No such file or directory"

Reminiscent of #17042, but different enough to merit its own issue. Also reminiscent of #20282.

Seen in: int+sys podman+remote fedora-37+fedora-38 root+rootless host sqlite

Metadata

Metadata

Assignees

Labels

flakesFlakes from Continuous Integrationlocked - please file new issue/PRAssist humans wanting to comment on an old issue or PR with locked comments.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions