Product:
Planning Analytics 2.0.9.18
Microsoft Windows 2019 server

Issue:

Error in TI process when run at random times.

Suggested solution:

Error: Prolog procedure line (9): Unable to register subset
Can be that the destroy of the subset did not work, as a view is around using that subset.
Check what views you have open.

Error: Prolog procedure line (103): Subset “xxx” not found in dimension “Period”
Can be that the subset is not around anymore, the subset have already been deleted.
Can be if you use the SubsetCreate(‘Region’, ‘Northern Europe’, 1);
Change to 0 (zero) in the TI process and see if that helps.

SubsetCreate(DimName, SubName, [AsTemporary]);

AsTemporary
This is an optional argument that specifies whether the subset being created is temporary. 1 indicates a temporary subset, 0 indicates a permanent subset. If this argument is omitted, the subset is permanent.

 

More Information:

https://www.ibm.com/docs/en/planning-analytics/2.0.0?topic=smtf-subsetcreate

https://www.ibm.com/support/pages/unable-register-subset-error-when-creating-dynamic-subset-data-tab-ti 

 

Product:
Planning Analytics 2.0.9.18
Microsoft Windows 2019

Issue:
The time value in log file is not correct.

Solution:

Add

# Specify GMT or Local timezone
log4j.appender.S1.TimeZone=Local

to your tm1s-log.properties file that should be in the same folder as your tm1s.cfg file.

This should give you have logfiles with same time stamp as the clock on the server.

To test create a TI process with this in PROLOG:

 

In the log file you will see lines like this:

13972 [4a] INFO 2023-11-03 15:17:41.836 TM1.TILogOutput This is the end of the process !!!
13972 [4a] INFO 2023-11-03 15:17:41.836 TM1.Process Process “S. 10 Test of time value”: finished executing normally, elapsed time 0.02 seconds
When GMT is set, the time in the logfile will be ENGLISH TIME (GMT), and depending on time difference it will differ from the server time. Check https://24timezones.com/difference/gmt/stockholm
15296 [4a] INFO 2023-11-03 16:27:43.826 TM1.TILogOutput This is the end of the process !!!
15296 [4a] INFO 2023-11-03 16:27:43.826 TM1.Process Process “S. 10 Test of time value”: finished executing normally, elapsed time 0.00 seconds

With Local set in the file – the time in the logfile should be the same as the windows server clock.

In the text file will the time be shown as above – this is always the computer time of the server. Function NOW give the server time.

The Chore is run at local time when you select local. If UTC is selected it will run at the GMT time shown.

18032 [4] INFO 2023-11-04 07:14:29.923 TM1.Chore Registering chore: “S. 10 test of time” Start time: 2023/11/04 06:15:45 Frequency: 01:00:00:00
15736 [] INFO 2023-11-04 07:15:45.050 TM1.Chore Chore “S. 10 test of time” executed by scheduler

15736 [] INFO 2023-11-04 07:15:45.050 TM1.Process Process “S. 10 Test of time value” executed by chore “S. 10 test of time”
15736 [] INFO 2023-11-04 07:15:45.053 TM1.TILogOutput This is the end of the process !!!
15736 [] INFO 2023-11-04 07:15:45.053 TM1.Process Process “S. 10 Test of time value”: finished executing normally, elapsed time 0.00 seconds
15736 [] INFO 2023-11-04 07:15:45.053 TM1.Chore Chore “S. 10 test of time” time = 0.00 seconds
15736 [] INFO 2023-11-04 07:15:45.054 TM1.Chore Chore “S. 10 test of time” finished executing

Recommend to use Local time setting in chores, if you do not have servers in different time zones.

The line in log file for when you set the start time will always be in GMT time, like Registering chore: “S. 10 test of time” Start time: 2023/11/04 06:25:45 Frequency: 01:00:00:00, even do you have selected local server time in the chore and choose to start at 7:25 AM.

