search

OllisGit / OctoPrint-FilamentManager

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

filament manager does not connect to either RPi postgresql or (omv based server ) postgresql #92

Open Doprintityourself opened 2 years ago

Doprintityourself commented 2 years ago

Again I cannot get filament manger to work! With new instance.

before I had one running prior to V1.9.1 but even former running octoprint client do connect any more after to the running seem after updating to 1.9.1.

New Database cannot be connected OMV based debian server:

I have set up everything working now on the new server omv based Postsql is up running sudo apt-get install libpq-dev python-dev ~/oprint/bin/pip install psycopg2 installed

Database ist setup and running sudo -u postgres -i createuser --interactive -P createdb -O octoprint octoprint_filamentmanager

grafik

made the appropriate changes: sudo nano /etc/postgresql/11/main/postgresql.conf grafik

sudo nano /etc/postgresql/11/main/pg_hba.conf

the entry host octoprint_filamentmanager octoprint 192.168.66.0/24 nor 92.168.0.0/24 md5 adapted for my network NEVER worked at any installations.

only in the old installation, when I added each single connecting pc or octoprint "instance IP" to the pg_hba.conf it seemd to allow connections.

since 1.9.1 I never achieved any successful connection any more to both postgresql installations from any octoprint clients.

First try without the explizit IP of the connecting Browser give this error grafik

After adding the line for 66.15

grafik 192.168.66.15 is the client Browser or

I get the next error , it seems do be able to connect somehow now after adding 192.168.66.15 but now it seems to refuse the TcP IP connection at all Prt 5432

So it seems to be able to connect through ..66.15 but the TCP IP connection is refused could connect to the old database with heidisql as an test

grafik grafik

So in this installation the question is why the postgresql refuses tcpip connection at all!?

so this my be the reason why octoprint is refused but with no error message at all after adding 66.15 to the conf file

The open question still to the filament-manager plugin still remains why has the connection on other octprint instances to the other working (pi postgresql) did stop working sind 1.9.1!?!

Is this the same problem now here with the new database and or is there a additional problem with the tcpip connection

Steps to reproduce

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior A clear and concise description of what you expected to happen.

Did the same happen when all other 3rd party plugins are disabled? If not which plugin is causing the issue?

Log file Drag and drop the octoprint.log here.

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

Additional context Add any other context about the problem octoprint (2).zip here.

Doprintityourself commented 2 years ago

uninstalled the plugin on a octoprint instance that used to connect to the pi database on 192.168.66.87 and re installed it, because I had more than once (older versions of filament manager) after a change that the plugin wont connect any more to the database. the only solution was to un and reinstall the plugin than suddenly the connection worked again. no here even remove and install V1.9.1 the plugin does not connect to the the working database with the same error than with the new database.

grafik