Webodm --update don't update odm version

Hi, first of all thanks for the great work :pray:.
When I launch webodm update the version remains 2.8.7, is that right? I see the version in lightning node is 2.9.1, I guess it should update to this.

Thank you!

It might have installed on another drive, the installer likes large drives.

Wrong thread?
Thank you

I’m on ubuntu 22.04.

Sorry!

Welcome! Sorry for the trouble.

Have you issued a webodm.sh --stop before updating, then webodm.sh --start after? You should then see the new version in the processing node’s info page.

1 Like

Yes i did it. I run webodm as root it’s ok?

[email protected]:~/WebODM$ sudo ./webodm.sh stop
Checking for docker...   OK
Checking for docker-compose...   OK
Stopping WebODM...
docker-compose -f docker-compose.yml -f docker-compose.nodeodm.yml -f docker-compose.nodemicmac.yml stop
[email protected]:~/WebODM$ sudo ./webodm.sh update
docker-compose -f docker-compose.yml -f docker-compose.nodeodm.yml -f docker-compose.nodemicmac.yml down --remove-orphans
Removing webapp            ... done
Removing worker            ... done
Removing webodm_node-odm_1 ... done
Removing broker            ... done
Removing db                ... done
Removing network webodm_default
Updating WebODM...
git pull origin master
From https://github.com/OpenDroneMap/WebODM
 * branch            master     -> FETCH_HEAD
