Node Shutdown

Greetings,

WEBODM worked great the first day. The second day this message was logged with qued projects:

LOG: database system was shut down at 2022-05-08 19:19:23 EDT
LOG: MultiXact member wraparound protections are now enabled
LOG: autovacuum launcher started
LOG: database system is ready to accept connections
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
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-16 13:17:42 EDT
LOG: MultiXact member wraparound protections are now enabled

I DO have access to the first day project output. It says “The processing node went offline. This could be due to insufficient memory or a network error”. I did stack several projects to run concurrently. The other projects have a string of code with “not found” at the end.

I’m not a developer and paid for the bundle, book and editor which is great.

Any feedback and guidance to get processing again would be appreciated. Thank you for this forum to the ask the question.

V/R

POST SCRIPT

I deleted all the files in the que and restarted the node. It seems to be working ok now.

Live and learn.

1 Like

Welcome!

Sorry for the trouble.

Yes, if the node fails or gets killed due to Out-Of-Memory, one path is to reboot the machine or manually kill all the child processes that were spawned to clean up, and then restart the program.

Resetting the queue/node also works, but you lose your processed Tasks unless you’ve already exported them.

1 Like

Thank you for the quick reply.

This forum is a blessing for a newbie like myself.

1 Like

Glad it helped and hopefully you feel comfortable going forward so you can show off some of your stuff :slight_smile:

1 Like