CMS Snapshot Analysis - Run Extensions at Application Level

Purpose (problem description)

This page provides the approach to troubleshoot the problems related to Run Extensions at Application Level during CMS Snapshot Analysis.

For more information, refer to Extensions - an introduction

Error Free Logs - CMS Snapshot Analysis - Run Extensions at Application Level - Web Service Linker - Error Free Logs - CAST AIP 83

Observed in CAST AIP

Release	Yes/No
8.3.x

Observed on RDBMS

RDBMS	Yes/No
CSS4
CSS3
CSS2

Action Plan

Perform the below actions

Locate the run extension at application level log file
Identify if the extensions registered at the beginning of the log are CAST official or custom extensions. You can verify this at CAST Extend by searching for the extension and looking at the extension details Last Published: Date By XXXX:
1. If XXX is CAST Product then the extension is supported
2. If XXX is CAST User Community or CAST Labs then the extension is not supported. If you discover in the next steps that the issue is caused by an unsupported extension, then contact directly the extension author by using the 'Contact Publishers' form found on the extension page.
Identify the step where the issue occurs. The issue can happen before, during, or after running an analysis of a specific extension. Locate the relevant log messages that describe the beginning and end of the analysis for that particular extension.
Log Messages
```
2018-01-05 17:25:56,212  INFO   MODULMSG ; Body      Running plugin com.castsoftware.angularjs...
2018-01-05 17:26:07,790  INFO   MODULMSG ; Body      Done running plugin com.castsoftware.angularjs. 
```
- If no ‘Running plugin’ information message is visible in the log, then an issue occurs before running analysis for a specific extension
- If the issue occurs after a ‘Running plugin’ message and before a ’Done Running plugin’ message, then it occurs during the analysis of a specific extension
- If the issue occurs after a ‘Done Running plugin’ and there is no new ‘Running plugin’ message, then it occurs after the analysis of a specific extension
Identify the kind of issue as per CAST Management Studio - Information - Type of issues
According to the identified step and type of issue, identified in previous steps:
1. If the issue occurs before the analysis of a specific extension
  1. If it is a performance issue:
    1. If it is a performance issue during updating CSV calculation:
      2016-12-16 09:53:32,142 INFO Updating cast system views ...
      1. If some unsupported extensions are used, then they may use update CSV steps. This is outside the scope of support and you should contact directly the extension author.
      2. If only supported extensions are used, CSV calculation is not used by the supported extensions and you can remove it by doing the following:
        Create a copy of <INSTALL_FOLDER>\Third-Party\Python34\Lib\site-packages\cast\application\internal\run_plugins.py and rename it to run_plugins.original
        n <INSTALL_FOLDER>\Third-Party\Python34\Lib\site-packages\cast\application\internal\run_plugins.py in a text editor like Notepad++ and replace following lines:
        
        logging.info("Updating cast system views ...") kb.update_cast_system_views() logging.info("Updating cast system views Done")
        
        with:
        
        logging.info("Updating cast system views function has been suspended...")
        
        Rerun analysis
2. If the issue occurs during the analysis of a specific extension
  1. If it is a performance issue:
    1. Upgrade to the latest functional release version of the extension and rerun analysis.
    2. Check troubleshooting guides for specific extensions
3. if the issue occurs after the analysis of a specific extension, Open the log "ApplicationExtensions-[DateTime].castlog" and check which extension is stuck.
4. If there are warnings in the ApplicationExtensions-[DateTime].castlog log as below:
```
  File "C:\Program Files\CAST\8.3\ThirdParty\Python34\lib\site-packages\sqlalchemy\pool.py", line 948, in _do_get
    return self._pool.get(wait, self._timeout)
  File "C:\Program Files\CAST\8.3\ThirdParty\Python34\lib\site-packages\sqlalchemy\util\queue.py", line 145, in get
    raise Empty
sqlalchemy.util.queue.Empty

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Program Files\CAST\8.3\ThirdParty\Python34\lib\site-packages\sqlalchemy\engine\strategies.py", line 90, in connect
    return dialect.connect(*cargs, **cparams)
  File "C:\Program Files\CAST\8.3\ThirdParty\Python34\lib\site-packages\sqlalchemy\engine\default.py", line 377, in connect
    return self.dbapi.connect(*cargs, **cparams)
  File "C:\Program Files\CAST\8.3\ThirdParty\Python34\lib\site-packages\pg8000\__init__.py", line 328, in connect
    user, host, unix_sock, port, database, password, ssl)
  File "C:\Program Files\CAST\8.3\ThirdParty\Python34\lib\site-packages\pg8000\core.py", line 1263, in __init__
    raise self.error
pg8000.ProgrammingError: (b'FATAL', b'53300', b'sorry, too many clients already')
```
  you need to follow this page RDBMS - CAST Storage Service - Error - Sorry too many clients to resolve this issue or you can just restart the CSS services for a quick fix.
Once you have identified the extension that is culprit, select the relevant page:
- CMS Snapshot Analysis - Run Extensions at Application Level - Security For Java
If the above steps do not solve your issue contact CAST Technical Support. with the following Relevant input

Relevant input

CAST Support Tool (CST) - alias Sherlock export with the following options Export Logs, Export Configuration files, Export CAST Bases with Management Base and Knowledge Base Export source code.

Notes/comments

Tickets # 7401, # 9988 , # 10827, # 10938, # 10968, # 10985, # 11039, # 11042

Related Pages