Webodm not opening

“Booting WebODM 1.9.12 build 55…”
“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 2 tasks\r\n”
“nodeodm: info: Checking for orphaned directories to be removed…\r\n”
“nodeodm: info: Server has started on port 29301\r\n”
“Connected to NodeODM 2.2.0”
“redis-server: . \n .-__ ''-._ \n _.- . . ‘’-._ Redis 3.2.100 (00000000/0) 64 bit\n .- .-```. ```\\/ _.,_ ''-._ \n ( ' , .-` | `, ) Running in standalone mode\n |`-._`-...-` __...-.-.|’_.-'| Port: 29379\n | -. ._ / _.-' | PID: 22028\n -._ -._ -./ .-’ .-’ \n |-._-. -.__.-' _.-'_.-'| \n | -.-._ _.-'_.-' | http://redis.io \n -._ -._-..-’.-’ .-’ \n |-._-. -.__.-' _.-'_.-'| \n | -.-._ _.-'_.-' | \n -._ -._-..-’_.-’ _.-’ \n -._ -..-’ _.-’ \n -._ _.-' \n -..-’ \n\n[22028] 11 May 14:37:08.224 # Server started, Redis version 3.2.100\n”
“redis-server: [22028] 11 May 14:37:08.293 * DB loaded from disk: 0.069 seconds\n[22028] 11 May 14:37:08.293 * The server is now ready to accept connections on port 29379\n”
“Trying to connect to postgres localhost:29543…”
“D:\WebODM\resources\app\apps\pgsql/bin/pg_ctl: server starting\r\n”
“D:\WebODM\resources\app\apps\pgsql/bin/pg_ctl: exited with code 0”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: psql: could not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (::1) and accepting\r\n\tTCP/IP connections on port 29543?\r\ncould not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (127.0.0.1) and accepting\r\n\tTCP/IP connections on port 29543?\r\n”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: exited with code 2”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: psql: could not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (::1) and accepting\r\n\tTCP/IP connections on port 29543?\r\ncould not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (127.0.0.1) and accepting\r\n\tTCP/IP connections on port 29543?\r\n”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: exited with code 2”
“Attempt 0 failed, retrying…”
“Trying to connect to postgres localhost:29543…”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: psql: could not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (::1) and accepting\r\n\tTCP/IP connections on port 29543?\r\ncould not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (127.0.0.1) and accepting\r\n\tTCP/IP connections on port 29543?\r\n”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: exited with code 2”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: psql: could not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (::1) and accepting\r\n\tTCP/IP connections on port 29543?\r\ncould not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (127.0.0.1) and accepting\r\n\tTCP/IP connections on port 29543?\r\n”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: exited with code 2”
“Attempt 1 failed, retrying…”
“Trying to connect to postgres localhost:29543…”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: psql: could not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (::1) and accepting\r\n\tTCP/IP connections on port 29543?\r\ncould not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (127.0.0.1) and accepting\r\n\tTCP/IP connections on port 29543?\r\n”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: exited with code 2”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: psql: could not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (::1) and accepting\r\n\tTCP/IP connections on port 29543?\r\ncould not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (127.0.0.1) and accepting\r\n\tTCP/IP connections on port 29543?\r\n”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: exited with code 2”
“Attempt 2 failed, retrying…”
“Trying to connect to postgres localhost:29543…”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: psql: could not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (::1) and accepting\r\n\tTCP/IP connections on port 29543?\r\ncould not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (127.0.0.1) and accepting\r\n\tTCP/IP connections on port 29543?\r\n”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: exited with code 2”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: psql: could not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (::1) and accepting\r\n\tTCP/IP connections on port 29543?\r\ncould not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (127.0.0.1) and accepting\r\n\tTCP/IP connections on port 29543?\r\n”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: exited with code 2”
“Attempt 3 failed, retrying…”
“Trying to connect to postgres localhost:29543…”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: psql: could not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (::1) and accepting\r\n\tTCP/IP connections on port 29543?\r\ncould not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (127.0.0.1) and accepting\r\n\tTCP/IP connections on port 29543?\r\n”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: exited with code 2”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: psql: could not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (::1) and accepting\r\n\tTCP/IP connections on port 29543?\r\ncould not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (127.0.0.1) and accepting\r\n\tTCP/IP connections on port 29543?\r\n”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: exited with code 2”
“Attempt 4 failed, retrying…”
“Trying to connect to postgres localhost:29543…”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: psql: could not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (::1) and accepting\r\n\tTCP/IP connections on port 29543?\r\ncould not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (127.0.0.1) and accepting\r\n\tTCP/IP connections on port 29543?\r\n”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: exited with code 2”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: psql: could not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (::1) and accepting\r\n\tTCP/IP connections on port 29543?\r\ncould not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (127.0.0.1) and accepting\r\n\tTCP/IP connections on port 29543?\r\n”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: exited with code 2”
“Attempt 5 failed, retrying…”
“Trying to connect to postgres localhost:29543…”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: psql: could not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (::1) and accepting\r\n\tTCP/IP connections on port 29543?\r\ncould not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (127.0.0.1) and accepting\r\n\tTCP/IP connections on port 29543?\r\n”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: exited with code 2”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: psql: could not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (::1) and accepting\r\n\tTCP/IP connections on port 29543?\r\ncould not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (127.0.0.1) and accepting\r\n\tTCP/IP connections on port 29543?\r\n”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: exited with code 2”
“Attempt 6 failed, retrying…”
“Trying to connect to postgres localhost:29543…”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: psql: could not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (::1) and accepting\r\n\tTCP/IP connections on port 29543?\r\ncould not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (127.0.0.1) and accepting\r\n\tTCP/IP connections on port 29543?\r\n”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: exited with code 2”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: psql: could not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (::1) and accepting\r\n\tTCP/IP connections on port 29543?\r\ncould not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (127.0.0.1) and accepting\r\n\tTCP/IP connections on port 29543?\r\n”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: exited with code 2”
“Attempt 7 failed, retrying…”
“Trying to connect to postgres localhost:29543…”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: psql: could not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (::1) and accepting\r\n\tTCP/IP connections on port 29543?\r\ncould not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (127.0.0.1) and accepting\r\n\tTCP/IP connections on port 29543?\r\n”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: exited with code 2”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: psql: could not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (::1) and accepting\r\n\tTCP/IP connections on port 29543?\r\ncould not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (127.0.0.1) and accepting\r\n\tTCP/IP connections on port 29543?\r\n”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: exited with code 2”
“Attempt 8 failed, retrying…”
“Trying to connect to postgres localhost:29543…”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: psql: could not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (::1) and accepting\r\n\tTCP/IP connections on port 29543?\r\ncould not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (127.0.0.1) and accepting\r\n\tTCP/IP connections on port 29543?\r\n”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: exited with code 2”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: psql: could not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (::1) and accepting\r\n\tTCP/IP connections on port 29543?\r\ncould not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (127.0.0.1) and accepting\r\n\tTCP/IP connections on port 29543?\r\n”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: exited with code 2”
“Attempt 9 failed, retrying…”
“Trying to connect to postgres localhost:29543…”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: psql: could not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (::1) and accepting\r\n\tTCP/IP connections on port 29543?\r\ncould not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (127.0.0.1) and accepting\r\n\tTCP/IP connections on port 29543?\r\n”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: exited with code 2”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: psql: could not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (::1) and accepting\r\n\tTCP/IP connections on port 29543?\r\ncould not connect to server: Connection refused (0x0000274D/10061)\r\n\tIs the server running on host “localhost” (127.0.0.1) and accepting\r\n\tTCP/IP connections on port 29543?\r\n”
“D:\WebODM\resources\app\apps\pgsql/bin/psql: exited with code 2”
{}

FATAL: the database system is starting up
LOG: database system was shut down at 2022-02-28 23:09:16 EST
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 2022-04-20 20:41:42 EDT
FATAL: the database system is starting up
LOG: database system was not properly shut down; automatic recovery in progress
LOG: redo starts at 0/27CC0760
FATAL: the database system is starting up
LOG: invalid record length at 0/27CEA4F0: wanted 24, got 0
LOG: redo done at 0/27CEA4C8
LOG: last completed transaction was at log time 2022-04-20 20:42:23.802664-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
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-04-20 22:10:37 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: 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: using stale statistics instead of current ones because stats collector is not responding
WARNING: worker took too long to start; canceled
WARNING: autovacuum worker started without a worker entry
WARNING: worker took too long to start; canceled
WARNING: autovacuum worker started without a worker entry
LOG: database system was interrupted; last known up at 2022-04-21 01:36:33 EDT
LOG: invalid primary checkpoint record
LOG: invalid secondary checkpoint record
PANIC: could not locate a valid checkpoint record
FATAL: the database system is starting up
FATAL: the database system is starting up
LOG: startup process (PID 19956) was terminated by exception 0xC0000409
HINT: See C include file “ntstatus.h” for a description of the hexadecimal value.
LOG: aborting startup due to startup process failure
LOG: database system is shut down
LOG: database system was interrupted; last known up at 2022-04-21 01:36:33 EDT
LOG: invalid primary checkpoint record
LOG: invalid secondary checkpoint record
PANIC: could not locate a valid checkpoint record
LOG: startup process (PID 5236) was terminated by exception 0xC0000409
HINT: See C include file “ntstatus.h” for a description of the hexadecimal value.
LOG: aborting startup due to startup process failure
LOG: database system is shut down
FATAL: the database system is starting up
LOG: database system was interrupted; last known up at 2022-04-21 01:36:33 EDT
LOG: invalid primary checkpoint record
LOG: invalid secondary checkpoint record
PANIC: could not locate a valid checkpoint record
FATAL: the database system is starting up
LOG: startup process (PID 13704) was terminated by exception 0xC0000409
HINT: See C include file “ntstatus.h” for a description of the hexadecimal value.
LOG: aborting startup due to startup process failure
LOG: database system is shut down
LOG: database system was interrupted; last known up at 2022-04-21 01:36:33 EDT
LOG: invalid primary checkpoint record
LOG: invalid secondary checkpoint record
PANIC: could not locate a valid checkpoint record
LOG: startup process (PID 18852) was terminated by exception 0xC0000409
HINT: See C include file “ntstatus.h” for a description of the hexadecimal value.
LOG: aborting startup due to startup process failure
LOG: database system is shut down
LOG: database system was interrupted; last known up at 2022-04-21 01:36:33 EDT
LOG: invalid primary checkpoint record
LOG: invalid secondary checkpoint record
PANIC: could not locate a valid checkpoint record
FATAL: the database system is starting up
FATAL: the database system is starting up
LOG: startup process (PID 18988) was terminated by exception 0xC0000409
HINT: See C include file “ntstatus.h” for a description of the hexadecimal value.
LOG: aborting startup due to startup process failure
LOG: database system is shut down
LOG: database system was interrupted; last known up at 2022-04-21 01:36:33 EDT
LOG: invalid primary checkpoint record
LOG: invalid secondary checkpoint record
PANIC: could not locate a valid checkpoint record
LOG: startup process (PID 14416) was terminated by exception 0xC0000409
HINT: See C include file “ntstatus.h” for a description of the hexadecimal value.
LOG: aborting startup due to startup process failure
LOG: database system is shut down
LOG: database system was interrupted; last known up at 2022-04-21 01:36:33 EDT
LOG: invalid primary checkpoint record
LOG: invalid secondary checkpoint record
PANIC: could not locate a valid checkpoint record
LOG: startup process (PID 21120) was terminated by exception 0xC0000409
HINT: See C include file “ntstatus.h” for a description of the hexadecimal value.
LOG: aborting startup due to startup process failure
LOG: database system is shut down
LOG: database system was interrupted; last known up at 2022-04-21 01:36:33 EDT
LOG: invalid primary checkpoint record
LOG: invalid secondary checkpoint record
PANIC: could not locate a valid checkpoint record
LOG: startup process (PID 22980) was terminated by exception 0xC0000409
HINT: See C include file “ntstatus.h” for a description of the hexadecimal value.
LOG: aborting startup due to startup process failure
LOG: database system is shut down
LOG: database system was interrupted; last known up at 2022-04-21 01:36:33 EDT
LOG: invalid primary checkpoint record
LOG: invalid secondary checkpoint record
PANIC: could not locate a valid checkpoint record
LOG: startup process (PID 21108) was terminated by exception 0xC0000409
HINT: See C include file “ntstatus.h” for a description of the hexadecimal value.
LOG: aborting startup due to startup process failure
LOG: database system is shut down
LOG: database system was interrupted; last known up at 2022-04-21 01:36:33 EDT
LOG: invalid primary checkpoint record
LOG: invalid secondary checkpoint record
PANIC: could not locate a valid checkpoint record
LOG: startup process (PID 10932) was terminated by exception 0xC0000409
HINT: See C include file “ntstatus.h” for a description of the hexadecimal value.
LOG: aborting startup due to startup process failure
LOG: database system is shut down

Can someone help me, i turned the firewall off and it still didnt work.

1 Like

Mm, strange, but this line (and a few others):

FATAL: password authentication failed for user “postgres”
DETAIL: Password does not match for user “postgres”.

Might indicate that somehow the postgres database got corrupted. The easiest way to “fix” this would be to reinstall (make a backup of your processing results, if you have any).

1 Like

it was reinstalled and it didn’t work

OG: 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: 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: 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: 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: 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: 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 2022-01-14 12:05:56 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
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-02-07 22:54:12 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
LOG: database system was shut down at 2022-02-08 12:31:24 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
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-02-08 19:12:47 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
LOG: database system was shut down at 2022-02-08 19:54:21 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
LOG: database system was shut down at 2022-02-08 20:04:33 EST
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: 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 2022-03-11 23:06:47 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
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-03-11 23:11:46 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
LOG: database system was shut down at 2022-03-11 23:19:26 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
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-04-11 14:15:56 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 2022-04-13 15:03:30 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
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2022-04-29 00:08: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
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-05-01 19:02:09 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: 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 2022-05-07 21:14:59 EDT
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
Mingw-w64 runtime failure:
VirtualProtect failed with code 0x5afLOG: server process (PID 20260) exited with exit code 3
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.
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
FATAL: the database system is in recovery mode
LOG: database system was interrupted; last known up at 2022-05-07 21:18:15 EDT
LOG: database system was not properly shut down; automatic recovery in progress
LOG: redo starts at 0/1EFA7AD0
FATAL: the database system is in recovery mode
FATAL: the database system is in recovery mode
LOG: invalid record length at 0/1EFFFE68: wanted 24, got 0
LOG: redo done at 0/1EFFFE40
LOG: last completed transaction was at log time 2022-05-07 21:20:28.297273-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 2022-05-07 21:35: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
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-07 21:49: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 2022-05-08 01:09:54 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: CreateProcess call failed: A blocking operation was interrupted by a call to WSACancelBlockingCall.
(error code 8)
LOG: could not fork new process for connection: No error
LOG: CreateProcess call failed: No error (error code 1455)
LOG: could not fork new process for connection: No error
LOG: CreateProcess call failed: No error (error code 8)
LOG: could not fork new process for connection: No error
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 2022-05-09 00:17:51 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 2022-05-10 14: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
LOG: autovacuum launcher shutting down
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2022-05-10 16:56: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 2022-05-11 21:41:09 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
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2022-05-11 23:18:05 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 2022-05-11 23:24:40 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 2022-05-12 13:46: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
FATAL: terminating connection due to administrator command
LOG: autovacuum launcher shutting down
LOG: shutting down
LOG: database system is shut down

1 Like

Do you have anything else running PostgreSQL on your machine? Did you try a reboot between uninstall and reinstall?

ready thanks!

1 Like