I'm running into a problem on my server getting the above error after webgui crash

 

all ready reboot the server and delete the docker.img file and reconfigure all my docker service

 

but the webgui crash and i have restart the gui using "/etc/rc.d/rc.php-fpm restart" command

 

imrannas-diagnostics-20250511-2158.zip

Syslog is being spammed with PCI (and other) errors, try this first:

 

https://forums.unraid.net/topic/118286-nvme-drives-throwing-errors-filling-logs-instantly-how-to-resolve/?do=findComment&comment=1165009

 

Then reboot and post new diags.

Hi Jorge
thank for the suggestion on the pcie off error in the syslog
Attached new diagnos file

 

as of now the server is running without webgui crash after reboot

imrannas-diagnostics-20250513-0729.zip

No more PCI errors, and docker service appears to have started, or do you still have issues?

Still have issue that webgui will crash and docker service hang

now after second reboot and disabling few of the docker service continue to monitoring the server

Edited May 14, 20251 yr by mrunknownpbu

Hi JorgeB
if i would like to rebuild the server without losing the array data, is that possible

If you mean resetting all the server settings but keeping the data, you can do that with the Dynamix Factory Reset plugin.

this would no impact the data, only the docker and plugin install on the server correct ?

Correct, and all the settings, also note that if you want to keep the docker containers, save the user template folder on the flash drive, not sure if that is kept.

Currently i have reboot into safe mode and performing parity check

then will use factory reset using the dynamix plugin

4 hours ago, mrunknownpbu said:

docker service hang

Why do you have 100G docker.img?

 

Have you had problems filling it?

 

Are you filling it now?

 

The usual reason for filling docker.img is an application writing to a path that isn't mapped.

Initially i setup 100gb for the docker image
 

attached latest diag file

after two days in safe mode

imrannas-diagnostics-20250516-0717.zip

Your syslog is being spammed with these:

May 16 07:10:44 ImranNas ntpd[2582]: Soliciting pool server 47.254.196.78
May 16 07:11:31 ImranNas ntpd[2582]: Soliciting pool server 111.90.158.16
May 16 07:12:38 ImranNas ntpd[2582]: Soliciting pool server 47.254.196.78

Recommend using time.google.com for 1st NTP and leave the others blank

just update the ntp services in my router

On 5/16/2025 at 8:18 AM, trurl said:

Your syslog is being spammed with these:

May 16 07:10:44 ImranNas ntpd[2582]: Soliciting pool server 47.254.196.78
May 16 07:11:31 ImranNas ntpd[2582]: Soliciting pool server 111.90.158.16
May 16 07:12:38 ImranNas ntpd[2582]: Soliciting pool server 47.254.196.78

Recommend using time.google.com for 1st NTP and leave the others blank

 

HI Trurl
after letting the nas running for 1 day,

again encounter the error "Docker Service failed to start" where all the docker is up but inaccesible

 

attached the diagnostics file

 

imrannas-diagnostics-20250518-1413.zip

Don't see anything relevant logged, post the output from

 

docker info

 

3 hours ago, JorgeB said:

Don't see anything relevant logged, post the output from

 

docker info

 

root@ImranNas:~# docker info
Client:
 Version:    27.5.1
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.20.1
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx

Server:
 Containers: 23
  Running: 22
  Paused: 0
  Stopped: 1
 Images: 23
 Server Version: 27.5.1
 Storage Driver: overlay2
  Backing Filesystem: xfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 nvidia runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: bcc810d6b9066471b0b6fa75f557a15a1cbf31bb
 runc version: v1.2.4-0-g6c52b3f
 init version: de40ad0
 Security Options:
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 6.12.24-Unraid
 Operating System: Unraid OS 7.1 x86_64
 OSType: linux
 Architecture: x86_64
 CPUs: 40
 Total Memory: 62.8GiB
 Name: ImranNas
 ID: bf1b6ecb-b628-48b5-a2e8-6b6817687d36
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false
 Product License: Community Engine

WARNING: No swap limit support

Docker service appears to be running normally, not sure why the GUI complains.

26 minutes ago, JorgeB said:

Docker service appears to be running normally, not sure why the GUI complains.

Hi Jorge
below are the latest output for the command "docker info"

root@ImranNas:~# docker info
Client:
 Version:    27.5.1
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.20.1
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx

Server:
ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
errors pretty printing info

Now it's not running, post new diags.

13 hours ago, JorgeB said:

Now it's not running, post new diags.

Hi Jorge
webgui was unresponsive

attached the new diag

imrannas-diagnostics-20250520-0657.zip

5 hours ago, mrunknownpbu said:

Hi Jorge
webgui was unresponsive

attached the new diag

imrannas-diagnostics-20250520-0657.zip 245.69 kB · 0 downloads

Can you uninstall the connect plugin, reboot and then try again.

 

Reason for the unresponsive gui is a file that was required is missing...  Not quite sure how though.  If that fixes the unresponsive, then see if the docker tab is working.  If / when it fails, and you can live with it until I notice a response from you, then I might have some ideas, or troubleshooting ideas that might help with what's going on...

7 hours ago, Squid said:

Can you uninstall the connect plugin, reboot and then try again.

 

Reason for the unresponsive gui is a file that was required is missing...  Not quite sure how though.  If that fixes the unresponsive, then see if the docker tab is working.  If / when it fails, and you can live with it until I notice a response from you, then I might have some ideas, or troubleshooting ideas that might help with what's going on...

I have stop docker service as of now and uninstall the plugin
 

On 5/20/2025 at 7:36 AM, mrunknownpbu said:

I have stop docker service as of now and uninstall the plugin
 

Was there any improvement?

Also, besides connect, are you running docker compose plugin or something like Portainer or NextCloudAIO in docker?