Another crash in 2 weeks, what am I supposed to do?

On 11/4/2025 at 2:01 AM, bmartino1 said:

If you guys see this again, can you post the output of

ls -ail /usr/local/emhttp/plugins/dynamix/scripts

during the crash I have following output:

@Squid please advise!

Edited November 14, 2025Nov 14 by Joloxx9

1 hour ago, Joloxx9 said:

during the crash I have following output:

@Squid please advise!

please file a bug report.
https://forums.unraid.net/bug-reports/stable-releases/

12 hours ago, Joloxx9 said:

during the crash I have following output:

@Squid please advise!

That looks like an incomplete list. The "total 12" line suggest there should be more shown.

3 hours ago, itimpi said:

That looks like an incomplete list. The "total 12" line suggest there should be more shown.

I can asure you that was all what was listed, it was barely usable.

Had another ceash this morning at this time nothing was in CLI, couldn't even log in through it so had to do another hard restart. This is getting to the point where system is being unusable for me as server

@itimpi

This is end of the log right before the crash:

4 hours ago, Joloxx9 said:

@itimpi

This is end of the log right before the crash:

that log end just means dockers were shutting down.
this puts veth and other docker created interfaces in a disabled and removed from host state.

so to me this looks like part of a host shutdown and the removable of a usb device. Most likely the keyboard at the terminal.

Please post a diag and make a bug report...

5 hours ago, bmartino1 said:

that log end just means dockers were shutting down.
this puts veth and other docker created interfaces in a disabled and removed from host state.

so to me this looks like part of a host shutdown and the removable of a usb device. Most likely the keyboard at the terminal.

Please post a diag and make a bug report...

I've posted a bug report. Was told to do syslog and what, once it crashes syslog doesn't record anything it just stops.

You are saying that something disconencted, well I have only 2 things plugged in, UPS and Unraid, UPS is plugged to another controller, 1.10.1 is the one where my unraid is plugged, so not sure what is happening here.

Jumping in on this. Unraid 7.2.2, have tried all of the potential fixes presented previously. Enabled syslog copy to USB, found same symptoms as presented previously (inability to stay logged in via console, web UI non-responsive while some containers are responsive, disabling VPN, server not responding to ACPI calls).

Visible from login prompt (console)
crond[2360] exit status 1 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

crond[2360] exit status 1 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

crond[2360] exit status 1 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

crond[2360] exit status 1 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null
crond[2360] exit status 1 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

crond[2360] exit status 1 from user root /usr/bin/run-parts /etc/cron.hourly 1> /dev/nulll

crond[2360] exit status 1 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

Unable to present diagnostics, as server needs to be rebooted to become usable again. The best I have are these following syslog entries:

Dec 1 20:36:42 tower rc.rsyslogd: Syslog server daemon... Started.

Dec 1 20:36:43 tower rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="88242" x-info="https://www.rsyslog.com"] start

Dec 1 20:37:02 tower ool www[78640]: /usr/local/emhttp/plugins/dynamix/scripts/rsyslog_config

Dec 1 20:37:02 tower rc.rsyslogd: Restarting Syslog server daemon...

Dec 1 20:37:02 tower rc.rsyslogd: Stopping Syslog server daemon...

Dec 1 20:37:03 tower rc.rsyslogd: killall --ns 88875 rsyslogd

Dec 1 20:37:06 tower rc.rsyslogd: Syslog server daemon... Started.

Dec 1 20:37:07 tower rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="88963" x-info="https://www.rsyslog.com"] start

Dec 1 21:55:47 tower webgui: Successful login user root from 192.168.1.226

Dec 1 21:55:59 tower webgui: CaddyV2: Could not download icon https://d1q6f0aelx0por.cloudfront.net/product-logos/library-caddy-logo.png

Dec 1 21:57:18 tower ool www[186718]: Successful logout user root from 192.168.1.226

Dec 1 22:02:25 tower webgui: Successful login user root from 192.168.1.226

Dec 1 22:02:32 tower webgui: CaddyV2: Could not download icon https://d1q6f0aelx0por.cloudfront.net/product-logos/library-caddy-logo.png

Dec 1 22:02:55 tower ool www[194847]: Successful logout user root from 192.168.1.226

Dec 2 01:24:27 tower monitor_nchan: Stop running nchan processes

All instances of the web UI were logged out and closed.

51 minutes ago, kaleb112494 said:

Jumping in on this. Unraid 7.2.2, have tried all of the potential fixes presented previously. Enabled syslog copy to USB, found same symptoms as presented previously (inability to stay logged in via console, web UI non-responsive while some containers are responsive, disabling VPN, server not responding to ACPI calls).

Visible from login prompt (console)
crond[2360] exit status 1 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

crond[2360] exit status 1 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

crond[2360] exit status 1 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

crond[2360] exit status 1 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null
crond[2360] exit status 1 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

crond[2360] exit status 1 from user root /usr/bin/run-parts /etc/cron.hourly 1> /dev/nulll

crond[2360] exit status 1 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

Unable to present diagnostics, as server needs to be rebooted to become usable again. The best I have are these following syslog entries:

Dec 1 20:36:42 tower rc.rsyslogd: Syslog server daemon... Started.

Dec 1 20:36:43 tower rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="88242" x-info="https://www.rsyslog.com"] start

Dec 1 20:37:02 tower ool www[78640]: /usr/local/emhttp/plugins/dynamix/scripts/rsyslog_config

Dec 1 20:37:02 tower rc.rsyslogd: Restarting Syslog server daemon...

Dec 1 20:37:02 tower rc.rsyslogd: Stopping Syslog server daemon...

Dec 1 20:37:03 tower rc.rsyslogd: killall --ns 88875 rsyslogd

Dec 1 20:37:06 tower rc.rsyslogd: Syslog server daemon... Started.

Dec 1 20:37:07 tower rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="88963" x-info="https://www.rsyslog.com"] start

Dec 1 21:55:47 tower webgui: Successful login user root from 192.168.1.226

Dec 1 21:55:59 tower webgui: CaddyV2: Could not download icon https://d1q6f0aelx0por.cloudfront.net/product-logos/library-caddy-logo.png

Dec 1 21:57:18 tower ool www[186718]: Successful logout user root from 192.168.1.226

Dec 1 22:02:25 tower webgui: Successful login user root from 192.168.1.226

Dec 1 22:02:32 tower webgui: CaddyV2: Could not download icon https://d1q6f0aelx0por.cloudfront.net/product-logos/library-caddy-logo.png

Dec 1 22:02:55 tower ool www[194847]: Successful logout user root from 192.168.1.226

Dec 2 01:24:27 tower monitor_nchan: Stop running nchan processes

All instances of the web UI were logged out and closed.

its is best to make your own general post... posting diag and other... IDK what you guys are doing to get the monitor script to go off the walls like this...

1 minute ago, bmartino1 said:

its is best to make your own general post... posting diag and other... IDK what you guys are doing to get the monitor script to go off the walls like this...

This is pretty much a fresh installation of Unraid 7.2.2 - no upgrades and very few plugins/containers/etc. Diag from server ~30 minutes after forced reboot.

blockbuster2.0-diagnostics-20251202-2054.zip

Edited December 3, 2025Dec 3 by kaleb112494

4 minutes ago, kaleb112494 said:

This is pretty much a fresh installation of Unraid 7.2.2 - no upgrades and very few plugins/containers/etc. Diag from server ~30 minutes after forced reboot.

blockbuster2.0-diagnostics-20251202-2054.zip

thank you for a diaga. not seeing much. looks like there some issues going on with unriad hype v system...

graphql-api.txt gettign constant failure with libvirt...

which is a little weird...

[02:12:04 INFO api]: Server listening on /var/run/unraid-api.sock {"apiVersion":"4.27.2+375dcd05","logger":"api"}

[02:12:04 INFO api]: Nest Server is now listening {"apiVersion":"4.27.2+375dcd05","logger":"api"}

[02:12:14 INFO VmsService]: Attempting to initialize VMs service...attempt 1/12 {"apiVersion":"4.27.2+375dcd05","logger":"api","context":"VmsService"}

[02:12:14 WARN VmsService]: Initial hypervisor connection failed: Libvirt is not running. Setting up watcher. {"apiVersion":"4.27.2+375dcd05","logger":"api","context":"VmsService"}

[02:12:24 INFO VmsService]: Attempting to initialize VMs service...attempt 2/12 {"apiVersion":"4.27.2+375dcd05","logger":"api","context":"VmsService"}

[02:12:24 WARN VmsService]: Initial hypervisor connection failed: Libvirt is not running. Setting up watcher. {"apiVersion":"4.27.2+375dcd05","logger":"api","context":"VmsService"}

[02:12:34 INFO VmsService]: Attempting to initialize VMs service...attempt 3/12 {"apiVersion":"4.27.2+375dcd05","logger":"api","context":"VmsService"}

[02:12:34 WARN VmsService]: Initial hypervisor connection failed: Libvirt is not running. Setting up watcher. {"apiVersion":"4.27.2+375dcd05","logger":"api","context":"VmsService"}

[02:12:44 INFO VmsService]: Attempting to initialize VMs service...attempt 4/12 {"apiVersion":"4.27.2+375dcd05","logger":"api","context":"VmsService"}

[02:12:44 WARN VmsService]: Initial hypervisor connection failed: Libvirt is not running. Setting up watcher. {"apiVersion":"4.27.2+375dcd05","logger":"api","context":"VmsService"}

[02:12:54 INFO VmsService]: Attempting to initialize VMs service...attempt 5/12 {"apiVersion":"4.27.2+375dcd05","logger":"api","context":"VmsService"}

[02:12:54 WARN VmsService]: Initial hypervisor connection failed: Libvirt is not running. Setting up watcher. {"apiVersion":"4.27.2+375dcd05","logger":"api","context":"VmsService"}

[02:12:04 INFO VmsService]: Attempting to initialize VMs service...attempt 6/12 {"apiVersion":"4.27.2+375dcd05","logger":"api","context":"VmsService"}

[02:12:04 WARN VmsService]: Initial hypervisor connection failed: Libvirt is not running. Setting up watcher. {"apiVersion":"4.27.2+375dcd05","logger":"api","context":"VmsService"}

[02:12:14 INFO VmsService]: Attempting to initialize VMs service...attempt 7/12 {"apiVersion":"4.27.2+375dcd05","logger":"api","context":"VmsService"}

[02:12:14 WARN VmsService]: Initial hypervisor connection failed: Libvirt is not running. Setting up watcher. {"apiVersion":"4.27.2+375dcd05","logger":"api","context":"VmsService"}

[02:12:24 INFO VmsService]: Attempting to initialize VMs service...attempt 8/12 {"apiVersion":"4.27.2+375dcd05","logger":"api","context":"VmsService"}

[02:12:24 WARN VmsService]: Initial hypervisor connection failed: Libvirt is not running. Setting up watcher. {"apiVersion":"4.27.2+375dcd05","logger":"api","context":"VmsService"}

[02:12:34 INFO VmsService]: Attempting to initialize VMs service...attempt 9/12 {"apiVersion":"4.27.2+375dcd05","logger":"api","context":"VmsService"}

[02:12:34 WARN VmsService]: Initial hypervisor connection failed: Libvirt is not running. Setting up watcher. {"apiVersion":"4.27.2+375dcd05","logger":"api","context":"VmsService"}

[02:12:44 INFO VmsService]: Attempting to initialize VMs service...attempt 10/12 {"apiVersion":"4.27.2+375dcd05","logger":"api","context":"VmsService"}

[02:12:44 WARN VmsService]: Initial hypervisor connection failed: Libvirt is not running. Setting up watcher. {"apiVersion":"4.27.2+375dcd05","logger":"api","context":"VmsService"}

[02:12:54 INFO VmsService]: Attempting to initialize VMs service...attempt 11/12 {"apiVersion":"4.27.2+375dcd05","logger":"api","context":"VmsService"}

[02:12:54 WARN VmsService]: Initial hypervisor connection failed: Libvirt is not running. Setting up watcher. {"apiVersion":"4.27.2+375dcd05","logger":"api","context":"VmsService"}

[02:12:04 INFO VmsService]: Attempting to initialize VMs service...attempt 12/12 {"apiVersion":"4.27.2+375dcd05","logger":"api","context":"VmsService"}

[02:12:04 WARN VmsService]: Initial hypervisor connection failed: Libvirt is not running. Setting up watcher. {"apiVersion":"4.27.2+375dcd05","logger":"api","context":"VmsService"}

[02:12:02 INFO app]: Exiting with signal 130 {"apiVersion":"4.27.2+375dcd05"}

[02:12:02 INFO UnraidFileModificationService]: Rolling back all modifications... {"apiVersion":"4.27.2+375dcd05","logger":"api","context":"UnraidFileModificationService"}

[02:12:02 INFO RCloneApiService]: RClone process not running or already stopped. {"apiVersion":"4.27.2+375dcd05","logger":"api","context":"RCloneApiService"}

[02:12:02 INFO RCloneApiService]: RCloneApiService module destroyed {"apiVersion":"4.27.2+375dcd05","logger":"api","context":"RCloneApiService"}

[02:12:05 INFO app]: ENV {"API_VERSION":"4.27.2+375dcd05","BYPASS_CORS_CHECKS":false,"BYPASS_PERMISSION_CHECKS":false,"CHOKIDAR_USEPOLLING":false,"DEBUG":false,"ECOSYSTEM_PATH":"/usr/local/unraid-

I'm not seing any vms or the VM sytem enabled...

I do see yor using ?bond? on a realtek driver for your eht0 nic...
standar plugin no cmd, or 3rd party appl;icaiton... singale cache disk pool per diag...

still combing thoguh the logs and diag... but not seeing anything abnoraml atm.
?Is this Unriad instace on baremetal aor virtualized?

Correct on all fronts so far. This is bare metal, was previously a Windows system until I convinced the owner to try Unraid out. Unfortunately, I feel that this has left a sour taste in his mouth.

Found this in /var/log/nginx/error.log just a moment ago

root@BlockBuster2:~# cat /var/log/nginx/error.log

2025/12/02 18:04:43 [info] 9694#9694: Using 116KiB of shared memory for nchan in /etc/nginx/nginx.conf:162

2025/12/02 18:04:43 [info] 9694#9694: Using 262144KiB of shared memory for nchan in /etc/nginx/nginx.conf:162

2025/12/02 18:10:45 [alert] 34899#34899: *309 open socket #20 left in connection 258

2025/12/02 18:10:45 [alert] 34899#34899: *317 open socket #29 left in connection 268

2025/12/02 18:10:45 [alert] 34899#34899: *336 open socket #38 left in connection 269

2025/12/02 18:10:45 [alert] 34899#34899: *361 open socket #34 left in connection 271

2025/12/02 18:10:45 [alert] 34899#34899: *321 open socket #30 left in connection 272

2025/12/02 18:10:45 [alert] 34899#34899: aborting

2025/12/02 18:10:46 [emerg] 37618#37618: "nchan_max_reserved_memory" directive is duplicate in /etc/nginx/nginx.conf:51

2025/12/02 18:21:01 [alert] 38228#38228: *1 open socket #3 left in connection 7

2025/12/02 18:21:01 [alert] 38228#38228: *17 open socket #19 left in connection 9

2025/12/02 18:21:01 [alert] 38228#38228: *15 open socket #21 left in connection 11

2025/12/02 18:21:01 [alert] 38228#38228: *9 open socket #22 left in connection 12

2025/12/02 18:21:01 [alert] 38228#38228: *11 open socket #23 left in connection 13

2025/12/02 18:21:01 [alert] 38228#38228: *13 open socket #24 left in connection 14

2025/12/02 18:21:01 [alert] 38228#38228: *1806 open socket #38 left in connection 20

2025/12/02 18:21:01 [alert] 38228#38228: *1788 open socket #30 left in connection 23

2025/12/02 18:21:01 [alert] 38228#38228: aborting

ker process: ./nchan-1.3.7/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed.

2025/12/02 18:21:03 [alert] 83383#83383: worker process 83384 exited on signal 6

2025/12/02 18:21:39 [alert] 83518#83518: *90 open socket #38 left in connection 21

2025/12/02 18:21:39 [alert] 83518#83518: *62 open socket #21 left in connection 24

2025/12/02 18:21:39 [alert] 83518#83518: *94 open socket #39 left in connection 26

2025/12/02 18:21:39 [alert] 83518#83518: *83 open socket #40 left in connection 27

2025/12/02 18:21:39 [alert] 83518#83518: *92 open socket #41 left in connection 28

2025/12/02 18:21:39 [alert] 83518#83518: *135 open socket #36 left in connection 29

2025/12/02 18:21:39 [alert] 83518#83518: aborting

2025/12/02 18:22:52 [alert] 86436#86436: *6 open socket #18 left in connection 8

2025/12/02 18:22:52 [alert] 86436#86436: *4 open socket #19 left in connection 9

2025/12/02 18:22:52 [alert] 86436#86436: *8 open socket #20 left in connection 10

2025/12/02 18:22:52 [alert] 86436#86436: *10 open socket #21 left in connection 11

2025/12/02 18:22:52 [alert] 86436#86436: *12 open socket #22 left in connection 12

2025/12/02 18:22:52 [alert] 86436#86436: *14 open socket #23 left in connection 13

2025/12/02 18:22:52 [alert] 86436#86436: *178 open socket #30 left in connection 16

2025/12/02 18:22:52 [alert] 86436#86436: *203 open socket #33 left in connection 28

2025/12/02 18:22:52 [alert] 86436#86436: aborting

2025/12/02 18:23:31 [alert] 87725#87725: *1 open socket #3 left in connection 7

2025/12/02 18:23:31 [alert] 87725#87725: *3 open socket #18 left in connection 8

2025/12/02 18:23:31 [alert] 87725#87725: *5 open socket #19 left in connection 9

2025/12/02 18:23:31 [alert] 87725#87725: *7 open socket #20 left in connection 10

2025/12/02 18:23:31 [alert] 87725#87725: *9 open socket #21 left in connection 11

2025/12/02 18:23:31 [alert] 87725#87725: *11 open socket #22 left in connection 12

2025/12/02 18:23:31 [alert] 87725#87725: *21 open socket #24 left in connection 14

2025/12/02 18:23:31 [alert] 87725#87725: *42 open socket #34 left in connection 24

2025/12/02 18:23:31 [alert] 87725#87725: aborting

ker process: ./nchan-1.3.7/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed.

2025/12/02 18:23:33 [alert] 88744#88744: worker process 88745 exited on signal 6

ker process: ./nchan-1.3.7/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed.

2025/12/02 18:23:35 [alert] 88744#88744: worker process 88822 exited on signal 6

2025/12/02 18:24:11 [alert] 88968#88968: *32 open socket #21 left in connection 8

2025/12/02 18:24:11 [alert] 88968#88968: *34 open socket #22 left in connection 9

2025/12/02 18:24:11 [alert] 88968#88968: *50 open socket #27 left in connection 14

2025/12/02 18:24:11 [alert] 88968#88968: *44 open socket #28 left in connection 15

2025/12/02 18:24:11 [alert] 88968#88968: *46 open socket #29 left in connection 16

2025/12/02 18:24:11 [alert] 88968#88968: *48 open socket #30 left in connection 17

2025/12/02 18:24:11 [alert] 88968#88968: *52 open socket #31 left in connection 18

2025/12/02 18:24:11 [alert] 88968#88968: *54 open socket #32 left in connection 19

2025/12/02 18:24:11 [alert] 88968#88968: aborting

ker process: ./nchan-1.3.7/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed.

2025/12/02 18:24:13 [alert] 90495#90495: worker process 90496 exited on signal 6

ker process: ./nchan-1.3.7/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed.

2025/12/02 18:24:15 [alert] 90495#90495: worker process 90534 exited on signal 6

2025/12/02 18:25:48 [alert] 90733#90733: *177 open socket #21 left in connection 9

2025/12/02 18:25:48 [alert] 90733#90733: *38 open socket #26 left in connection 13

2025/12/02 18:25:48 [alert] 90733#90733: *40 open socket #27 left in connection 14

2025/12/02 18:25:48 [alert] 90733#90733: *42 open socket #28 left in connection 15

2025/12/02 18:25:48 [alert] 90733#90733: *46 open socket #30 left in connection 17

2025/12/02 18:25:48 [alert] 90733#90733: *49 open socket #31 left in connection 18

2025/12/02 18:25:48 [alert] 90733#90733: aborting

ker process: ./nchan-1.3.7/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed.

2025/12/02 18:25:49 [alert] 94566#94566: worker process 94567 exited on signal 6

ker process: ./nchan-1.3.7/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed.

2025/12/02 18:25:51 [alert] 94566#94566: worker process 94612 exited on signal 6

2025/12/02 18:26:22 [alert] 94789#94789: *24 open socket #5 left in connection 7

2025/12/02 18:26:22 [alert] 94789#94789: *29 open socket #22 left in connection 9

2025/12/02 18:26:22 [alert] 94789#94789: *41 open socket #28 left in connection 15

2025/12/02 18:26:22 [alert] 94789#94789: *43 open socket #29 left in connection 16

2025/12/02 18:26:22 [alert] 94789#94789: *45 open socket #30 left in connection 17

2025/12/02 18:26:22 [alert] 94789#94789: *47 open socket #31 left in connection 18

2025/12/02 18:26:22 [alert] 94789#94789: aborting

ker process: ./nchan-1.3.7/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed.

2025/12/02 18:26:24 [alert] 96348#96348: worker process 96349 exited on signal 6

ker process: ./nchan-1.3.7/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed.

2025/12/02 18:26:26 [alert] 96348#96348: worker process 96418 exited on signal 6

2025/12/02 18:47:08 [alert] 96633#96633: *2232 open socket #5 left in connection 27

2025/12/02 18:47:08 [alert] 96633#96633: aborting

root@BlockBuster2:~#

I do have two Web UI tabs open currently - one on his network, and one on my workstation from home. I am accessing it from a domain that is reverse proxied via a caddy container on this same Unraid system.

Edited December 3, 2025Dec 3 by kaleb112494

per sytem log your experiencing ntp time server error adn soemthing comand wise stoped teh nginx server adn caused a reboot loop...

Dec 2 18:08:51 BlockBuster2 rc.nginx: Stopping Nginx server daemon gracefully...

Dec 2 18:09:40 BlockBuster2 sshd-session[34507]: Connection from 192.168.1.226 port 53807 on 192.168.1.69 port 22 rdomain ""

Dec 2 18:09:41 BlockBuster2 sshd-session[34507]: Postponed keyboard-interactive for root from 192.168.1.226 port 53807 ssh2 [preauth]

Dec 2 18:09:48 BlockBuster2 sshd-session[34507]: Postponed keyboard-interactive/pam for root from 192.168.1.226 port 53807 ssh2 [preauth]

Dec 2 18:09:48 BlockBuster2 sshd-session[34507]: Accepted keyboard-interactive/pam for root from 192.168.1.226 port 53807 ssh2

Dec 2 18:09:48 BlockBuster2 sshd-session[34507]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0)

