" Cannot process dataset " since update this morning to 1.9.14 built 61

Hi all,

I have problems with this last update guys. The dataset that webODM processed yesterday without any problem it cannot be processed today before update. Indeed, non of my datasets can be processed now.

Has anybody the same problem before updating or reinstalling WebODM recently ? how could I reinstall previous version?

Thanks in advance.

1 Like

Mm, strange. Can you share the task output?

1 Like

I can’t reproduce locally.

Anything special about your machine? What are your specifications?

default ‘High resolution’ option… I’ve nothing changed.

1 Like

specs :

Microsoft Windows 10 Professional (x64) Build 19044.1706

Intel C236 (Skylake PCH-H), Intel Core i7-7700

Number Of Processor Cores: 4

NVIDIA Quadro P600, 2048 MBytes of GDDR5 SDRAM [Samsung]

Total Memory Size: 32 GBytes

Samsung SSD 860 QVO 1TB, 142 GB free space (1000 GB).

I didn’t have any problem before update so I think the problem came from there… I would like to install any previous version but I don’t now how :frowning:

1 Like

Hello. First of all to indicate that I am new to all this and that my computer knowledge is limited.
Yesterday I had the same problem, with the same message. I have solved it by disabling the antivirus and malware search engine.

Hope that helps.

Greetings.

1 Like

Can you re-try with Default instead of High Resolution on a known-good dataset like Brighton Beach?

no, it doesn’t work… :frowning:

same erreur “Cannot process dataset”

1 Like

It does not work for me without antivirus. Gracias de todas formas

1 Like

Can you supply the full processing log so we can read what is going on?

app.log

“python: [2022-05-19 16:14:21,657: INFO/MainProcess] Received task: worker.tasks.process_task[3f27f8ac-8496-4b5e-a81f-d02c9eaf55d6] \r\n”
“python: [2022-05-19 16:14:21,690: INFO/MainProcess] Task worker.tasks.process_task[3f27f8ac-8496-4b5e-a81f-d02c9eaf55d6] succeeded in 0.03200000000288128s: None\r\n”
“python: [2022-05-19 16:14:21,705: INFO/MainProcess] Received task: worker.tasks.process_task[da860f26-0af1-4927-a0f4-e2f0f17c41a5] \r\n”
“python: INFO Restarting Task [Brighton Beach Road - 23/06/2016] (7752bb9c-102c-4cf9-a859-132e7f863834)\r\n[2022-05-19 16:14:21,747: INFO/MainProcess] worker.tasks.process_task[da860f26-0af1-4927-a0f4-e2f0f17c41a5]: Restarting Task [Brighton Beach Road - 23/06/2016] (7752bb9c-102c-4cf9-a859-132e7f863834)\r\n”
“nodeodm: info: About to run: U:\WebODM\resources\app\apps\ODM\run.bat --rerun-from odm_postprocess --auto-boundary --dsm --pc-ept --cog --project-path U:\WebODM\resources\app\apps\NodeODM\data 5ece4533-e9dd-4dbf-83e4-0e08829064df\r\n”
“python: [2022-05-19 16:14:22,202: INFO/MainProcess] Task worker.tasks.process_task[da860f26-0af1-4927-a0f4-e2f0f17c41a5] succeeded in 0.5s: None\r\n”
“python: [2022-05-19 16:14:24,847: INFO/MainProcess] Received task: worker.tasks.process_task[4fe866e1-6718-48af-9573-67bbf620aebf] \r\n”
“python: INFO Processing status: 30 for Task [Brighton Beach Road - 23/06/2016] (7752bb9c-102c-4cf9-a859-132e7f863834)\r\n[2022-05-19 16:14:26,128: INFO/MainProcess] worker.tasks.process_task[4fe866e1-6718-48af-9573-67bbf620aebf]: Processing status: 30 for Task [Brighton Beach Road - 23/06/2016] (7752bb9c-102c-4cf9-a859-132e7f863834)\r\n”
“python: [2022-05-19 16:14:26,137: INFO/MainProcess] Task worker.tasks.process_task[4fe866e1-6718-48af-9573-67bbf620aebf] succeeded in 1.2809999999990396s: None\r\n”
“redis-server: [4768] 19 May 16:16:57.030 * 10 changes in 300 seconds. Saving…\n”
“redis-server: [4768] 19 May 16:16:57.038 * Background saving started by pid 4260\n”
“redis-server: [4768] 19 May 16:16:57.142 # fork operation complete\n”
“redis-server: [4768] 19 May 16:16:57.142 * Background saving terminated with success\n”

pgsql.log

LOG: database system was shut down at 2022-05-17 16:38:54 EDT
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
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
FATAL: terminating connection due to administrator command
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2022-05-19 04:21:56 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: unrecognized winsock error 10054
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 2022-05-19 05:10:57 EDT
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started

Samuel, have you tried uninstalling, rebooting, and then installing the latest release?

Hi,

Yes, I did that, and the same problem appeared after the new install. That’s why I would like to try installing previous version, but I don’t know how to find it.

1 Like

We don’t keep an archive of prior WebODM for Windows releases as we’re on a rolling-release and don’t support superseded releases.

Can you write into [email protected] so we can schedule a remote support session so I can take a look at what is going on?

1 Like

I did as you told me. I have send a mail to ‘[email protected]:slight_smile:

1 Like

Hi again Saijin,

I’ve tried the new update (13/6/2022) as you told me in our last conversation. Unfortunately the same error message appears :

I’m gonna try uninstalling Qgis.

1 Like

Nothing changed after Qgis (OsGeo) uninstalled neither. Same WebODM error :frowning:

I’ve installed last WebODM version with the adresse you send to me on my personal pc and it’s ok, but I need WebODM to be “repaired” on my enterprise’s pc witch I use daily to create orthophotos from drone images. If you have any suggestion…

1 Like

Not at this juncture, no. Our updates recently were to address this issue, so I might have to remote in and work on your enterprise PC to see what is going on.

E-mail me again so we can schedule something, if you don’t mind.

I’ve just send you an email. :+1:

1 Like