You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i've followed the official install instruction for redhat with the following exceptions:
i'm using AWS RDS as my postgresql so while i did install postgres for the tools i'm not running the service
installed postgresql12-server explicitly since postgresql-server was giving me v10
sudo postgresql-setup --initdb not done since using RDS
updated /var/lib/pgsql/12/data/pg_hba.conf rather than /var/lib/pgsql/data/pg_hba.conf because that's where the v12 config is located. not sure this is even needed if i'm using RDS
did not start the postgresql service since i'm using RDS
psycopg2-binary does not support systems in FIPS mode. it must be compiled from source
uninstalled psycopg2
reinstalled psycopg2 from source (psycopg2[c])
nautobot-server migrate ran fine and i can see tables in the database
nautobot-server check shows no errors
nautobot-server runserver 0.0.0.0:8080 --insecure fires up with no issue
i don't see any service attached to port 8080 on the system
full disclosure, i did not use the runserver test at the point it occurs in the instructions and i went through the rest of the configuration. nginx was not showing as listening on any ports either which is why i fell back to the direct nautobot test
RHEL 8.10.0, FIPS enabled
Python 3.8.17
Nautobot 2.3.4
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
i've followed the official install instruction for redhat with the following exceptions:
i'm using AWS RDS as my postgresql so while i did install postgres for the tools i'm not running the service
psycopg2-binary does not support systems in FIPS mode. it must be compiled from source
nautobot-server migrate ran fine and i can see tables in the database
nautobot-server check shows no errors
nautobot-server runserver 0.0.0.0:8080 --insecure fires up with no issue
i don't see any service attached to port 8080 on the system
full disclosure, i did not use the runserver test at the point it occurs in the instructions and i went through the rest of the configuration. nginx was not showing as listening on any ports either which is why i fell back to the direct nautobot test
RHEL 8.10.0, FIPS enabled
Python 3.8.17
Nautobot 2.3.4
Beta Was this translation helpful? Give feedback.
All reactions