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

Zombie wget-at and curl processes #87

Open
cdzombak opened this issue Aug 2, 2024 · 1 comment
Open

Zombie wget-at and curl processes #87

cdzombak opened this issue Aug 2, 2024 · 1 comment

Comments

@cdzombak
Copy link

cdzombak commented Aug 2, 2024

After running Warrior in Docker for a couple weeks, I noticed a large number (>1800) of zombie processes on my server.

These are curl and wget-at instances that I traced back to ArchiveTeam Warrior. A sample:

…
cdzombak  670782  0.0  0.0      0     0 ?        Z    Jul30   0:00      \_ [wget-at] <defunct>
cdzombak  671093  0.0  0.0      0     0 ?        Z    Jul30   0:00      \_ [wget-at] <defunct>
cdzombak  671957  0.0  0.0      0     0 ?        Z    Jul30   0:00      \_ [wget-at] <defunct>
cdzombak  672247  0.0  0.0      0     0 ?        Z    Jul30   0:00      \_ [wget-at] <defunct>
cdzombak  672484  0.0  0.0      0     0 ?        Z    Jul30   0:00      \_ [wget-at] <defunct>
cdzombak  672878  0.0  0.0      0     0 ?        Z    Jul30   0:00      \_ [wget-at] <defunct>
cdzombak  673095  0.0  0.0      0     0 ?        Z    Jul30   0:00      \_ [wget-at] <defunct>
…
cdzombak  670960  0.0  0.0      0     0 ?        Z    Jul30   0:00      \_ [curl] <defunct>
cdzombak  674664  0.0  0.0      0     0 ?        Z    Jul30   0:00      \_ [curl] <defunct>
cdzombak  676110  0.0  0.0      0     0 ?        Z    Jul30   0:00      \_ [curl] <defunct>
cdzombak  677882  0.0  0.0      0     0 ?        Z    Jul30   0:00      \_ [curl] <defunct>
cdzombak  680172  0.0  0.0      0     0 ?        Z    Jul30   0:00      \_ [curl] <defunct>
cdzombak  683753  0.0  0.0      0     0 ?        Z    Jul30   0:00      \_ [curl] <defunct>
cdzombak  685059  0.0  0.0      0     0 ?        Z    Jul30   0:00      \_ [curl] <defunct>
cdzombak  686465  0.0  0.0      0     0 ?        Z    Jul30   0:00      \_ [curl] <defunct>
cdzombak  688020  0.0  0.0      0     0 ?        Z    Jul30   0:00      \_ [curl] <defunct>
cdzombak  689696  0.0  0.0      0     0 ?        Z    Jul30   0:00      \_ [curl] <defunct>
…

My docker-compose file:

---
services:
  archiveTeamWarrior:
    image: atdr.meo.ws/archiveteam/warrior-dockerfile
    container_name: archiveTeamWarrior
    hostname: archiveTeamWarrior
    ports:
      - "9050:8001"
    labels:
      com.centurylinklabs.watchtower.enable: "true"
    restart: unless-stopped
    environment:
      - DOWNLOADER=<omitted>
      - SELECTED_PROJECT=auto

OS: Ubuntu 22.04.4 LTS
Docker: version 27.0.3, build 7d4bcd8

@kostirez1
Copy link

Seems to me like these could belong to the healthcheck defined in the Dockerfile:

HEALTHCHECK --interval=5s --timeout=3s CMD /home/warrior/data/wget-at -nv -t1 'http://localhost:8001/index.html' -O /dev/null || exit 1

Two healthchecks failed for me:

screenshot

And the two processes can be seen under the running container, under the python start.py

screenshot

Afaik python start.py (PID 1 in the container) is supposed to reap them, but never does.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants