6.9.2/6.10.3/6.11.0 Unable to fork docker network

[shunde]

Diagnostics: morn-diagnostics-20220915-1214.zip

 

When visiting the Docker tab I sometimes stumble into an error message:

 

Quote

Warning: exec(): Unable to fork [docker network ls --format='{{.Name}}={{.Driver}}' 2>/dev/null] in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 979

 

And earlier today I received a similar error within CA on the apps tab.

 

Something really wrong went on during defaultSortOrder
Post the ENTIRE contents of this message in the Community Applications Support Thread

OS: 6.9.2
Modified CA
Browser: Mozilla/5.0 (X11; Linux x86_64; rv:104.0) Gecko/20100101 Firefox/104.0
Language:

<br /> <b>Warning</b>: exec(): Unable to fork [docker network ls --format='{{.Name}}={{.Driver}}' 2&gt;/dev/null] in <b>/usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php</b> on line <b>979</b><br /> <br /> <b>Warning</b>: exec(): Unable to fork [/usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin 'version' '/var/log/plugins/community.applications.plg'] in <b>/usr/local/emhttp/plugins/dynamix.plugin.manager/include/PluginHelpers.php</b> on line <b>17</b><br /> <br /> <b>Warning</b>: shell_exec(): Unable to execute 'cd /usr/local/emhttp/plugins/community.applications &amp;&amp; md5sum -c ca.md5' in <b>/usr/local/emhttp/plugins/community.applications/include/exec.php</b> on line <b>62</b><br /> {"status":"ok"}

Ive also attached massivelog.txt  from the CA tab.massivelog.txt

 

Bonus bug:
Tried to download diagnostics and was met with

/boot/logs
Warning: exec(): Unable to fork [echo /usr/local/emhttp/webGui/scripts/diagnostics '/usr/local/emhttp/morn-diagnostics-20220915-1212.zip' | at NOW > /dev/null 2>&1] in /usr/local/emhttp/plugins/dynamix/include/Download.php on line 37
/morn-diagnostics-20220915-1212.zip

But trying to download again worked.

 

But the main issue seems to be DockerClient.php line 979.

Edited September 24, 2022 by shunde

[Squid]

I'd reboot and see what happens.  If there's still a problem, then post a new set of diagnostics (there's a ton of repeating errors logged, possibly all related, but hard to determine what exactly happened)

 

Would also be worthwhile to update to 6.10.3

[shunde]

The specific issue with unable to fork docker network seems to pup up randomly. I've even switched hardware (not the usb stick I boot with). But just restarted and I can see stuff in Apps for now.

[shunde]

It's back

Warning: exec(): Unable to fork [docker network ls --format='{{.Name}}={{.Driver}}' 2>/dev/null] in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 979

morn-diagnostics-20220915-1938.zip

 

Going to give 6.10.3 a try

Edited September 15, 2022 by shunde

[shunde]

Happens on 6.10.3 as well.

 

morn-diagnostics-20220923-0930.zip
Over at the docker tab I have:

Quote

Warning: exec(): Unable to fork [docker network ls --format='{{.Name}}={{.Driver}}' 2>/dev/null] in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 1011

[09:03]

And in settings I get:

Quote

Warning: exec(): Unable to fork [pkill -f /usr/local/emhttp/plugins/dynamix.docker.manager/nchan/docker_load >/dev/null &] in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php on line 545

 

 

Edit:
I did a reboot and still see the issue. But Diagnostics is never downloading. Its stuck on Downloading... - I've tried several times and the most scary thing is that I see "Unraid OS No Flash" instead of "Unraid OS Pro" from time to time.

 
On the bottom of the docker tab I have:

Quote

Warning: exec(): Unable to fork [pgrep 'rc.docker'] in /usr/local/emhttp/plugins/dynamix/include/Helpers.php on line 225

Edit:
Same errors in 6.11.0

Edited September 24, 2022 by shunde

[shunde]

Right.

 

I think I tested 3 CPUs, 2 motherboards and 5 or 6 sets of RAM (both ECC and non ECC) and had issues with memtest86+. Went and bought Memtest86 Pro and ran the same test many more times until I found a setup that worked.

 

That still gave me the errors with docker. So I bought a new USB stick and now it's gone. Yay