To setup a chore:

  1. In the Server Explorer, select the Chores icon beneath the server on which you want to create the chore.
  2. Choose ChoresCreate New Chore.

    The Chore Setup Wizard opens.

  3. In the Available list, select the process for which you want to create a chore.
  4. Click the right arrow icon.
  5. Click Next.
  6. Click a date on the calendar to specify a start date for the initial execution of the chore.
  7. Enter a time to specify the start time for the initial execution of the chore.
  8. Set the fields in the Chore Execution Frequency box to define the interval at which the chore is executed.
  9. Select a Run Chore Time option.
    • Local Server Time – Runs at the local server time, including during Daylight Saving Time/Summer Time periods.
    • UTC Time – Always runs at UTC, regardless of local Daylight Saving Time/Summer Time.
  10. Fill the Chore Schedule is Active box.
  11. Click Finish.

    The Save Chore As dialog box opens.

  12. Enter a name for the chore and click Save.

 

More Information:

https://exploringtm1.com/changing-tm1-server-log-time-zone-stamp/ 

https://everanalytics.wordpress.com/2015/07/23/write-to-tm1server-log-file-from-turbo-intergrator-ti-process-in-cognos-tm1/ 

https://www.ibm.com/docs/en/planning-analytics/2.0.0?topic=dtrf-timst 

https://exploringtm1.com/date-and-time-functions-for-easy-date-manipulation/ 

https://www.ibm.com/docs/el/planning-analytics/2.0.0?topic=turbointegrator-scheduling-process-automatic-execution-chores 

https://tm1up.com/9-chores-in-tm1.html 

How to set up Turbo Integrator Chores to run Advanced Scheduling

https://www.bihints.com/pushing-data-iseries-tm1 

Product:
Planning Analytics Workspace version 88

Issue:

How to select the lowest leaf members in the subset editor in workspace?

Suggested Solution:

On the left side, select all leaves to list only the members.

Click on replace icon, to move all selected on left to the right, and replace any previous values there.

Click Apply to update the view with the new subset.

 

More Information:

https://pmsquare.com/analytics-blog/2022/5/5/new-cube-viewer-set-editor-in-planning-analytics 

https://revelwood.com/ibm-planning-analytics-tips-tricks-new-parameters-for-turbo-integrator/ 

https://community.ibm.com/community/user/businessanalytics/blogs/stuart-king1/2021/12/13/planning-analytics-workspace-new-cube-viewer-and-s 

Product:
Planning Analytics Workspace Version 88
PAA Agent version 2.0.88.1607  ( version found in file D:\Program Files\ibm\cognos\tm1_64\paa_agent\wlp\usr\servers\kate-agent\version.txt)

Issue:

Planning Analytics Workspace Administration page can not display information about the TM1 instances.

You need to check the PA Administration Agent log files to get more information.

The message.log files are found in folder D:\Program Files\ibm\cognos\tm1_64\paa_agent\wlp\usr\servers\kate-agent\logs on the TM1 server.

You have some TM1 instance that there name is shown in garbage character – you are probably using a character only used in your language, and not in English.

Even that you stop your TM1 instance with the none-english name, the PAW administration page does not give you access to the other TM1 instances.

Error message in log file:

[10/6/23 9:30:58:542 CEST] 00000069 SystemErr R ERROR:status.py:Exception while getting windows registry details:
Traceback (most recent call last):
File “kateagent/scripts\status.py”, line 904, in get_win_registry_detail_batch
p = subprocess.Popen([“powershell.exe”, service_cmd],
File “D:\Program Files\ibm\cognos\tm1_64\paa_agent\wlp\usr\servers\kate-agent\apps\expanded\PA_KATE_AGENT.war\WEB-INF\lib\jython-standalone-2.7.2.jar\Lib\subprocess.py”, line 892, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File “D:\Program Files\ibm\cognos\tm1_64\paa_agent\wlp\usr\servers\kate-agent\apps\expanded\PA_KATE_AGENT.war\WEB-INF\lib\jython-standalone-2.7.2.jar\Lib\subprocess.py”, line 1361, in _execute_child
args = [fileSystemDecode(arg) for arg in args]
UnicodeDecodeError: ‘utf-8’ codec can’t decode bytes in position 437-438: invalid data
[10/6/23 9:30:58:542 CEST] 00000069 com.ibm.pa.kate.agent.scheduler.ScheduledTask E Error occurred while updating the server info json file
Traceback (most recent call last):
File “kateagent/scripts\status.py”, line 1025, in <module>
configPaths = get_win_registry_detail_batch(allServers)
File “kateagent/scripts\status.py”, line 922, in get_win_registry_detail_batch
return mapped
UnboundLocalError: local variable ‘mapped’ referenced before assignment

 

Suggested Solution:

The PAA agent will run a python script status.py to check for what Tm1 instance exist and other information, on line 922 it will read the windows registry to find the started TM1 instances – in key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services – check at that location in REGEDIT.EXE program. If there is any non-english character, like in service name or “DisplayName”=”IBM Cognos TM1 Server … then this can be the issue.

The error say it found a character that it can not understand with UTF-8, and therefor have problem scanning for more information.

Inside Cognos Configuration for Planning Analytics, remove the application with the strange name, and register it again with a name that only use English characters.

It can be that you have created the TM1 instance from the command prompt and not from the Cognos Configuration program, then it can be registered with wrong codepage.

Like;

tm1sd.exe -install -n”TM1 Production Server” -z”C:\Program Files\Cognos\TM1\Custom\TM1Data\PData”

Check that the values in registry is readable, and then restart the kate-agent (IBM Planning Analytics Administration Agent)

More information:

https://www.joelonsoftware.com/2003/10/08/the-absolute-minimum-every-software-developer-absolutely-positively-must-know-about-unicode-and-character-sets-no-excuses/ 

https://www.ibm.com/docs/en/planning-analytics/2.0.0?topic=rtso-setting-up-tm1-server-run-as-windows-service 

https://www.ibm.com/support/pages/setting-tm1-server-run-service 

The python code to find the information;

def get_win_registry_detail_batch(service_names):
paths = []
for n in service_names:
paths.append("'HKLM:\SYSTEM\CurrentControlSet\Services\{}'".format(n))
service_cmd = "Get-ItemPropertyValue -Path {} -Name ConfigPath".format(", ".join(paths))
try:
p = subprocess.Popen(["powershell.exe", service_cmd],
stdout=subprocess.PIPE,
stderr=subprocess.PIPE)
out, err = p.communicate()
vettedResults = [line.strip()
for line in out.replace('\r', '').split('\n')
if line != '' and re.match(r'^.:\\', line)]
mapped = zip(service_names, vettedResults)
if p is not None and p.poll() == None:
p.kill()
if err and out is None:
logger.error('Error while getting windows registry details: {}'.format(err))
except Exception as e:
logger.exception('Exception while getting windows registry details: {}'.format(e.message))
return mapped

 

 

Product:

Planning Analytics Workspace

Problem:

List of versions that match other parts like the server and the workspace.

Solution:

Check the web for a list of matches.

https://www.ibm.com/support/pages/node/6519826

 

 

*IBM recommends that those who use Custom Reports and Dynamic Reports upgrade to Planning Analytics for Excel 2.0.89 immediately. For more details, see this Flash Alert.

*IBM recommends that customers upgrade to Planning Analytics Local 2.0.9.18. For more details, see this Flash Alert.

The version of PAW to use with PAX is the same version number or one above or one below. For example, if you have PAX version 2.0.50 installed, then use PAW version 2.0.49, 2.0.50 or 2.0.51.

New version for Planning Analytics Workspace, Planning Analytics for Excel comes out every 15-40 days, for Planning analytics new version comes out every 3-6 months.

 

More Information:

https://exploringtm1.com/planning-analytics-version-management/ 

https://www.tm1forum.com/viewtopic.php?t=16128 

https://blog.octanesolutions.com.au/pa-paw-pax-version-conformance

Product:
Planning Analytics workspace version 88
Microsoft Windows 2019 server

Issue:

OS report that all memory is used on the Windows server.

Solution:

First check the task manager to find what application is eating the memory.

It can be the anti-virus program is using all memory. If registry or msmpeng.exe is using all page pools then that can be that (anti-virus) program who is using all memory.

Exclude the TM1 PAW folders from the anti-virus scanning and restart the windows server.

D:\Docker

D:\PAW88

C:\ProgramData\docker

C:\Program Files\docker

 

The docker program is listed as dockerd.exe in task manager.

More information:

https://www.minitool.com/news/microsoft-defender-antivirus-service-high-memory.html 

https://www.ibm.com/docs/en/SSD29G_2.0.0/com.ibm.swg.ba.cognos.tm1_prism_gs.2.0.0.doc/tm1_prism_gs.pdf 

https://exploringtm1.com/planning-analytics-workspace-scripts/ 

Product:
Planning Analytics 2.0.9.18
Microsoft Windows 2019 Server

Issue:

When running TI process that have worked before we get error random like this;

Error in process completion: Unable to save subset “computed subsetname here” in dimension “Version”

Possible Solution:

That the a new anti-virus software is installed, that blocks the TM1 TI process from delete old subset files in data folder.

If you have MS Defender, ask to exclude the data folder and subfolders from the scanning. E.g. d:\tm1\budget\data

The anti-virus software is running from folder C:\ProgramData\Microsoft\Windows Defender\Platform\4.18.23080.2006-0

More Information:

https://answers.microsoft.com/en-us/windows/forum/all/windows-defender-real-time-protection-service/fda3f73e-cc0a-4946-9b9d-3c05057ef90c

https://www.softeng.es/en/blog/microsoft-defender-for-endpoint-the-solution-to-protect-detect-and-respond-to-the-most-advanced-attacks/ 

https://code.cubewise.com/bedrock 

Product:

Planning Analytics 2.0.9.18

Microsoft Windows 2019 server

Issue:

TM1 TI process that have worked before, crash now with error:

Error: Data procedure line (0): Exception Occurred during process execution: TM1MemoryException: Temporary pool exceeded

Possible Solution:

Change in the Tm1s.cfg file for your application to have a bigger value for MaximumViewSize, like MaximumViewSize=1000.

Restart the TM1 service, and run your process again.

MaximumViewSize is a per thread limitation.

More information:

https://www.ibm.com/support/pages/warning-noted-tm1-server-log-memorytemppoolexceeded 

https://www.ibm.com/docs/en/planning-analytics/2.0.0?topic=pitf-applymaximumviewsizetoentiretransaction#concept_ur1_bbp_rq 

By default MaximumViewSize checks individual view processing. For example, if 10 views are processed in a single transaction, the threshold is crossed only if the processing of any single view crosses the threshold. See MaximumViewSize.

With ApplyMaximumViewSizeToEntireTransaction=T parameter set to True, the cumulative memory usage of all views processed in a single transaction is compared against the threshold value. This allows the memory size threshold to catch more transactions that consume large amounts of memory.

Product:
Planning Analytics Local 2.0.9.18
TM1_version=TM1-AW64-ML-RTM-11.0.918.3-0
Microsoft Windows 2019 server

Problem:

After upgrade of Planning Analytics Local installation (PAL), the TM1 App Web is not showing the applications.

Suggested Solution:

Stop the service IBM Cognos TM1

Go to folder D:\Program Files\ibm\cognos\tm1_64\webapps\pmpsvc\WEB-INF\configuration

Rename fpmsvc_config.xml to fpmsvc_config.xml.old.txt

Rename fpmsvc_config.xml.new to fpmsvc_config.xml

Copy the lines between, the tm1 markers, that contain the name of the applications:

<tm1>
 </tm1>

from the file fpmsvc_config.xml.old.txt to the file fpmsvc_config.xml

Now the applications and gateway uri should be listed in the new file.

Start the service IBM Cognos TM1

More information:

https://www.ibm.com/support/pages/tm1-application-does-not-appear-tm1-applications-list-after-deployment

Product:

Planning Analytics Workspace 88  (file version.ps1 in folder paw\config contains a version number)
$env:PAW_BUILD=”121″
$env:PAW_RELEASE=”2.0.88″
Microsoft Windows 2019 server

Issue:

What containers should be running in a working PAW installation?

Solution:

Start powershell as administrator and enter command:

docker ps

This will list all running containers – should be these:

CONTAINER ID IMAGE                                                               PORTS                        NAMES
b6874749d0a5 127.0.0.1:5000/planninganalytics/prism-platform:3.0.2365.2-ltsc2019 9080/tcp                     prism-platform
5f104714f851 127.0.0.1:5000/planninganalytics/bss:1.0.1397-ltsc2019              8082/tcp                     bss
a946de8db063 127.0.0.1:5000/planninganalytics/pa-gateway:1.0.1098-ltsc2019       0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp pa-gateway
83e22e0be1f8 127.0.0.1:5000/planninganalytics/neo-provision:1.0.392-ltsc2019     8083/tcp                     neo-provision
6d11be2a5fd7 127.0.0.1:5000/planninganalytics/neo-idviz:9.0.982-ltsc2019         9060/tcp                     neo-idviz
e8c3bd52ca54 127.0.0.1:5000/planninganalytics/monitor:2.0.88.3035-ltsc2019       9082/tcp                     monitor
bfa3ef090459 127.0.0.1:5000/planninganalytics/wa-proxy:1.0.1020-ltsc2019         1338/tcp                     wa-proxy
fb7bd169d5b3 127.0.0.1:5000/planninganalytics/async-service:1.0.387-ltsc2019     9666/tcp                     async-service
fef9418814e5 127.0.0.1:5000/planninganalytics/share-platform:1.0.425-ltsc2019    9110/tcp                     share-platform
afaeb58c897c 127.0.0.1:5000/planninganalytics/pa-plan-service:1.0.2023051901-ltsc2019 9080/tcp                plan-service
b84bc681967b 127.0.0.1:5000/planninganalytics/paw-ui-api:1.0.260-ltsc2019        3000/tcp                     paw-ui-api
31ac3574ea06 127.0.0.1:5000/planninganalytics/user-admin:1.0.737-ltsc2019        3333/tcp                     user-admin
5e55f009d40f 127.0.0.1:5000/planninganalytics/pa-glass:3.0.9788-ltsc2019         9080/tcp                     glass
8dc5e074265d 127.0.0.1:5000/planninganalytics/atlas-service:125-ltsc2019         9076/tcp                     atlas
5d482449ac97 127.0.0.1:5000/planninganalytics/prism-proxy:3.0.11099-ltsc2019     9090/tcp, 9100/tcp           prism-proxy
59b615950e2b 127.0.0.1:5000/planninganalytics/couchdb:234-ltsc2019               5984/tcp                     couchdb
1c0305d7d945 127.0.0.1:5000/planninganalytics/share-app:1.0.605-ltsc2019         9700/tcp                     share-app
010ac1fac8db 127.0.0.1:5000/planninganalytics/mongo:1.0.205-ltsc2019             27017/tcp                    mongo
481b8cb26b29 127.0.0.1:5000/planninganalytics/prism-app:3.0.5536-ltsc2019        9600/tcp                     prism-app
78709cb2d0d1 127.0.0.1:5000/planninganalytics/palm-service:1.0.340-ltsc2019      9085/tcp                     palm-service
545cf6eb986f 127.0.0.1:5000/planninganalytics/pa-content-service:1.0.310-ltsc2019 9191/tcp                    pa-content
61093630f145 127.0.0.1:5000/planninganalytics/redis:1.0.206-ltsc2019             6379/tcp                     redis
4e149a0ae6ea 127.0.0.1:5000/planninganalytics/pa-cdn:3.0.9788-ltsc2019           8080/tcp                     cdn
927748e22277 127.0.0.1:5000/planninganalytics/share-proxy:1.0.605-ltsc2019       9070/tcp                     share-proxy
8004ed0c651d 127.0.0.1:5000/planninganalytics/pa-predict-svc:1.0.1054-ltsc2019   9610/tcp                     pa-predict
0b084764c655 127.0.0.1:5000/planninganalytics/tm1proxy:1.0.411-ltsc2019          1339/tcp                     tm1proxy
394e473a354d 127.0.0.1:5000/planninganalytics/admintool:1.0.340-ltsc2019         8888/tcp                     admintool

Command docker images will list all installed images, should normally be these:

REPOSITORY                                       TAG                  IMAGE ID     CREATED      SIZE
127.0.0.1:5000/planninganalytics/monitor         2.0.88.3035-ltsc2019 cdd1118734aa 7 weeks ago  5.35GB
127.0.0.1:5000/planninganalytics/pa-glass        3.0.9788-ltsc2019    eda31db65292 2 months ago 5.27GB
127.0.0.1:5000/planninganalytics/pa-cdn          3.0.9788-ltsc2019    e30ce3e584eb 2 months ago 5.34GB
127.0.0.1:5000/planninganalytics/prism-proxy     3.0.11099-ltsc2019   ad0700244d5f 2 months ago 4.77GB
127.0.0.1:5000/planninganalytics/share-proxy     1.0.605-ltsc2019     7c0f57f0564c 2 months ago 4.71GB
127.0.0.1:5000/planninganalytics/share-app       1.0.605-ltsc2019     30028e59100d 2 months ago 4.72GB
127.0.0.1:5000/planninganalytics/pa-gateway      1.0.1098-ltsc2019    bc188fbdba7e 2 months ago 4.71GB
127.0.0.1:5000/planninganalytics/prism-platform  3.0.2365.2-ltsc2019  1af1c76c5ebe 2 months ago 5.66GB
127.0.0.1:5000/planninganalytics/prism-app       3.0.5536-ltsc2019    149080a8fc2d 2 months ago 4.73GB
127.0.0.1:5000/planninganalytics/palm-service    1.0.340-ltsc2019     5870fb15710e 2 months ago 4.76GB
127.0.0.1:5000/planninganalytics/tm1proxy        1.0.411-ltsc2019     301bf315ca8b 2 months ago 4.63GB
127.0.0.1:5000/planninganalytics/bss             1.0.1397-ltsc2019    16a9f3403a03 2 months ago 5.32GB
127.0.0.1:5000/planninganalytics/wa-proxy        1.0.1020-ltsc2019    d365a00fbcb0 2 months ago 4.73GB
127.0.0.1:5000/planninganalytics/paw-ui-api      1.0.260-ltsc2019     9e3f8ca98062 2 months ago 4.82GB
127.0.0.1:5000/planninganalytics/async-service   1.0.387-ltsc2019     f7e111569a61 2 months ago 4.82GB
127.0.0.1:5000/planninganalytics/pa-predict-svc  1.0.1054-ltsc2019    6dabd0bfa755 2 months ago 5.34GB
127.0.0.1:5000/planninganalytics/user-admin      1.0.737-ltsc2019     e4ea0b9f71cf 2 months ago 4.82GB
127.0.0.1:5000/planninganalytics/neo-provision   1.0.392-ltsc2019     7c04066c0fed 2 months ago 5.35GB
127.0.0.1:5000/planninganalytics/couchdb         234-ltsc2019         7832c5ecc13c 2 months ago 4.93GB
127.0.0.1:5000/planninganalytics/neo-idviz       9.0.982-ltsc2019     6847d7d6725d 2 months ago 5.55GB
127.0.0.1:5000/planninganalytics/pa-plan-service 1.0.2023051901-ltsc2019 04c8517f2f3a 2 months ago 5.28GB
127.0.0.1:5000/planninganalytics/admintool       1.0.340-ltsc2019     428093815025 2 months ago 4.72GB
127.0.0.1:5000/planninganalytics/pa-content-service 1.0.310-ltsc2019  bfa8b7dcb3f4 2 months ago 4.73GB
127.0.0.1:5000/planninganalytics/atlas-service   125-ltsc2019         f012ea094ed4 2 months ago 5.31GB
127.0.0.1:5000/planninganalytics/share-platform  1.0.425-ltsc2019     9ff87c1b417a 2 months ago 5.29GB
127.0.0.1:5000/planninganalytics/bss-init        1.0.342-ltsc2019     caf9f295cdcb 2 months ago 4.71GB
127.0.0.1:5000/planninganalytics/redis           1.0.206-ltsc2019     c5f67bbdafc5 2 months ago 4.64GB
127.0.0.1:5000/planninganalytics/mongo           1.0.205-ltsc2019     852817ecb6fe 2 months ago 4.85GB
127.0.0.1:5000/planninganalytics/ibm-java8       225-ltsc2019         7d2f0cc5bd1f 2 months ago 5.11GB
127.0.0.1:5000/planninganalytics/couchdb-init    1.0.835-ltsc2019     85873eaa9a40 2 months ago 4.62GB

 

If you are missing a image, the installation have failed. If not all containers is running, then you may have issues with your Anti-virus software.

Uninstall Trellix/McAfee and reboot server and try again to install PAW.

 

More Information:

https://www.ibm.com/support/pages/download-ibm-planning-analytics-local-v20-planning-analytics-workspace-release-88-fix-central

https://exploringtm1.com/how-to-install-planning-analytics-workspace-to-windows-server-2019/

https://www.ibm.com/support/pages/after-each-reboot-some-planning-analytics-workspace-containers-are-failing-start

https://circleci.com/blog/docker-and-cicd-tutorial-a-deep-dive-into-containers/

https://gist.github.com/danijeljw/a7a2553bd06742648172363ce3983a9a