HELP problemi all'apertura di ODM

ho un problema all’apertura di ODM e non riesco a risolverlo qualcuno mi puo aiutare
Questi sono il file log che mi davaProcessing: app.log…
Processing: pgsql.log…“Trying to connect to NodeODM localhost:29301…”
“Attempt 0 failed, retrying…”
“Trying to connect to NodeODM localhost:29301…”
“Attempt 1 failed, retrying…”
“Trying to connect to NodeODM localhost:29301…”
“Attempt 2 failed, retrying…”
“Trying to connect to NodeODM localhost:29301…”
“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 6 tasks\r\n”
“nodeodm: info: Checking for orphaned directories to be removed…\r\n”
“nodeodm: info: About to run: C:\WebODM\resources\app\apps\ODM\run.bat --ignore-gsd --pc-quality high --dsm --dem-resolution 2 --orthophoto-resolution 2 --pc-ept --project-path C:\WebODM\resources\app\apps\NodeODM\data 4eb6ce9e-f089-48ac-85d0-4f9755f02119\r\n”
“nodeodm: info: Server has started on port 29301\r\n”
“Connected to NodeODM 2.1.5”
"redis-server: .
LOG: database system was shut down at 2021-06-01 20:58:34 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”
FATAL: the database system is starting up
LOG: database system was interrupted; last known up at 2021-06-02 04:34:24 EDT
LOG: database system was not properly shut down; automatic recovery in progress
LOG: redo starts at 0/CAE1CE8
LOG: invalid record length at 0/CB03090: wanted 24, got 0
LOG: redo done at 0/CB03068
LOG: last completed transaction was at log time 2021-06-02 04:38:22.532155-04
FATAL: the database system is starting up
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: database system was interrupted; last known up at 2021-06-07 11:06:23 EDT
FATAL: the database system is starting up
LOG: database system was not properly shut down; automatic recovery in progress
LOG: invalid record length at 0/CBFD298: wanted 24, got 0
LOG: redo is not required
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
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 2021-06-09 07:19:28 EDT
FATAL: the database system is starting up
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
FATAL: the database system is starting up
LOG: autovacuum launcher started
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 2021-06-09 15:15:56 EDT
FATAL: the database system is starting up
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
FATAL: the database system is starting up
LOG: autovacuum launcher started
LOG: received fast shutdown request
LOG: aborting any active transactions
LOG: autovacuum launcher shutting down
LOG: shutting down
LOG: database system is shut down
FATAL: the database system is starting up
LOG: database system was shut down at 2021-06-10 04:03:29 EDT
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
LOG: database system was interrupted; last known up at 2021-07-06 15:32:23 EDT
FATAL: the database system is starting up
LOG: database system was not properly shut down; automatic recovery in progress
LOG: invalid record length at 0/EAC56F8: wanted 24, got 0
LOG: redo is not required
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
FATAL: the database system is starting up
LOG: autovacuum launcher started
FATAL: the database system is starting up
LOG: database system was interrupted; last known up at 2021-07-13 20:10:38 EDT
LOG: database system was not properly shut down; automatic recovery in progress
LOG: redo starts at 0/F8FA370
LOG: invalid record length at 0/F9037A0: wanted 24, got 0
LOG: redo done at 0/F903778
LOG: last completed transaction was at log time 2021-07-13 20:10:51.946587-04
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
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2021-07-14 00:32:19 EDT
FATAL: the database system is starting up
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 2021-07-14 10:18:29 EDT
FATAL: the database system is starting up
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
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2021-10-24 05:03:04 EDT
FATAL: the database system is starting up
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
FATAL: the database system is starting up
LOG: autovacuum launcher started
LOG: received fast shutdown request
LOG: aborting any active transactions
FATAL: terminating autovacuum process due to administrator command
LOG: autovacuum launcher shutting down
FATAL: the database system is shutting down
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2021-11-14 12:03:17 EST
FATAL: the database system is starting up
FATAL: the database system is starting up
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
WARNING: worker took too long to start; canceled
WARNING: autovacuum worker started without a worker entry
LOG: could not rename temporary statistics file “pg_stat_tmp/global.tmp” to “pg_stat_tmp/global.stat”: Permission denied
LOG: using stale statistics instead of current ones because stats collector is not responding
LOG: database system was interrupted; last known up at 2021-11-14 16:47:00 EST
FATAL: the database system is starting up
LOG: database system was not properly shut down; automatic recovery in progress
FATAL: the database system is starting up
LOG: redo starts at 0/10F8B378
LOG: invalid record length at 0/10F8CC10: wanted 24, got 0
LOG: redo done at 0/10F8CBA0
LOG: last completed transaction was at log time 2021-11-14 16:46:59.028949-05
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
ERROR: missing chunk number 0 for toast value 78790 in pg_toast_18068
STATEMENT: SELECT “nodeodm_processingnode”.“id”, “nodeodm_processingnode”.“hostname”, “nodeodm_processingnode”.“port”, “nodeodm_processingnode”.“api_version”, “nodeodm_processingnode”.“last_refreshed”, “nodeodm_processingnode”.“queue_count”, “nodeodm_processingnode”.“available_options”, “nodeodm_processingnode”.“token”, “nodeodm_processingnode”.“max_images”, “nodeodm_processingnode”.“engine_version”, “nodeodm_processingnode”.“label”, “nodeodm_processingnode”.“engine” FROM “nodeodm_processingnode” WHERE “nodeodm_processingnode”.“hostname” = ‘127.0.0.1’ FOR UPDATE
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 2021-11-14 17:04:00 EST
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
ERROR: missing chunk number 0 for toast value 78790 in pg_toast_18068
STATEMENT: SELECT “nodeodm_processingnode”.“id”, “nodeodm_processingnode”.“hostname”, “nodeodm_processingnode”.“port”, “nodeodm_processingnode”.“api_version”, “nodeodm_processingnode”.“last_refreshed”, “nodeodm_processingnode”.“queue_count”, “nodeodm_processingnode”.“available_options”, “nodeodm_processingnode”.“token”, “nodeodm_processingnode”.“max_images”, “nodeodm_processingnode”.“engine_version”, “nodeodm_processingnode”.“label”, “nodeodm_processingnode”.“engine” FROM “nodeodm_processingnode” WHERE “nodeodm_processingnode”.“hostname” = ‘127.0.0.1’ FOR UPDATE
LOG: database system was interrupted; last known up at 2021-11-14 17:04:03 EST
LOG: invalid record length at 0/10F8E5D8: wanted 24, got 0
LOG: invalid primary checkpoint record
LOG: using previous checkpoint record at 0/10F8CC10
LOG: database system was not properly shut down; automatic recovery in progress
FATAL: the database system is starting up
LOG: redo starts at 0/10F8CC80
LOG: redo done at 0/10F8E5B0
LOG: last completed transaction was at log time 2021-11-14 17:02:07.273343-05
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
FATAL: the database system is starting up
LOG: autovacuum launcher started
LOG: could not rename temporary statistics file “pg_stat_tmp/global.tmp” to “pg_stat_tmp/global.stat”: Permission denied
LOG: using stale statistics instead of current ones because stats collector is not responding
LOG: could not rename temporary statistics file “pg_stat_tmp/global.tmp” to “pg_stat_tmp/global.stat”: Permission denied
LOG: using stale statistics instead of current ones because stats collector is not responding
ERROR: missing chunk number 0 for toast value 78790 in pg_toast_18068
STATEMENT: SELECT “nodeodm_processingnode”.“id”, “nodeodm_processingnode”.“hostname”, “nodeodm_processingnode”.“port”, “nodeodm_processingnode”.“api_version”, “nodeodm_processingnode”.“last_refreshed”, “nodeodm_processingnode”.“queue_count”, “nodeodm_processingnode”.“available_options”, “nodeodm_processingnode”.“token”, “nodeodm_processingnode”.“max_images”, “nodeodm_processingnode”.“engine_version”, “nodeodm_processingnode”.“label”, “nodeodm_processingnode”.“engine” FROM “nodeodm_processingnode” WHERE “nodeodm_processingnode”.“hostname” = ‘127.0.0.1’ FOR UPDATE
LOG: received fast shutdown request
LOG: aborting any active transactions
LOG: autovacuum launcher shutting down
LOG: shutting down
LOG: database system is shut down
FATAL: the database system is starting up
LOG: database system was shut down at 2021-11-14 18:00:02 EST
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
FATAL: the database system is starting up
LOG: autovacuum launcher started
ERROR: missing chunk number 0 for toast value 78790 in pg_toast_18068
STATEMENT: SELECT “nodeodm_processingnode”.“id”, “nodeodm_processingnode”.“hostname”, “nodeodm_processingnode”.“port”, “nodeodm_processingnode”.“api_version”, “nodeodm_processingnode”.“last_refreshed”, “nodeodm_processingnode”.“queue_count”, “nodeodm_processingnode”.“available_options”, “nodeodm_processingnode”.“token”, “nodeodm_processingnode”.“max_images”, “nodeodm_processingnode”.“engine_version”, “nodeodm_processingnode”.“label”, “nodeodm_processingnode”.“engine” FROM “nodeodm_processingnode” WHERE “nodeodm_processingnode”.“hostname” = ‘127.0.0.1’ FOR UPDATE
FATAL: the database system is starting up
LOG: database system was interrupted; last known up at 2021-11-14 18:05:05 EST
LOG: database system was not properly shut down; automatic recovery in progress
LOG: invalid record length at 0/10F91A30: wanted 24, got 0
LOG: redo is not required
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
ERROR: missing chunk number 0 for toast value 78790 in pg_toast_18068
STATEMENT: SELECT “nodeodm_processingnode”.“id”, “nodeodm_processingnode”.“hostname”, “nodeodm_processingnode”.“port”, “nodeodm_processingnode”.“api_version”, “nodeodm_processingnode”.“last_refreshed”, “nodeodm_processingnode”.“queue_count”, “nodeodm_processingnode”.“available_options”, “nodeodm_processingnode”.“token”, “nodeodm_processingnode”.“max_images”, “nodeodm_processingnode”.“engine_version”, “nodeodm_processingnode”.“label”, “nodeodm_processingnode”.“engine” FROM “nodeodm_processingnode” WHERE “nodeodm_processingnode”.“hostname” = ‘127.0.0.1’ FOR UPDATE
LOG: could not rename temporary statistics file “pg_stat_tmp/global.tmp” to “pg_stat_tmp/global.stat”: Permission denied
LOG: could not rename temporary statistics file “pg_stat_tmp/global.tmp” to “pg_stat_tmp/global.stat”: Permission denied
LOG: using stale statistics instead of current ones because stats collector is not responding
LOG: using stale statistics instead of current ones because stats collector is not responding
LOG: could not rename temporary statistics file “pg_stat_tmp/global.tmp” to “pg_stat_tmp/global.stat”: Permission denied
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 2021-11-15 04:21:13 EST
FATAL: the database system is starting up
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”
ERROR: missing chunk number 0 for toast value 78790 in pg_toast_18068
STATEMENT: SELECT “nodeodm_processingnode”.“id”, “nodeodm_processingnode”.“hostname”, “nodeodm_processingnode”.“port”, “nodeodm_processingnode”.“api_version”, “nodeodm_processingnode”.“last_refreshed”, “nodeodm_processingnode”.“queue_count”, “nodeodm_processingnode”.“available_options”, “nodeodm_processingnode”.“token”, “nodeodm_processingnode”.“max_images”, “nodeodm_processingnode”.“engine_version”, “nodeodm_processingnode”.“label”, “nodeodm_processingnode”.“engine” FROM “nodeodm_processingnode” WHERE “nodeodm_processingnode”.“hostname” = ‘127.0.0.1’ FOR UPDATE