Already up to date.
docker-compose -f docker-compose.yml -f docker-compose.nodeodm.yml pull
Pulling broker   ... done
Pulling node-odm ... done
Pulling db       ... done
Pulling worker   ... done
Pulling webapp   ... done
Done! You can now start WebODM by running ./webodm.sh start
[email protected]:~/WebODM$ sudo ./webodm.sh start --gpu -media-dir /home/odm/ODM/data 
01:00.0 VGA compatible controller: NVIDIA Corporation GA104M [GeForce RTX 3070 Mobile / Max-Q] (rev a1)
01:00.1 Audio device: NVIDIA Corporation GA104 High Definition Audio Controller (rev a1)
GPU_NVIDIA has been found
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.gpu.nvidia.yml up --scale node-odm=1
Creating network "webodm_default" with the default driver
Creating webodm_node-odm_1 ... done
Creating broker            ... done
Creating db                ... done
Creating worker            ... done
Creating webapp            ... done
Attaching to broker, db, webodm_node-odm_1, worker, webapp
broker      | 1:C 23 Nov 2022 08:55:41.798 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
broker      | 1:C 23 Nov 2022 08:55:41.798 # Redis version=7.0.5, bits=64, commit=00000000, modified=0, pid=1, just started
broker      | 1:C 23 Nov 2022 08:55:41.798 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
db          | 
db          | PostgreSQL Database directory appears to contain a database; Skipping initialization
db          | 
broker      | 1:M 23 Nov 2022 08:55:41.799 * monotonic clock: POSIX clock_gettime
db          | LOG:  database system was shut down at 2022-11-23 08:51:31 UTC
broker      | 1:M 23 Nov 2022 08:55:41.799 * Running mode=standalone, port=6379.
worker      | Postgres is up - executing command
broker      | 1:M 23 Nov 2022 08:55:41.799 # Server initialized
broker      | 1:M 23 Nov 2022 08:55:41.799 # 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 23 Nov 2022 08:55:41.800 * Ready to accept connections
node-odm_1  | info: Authentication using NoTokenRequired
db          | LOG:  MultiXact member wraparound protections are now enabled
node-odm_1  | info: Listening on 0.0.0.0:6367 UDP for progress updates
db          | LOG:  database system is ready to accept connections
db          | LOG:  autovacuum launcher started
node-odm_1  | info: No tasks dump found
worker      | wait-for-it.sh: waiting for broker:6379 without a timeout
node-odm_1  | info: Checking for orphaned directories to be removed...
worker      | wait-for-it.sh: broker:6379 is available after 0 seconds
node-odm_1  | info: Server has started on port 3000
worker      | wait-for-it.sh: waiting for webapp:8000 without a timeout
webapp      | Postgres is up - executing command
webapp      | wait-for-it.sh: waiting for broker:6379 without a timeout
webapp      | wait-for-it.sh: broker:6379 is available after 0 seconds
webapp      | 
webapp      |  _       __     __    ____  ____  __  ___
webapp      | | |     / /__  / /_  / __ \/ __ \/  |/  /
webapp      | | | /| / / _ \/ __ \/ / / / / / / /|_/ / 
webapp      | | |/ |/ /  __/ /_/ / /_/ / /_/ / /  / /  
webapp      | |__/|__/\___/_.___/\____/_____/_/  /_/   
webapp      | 
webapp      | 
webapp      | Checking python version... 3.x, good!
webapp      | Checking GDAL version... GDAL 3.2.2, released 2021/03/05, excellent!
webapp      | Running migrations
webapp      | Generated secret key
webapp      | Operations to perform:
webapp      |   Apply all migrations: admin, app, auth, contenttypes, guardian, nodeodm, sessions
webapp      | Running migrations:
webapp      |   No migrations to apply.
webapp      | Checking for celery...   OK
webapp      | Scheduler is not running.
webapp      | Generating nginx configurations from templates...
webapp      | - nginx/nginx-ssl.conf
webapp      | - nginx/nginx.conf
worker      | wait-for-it.sh: webapp:8000 is available after 4 seconds
worker      | Checking for celery...   OK
worker      | Starting worker using broker at redis://broker
webapp      | celery beat v4.4.0 (cliffs) is starting.
webapp      | [2022-11-23 08:55:47 +0000] [144] [INFO] Starting gunicorn 19.7.1
webapp      | [2022-11-23 08:55:47 +0000] [144] [INFO] Listening at: unix:/tmp/gunicorn.sock (144)
webapp      | [2022-11-23 08:55:47 +0000] [144] [INFO] Using worker: sync
webapp      | /usr/lib/python3.9/os.py:1023: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used
webapp      |   return io.open(fd, *args, **kwargs)
webapp      | [2022-11-23 08:55:47 +0000] [195] [INFO] Booting worker with pid: 195
webapp      | [2022-11-23 08:55:47 +0000] [196] [INFO] Booting worker with pid: 196
webapp      | [2022-11-23 08:55:47 +0000] [197] [INFO] Booting worker with pid: 197
webapp      | __    -    ... __   -        _
webapp      | LocalTime -> 2022-11-23 08:55:47
webapp      | Configuration ->
webapp      |     . broker -> redis://broker:6379//
webapp      |     . loader -> celery.loaders.app.AppLoader
webapp      |     . scheduler -> celery.beat.PersistentScheduler
webapp      |     . db -> celerybeat-schedule
webapp      |     . logfile -> [stderr]@%WARNING
webapp      |     . maxinterval -> 5.00 minutes (300s)
webapp      | [2022-11-23 08:55:47 +0000] [198] [INFO] Booting worker with pid: 198
worker      | /usr/local/lib/python3.9/dist-packages/celery/platforms.py:800: RuntimeWarning: You're running the worker with superuser privileges: this is
worker      | absolutely not recommended!
worker      | 
worker      | Please specify a different user using the --uid option.
worker      | 
worker      | User information: uid=0 euid=0 gid=0 egid=0
worker      | 
worker      |   warnings.warn(RuntimeWarning(ROOT_DISCOURAGED.format(
webapp      | [2022-11-23 08:55:47 +0000] [199] [INFO] Booting worker with pid: 199
webapp      | [2022-11-23 08:55:47 +0000] [200] [INFO] Booting worker with pid: 200
webapp      | [2022-11-23 08:55:47 +0000] [201] [INFO] Booting worker with pid: 201
webapp      | [2022-11-23 08:55:47 +0000] [202] [INFO] Booting worker with pid: 202
webapp      | [2022-11-23 08:55:47 +0000] [203] [INFO] Booting worker with pid: 203
webapp      | [2022-11-23 08:55:47 +0000] [204] [INFO] Booting worker with pid: 204
webapp      | [2022-11-23 08:55:47 +0000] [205] [INFO] Booting worker with pid: 205
webapp      | [2022-11-23 08:55:47 +0000] [206] [INFO] Booting worker with pid: 206
webapp      | [2022-11-23 08:55:47 +0000] [207] [INFO] Booting worker with pid: 207
webapp      | [2022-11-23 08:55:47 +0000] [208] [INFO] Booting worker with pid: 208
webapp      | [2022-11-23 08:55:47 +0000] [209] [INFO] Booting worker with pid: 209
webapp      | [2022-11-23 08:55:48 +0000] [210] [INFO] Booting worker with pid: 210
webapp      | [2022-11-23 08:55:48 +0000] [211] [INFO] Booting worker with pid: 211
webapp      | [2022-11-23 08:55:48 +0000] [212] [INFO] Booting worker with pid: 212
webapp      | [2022-11-23 08:55:48 +0000] [213] [INFO] Booting worker with pid: 213
webapp      | [2022-11-23 08:55:48 +0000] [214] [INFO] Booting worker with pid: 214
webapp      | [2022-11-23 08:55:48 +0000] [215] [INFO] Booting worker with pid: 215
webapp      | [2022-11-23 08:55:48 +0000] [216] [INFO] Booting worker with pid: 216
webapp      | [2022-11-23 08:55:48 +0000] [217] [INFO] Booting worker with pid: 217
webapp      | [2022-11-23 08:55:48 +0000] [218] [INFO] Booting worker with pid: 218
webapp      | [2022-11-23 08:55:48 +0000] [219] [INFO] Booting worker with pid: 219
webapp      | [2022-11-23 08:55:48 +0000] [220] [INFO] Booting worker with pid: 220
webapp      | [2022-11-23 08:55:48 +0000] [221] [INFO] Booting worker with pid: 221
webapp      | [2022-11-23 08:55:48 +0000] [222] [INFO] Booting worker with pid: 222
webapp      | [2022-11-23 08:55:48 +0000] [223] [INFO] Booting worker with pid: 223
webapp      | [2022-11-23 08:55:48 +0000] [224] [INFO] Booting worker with pid: 224
webapp      | [2022-11-23 08:55:48 +0000] [225] [INFO] Booting worker with pid: 225
webapp      | [2022-11-23 08:55:48 +0000] [226] [INFO] Booting worker with pid: 226
webapp      | [2022-11-23 08:55:49 +0000] [227] [INFO] Booting worker with pid: 227
webapp      | 
webapp      | Trying to establish communication...
webapp      | INFO Booting WebODM 1.9.16
webapp      | INFO Registered [coreplugins.lightning.plugin]
webapp      | INFO Registered [coreplugins.fullscreen.plugin]
webapp      | INFO Registered [coreplugins.diagnostic.plugin]
webapp      | INFO Registered [coreplugins.measure.plugin]
webapp      | INFO Registered [coreplugins.contours.plugin]
webapp      | INFO Registered [coreplugins.posm-gcpi.plugin]
webapp      | INFO Registered [coreplugins.changedetection.plugin]
webapp      | 
webapp      | Congratulations! └@(・◡・)@┐
webapp      | ==========================
webapp      | 
webapp      | If there are no errors, WebODM should be up and running!
webapp      | 
webapp      | Open a web browser and navigate to http://localhost:8000
webapp      | 
webapp      | NOTE: Windows users using docker should replace localhost with the IP of their docker machine's IP. To find what that is, run: docker-machine ip
webapp      | WARNING Session data corrupted
webapp      | WARNING Session data corrupted
webapp      | WARNING Session data corrupted
webapp      | WARNING Session data corrupted
webapp      | WARNING Session data corrupted
webapp      | WARNING Session data corrupted
webapp      | WARNING Session data corrupted
webapp      | WARNING Session data corrupted
webapp      | WARNING Session data corrupted


1 Like

What happens if you don’t force the usage of the GPU node?

1 Like

The version without --gpu is 2.9.2!!!

1 Like

If I recall correctly, to update the GPU node you need to issue:

./webodm.sh update --gpu

2 Likes

You recall perfectly, it works!
Se passi per Trieste sarà un paicere offrirti una un calice! :wink:

3 Likes