Dec 2 18:09:48 BlockBuster2 sshd-session[34507]: User child is on pid 34600

Dec 2 18:09:48 BlockBuster2 sshd-session[34600]: Starting session: shell on pts/0 for root from 192.168.1.226 port 53807 id 0

Dec 2 18:10:04 BlockBuster2 rc.nginx: Stopping Nginx server daemon gracefully...

Dec 2 18:10:04 BlockBuster2 rc.nginx: Nginx server daemon... Already stopped.

Dec 2 18:10:04 BlockBuster2 rc.nginx: Starting Nginx server daemon...

Dec 2 18:10:08 BlockBuster2 rc.nginx: Nginx server daemon... Started.

Dec 2 18:10:33 BlockBuster2 ntpd[2339]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized

Dec 2 18:10:44 BlockBuster2 rc.nginx: Stopping Nginx server daemon gracefully...

Dec 2 18:10:45 BlockBuster2 nginx: 2025/12/02 18:10:45 [alert] 34899#34899: *309 open socket #20 left in connection 258

Dec 2 18:10:45 BlockBuster2 nginx: 2025/12/02 18:10:45 [alert] 34899#34899: *317 open socket #29 left in connection 268

Dec 2 18:10:45 BlockBuster2 nginx: 2025/12/02 18:10:45 [alert] 34899#34899: *336 open socket #38 left in connection 269