Sorry you’re having trouble.

Could you start by uninstalling WebODM, deleting the C:\WebODM folder, and re-installing?

1 Like

Grazie
innanzi tutto grazie per avermi accettato nel gruppo,
sono un volontario della Croce Rossa Italiana ed usiamo questo software con i nostri droni in protezione civile, ancor di più per la ricerca dispersi ,lo usiamo in virtù dell’analisi di post produzione, anche se ci cimentiamo senza un manuale in italiano, è un bel software con molte potenzialità anche per chi , come noi non fa fotogrammetria a livello professionale non costa come metashape e ci da gli stessi risultati al nostro livello molto importanti, non ha necessità di macchine dal costo importante.
grazie di tutto della Vostra collaborazione .
si ho riprovato ad installarlo e sembra sia ripartito, abbiamo due versioni su un portatile quella a pagamento mentre sul fisso quella con Docher. su quella a pagamento però ho perso quelle fatte prima , mi dispiace ma l’importante che funzioni per la prossima emergenza

1 Like

Grazie per il tuo grande lavoro nel sostenere gli altri e aiutare nella risposta alle emergenze!

Ah, sfortunatamente, sì, l’eliminazione della cartella è un “reset”, ma sono contento che tu sia attivo e funzionante ora.

Fateci sapere se avete ulteriori domande in futuro.

E, se il tempo lo consente, mostra qualcosa di divertente su cui stai lavorando o un posto pulito che hai visto. Ci piace vedere cosa stanno su le persone con OpenDroneMap!

[Tradotto automaticamente]

Thank you for your great work supporting others and helping in emergency response!

Ah, unfortunately, yes, deleting the folder is a "reset", but I'm glad you're up and running now.

Please let us know if you have any further questions in the future.

And, if time permits, show off something fun you're working on, or a neat place you saw. We love seeing what folks are up to with OpenDroneMap!

[Machine Translated]

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.