after instal a new mainboard and cpu I got this report. What is wrong?
After install an new Mainboard and cpu I get this report. What is wrong?
1 Like
Welcome!
Sorry for the trouble! Could you please start with giving me a bit more information about your system?
For instance:
- Operating System and Version
eg: Windows 11, MacOS 12.4, Ubuntu Linux 22.04LTS, etc… - Hardware Specifications
eg: 32GB RAM, i7-6700k, NVIDIA GTX 1050TI OC, 1TB SSD, etc… - WebODM Install Method
eg: Native installer, Docker, Snap, GitHub download, compiled from source - WebODM/ODM Version
eg: WebODM v1.9.14 Build 64, ODM v2.8.7, etc… - Procesing Node
eg: Automatic, Lightning, local (node-odm-1), etc… - Screenshots demonstrating the issue/behavior/error messages
Hello,
this are the logs.
My system Windows 10
CPU I 9 13900
Grafik NVIDIA 2060
LOG: could not bind IPv6 socket: Only one usage of each socket address (protocol/network address/port) is normally permitted.
HINT: Is another postmaster already running on port 29543? If not, wait a few seconds and retry.
LOG: could not bind IPv4 socket: Only one usage of each socket address (protocol/network address/port) is normally permitted.
HINT: Is another postmaster already running on port 29543? If not, wait a few seconds and retry.
WARNING: could not create listen socket for “localhost”
FATAL: could not create any TCP/IP sockets
LOG: database system is shut down
LOG: database system was shut down at 2021-09-28 14:33:14 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
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2021-10-18 12:51:41 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 2021-10-18 14:00:57 EDT
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
LOG: server process (PID 23580) was terminated by exception 0x40010004
DETAIL: Failed process was running: COMMIT
HINT: See C include file “ntstatus.h” for a description of the hexadecimal value.
LOG: terminating any other active server processes
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
LOG: all server processes terminated; reinitializing
LOG: database system was interrupted; last known up at 2021-10-20 06:41:46 EDT
LOG: database system was not properly shut down; automatic recovery in progress
LOG: redo starts at 0/13F6C6A8
FATAL: the database system is starting up
FATAL: the database system is starting up
LOG: invalid record length at 0/1408D638: wanted 24, got 0
LOG: redo done at 0/1408D610
LOG: last completed transaction was at log time 2021-10-20 06:42:49.302275-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
FATAL: terminating connection due to administrator command
FATAL: terminating connection due to administrator command
FATAL: terminating connection due to administrator command
STATEMENT: SELECT “auth_user”.“id”, “auth_user”.“password”, “auth_user”.“last_login”, “auth_user”.“is_superuser”, “auth_user”.“username”, “auth_user”.“first_name”, “auth_user”.“last_name”, “auth_user”.“email”, “auth_user”.“is_staff”, “auth_user”.“is_active”, “auth_user”.“date_joined” FROM “auth_user” WHERE “auth_user”.“id” = 2
FATAL: terminating connection due to administrator command
FATAL: terminating connection due to administrator command
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2021-10-20 11:40:59 EDT
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
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-10-20 21:53:01 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-10-21 13:43:55 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
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-22 08:14:12 EDT
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
ERROR: canceling autovacuum task
CONTEXT: automatic vacuum of table “webodm_dev.pg_toast.pg_toast_18172”
LOG: received fast shutdown request
LOG: aborting any active transactions
LOG: autovacuum launcher shutting down
FATAL: terminating connection due to administrator command
FATAL: terminating connection due to administrator command
FATAL: terminating connection due to administrator command
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2021-10-22 10:05: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
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-10-22 17:39:38 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-10-26 07:44: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
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-10-26 10:56:51 EDT
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
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 2021-12-08 08:45:10 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”
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 2022-10-01 10:18:33 EDT
FATAL: the database system is starting up
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
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-02-21 13:44:19 EST
FATAL: the database system is starting up
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
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-02-24 16:05:11 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
LOG: autovacuum launcher shutting down
LOG: shutting down
LOG: database system is shut down
“Booting WebODM 1.9.7 build 32…”
“Trying to connect to NodeODM localhost:29301…”
“nodeodm: error: Error during startup: Cannot read list of options from ODM (from temporary file). Is ODM installed in G:\WebODM\resources\app\apps\ODM?\r\n”
“nodeodm: exited with code 1”
“(node:28368) UnhandledPromiseRejectionWarning: Error: Exit code: 1\n at ChildProcess. (G:\WebODM\resources\app\utils.js:63:19)\n at ChildProcess.emit (events.js:210:5)\n at maybeClose (internal/child_process.js:1021:16)\n at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)”
“(node:28368) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)”
“(node:28368) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.”
“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…”
“Attempt 3 failed, retrying…”
“Trying to connect to NodeODM localhost:29301…”
“Attempt 4 failed, retrying…”
“Trying to connect to NodeODM localhost:29301…”
“Attempt 5 failed, retrying…”
“Trying to connect to NodeODM localhost:29301…”
“Attempt 6 failed, retrying…”
“Trying to connect to NodeODM localhost:29301…”
“Attempt 7 failed, retrying…”
“Trying to connect to NodeODM localhost:29301…”
“Attempt 8 failed, retrying…”
“Trying to connect to NodeODM localhost:29301…”
“Attempt 9 failed, retrying…”
“Trying to connect to NodeODM localhost:29301…”
“Attempt 10 failed, retrying…”
“Trying to connect to NodeODM localhost:29301…”
“Attempt 11 failed, retrying…”
“Trying to connect to NodeODM localhost:29301…”
“Attempt 12 failed, retrying…”
“Trying to connect to NodeODM localhost:29301…”
“Attempt 13 failed, retrying…”
“Trying to connect to NodeODM localhost:29301…”
“Attempt 14 failed, retrying…”
“Trying to connect to NodeODM localhost:29301…”
{}
1 Like
Can you please try again with a current version of the installer?
Uninstall what you have now, reboot, and try installing the current version.
so i have to pay again?
1 Like
Not at all.
You use the same download link as before. If you can’t find it, reach out to [email protected] and I’ll send it to you again.
1 Like
Thank you, the problem is fixed.
2 Likes