Dec 2 18:10:45 BlockBuster2 nginx: 2025/12/02 18:10:45 [alert] 34899#34899: *361 open socket #34 left in connection 271

Dec 2 18:10:45 BlockBuster2 nginx: 2025/12/02 18:10:45 [alert] 34899#34899: *321 open socket #30 left in connection 272

Dec 2 18:10:45 BlockBuster2 nginx: 2025/12/02 18:10:45 [alert] 34899#34899: aborting

Dec 2 18:10:46 BlockBuster2 rc.nginx: Nginx server daemon... Stopped.

Dec 2 18:10:46 BlockBuster2 rc.nginx: Starting Nginx server daemon...

Dec 2 18:10:50 BlockBuster2 webgui: curl error: Failed to connect to localhost port 80 after 0 ms: Could not connect to server endpoint: notify

Dec 2 18:10:50 BlockBuster2 publish: curl to notify failed

Dec 2 18:10:50 BlockBuster2 webgui: curl error: Failed to connect to localhost port 80 after 0 ms: Could not connect to server endpoint: session

Dec 2 18:10:50 BlockBuster2 publish: curl to session failed

Dec 2 18:10:50 BlockBuster2 webgui: curl error: Failed to connect to localhost port 80 after 0 ms: Could not connect to server endpoint: temperature

