GeezerVisonThe World Wide Web, restored to 800 pixels of glory. |
| Home|About|Gaming cabinet|Archives|How it works|Starter sites |
GeezerVison is showing github.com — Troubleshooting Troubleshooting
Nick Sweeting edited this page
What are you having an issue with?:
If using Then make sure apt show archivebox # show info about the apt-installed version of archivebox brew info archivebox # show info about the brew-installed version of archivebox uv tool list # show info about uv-installed tools echo $PATH # show the directories your system is searching for binaries type -a archivebox # show all installed archivebox binaries available ⭐️ Show the full archivebox version info + info about all installed dependencies: archivebox version # shows lots of useful info about installed dependencies and more(ensure the version shown is the most recent available from Releases) ArchiveBox can be installed with Homebrew or brew tap archivebox/archivebox brew trust archivebox/archivebox brew install archivebox mkdir -p ~/archivebox/data cd ~/archivebox/data # (for example, can be anywhere) archivebox init archivebox install # finish installing runtime dependencies More info: https://github.com/ArchiveBox/homebrew-archivebox ArchiveBox's supported bare-metal install uses uv --version uv tool list archivebox version If For more info, see the Chromium Install page. ArchiveBox resolves Chrome through archivebox install chrome archivebox version The version output shows the selected provider, version, and projected path. If it reports an incompatible host browser, update that browser or let ArchiveBox install the managed fallback; do not bypass the resolver with an unrelated path. Resolve or update both tools through the same installer: archivebox install wget curl archivebox version Node.js and JavaScript extractor packages such as cd ~/archivebox/data # go into your data directory archivebox install node singlefile readability archivebox version Please open an issue with a description of where you got the export, and preferably your export file attached (you can redact the links). We'll fix the parser to support your format. If you ran the archiver once, it wont re-download sites subsequent times, it will only download new links. If you haven't already run it, make sure you have a working internet connection and that the parsed URLs look correct. You can check the ArchiveBox stdout logs or the Web UI to see what links it's downloading. To intentionally capture an already indexed URL again, use Make sure you have all the dependencies installed and that you're able to visit the links from your browser normally. Open an issue with a description of the errors if you're still having problems. Not all sites can be effectively archived with each method, that's why it's best to use a combination of
If you're having issues trying to host the archive via nginx, make sure you already have nginx running with SSL. If you don't, google around, there are plenty of tutorials to help get that set up. Open an issue if you have problem with a particular nginx config. Make sure the mounted data directory is writable by its intended non-root owner. The current Docker entrypoint detects the first non-root collection owner and runs ArchiveBox with matching numeric UID/GID; a new root-owned collection falls back to the image's Database and filesystem issues are uncommon but do come up from time to time (especially when using networked storage, large archives, or multiple ArchiveBox processes for a single collection). ℹ️ Generally, these commands can help you resolve most issues: archivebox init # upgrade the archivebox collection archivebox install # upgrade the archivebox runtime dependencies archivebox update --migrate-only # migrate/reconcile Snapshot files and metadata archivebox server --debug # run the server with more verbose debug log output archivebox shell # access the Python API / Django management shell sqlite3 index.sqlite3 # access the SQLite3 SQL database shell Don't be scared by the volume of content here. Almost all of these issues linked below are duplicates or old resolved bugs, but they contain valuable context and troubleshooting steps if you're trying to figure out the cause of a problem with your setup. The
More info:
ArchiveBox can sometimes struggle when archiving many links in parallel with multiple ArchiveBox processes trying to write to the database at the same time, leading to errors like this: Unable to create the django_migrations table (database is locked) These errors can also be encountered when there are permissions, network, or filesystem issues preventing writes to
More info:
Migration or upgrade issues happen occasionally with some niche setups or when skipping major versions during archiving. archivebox init # this usually applies any necessary migrations (atomically and indempotently, safe to run multiple times)
More info:
A corrupted database file can theoretically only happen if an external process or filesystem error corrupts the SQLite3 database (there have only been two reports of a user encountering this in real life). If you ever need to repair a corrupted ArchiveBox index you can run the following steps. Note this is specific to this error, these steps do not apply to other migrations/db errors (see above/below for other issues): sqlite3.DatabaseError: database disk image is malformed Generally all index issues should be fixable by running Error output: [i] [2022-03-24 20:37:27] ArchiveBox v0.6.2: archivebox init > /data [^] Verifying and updating existing ArchiveBox collection to v0.6.2... ---------------------------------------------------------------------- [*] Verifying archive folder structure... + ./archive, ./sources, ./logs... + ./ArchiveBox.conf... [*] Verifying main SQL index and running any migrations needed... Traceback (most recent call last): File "/usr/local/lib/python3.9/site-packages/django/db/backends/utils.py", line 82, in _execute return self.cursor.execute(sql) File "/usr/local/lib/python3.9/site-packages/django/db/backends/sqlite3/base.py", line 411, in execute return Database.Cursor.execute(self, query) sqlite3.DatabaseError: database disk image is malformed Steps to fix: cd ~/archivebox/data echo '.dump' | sqlite3 index.sqlite3 | sqlite3 repaired_index.sqlite3 mv index.sqlite3 corrupt_index.sqlite3 mv repaired_index.sqlite3 index.sqlite3 More info:
See here for more info:
Clone this wiki locally |
| You are visitor 01402503 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |
