mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 17:16:00 +03:00
[GH-ISSUE #1665] Bug: Fails to stop a supervisord process that doesn't exist #996
Labels
No labels
expected: maybe someday
expected: next release
expected: release after next
expected: unlikely unless contributed
good first ticket
help wanted
pull-request
scope: all users
scope: windows users
size: easy
size: hard
size: medium
size: medium
status: backlog
status: blocked
status: done
status: idea-phase
status: needs followup
status: wip
status: wontfix
touches: API/CLI/Spec
touches: configuration
touches: data/schema/architecture
touches: dependencies/packaging
touches: docs
touches: js
touches: views/replayers/html/css
why: correctness
why: functionality
why: performance
why: security
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ArchiveBox#996
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sclu1034 on GitHub (Feb 26, 2025).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/1665
Originally assigned to: @pirate on GitHub.
Provide a screenshot and describe the bug
During startup, ArchiveBox failed consistently by trying to terminate a supervisord process that didn't exist.
It took me a while to figure out that there is a
/data/tmp/supervisord.pidfile that can outlive previous instances, because it's in the persisted/datavolume. This made ArchiveBox incorrectly believe that a process was already running.Deleting the file solved my issue for the time being, but some suggestions to improve this:
/dataas the directory to store permanently, putting atmpfolder in there seems rather counter-productive. If, for some reason, the application architecture demands that anyways, the documentation should point out this folder (e.g. the exampledocker-compose.ymlcould include a volume entry to mount it to the host's/tmp)/tmp, not to a volume that may be persisted outside the containerstop_existing_supervisord_processshould recognize the scenario where a PID file exists but no matching process, and correctly clean up the file, then proceed startup as usual.Steps to reproduce
Logs or errors
ArchiveBox Version
How did you install the version of ArchiveBox you are using?
Docker (or Podman/LXC/K8s/TrueNAS/Proxmox/etc)
What operating system are you running on?
Unraid
What type of drive are you using to store your ArchiveBox data?
data/is on a local SSD or NVMe drivedata/is on a spinning hard drive or external USB drivedata/is on a network mount (e.g. NFS/SMB/Ceph/GlusterFS/etc.)data/is on a FUSE mount (e.g. SSHFS/RClone/S3/B2/Google Drive/Dropbox/etc.)Docker Compose Configuration
ArchiveBox Configuration