Dec 2 18:10:50 BlockBuster2 publish: curl to temperature failed

Dec 2 18:10:50 BlockBuster2 webgui: curl error: Failed to connect to localhost port 80 after 0 ms: Could not connect to server endpoint: devices

Dec 2 18:10:50 BlockBuster2 publish: curl to devices failed

Dec 2 18:10:50 BlockBuster2 webgui: curl error: Failed to connect to localhost port 80 after 0 ms: Could not connect to server endpoint: arraymonitor

Dec 2 18:10:50 BlockBuster2 publish: curl to arraymonitor failed

Dec 2 18:10:50 BlockBuster2 webgui: curl error: Failed to connect to localhost port 80 after 0 ms: Could not connect to server endpoint: mainPingListener

Dec 2 18:10:50 BlockBuster2 publish: curl to mainPingListener failed

Dec 2 18:10:50 BlockBuster2 webgui: curl error: Failed to connect to localhost port 80 after 0 ms: Could not connect to server endpoint: parity

Dec 2 18:10:50 BlockBuster2 publish: curl to parity failed

Dec 2 18:10:50 BlockBuster2 webgui: curl error: Failed to connect to localhost port 80 after 0 ms: Could not connect to server endpoint: paritymonitor

Dec 2 18:10:50 BlockBuster2 publish: curl to paritymonitor failed

Dec 2 18:10:50 BlockBuster2 webgui: curl error: Failed to connect to localhost port 80 after 0 ms: Could not connect to server endpoint: fsState

Dec 2 18:10:50 BlockBuster2 publish: curl to fsState failed

Dec 2 18:10:50 BlockBuster2 webgui: curl error: Failed to connect to localhost port 80 after 0 ms: Could not connect to server endpoint: mymonitor

Dec 2 18:10:50 BlockBuster2 publish: curl to mymonitor failed

Dec 2 18:10:50 BlockBuster2 webgui: curl error: Failed to connect to localhost port 80 after 0 ms: Could not connect to server endpoint: mainPingListener

Dec 2 18:10:50 BlockBuster2 publish: curl to mainPingListener failed

Dec 2 18:10:50 BlockBuster2 rc.nginx: Nginx server daemon... Failed.

Dec 2 18:10:51 BlockBuster2 webgui: curl error: Failed to connect to localhost port 80 after 0 ms: Could not connect to server endpoint: devices

Dec 2 18:10:51 BlockBuster2 publish: curl to devices failed

Dec 2 18:10:51 BlockBuster2 webgui: curl error: Failed to connect to localhost port 80 after 0 ms: Could not connect to server endpoint: arraymonitor

Dec 2 18:10:51 BlockBuster2 publish: curl to arraymonitor failed

Dec 2 18:10:51 BlockBuster2 webgui: curl error: Failed to connect to localhost port 80 after 0 ms: Could not connect to server endpoint: mainPingListener

Dec 2 18:10:51 BlockBuster2 publish: curl to mainPingListener failed

Dec 2 18:10:52 BlockBuster2 webgui: curl error: Failed to connect to localhost port 80 after 0 ms: Could not connect to server endpoint: devices

Dec 2 18:10:52 BlockBuster2 publish: curl to devices failed

Dec 2 18:10:52 BlockBuster2 webgui: curl error: Failed to connect to localhost port 80 after 0 ms: Could not connect to server endpoint: arraymonitor

Dec 2 18:10:52 BlockBuster2 publish: curl to arraymonitor failed

Dec 2 18:10:52 BlockBuster2 webgui: curl error: Failed to connect to localhost port 80 after 0 ms: Could not connect to server endpoint: mainPingListener

Dec 2 18:10:52 BlockBuster2 publish: curl to mainPingListener failed

Dec 2 18:10:53 BlockBuster2 webgui: curl error: Failed to connect to localhost port 80 after 0 ms: Could not connect to server endpoint: devices

Dec 2 18:10:53 BlockBuster2 publish: curl to devices failed

Dec 2 18:10:53 BlockBuster2 webgui: curl error: Failed to connect to localhost port 80 after 0 ms: Could not connect to server endpoint: arraymonitor

Dec 2 18:10:53 BlockBuster2 publish: curl to arraymonitor failed

