When trying to open my WebUI, it goes unresponsive/infinite load/some partial loads.

 

When trying to get logs it is filled with

 

 

kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6.
nginx: 2025/05/05 19:23:04 [alert] 14315#14315: worker process 1991285 exited on signal 11
kernel: nginx[1991301]: segfault at 0 ip 0000000000000000 sp 00007ffd10cf3748 error 14 in nginx[400000+24000] likely on CPU 22 (core 38, socket 0)
kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6.
nginx: 2025/05/05 19:23:05 [alert] 14315#14315: worker process 1991301 exited on signal 11
kernel: nginx[1991386]: segfault at 0 ip 0000000000000000 sp 00007ffd10cf3798 error 14 in nginx[400000+24000] likely on CPU 19 (core 35, socket 0)
kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6.
nginx: 2025/05/05 19:23:05 [alert] 14315#14315: worker process 1991386 exited on signal 11
kernel: nginx[1991387]: segfault at 0 ip 0000000000000000 sp 00007ffd10cf3748 error 14 in nginx[400000+24000] likely on CPU 14 (core 28, socket 0)
kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6.
nginx: 2025/05/05 19:23:06 [alert] 14315#14315: worker process 1991387 exited on signal 11
kernel: nginx[1991458]: segfault at 0 ip 0000000000000000 sp 00007ffd10cf3798 error 14 in nginx[400000+24000] likely on CPU 20 (core 36, socket 0)
kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6.
nginx: 2025/05/05 19:23:06 [alert] 14315#14315: worker process 1991458 exited on signal 11
kernel: nginx[1991459]: segfault at 0 ip 0000000000000000 sp 00007ffd10cf3798 error 14 in nginx[400000+24000] likely on CPU 4 (core 8, socket 0)
kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6.
nginx: 2025/05/05 19:23:07 [alert] 14315#14315: worker process 1991459 exited on signal 11
nginx: 2025/05/05 19:23:07 [alert] 14315#14315: worker process 1991542 exited on signal 11
kernel: show_signal_msg: 1 callbacks suppressed
kernel: nginx[1991552]: segfault at 0 ip 0000000000000000 sp 00007ffd10cf3798 error 14 in nginx[400000+24000] likely on CPU 1 (core 0, socket 0)
kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6.
nginx: 2025/05/05 19:23:08 [alert] 14315#14315: worker process 1991552 exited on signal 11
kernel: nginx[1991562]: segfault at 0 ip 0000000000000000 sp 00007ffd10cf3748 error 14 in nginx[400000+24000] likely on CPU 4 (core 8, socket 0)
kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6.
nginx: 2025/05/05 19:23:09 [alert] 14315#14315: worker process 1991562 exited on signal 11
kernel: nginx[1991631]: segfault at 0 ip 0000000000000000 sp 00007ffd10cf3798 error 14 in nginx[400000+24000] likely on CPU 18 (core 34, socket 0)
kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6.
nginx: 2025/05/05 19:23:09 [alert] 14315#14315: worker process 1991631 exited on signal 11
kernel: nginx[1991636]: segfault at 0 ip 0000000000000000 sp 00007ffd10cf3748 error 14 in nginx[400000+24000] likely on CPU 10 (core 20, socket 0)
kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6.
nginx: 2025/05/05 19:23:10 [alert] 14315#14315: worker process 1991636 exited on signal 11
kernel: nginx[1991724]: segfault at 0 ip 0000000000000000 sp 00007ffd10cf3798 error 14 in nginx[400000+24000] likely on CPU 2 (core 4, socket 0)
kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6.
nginx: 2025/05/05 19:23:10 [alert] 14315#14315: worker process 1991724 exited on signal 11
rc.nginx: Reloading Nginx server daemon...
kernel: nginx[1991725]: segfault at 0 ip 0000000000000000 sp 00007ffd10cf3748 error 14 in nginx[400000+24000] likely on CPU 6 (core 12, socket 0)
kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6.
nginx: 2025/05/05 19:23:11 [alert] 14315#14315: worker process 1991725 exited on signal 11
kernel: nginx[1991801]: segfault at 0 ip 0000000000000000 sp 00007ffd10cf3798 error 14 in nginx[400000+24000] likely on CPU 22 (core 38, socket 0)
kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6.

 

I have attached diagnostics. They didn't want to download correctly (stalled with `.crdownload` extension. I checked at least syslog and it looked good).

 

You can ignore disk sdk actively failing. I have been moving data off that dying drive the last 2 days.

 

I was able to resolve this through going to the physical server and using the terminal entering:

 

/etc/rc.d/rc.nginx reload

 

And I expect it had to do with me having WebUI pages open not closing properly (seen that as a common bug). But am open to it being something else. Sharing so hopefully someone else with this can see.

etemenanki-diagnostics-20250505-1937.zip

For those that jump straight to the comments for answers. For me, I was able to recover my WebUI through

 

 

/etc/rc.d/rc.nginx reload

 

Best of luck!

I just had this same issue on my server running 6.12.15. Uptime 38 days. Had to completely stop and then restart nginx, then it came good again.