search

containers / podman

Podman: A tool for managing OCI containers and pods.
https://podman.io
Apache License 2.0
22.4k stars 2.31k forks source link

Can't view logs: "Error: initial journal cursor: failed to get cursor: cannot assign requested address" #23004

Closed nlavalle closed 2 weeks ago

nlavalle commented 2 weeks ago

Issue Description

Describe your issue I have a fresh debian 12 droplet I created on digital ocean, did a sudo apt-get -y install podman then tried to load a simple postgres:bullseye container, but when I try to do sudo podman logs postgres it returns the error: "Error: initial journal cursor: failed to get cursor: cannot assign requested address"

Steps to reproduce the issue

Steps to reproduce the issue

  1. sudo apt-get -y install podman
  2. sudo podman pull docker.io/library/postgres:bullseye
  3. sudo podman run -d --name postgres -p 5432:5432 -e POSTGRES_PASSWORD=postgres -v postgres:/var/lib/postgresql/data postgres:bullseye
  4. sudo podman logs -f postgres

Describe the results you received

Describe the results you received "Error: initial journal cursor: failed to get cursor: cannot assign requested address"

Describe the results you expected

Describe the results you expected Logs from the database

podman info output

If you are unable to run podman info for any reason, please provide the podman version, operating system and its version and the architecture you are running.

Podman version 4.3.1
Debian 12 bookworm
I'm not sure what the droplet specs are, it's "Basic Regular Intel 1vCPU 1 GB RAM"

Podman in a container

No

Privileged Or Rootless

Privileged

Upstream Latest Release

No

Additional environment details

Additional environment details Digital Ocean droplet, running via terminal ssh'd into the droplet

Additional information

Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting

nlavalle commented 2 weeks ago

I have committed the IT folly of not trying to turn it off and on again. I did a sudo reboot of the droplet and it worked after that, is there some kind of journal thing that requires a restart after installing podman?

mheon commented 2 weeks ago

Not that I'm aware of. That definitely looks like an error out of the journal DBus API, not our API, so possibly an intermittent issue with the journal itself?

nlavalle commented 2 weeks ago

I'll chalk this up to something probably with the DO provisioning and go ahead and close this out, sorry for the noise.