Dec 2 18:10:53 BlockBuster2 webgui: curl error: Failed to connect to localhost port 80 after 0 ms: Could not connect to server endpoint: mainPingListener

Dec 2 18:10:53 BlockBuster2 publish: curl to mainPingListener failed

Dec 2 18:10:53 BlockBuster2 webgui: curl error: Failed to connect to localhost port 80 after 0 ms: Could not connect to server endpoint: parity

Dec 2 18:10:53 BlockBuster2 publish: curl to parity failed

Dec 2 18:10:53 BlockBuster2 webgui: curl error: Failed to connect to localhost port 80 after 0 ms: Could not connect to server endpoint: paritymonitor

Dec 2 18:10:53 BlockBuster2 publish: curl to paritymonitor failed

Dec 2 18:10:53 BlockBuster2 webgui: curl error: Failed to connect to localhost port 80 after 0 ms: Could not connect to server endpoint: fsState

Dec 2 18:10:53 BlockBuster2 publish: curl to fsState failed

Dec 2 18:10:53 BlockBuster2 webgui: curl error: Failed to connect to localhost port 80 after 0 ms: Could not connect to server endpoint: mymonitor

Dec 2 18:10:53 BlockBuster2 publish: curl to mymonitor failed

Dec 2 18:10:53 BlockBuster2 webgui: curl error: Failed to connect to localhost port 80 after 0 ms: Could not connect to server endpoint: mainPingListener

Dec 2 18:10:53 BlockBuster2 publish: curl to mainPingListener failed

Dec 2 18:10:54 BlockBuster2 webgui: curl error: Failed to connect to localhost port 80 after 0 ms: Could not connect to server endpoint: devices

Dec 2 18:10:54 BlockBuster2 publish: curl to devices failed

Dec 2 18:10:54 BlockBuster2 webgui: curl error: Failed to connect to localhost port 80 after 0 ms: Could not connect to server endpoint: arraymonitor

Dec 2 18:10:54 BlockBuster2 publish: curl to arraymonitor failed

Dec 2 18:10:54 BlockBuster2 webgui: curl error: Failed to connect to localhost port 80 after 0 ms: Could not connect to server endpoint: mainPingListener

Dec 2 18:10:54 BlockBuster2 publish: curl to mainPingListener failed

Dec 2 18:10:55 BlockBuster2 webgui: curl error: Failed to connect to localhost port 80 after 0 ms: Could not connect to server endpoint: temperature

Dec 2 18:10:55 BlockBuster2 publish: curl to temperature failed

Dec 2 18:10:55 BlockBuster2 webgui: curl error: Failed to connect to localhost port 80 after 0 ms: Could not connect to server endpoint: devices

Dec 2 18:10:55 BlockBuster2 publish: curl to devices failed

Dec 2 18:10:55 BlockBuster2 webgui: curl error: Failed to connect to localhost port 80 after 0 ms: Could not connect to server endpoint: arraymonitor

Dec 2 18:10:55 BlockBuster2 publish: curl to arraymonitor failed

Dec 2 18:10:55 BlockBuster2 webgui: curl error: Failed to connect to localhost port 80 after 0 ms: Could not connect to server endpoint: mainPingListener

Dec 2 18:10:55 BlockBuster2 publish: curl to mainPingListener failed

Dec 2 18:11:13 BlockBuster2 rc.nginx: Stopping Nginx server daemon gracefully...

Dec 2 18:11:13 BlockBuster2 rc.nginx: Nginx server daemon... Already stopped.

Dec 2 18:11:13 BlockBuster2 rc.nginx: Starting Nginx server daemon...

Dec 2 18:11:17 BlockBuster2 rc.nginx: Nginx server daemon... Started.

Dec 2 18:13:43 BlockBuster2 webgui: Successful login user root from 192.168.1.226

Dec 2 18:14:20 BlockBuster2 webgui: CaddyV2: Could not download icon https://d1q6f0aelx0por.cloudfront.net/product-logos/library-caddy-logo.png

IO would suspect a issue inteh bond and potenal need to install teh net driver plugin for realek devices.

NTP failed earlier int he boot before your first web ui and ssh login to the system. The sytem is not mainting a stable netowrk conection per the log and evental fails.

Installed the Realtek RTL8111 plugin from CA as suggested, and set upstream router as NTP sync. Will update around this time tomorrow. Thanks for helping to take a look @bmartino1