FATAL: Ident authentication failed for user "netbox" #17412
-
Hello, I have been trying to move netbox from an old CentOS Stream 8 server to a RHEL 9. The version that I want to move is 2.11.11 (I had issues upgrading it on the old server because of ancient postgresql versions, so I want to move it and upgrade it there). As per the instructions (https://netboxlabs.com/docs/netbox/en/stable/installation/, https://netboxlabs.com/docs/netbox/en/stable/administration/replicating-netbox/), I have set up a new instance and imported the database. Import goes fine, the user is set up with the correct password.
But after runing ./upgrade.sh and accessing the server,
CMD login to DB works fine.
I do not know what else I can do to fix this issue. Any advice will be greatly apreciated. Logs, configs, etc...:./uprade.sh works fine (or at least I dont see any errors).
Configuration file:
Config copy went something like this (this was taken from the 2.9.0 to 2.11.11 upgrade, hence the oldver & newver):
PostgreSQL is listening.
PostgreSQL log is empty, it does not show any connection attempts. Todays log (/var/lib/pgsql/data/log/postgresql-Mon.log) is empty. After restarting postgresql service, it shows normal entries.
Some changes I did to postgresql to allow connections from CMD (/var/lib/pgsql/data/pg_hba.conf):
FW is shut down .
SELinux shows no errors (grep AVC /var/log/audit/audit.log -> no results). |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
I have no idea why the "wrong" python version is being reported. However, I will point out that you don't need to install 2.11.11 on the new server. You can install 3.7.8, which is the final version that can import a database from 2.11.x. This gives the following plan: First: install 3.7.8 on the new server (with an empty database), and test that it's working properly. No exceptions etc. You can create test sites and devices in this database to check. Second: drop the database, import the database dump from 2.11.11, and run Third: upgrade this system to the final version you want, e.g. v4.0.11 or v4.1.0 Doing it this way avoids the problems from installing an ancient Netbox on a modern system, especially broken dependencies. This is because Netbox installs are not reproducible; it doesn't define the exact or "frozen" full sent of dependencies, only a set of top-level constraints, and often new versions of packages are released which break those dependencies. If you must install v2.11.11 then there's a repo of netbox "freezes" out there somewhere. What I'm trying to say though is, because you're not trying to import your database from something earlier than 2.11, you can jump straight to 3.7 |
Beta Was this translation helpful? Give feedback.
I have no idea why the "wrong" python version is being reported.
However, I will point out that you don't need to install 2.11.11 on the new server. You can install 3.7.8, which is the final version that can import a database from 2.11.x.
This gives the following plan:
First: install 3.7.8 on the new server (with an empty database), and test that it's working properly. No exceptions etc. You can create test sites and devices in this database to check.
Second: drop the database, import the database dump from 2.11.11, and run
./upgrade.sh
. That will modify the database to work with 3.7.8. Again, check that it's all working, but this time it will have the imported data.Third: upgrade this s…