No problem, didn’t know it existed till this thread
1 Like
Just as an aside if in a project I click the DroneDB import button, I just end on a white screen
1 Like
I believe that is part of the same fix, but I’ll have to test again to be sure.
1 Like
did wonder if it might be connected
1 Like
Yep, this is all fixed on the current testing releases for Docker.
This should be tagged and packaged up for Windows once we roll up some other fixes and improvements.
1 Like
Brilliant, look forward to giving it a go👍
1 Like
Hello, any ETA on rolling out the new version? We are eager to test.
2 Likes
We recently tagged a new release of ODM (v3.1.1) with some important fixes for users with non-ASCII characters in their PATH, so very likely a new WebODM for Windows build will be generated and released shortly.
1 Like
Tried this with 2.0.1 on 2 machines and getting a failure on both
1 Like
Can confirm/reproduce on the Windows build (though not so on the Docker/Linux build).
I’ll make an issue.
Thanks for raising this!
No problem, you’re welcome👍
1 Like
I downloaded the latest version of WebODM (ver 2.0.1). Still erroring out. Same error.
1 Like
I have notified HeDoth who maintains the plugin, so we are waiting on a reproduction and fix.
In the meanwhile, though much less convenient, you can use the WebUI through dronedb.app to uload files or the all.zip
1 Like
10 Days have passed and no update. Do you want Log files to see what can be reproduced?
1 Like
Sure, logs are always helpful and will supplement what I sent them, so thank you.
app.log:
“Booting WebODM 2.0.1 build 88…”
“Trying to connect to NodeODM localhost:29301…”
“Attempt 0 failed, retrying…”
“nodeodm: info: Authentication using SimpleToken\r\n”
“nodeodm: info: Listening on 0.0.0.0:6367 UDP for progress updates\r\n”
“nodeodm: info: Initialized 0 tasks\r\n”
“nodeodm: info: Checking for orphaned directories to be removed…\r\n”
“nodeodm: info: Server has started on port 29301\r\n”
“Trying to connect to NodeODM localhost:29301…”
“Connected to NodeODM 2.2.2”
“redis-server: . \n .-__ ''-._ \n _.- . . ‘’-._ Redis 3.2.100 (00000000/0) 64 bit\n .- .-```. ```\\/ _.,_ ''-._ \n ( ' , .-` | `, ) Running in standalone mode\n |`-._`-...-` __...-.-.|'_.-'| Port: 29379\n | -. ._ / _.-' | PID: 62172\n -._ -._ -./ .-’ .-’ \n |-._-. -.__.-' _.-'_.-'| \n | -.-._ _.-'_.-' | http://redis.io \n -._ -._-..-'.-’ .-’ \n |-._-. -.__.-' _.-'_.-'| \n | -.-._ _.-'_.-' | \n -._ -._-..-‘_.-’ _.-’ \n -._ -..-’ _.-’ \n -._ _.-' \n -..-’ \n\n[62172] 15 May 14:15:52.867 # Server started, Redis version 3.2.100\n”
“redis-server: [62172] 15 May 14:15:52.873 * DB loaded from disk: 0.006 seconds\n[62172] 15 May 14:15:52.873 * The server is now ready to accept connections on port 29379\n”
“Trying to connect to postgres localhost:29543…”
“C:\WebODM\resources\app\apps\pgsql/bin/pg_ctl: server starting\r\n”
“C:\WebODM\resources\app\apps\pgsql/bin/psql: exited with code 0”
“python: Operations to perform:\r\n Apply all migrations: admin, app, auth, contenttypes, guardian, nodeodm, sessions\r\nRunning migrations:\r\n No migrations to apply.\r\n”
“python: exited with code 0”
“python: exited with code 0”
“python: INFO:waitress:Serving on http://127.0.0.1:29800\r\n”
“python: [2023-05-15 14:16:33,820: INFO/MainProcess] Connected to redis://:@127.0.0.1:29379//\r\n"
“python: [2023-05-15 14:16:33,837: INFO/MainProcess] mingle: searching for neighbors\r\n”
“python: INFO Booting WebODM 2.0.1\r\nINFO:app.logger:Booting WebODM 2.0.1\r\n”
“python: INFO Running npm install for [coreplugins.changedetection.plugin]\r\nINFO:app.logger:Running npm install for [coreplugins.changedetection.plugin]\r\n”
“python: WARNING npm is not installed, will skip this plugin\r\nWARNING:app.logger:npm is not installed, will skip this plugin\r\n”
“python: INFO Running npm install for [coreplugins.cloudimport.plugin]\r\nINFO:app.logger:Running npm install for [coreplugins.cloudimport.plugin]\r\n”
“python: WARNING npm is not installed, will skip this plugin\r\nWARNING:app.logger:npm is not installed, will skip this plugin\r\n”
“python: INFO Running npm install for [coreplugins.dronedb.plugin]\r\nINFO:app.logger:Running npm install for [coreplugins.dronedb.plugin]\r\n”
“python: WARNING npm is not installed, will skip this plugin\r\nWARNING:app.logger:npm is not installed, will skip this plugin\r\n”
“python: INFO Running npm install for [coreplugins.elevationmap.plugin]\r\nINFO:app.logger:Running npm install for [coreplugins.elevationmap.plugin]\r\n”
“python: WARNING npm is not installed, will skip this plugin\r\nWARNING:app.logger:npm is not installed, will skip this plugin\r\n”
“python: INFO Running npm install for [coreplugins.measure.plugin]\r\nINFO:app.logger:Running npm install for [coreplugins.measure.plugin]\r\n”
“python: WARNING npm is not installed, will skip this plugin\r\nWARNING:app.logger:npm is not installed, will skip this plugin\r\n”
“python: INFO Registered [coreplugins.contours.plugin]\r\nINFO:app.logger:Registered [coreplugins.contours.plugin]\r\n”
“python: INFO Registered [coreplugins.diagnostic.plugin]\r\nINFO:app.logger:Registered [coreplugins.diagnostic.plugin]\r\nINFO Registered [coreplugins.dronedb.plugin]\r\nINFO:app.logger:Registered [coreplugins.dronedb.plugin]\r\n”
“python: [2023-05-15 14:16:34,886: INFO/MainProcess] mingle: all alone\r\n”
"python: [2023-05-15 14:16:34,927: INFO/MainProcess] pidbox: Connected to redis://:@127.0.0.1:29379//.\r\n”
“python: [2023-05-15 14:16:34,939: INFO/MainProcess] celery@DESKTOP-UKSL16I ready.\r\n”
“python: [2023-05-15 14:16:34,969: INFO/MainProcess] Received task: worker.tasks.cleanup_tmp_directory[7fddf6e6-53e9-4519-87b8-a4b5deb3111d] expires:[2023-05-15 18:46:32.744421+00:00]\r\n”
“python: [2023-05-15 14:16:34,982: INFO/MainProcess] Task worker.tasks.cleanup_tmp_directory[7fddf6e6-53e9-4519-87b8-a4b5deb3111d] succeeded in 0.0s: None\r\n”
“python: INFO Installing requirements.txt for [coreplugins.elevationmap.plugin]\r\nINFO:app.logger:Installing requirements.txt for [coreplugins.elevationmap.plugin]\r\n”
“python: Collecting geojson==2.4.1\r\n”
“python: Using cached geojson-2.4.1-py2.py3-none-any.whl (15 kB)\r\n”
“python: Collecting opencv-python-headless==4.4.0.46\r\n”
“python: Using cached opencv_python_headless-4.4.0.46-cp39-cp39-win_amd64.whl (33.4 MB)\r\n”
“python: Collecting numpy>=1.19.3\r\n”
“python: Using cached numpy-1.24.3-cp39-cp39-win_amd64.whl (14.9 MB)\r\n”
“python: Installing collected packages: numpy, opencv-python-headless, geojson\r\n”
“python: Successfully installed geojson-2.4.1 numpy-1.24.3 opencv-python-headless-4.4.0.46\r\n”
“python: WARNING: You are using pip version 21.2.4; however, version 23.1.2 is available.\r\nYou should consider upgrading via the ‘C:\WebODM\resources\app\apps\grass78\Python39\python.exe -m pip install --upgrade pip’ command.\r\n”
“python: WARNING Failed to install requirements.txt for [coreplugins.elevationmap.plugin]\r\nWARNING:app.logger:Failed to install requirements.txt for [coreplugins.elevationmap.plugin]\r\nINFO Registered [coreplugins.elevationmap.plugin]\r\nINFO:app.logger:Registered [coreplugins.elevationmap.plugin]\r\n”
“python: INFO Registered [coreplugins.fullscreen.plugin]\r\nINFO:app.logger:Registered [coreplugins.fullscreen.plugin]\r\nINFO Registered [coreplugins.lightning.plugin]\r\nINFO:app.logger:Registered [coreplugins.lightning.plugin]\r\nINFO Registered [coreplugins.measure.plugin]\r\nINFO:app.logger:Registered [coreplugins.measure.plugin]\r\n”
“python: INFO Registered [coreplugins.openaerialmap.plugin]\r\nINFO:app.logger:Registered [coreplugins.openaerialmap.plugin]\r\nINFO Registered [coreplugins.osm-quickedit.plugin]\r\nINFO:app.logger:Registered [coreplugins.osm-quickedit.plugin]\r\n”
“python: INFO Registered [coreplugins.posm-gcpi.plugin]\r\nINFO:app.logger:Registered [coreplugins.posm-gcpi.plugin]\r\n”
“python: INFO Registered [coreplugins.shortlinks.plugin]\r\nINFO:app.logger:Registered [coreplugins.shortlinks.plugin]\r\n”
“redis-server: [62172] 15 May 14:20:53.078 * 10 changes in 300 seconds. Saving…\n”
“redis-server: [62172] 15 May 14:20:53.088 * Background saving started by pid 25716\n”
“redis-server: [62172] 15 May 14:20:53.310 # fork operation complete\n”
“redis-server: [62172] 15 May 14:20:53.312 * Background saving terminated with success\n”
“python: [2023-05-15 14:21:04,543: INFO/MainProcess] Received task: coreplugins.dronedb.api_views.share_to_ddb[5ea1618d-853e-4cd0-8fe3-467dcde77e8a] \r\n”
“python: INFO Logged in to DroneDB as user snyderld.\r\n”
“python: [2023-05-15 14:21:05,650: INFO/MainProcess] coreplugins.dronedb.api_views.share_to_ddb[5ea1618d-853e-4cd0-8fe3-467dcde77e8a]: Logged in to DroneDB as user snyderld.\r\n”
“python: INFO Error uploading file odm_report\report.pdf: Failed to upload file… Retrying…\r\n[2023-05-15 14:21:13,326: INFO/MainProcess] coreplugins.dronedb.api_views.share_to_ddb[5ea1618d-853e-4cd0-8fe3-467dcde77e8a]: Error uploading file odm_report\report.pdf: Failed to upload file… Retrying…\r\n”
“python: INFO Error uploading file odm_report\report.pdf: Failed to upload file… Retrying…\r\n[2023-05-15 14:21:20,283: INFO/MainProcess] coreplugins.dronedb.api_views.share_to_ddb[5ea1618d-853e-4cd0-8fe3-467dcde77e8a]: Error uploading file odm_report\report.pdf: Failed to upload file… Retrying…\r\n”
“python: ERROR Error uploading file odm_report\report.pdf: Failed to upload file.\r\n[2023-05-15 14:21:27,254: ERROR/MainProcess] coreplugins.dronedb.api_views.share_to_ddb[5ea1618d-853e-4cd0-8fe3-467dcde77e8a]: Error uploading file odm_report\report.pdf: Failed to upload file.\r\n”
“python: [2023-05-15 14:21:27,268: INFO/MainProcess] Task coreplugins.dronedb.api_views.share_to_ddb[5ea1618d-853e-4cd0-8fe3-467dcde77e8a] succeeded in 22.71799999999348s: None\r\n”
“redis-server: [62172] 15 May 14:25:54.065 * 10 changes in 300 seconds. Saving…\n”
“redis-server: [62172] 15 May 14:25:54.469 * Background saving started by pid 71928\n”
“redis-server: [62172] 15 May 14:25:54.688 # fork operation complete\n”
“redis-server: [62172] 15 May 14:25:54.690 * Background saving terminated with success\n”
“redis-server: [62172] 15 May 14:30:55.019 * 10 changes in 300 seconds. Saving…\n”
“redis-server: [62172] 15 May 14:30:55.025 * Background saving started by pid 70248\n”
“redis-server: [62172] 15 May 14:30:55.238 # fork operation complete\n”
“redis-server: [62172] 15 May 14:30:55.239 * Background saving terminated with success\n”
1 Like
pgsql.log:
LOG: database system was shut down at 2023-01-16 21:11:31 EST
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
FATAL: password authentication failed for user “postgres”
DETAIL: Password does not match for user “postgres”.
Connection matched pg_hba.conf line 86: “host all all ::1/128 password”
LOG: received fast shutdown request
LOG: aborting any active transactions
LOG: autovacuum launcher shutting down
FATAL: terminating connection due to administrator command
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2023-03-05 20:45:03 EST
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
LOG: received fast shutdown request
LOG: aborting any active transactions
FATAL: terminating connection due to administrator command
FATAL: terminating connection due to administrator command
FATAL: terminating connection due to administrator command
FATAL: terminating connection due to administrator command
FATAL: terminating connection due to administrator command
FATAL: terminating connection due to administrator command
FATAL: terminating connection due to administrator command
FATAL: terminating connection due to administrator command
FATAL: terminating connection due to administrator command
LOG: autovacuum launcher shutting down
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2023-03-05 21:10:58 EST
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
LOG: received fast shutdown request
LOG: aborting any active transactions
FATAL: terminating connection due to administrator command
FATAL: terminating connection due to administrator command
LOG: autovacuum launcher shutting down
FATAL: terminating connection due to administrator command
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2023-03-06 06:16:45 EST
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
LOG: received fast shutdown request
LOG: aborting any active transactions
FATAL: terminating connection due to administrator command
FATAL: terminating connection due to administrator command
LOG: autovacuum launcher shutting down
FATAL: terminating connection due to administrator command
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2023-03-06 07:31:13 EST
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
LOG: received fast shutdown request
LOG: aborting any active transactions
FATAL: terminating connection due to administrator command
FATAL: terminating connection due to administrator command
FATAL: terminating connection due to administrator command
FATAL: terminating connection due to administrator command
FATAL: terminating connection due to administrator command
FATAL: terminating connection due to administrator command
FATAL: terminating connection due to administrator command
FATAL: terminating connection due to administrator command
LOG: autovacuum launcher shutting down
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2023-03-12 14:27:37 EDT
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
LOG: received fast shutdown request
LOG: aborting any active transactions
FATAL: terminating connection due to administrator command
FATAL: terminating connection due to administrator command
FATAL: terminating connection due to administrator command
FATAL: terminating connection due to administrator command
LOG: autovacuum launcher shutting down
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2023-03-19 07:53:43 EDT
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
LOG: CreateProcess call failed: A blocking operation was interrupted by a call to WSACancelBlockingCall.
(error code 1455)
LOG: could not fork new process for connection: No error
LOG: received fast shutdown request
LOG: aborting any active transactions
LOG: autovacuum launcher shutting down
FATAL: terminating connection due to administrator command
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2023-03-21 11:04:47 EDT
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
LOG: received fast shutdown request
LOG: aborting any active transactions
FATAL: terminating connection due to administrator command
STATEMENT: SELECT “app_project”.“id”, “app_project”.“owner_id”, “app_project”.“name”, “app_project”.“description”, “app_project”.“created_at”, “app_project”.“deleting”, COUNT(“app_task”.“id”) AS “tasks_count” FROM “app_project” LEFT OUTER JOIN “app_task” ON (“app_project”.“id” = “app_task”.“project_id”) WHERE “app_project”.“deleting” = true GROUP BY “app_project”.“id” HAVING COUNT(“app_task”.“id”) = 0
LOG: autovacuum launcher shutting down
FATAL: terminating connection due to administrator command
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2023-03-22 08:48:16 EDT
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
LOG: received fast shutdown request
LOG: aborting any active transactions
LOG: autovacuum launcher shutting down
FATAL: terminating connection due to administrator command
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2023-03-23 00:58:35 EDT
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
LOG: received fast shutdown request
LOG: aborting any active transactions
LOG: autovacuum launcher shutting down
FATAL: terminating connection due to administrator command
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2023-03-23 20:34:35 EDT
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
LOG: received fast shutdown request
LOG: aborting any active transactions
FATAL: terminating connection due to administrator command
FATAL: terminating connection due to administrator command
FATAL: terminating connection due to administrator command
LOG: autovacuum launcher shutting down
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2023-03-29 03:21:07 EDT
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
LOG: received fast shutdown request
LOG: aborting any active transactions
LOG: autovacuum launcher shutting down
FATAL: terminating connection due to administrator command
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2023-04-01 07:05:22 EDT
LOG: MultiXact member wraparound protections are now enabled
FATAL: the database system is starting up
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
FATAL: password authentication failed for user “postgres”
DETAIL: Password does not match for user “postgres”.
Connection matched pg_hba.conf line 86: “host all all ::1/128 password”
LOG: could not receive data from client: An existing connection was forcibly closed by the remote host.
LOG: could not receive data from client: An existing connection was forcibly closed by the remote host.
LOG: could not receive data from client: An existing connection was forcibly closed by the remote host.
LOG: received fast shutdown request
LOG: aborting any active transactions
LOG: autovacuum launcher shutting down
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2023-04-05 20:50:57 EDT
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
LOG: received fast shutdown request
LOG: aborting any active transactions
LOG: autovacuum launcher shutting down
FATAL: terminating connection due to administrator command
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2023-04-05 20:52:24 EDT
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
LOG: received fast shutdown request
LOG: aborting any active transactions
FATAL: terminating connection due to administrator command
LOG: autovacuum launcher shutting down
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2023-04-13 17:03:54 EDT
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
LOG: received fast shutdown request
LOG: aborting any active transactions
LOG: autovacuum launcher shutting down
FATAL: terminating connection due to administrator command
FATAL: terminating autovacuum process due to administrator command
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2023-04-23 14:56:57 EDT
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
LOG: received fast shutdown request
LOG: aborting any active transactions
FATAL: terminating connection due to administrator command
FATAL: terminating connection due to administrator command
FATAL: terminating connection due to administrator command
FATAL: terminating connection due to administrator command
LOG: autovacuum launcher shutting down
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2023-05-05 17:48:18 EDT
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
LOG: could not receive data from client: An existing connection was forcibly closed by the remote host.
LOG: could not receive data from client: An existing connection was forcibly closed by the remote host.
LOG: received fast shutdown request
LOG: aborting any active transactions
LOG: autovacuum launcher shutting down
ERROR: canceling statement due to user request
LOG: autovacuum launcher shutting down
ERROR: canceling statement due to user request
LOG: autovacuum launcher shutting down
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2023-05-05 17:54:29 EDT
LOG: MultiXact member wraparound protections are now enabled
FATAL: the database system is starting up
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
FATAL: password authentication failed for user “postgres”
DETAIL: Password does not match for user “postgres”.
Connection matched pg_hba.conf line 86: “host all all ::1/128 password”
LOG: received fast shutdown request
LOG: aborting any active transactions
FATAL: terminating connection due to administrator command
LOG: autovacuum launcher shutting down
FATAL: terminating connection due to administrator command
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2023-05-06 06:38:38 EDT
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
LOG: received fast shutdown request
LOG: aborting any active transactions
LOG: autovacuum launcher shutting down
FATAL: terminating connection due to administrator command
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2023-05-10 09:13:26 EDT
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
LOG: received fast shutdown request
LOG: aborting any active transactions
FATAL: terminating connection due to administrator command
FATAL: terminating connection due to administrator command
LOG: autovacuum launcher shutting down
FATAL: terminating connection due to administrator command
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2023-05-15 11:21:30 EDT
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
1 Like
I downloaded version 2.0.1 build 88 and still has the same error on mi side.
1 Like
Welcome!
Correct, the fix has not been implemented into the latest releases yet.
We are working on it, though.
3 Likes
Is there a guide on how and what to manually upload the data?
1 Like