DBC:Errors/Executing: Difference between revisions

From Dirty Cache Wiki
Jump to navigation Jump to search
Line 22: Line 22:


<code>alternatives --set python /usr/bin/python3</code>
<code>alternatives --set python /usr/bin/python3</code>
If you cannot set alternatives correctly, you can also run dbcollect directly with the right Python version:
<code>python3 /usr/local/bin/dbcollect</code>


== Git Clone issues ==
== Git Clone issues ==

Revision as of 09:30, 15 November 2024


Some known errors that happen when running dbcollect.

PK... errors

File "dbcollect", line 2
  PK"""

This means you are running a very old Python version (before 2.6) that does not understand Python ZipApp packages

Environment problems

/usr/bin/env: ‘python’: No such file or directory

This means python is not in $PATH. On more recent RHEL Linux variants (EL 8), you need to specify which Python major version is to be used. Select Python3 if unsure.

alternatives --set python /usr/bin/python3

If you cannot set alternatives correctly, you can also run dbcollect directly with the right Python version:

python3 /usr/local/bin/dbcollect

Git Clone issues

Error: No buildinfo

You are trying to run dbcollect using a cloned repository (git clone). dbcollect should run as a ZipApp package and be downloaded from Github Releases to be reliable. You can manually build dbcollect if you really want to use the git repository.

dbcollect must run from a ZipApp package, use https://github.com/outrunnl/dbcollect/releases/latest

Same as above except somehow you managed to create the buildinfo. Either go with the released ZipApp or follow the build procedure.