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

errors with varlink via systemd #4005

Closed
cevich opened this issue Sep 12, 2019 · 4 comments · Fixed by #4089
Closed

errors with varlink via systemd #4005

cevich opened this issue Sep 12, 2019 · 4 comments · Fixed by #4089
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@cevich
Copy link
Member

cevich commented Sep 12, 2019

/kind bug

Description

When executing in a tight loop, or multiple simultaneous podman-remote throws EOF errors.

Steps to reproduce the issue:

  1. make podman podman-remote
  2. make install PREFIX=/usr
  3. systemctl daemon-reload
  4. systemctl enable io.podman.socket
  5. systemctl enable io.podman.service
  6. systemctl start io.podman.socket
  7. while podman-remote run -it --rm alpine echo "hi"; do :; done

Describe the results you received:

Either:

hi
...cut several repeats...
hi
Error: unexpected EOF
...

or

hi
...cut several repeats...
hi
Error: Virtual Read failed, 0: EOF
...

Describe the results you expected:

A continuous stream of hi and no errors.

Additional information you deem important (e.g. issue happens only occasionally):

Found while discovering/debugging issue #3998

Also sometimes reproducible with:
podman-remote run --rm alpine echo "hello" & podman-remote run --rm alpine echo "hello"

Output of podman version:

(paste your output here)

Output of podman info --debug:

# podman-remote version
Client:
Version:            1.5.2-dev
RemoteAPI Version:  1
Go Version:         go1.12.7
OS/Arch:            linux/amd64

Service:
Version:            1.5.2-dev
RemoteAPI Version:  1
Go Version:         go1.12.7
OS/Arch:            linux/amd64

Package info (e.g. output of rpm -q podman or apt list podman):

af8fedc

Additional environment details (AWS, VirtualBox, physical, etc.):

Reproduced on a VM with 2 vCPUs (no threads) and 4 GiB memory.

@openshift-ci-robot openshift-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Sep 12, 2019
@vrothberg vrothberg self-assigned this Sep 23, 2019
@vrothberg
Copy link
Member

I can reproduce immediately. Interestingly, I cannot reproduce when avoiding the socket activation and running sudo podman varlink -t 0 unix:/run/podman/io.podman directly.

@vrothberg
Copy link
Member

vrothberg commented Sep 23, 2019

I get a 100 percent error rate when doing a podman-remote run alpine echo "hi" > /dev/null.
...that was a red herring.

@vrothberg vrothberg changed the title Virtual Read failed, 0: EOF errors with varlink via systemd Sep 23, 2019
vrothberg added a commit to vrothberg/libpod that referenced this issue Sep 24, 2019
Fix the logic when getting the runtime for varlink to actually disable
SDNotify support.

Fixes: containers#4005
Signed-off-by: Valentin Rothberg <[email protected]>
@vrothberg
Copy link
Member

It looks like the logic to disable sdnotify was wrong. Opened #4089 to address the issue. It fixes the issues locally but lets wait what the CI has to say.

@cevich
Copy link
Member Author

cevich commented Sep 24, 2019

Oh this is fantastic! Thanks @vrothberg 😺

@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 Sep 23, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants