Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

invalid internal status, try resetting the pause process with \"/var/tmp/go/src/github.com/containers/podman/bin/podman system migrate\": setting up the process: open /run/user/3271/libpod/tmp/pause.pid: no such file or directory #18448

Closed
edsantiago opened this issue May 3, 2023 · 7 comments
Labels
flakes Flakes from Continuous Integration locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@edsantiago
Copy link
Member

New one-off flake, seen in debian root:

not ok 232 podman image scp transfer
...
# podman image scp some9724dude@localhost::foo.bar/nonesuch/c_v59yduh5oc:mytag foobar:123
error creating temporary file: No such file or directory
time="2023-05-02T13:25:28Z"
      level=error
      msg="invalid internal status, try resetting the pause process with \"podman system migrate\": 
         setting up the process: open /run/user/3271/libpod/tmp/pause.pid: no such file or directory"
Error: exit status 1
@edsantiago edsantiago added the flakes Flakes from Continuous Integration label May 3, 2023
@github-actions
Copy link

github-actions bot commented Jun 3, 2023

A friendly reminder that this issue had no activity for 30 days.

@edsantiago
Copy link
Member Author

Still happening as of yesterday

@basilgello
Copy link

Reproducible on Debian 12 / bookworm as well. $XDG_RUNTIME_DIR/libpod gets recreated on relogin but tmp subfolder of it does not. Recreating the tmp directory prior to running podmn solves the issue but the running containers dont survive logout.

@github-actions
Copy link

A friendly reminder that this issue had no activity for 30 days.

@edsantiago
Copy link
Member Author

Last seen June 23. All instances were on Debian 12, and we're now running 13, so I'm tempted to la-la-la sweep this under the rug.

@basilgello does this remain a problem/priority for you? And, have you tried (as root) loginctl enable-linger YOURUSERNAME?

@basilgello
Copy link

I do that and/or tmuxing but the patch is definitely on my list

@edsantiago
Copy link
Member Author

No instances of the flake since my last post. All I can do here is close.

@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Apr 12, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 12, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
flakes Flakes from Continuous Integration locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

No branches or pull requests

3 participants