You can generate and send the Polyspace Access service logs to MathWorks Support to help diagnose a Polyspace Access issue, be it an issue related to uploads, downloads, or performance.
To do that, use the access_debug tool to generate a zipped folder that contains the Docker logs and other output files.
If your Polyspace Access server is running under Kubernetes, please refer to this other article: https://www.mathworks.com/matlabcentral/answers/2112996-how-can-i-get-debug-information-for-polyspace-access-running-in-kubernetes
If you are using Polyspace Access via the Cluster Admin Agent, the script attached to this article can be used with Polyspace Access version R2020b and later.
Here is how to use it:
- Before you launch the script, activate the Polyspace Access debug mode to create logs with a more verbose output. To activate the debug mode, use URL: "http(s)://<FQDN>:<port>/setdebugmode/on", where "FQDN" is the Fully Qualified Domain Name of your Polyspace Access server. For example, https://example.access.server:9443/setdebugmode/on
- Then reproduce your issue. For instance, if it is an upload issue, you can execute upload again with option -log cli.txt (polyspace-access -log cli.txt -upload...). Then you will attach cli.txt with all_info.zip.
- As soon as the issue has been reproduced, use the attached script on this page. The script usage is as follows:
- Connect to the server where you installed Polyspace Access and open a shell session.
- Unzip the file access_debug.zip (attached to this post) in a folder, for example a subfolder of the Polyspace Access installation folder (where the Polyspace Access Cluster admin agent is located)
- In the folder where you unzipped the file, set the appropriate execution rights for the script access_debug.sh by running the command below: chmod u+x access_debug.sh
- Launch the script: ./access_debug.sh <path to the Polyspace Access folder>
- If you installed the tool in a subfolder of the Polyspace Access installation, no need to specify the argument, simply launch: ./access_debug.sh
- The script will then create a file named all_info_<date>.zip. Attach this zip file to your service request.
- Deactivate debug mode: http(s)://<FQDN>:<port>/setdebugmode/off
Note: The generated logs might contain names of projects that you uploaded to Polyspace Access. A copy of settings.json is done where the passwords have been removed.
