Same problem ( and same solution ) here with PAW 2.0.87 on Windows Server 2016 and Mirantis Container Runtime (MCR) 20.10.21 on a virtual server with lots of free RAM and disk space:
All of a sudden creating containers by the PowerShell script ".\scripts\paw.ps1" failed, each time the error messages pointing to other random containers.
A full uninstall / removal of PAW by
./scripts/clean.ps1
./scripts/paw.ps1 down --rmi all -v
docker system prune -a
followed by an uninstall & re-install of the MCR did not resolve the issue.
But we got a different ( german ) error message:
ERROR: for <container> Cannot start service <container>: hcsshim::CreateComputeSystem <UniqueID>: Nicht gen³gend Systemressourcen, um den angeforderten Dienst auszuf³hren.
for instance:
ERROR: for prism-proxy Cannot start service prism-proxy: hcsshim::CreateComputeSystem 65ec1d682fc51616524e5e49fe96ea9d3e8477f71cb17c03c06573455651dc00: Nicht gen³gend Systemressourcen, um den angeforderten Dienst auszuf³hren.
No containers to start
In C:\PAW\ipa_workspace_win_2016_2.0.87.1495\scripts\init.ps1:78 Zeichen:13
+ throw "Execution failed with exit code ${LASTEXITCODE}: $ ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OperationStopped: (Execution faile...ainers to start:String) [], RuntimeException
+ FullyQualifiedErrorId : Execution failed with exit code 1: start service prism-proxy: hcsshim::CreateComputeSystem
8952bef3ab7c4a980b3f65e9ba5ba5d6a9e7da3fef088482d8f4da026b4115ee: Nicht gen³gend Systemressourcen, um den angeforderten Dienst auszuf³hren.
being a translation of the english error message:
ERROR: for <container> Cannot start service <container>: hcsshim::CreateComputeSystem <UniqueID>: Insufficient system resources exist to complete the requested service.
------------------------------
Bernd Siebert
------------------------------
Original Message:
Sent: Mon March 25, 2024 10:55 AM
From: Jaganathan Chetty Palanisamy
Subject: Planning Analytics workspace is down due to space error on docker/windowsfilter folder
Hi,
The issue is resolved. IBM gave the below steps to resolve the issue.
1. docker rm $(docker ps -a -q)
2. edit regedit
Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\NDIS\IfTypes\23
registry name - IfUsedNetLuidIndices
do modify select all values, delete them and type in '01'
save and exit
3. reboot the server
4. check docker engine is running
5. Run ./paw.ps1 to create the containers
------------------------------
Jaganathan Chetty Palanisamy
------------------------------
Original Message:
Sent: Tue March 19, 2024 04:39 PM
From: Jaganathan Chetty Palanisamy
Subject: Planning Analytics workspace is down due to space error on docker/windowsfilter folder
Thanks Walter for your response.
Our Wintel has increased the size of C: by 100 GB (we have 128 GB of free space now in C:) and reboot the server. But still the PAW startup is saying the same message as insufficient resources. Now it does not look like a space issue on C: drive. Docker engine seems to be running fine.
The problem initially started after Wintel team installed some OS patches on the server and rebooted, PAW service did not come up after that. Wintel team has rolled back the installed patches too now but no luck. It looks like there is an antivirus called Crowdstrike running on the box, I am going to have them turned off and try again. If you have the instructions on removing PAW and reinstalling again on windows 2016, could you share it. I am going to try that if turning off the antivirus does not work.
------------------------------
Jaganathan Chetty Palanisamy
Original Message:
Sent: Mon March 18, 2024 04:52 PM
From: Walter Coffen
Subject: Planning Analytics workspace is down due to space error on docker/windowsfilter folder
Jagan.
Make sure your server has been backed up by IT.
Delete or move off of the C:\ drive ipa_workspace_win_2.0.55.1184.zip and /images/images.tar. This will free up more than 24GB. They are only needed if you install, or re-install PAW; they are not needed to run PAW day-to-day. The first file can be re-downloaded from IBM if you delete it, and it contains the second file. If you delete, make sure you empty the server's Recycle bin, otherwise disk space will not free up. You should look for other wasted space such as prior versions of PAW where you might have the old version's zip and tar files. Maybe a ton of log files have accumulated too. Additionally, there is a \scripts\clean.ps1 that should be run in the old/prior PAW folder when a newly upgraded PAW has been installed. Do not run clean.ps1 for the current PAW until a newer PAW is up and validated. If you run this incorrectly, you will likely need the server restored by IT.
Reboot, Docker is probably in a funk after not being able to fully start PAW.
You should probably have a BIG D:\ or E:\ data drive where PAW gets stored, rather than the C:\ drive where Microsoft does all its work. PAW can be told to write to a different drive as the C:\ drive is usually not where IT wants stuff written.
You should upgrade PAW and PA. A lot has happened since 2020.
------------------------------
Walter Coffen
Technology Manager
QueBIT Consulting, LLC