malnvenshorn / OctoPrint-FilamentManager

OctoPrint plugin to manage your filament inventory
GNU Affero General Public License v3.0
131 stars 59 forks source link

Can't connect to Postgres database #188

Closed ithelpme closed 4 years ago

ithelpme commented 4 years ago

Describe the bug I can't use postgres database. Specifically, in the octoprint log, I'm seeing No module named psycopg2. It is in fact installed using the path applicable to my install which is Octoprint Stretch so the path is ~/oprint/bin/pip . I've followed many guides but no luck. I've started all over using a brand new SD card to install Octoprint stretch and followed line by line on several guides and I can't get the Test Connection button to turn green. I installed Postgres on the raspberry pi itself and also tried using the postgres database on my UnRaid server.

Steps to reproduce Install Octoprint Stretch from scratch to Raspberry Pi 3B +. Followed this guide precisely: https://community.octoprint.org/t/filament-manager-plugin-how-to-setup-postgresql-database/10698

Expected behavior Button to turn green

Did the same happen when all other 3rd party plugins are disabled? No other plugins are installed other than Filament Manager

Log file Drag and drop the octoprint.log here.. Attached octoprint (5).log

Screenshots If applicable, add screenshots to help explain your problem.

Additional context Add any other context about the problem here.

ithelpme commented 4 years ago

Responding to my own post. Octoprint buster light or version .17 works fine so it must be some sort of interoperability with .16 and the psycopg2 module. I guess I will need to install .17 on all of my raspberry pi. Using Octoprint .17, I was able to connect to a Postgres on my UnRaid server without any issue which is my preferred way to use this plugin anyways. Thanks for creating this plugin

malnvenshorn commented 4 years ago

Great that you figured it out.

hermy65 commented 4 years ago

@ithelpme Im running into issues getting this to work with a postgres container on my unraid as well. Any input on what you did by chance?