Hello,
I’m back with a new machine (fujitsu primergy tx1310 m3) with a Intel(R) Xeon(R) CPU E3-1225 v6 @ 3.30GHz and 64GB of ram and 2x1tb and a nvidia quadro P400.
Clean install of ubuntu 22.04 and all the software needed to run webodm.
Did all the setup to run the nvidia-docker and try out the GPU option.
All went well until I ran the webodm.sh start and it doesn’t run with a log like this:
[email protected]:~/WebODM$ sudo ./webodm.sh start
[sudo] password for carlossousa:
Checking for docker… OK
Checking for docker-compose… OK
Starting WebODM…
Using the following environment:
Host: localhost
Port: 8000
Media directory: appmedia
SSL: NO
SSL key:
SSL certificate:
SSL insecure port redirect: 80
Celery Broker: redis://broker
Default Nodes: 1
Make sure to issue a ./webodm.sh down if you decide to change the environment.
docker-compose -f docker-compose.yml -f docker-compose.nodeodm.yml up --scale node-odm=1
Creating network “webodm_default” with the default driver
Creating webodm_node-odm_1 … done
Creating db … done
Creating broker … done
Creating worker … done
Creating webapp … done
Attaching to db, broker, webodm_node-odm_1, worker, webapp
db |
db | PostgreSQL Database directory appears to contain a database; Skipping initialization
db |
db | LOG: database system was interrupted; last known up at 2022-09-09 22:16:36 UTC
broker | 1:C 09 Sep 2022 22:44:33.684 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
broker | 1:C 09 Sep 2022 22:44:33.684 # Redis version=7.0.4, bits=64, commit=00000000, modified=0, pid=1, just started
broker | 1:C 09 Sep 2022 22:44:33.684 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
db | LOG: database system was not properly shut down; automatic recovery in progress
broker | 1:M 09 Sep 2022 22:44:33.685 * monotonic clock: POSIX clock_gettime
db | LOG: invalid record length at 0/1702C48
db | LOG: redo is not required
broker | 1:M 09 Sep 2022 22:44:33.685 * Running mode=standalone, port=6379.
db | LOG: MultiXact member wraparound protections are now enabled
node-odm_1 | info: Authentication using NoTokenRequired
db | LOG: database system is ready to accept connections
broker | 1:M 09 Sep 2022 22:44:33.685 # Server initialized
broker | 1:M 09 Sep 2022 22:44:33.685 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add ‘vm.overcommit_memory = 1’ to /etc/sysctl.conf and then reboot or run the command ‘sysctl vm.overcommit_memory=1’ for this to take effect.
broker | 1:M 09 Sep 2022 22:44:33.685 * Ready to accept connections
worker | psql: error: FATAL: no pg_hba.conf entry for host “172.26.0.5”, user “postgres”, database “postgres”
db | LOG: autovacuum launcher started
db | FATAL: no pg_hba.conf entry for host “172.26.0.5”, user “postgres”, database “postgres”
node-odm_1 | info: Listening on 0.0.0.0:6367 UDP for progress updates
db | FATAL: no pg_hba.conf entry for host “172.26.0.5”, user “postgres”, database “postgres”
worker | Postgres is unavailable - sleeping
node-odm_1 | info: No tasks dump found
db | FATAL: no pg_hba.conf entry for host “172.26.0.5”, user “postgres”, database “postgres”
node-odm_1 | info: Checking for orphaned directories to be removed…
node-odm_1 | info: Server has started on port 3000
worker | psql: error: FATAL: no pg_hba.conf entry for host “172.26.0.5”, user “postgres”, database “postgres”
worker | Postgres is unavailable - sleeping
worker | psql: error: FATAL: no pg_hba.conf entry for host “172.26.0.5”, user “postgres”, database “postgres”
worker | Postgres is unavailable - sleeping
db | FATAL: no pg_hba.conf entry for host “172.26.0.6”, user “postgres”, database “postgres”
webapp | psql: error: FATAL: no pg_hba.conf entry for host “172.26.0.6”, user “postgres”, database “postgres”
webapp | Postgres is unavailable - sleeping
db | FATAL: no pg_hba.conf entry for host “172.26.0.5”, user “postgres”, database “postgres”
worker | psql: error: FATAL: no pg_hba.conf entry for host “172.26.0.5”, user “postgres”, database “postgres”
worker | Postgres is unavailable - sleeping
db | FATAL: no pg_hba.conf entry for host “172.26.0.6”, user “postgres”, database “postgres”
webapp | psql: error: FATAL: no pg_hba.conf entry for host “172.26.0.6”, user “postgres”, database “postgres”
webapp | Postgres is unavailable - sleeping
worker | psql: error: FATAL: no pg_hba.conf entry for host “172.26.0.5”, user “postgres”, database “postgres”
db | FATAL: no pg_hba.conf entry for host “172.26.0.5”, user “postgres”, database “postgres”
worker | Postgres is unavailable - sleeping
db | FATAL: no pg_hba.conf entry for host “172.26.0.6”, user “postgres”, database “postgres”
webapp | psql: error: FATAL: no pg_hba.conf entry for host “172.26.0.6”, user “postgres”, database “postgres”
webapp | Postgres is unavailable - sleeping
db | FATAL: no pg_hba.conf entry for host “172.26.0.5”, user “postgres”, database “postgres”
worker | psql: error: FATAL: no pg_hba.conf entry for host “172.26.0.5”, user “postgres”, database “postgres”
…
and so on.
Did a webodm.sh rebuild and it still gives out the same information about postgres.
I’m out of ideas …
Any help?
Thanks