Issue Updating Filament Manager to 1.6.2

When trying to update my vanilla 1.4.2 Octoprint running on Octopi (Pi 4B)'s Filament Manager Plugin to the latest version, the following error is given:

Now updating Filament Manager to 1.6.2
/home/pi/oprint/bin/python2 -m pip --disable-pip-version-check install > --no-[...]
ERROR: Command errored out with exit status 1:
command: /home/pi/oprint/bin/python2 -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip->install-m3M3oY/psycopg2-binary/'"'"'; file='"'"'/tmp/pip-install-m3M3oY/psycopg2->binary/'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);'"'"'\r\n'"'"', >'"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' egg_info --egg-base /tmp/pip-install->m3M3oY/psycopg2-binary/pip-egg-info
cwd: /tmp/pip-install-m3M3oY/psycopg2-binary/
Complete output (23 lines):
running egg_info
creating /tmp/pip-install-m3M3oY/psycopg2-binary/pip-egg-info/psycopg2_binary.egg-info
writing /tmp/pip-install-m3M3oY/psycopg2-binary/pip-egg-info/psycopg2_binary.egg-info/PKG-INFO
writing top-level names to /tmp/pip-install-m3M3oY/psycopg2-binary/pip-egg->info/psycopg2_binary.egg-info/top_level.txt
writing dependency_links to /tmp/pip-install-m3M3oY/psycopg2-binary/pip-egg->info/psycopg2_binary.egg-info/dependency_links.txt
writing manifest file '/tmp/pip-install-m3M3oY/psycopg2-binary/pip-egg-info/psycopg2_binary.egg->info/SOURCES.txt'
Error: pg_config executable not found.
pg_config is required to build psycopg2 from source. Please add the directory
containing pg_config to the $PATH or specify the full executable path with the
python build_ext --pg-config /path/to/pg_config build ...
or with the pg_config option in 'setup.cfg'.
If you prefer to avoid building psycopg2 from source, please install the PyPI
'psycopg2-binary' package instead.
For further information please check the 'doc/src/install.rst' file (also at

ERROR: Command errored out with exit status 1: python egg_info Check the logs for full >command output.
The update did not finish successfully. Please consult octoprint.log and >plugin_softwareupdate_console.log for details.

Anything else I could do other than ignoring the update? Rebooting has not helped.

Seems this issue is reproducable by other users too:

1 Like

Issue seems to persist, but a workaround was found on the plugin's github issue page.

To save you some scrolling, the solution is to use ssh to your octopi (e.g. via Putty) and then run the following two commands:

sudo apt update
sudo apt-get install libpq-dev

After this, the normal installation routine from within octoprints web interface plugin update process will work.

1 Like

Thank you for sharing that here! Made it super easy.