Troubleshooting Posit Team

Advanced

Posit Team is designed to be a fully managed solution.

Debugging

Diagnostics

The Posit Team diagnostics bundle is an archive that includes information about the environment that can be shared with Posit Support.

Download the diagnostics bundle from the System page in the Posit Team UI.

System page with diagnostics

System page with diagnostics

Posit Team logs

Logs for the Posit Team application are available in the diagnostics bundle, which can be downloaded from the System page in the Posit Team UI.

You can also access logs for the Posit Team controller using the SYSTEM$GET_SERVICE_LOGS Snowflake SQL function.

Snowsight UI
-- controller service logs
SELECT SYSTEM$GET_SERVICE_LOGS('POSIT_TEAM.services.controller', 0, 'controller');

If you do not have access, be sure that one of your user roles is granted the POSIT_TEAM_ADMIN application role.

Snowsight UI
GRANT APPLICATION ROLE POSIT_TEAM.POSIT_TEAM_ADMIN TO ROLE YOUR_USER_ROLE;

Product health and logs

The product management page shows the system health and service logs for that product.

The management page for each product shows the system health for that product and its service logs.

Manage page

Manage page

You can also access logs for the Posit Team controller using the SYSTEM$GET_SERVICE_LOGS Snowflake SQL function.

Run the following to access individual product service logs:

Snowsight UI
-- workbench service logs
SELECT SYSTEM$GET_SERVICE_LOGS('POSIT_TEAM.services.workbench', 0, 'workbench');
-- connect service logs
SELECT SYSTEM$GET_SERVICE_LOGS('POSIT_TEAM.services.connect', 0, 'connect');
-- package manager service logs
SELECT SYSTEM$GET_SERVICE_LOGS('POSIT_TEAM.services.package_manager', 0, 'package-manager');

If you do not have access, be sure that one of your user roles is granted the POSIT_TEAM_ADMIN application role.

Snowsight UI
GRANT APPLICATION ROLE POSIT_TEAM.POSIT_TEAM_ADMIN TO ROLE YOUR_USER_ROLE;

Customized account parameters

To identify all non-default account parameters for troubleshooting:

Snowsight UI
SHOW PARAMETERS IN ACCOUNT;
SELECT "key" AS parameter_name, "value" AS current_value, "default" AS default_value
FROM TABLE(RESULT_SCAN(LAST_QUERY_ID()))
WHERE "value" != "default"
ORDER BY "key";

Known issues

QUOTED_IDENTIFIERS_IGNORE_CASE

Posit Team is incompatible with QUOTED_IDENTIFIERS_IGNORE_CASE=true at the account level. The QUOTED_IDENTIFIERS_IGNORE_CASE Snowflake account parameter changes how quoted identifiers are handled, which prevents the native application from starting correctly.

If Posit Team fails to start and produces an error stating warehouse is required, check if this parameter has been modified:

Snowsight UI
SHOW PARAMETERS LIKE 'QUOTED_IDENTIFIERS_IGNORE_CASE' IN ACCOUNT;

If the value is true, reset it to the default:

Snowsight UI
ALTER ACCOUNT SET QUOTED_IDENTIFIERS_IGNORE_CASE = false;

A future Posit Team update will automatically adjust this parameter at the session level.

To identify all non-default account parameters for troubleshooting:

Snowsight UI
SHOW PARAMETERS IN ACCOUNT;
SELECT "key" AS parameter_name, "value" AS current_value, "default" AS default_value
FROM TABLE(RESULT_SCAN(LAST_QUERY_ID()))
WHERE "value" != "default"
ORDER BY "key";

Failed authenticating user error

By default Snowflake assigns secondary roles as ALL. If your account has modified this default behavior, users may encounter authentication issues. In that case, ensure that the default role for any user authenticating to the Posit Team App is set to one of the application roles for the Native App. The core issue here is that the authentication into the application uses your default role and all application roles are inferred from that role only if you have secondary roles disabled. There are two solutions we are aware of:

  1. Enable secondary roles for users who need access to the Native App ALTER USER "..." SET DEFAULT_SECONDARY_ROLES=('ALL') (recommended and is the Snowflake default value).
  2. Ensure that the user’s default role is granted one of the application roles for the Native App. This may not be ideal since typically default roles for users are set to be very broad and include many other users of the account. Additionally the application roles attached to the user’s default role will be the only application roles they have.

Workbench hangs in PENDING state after high memory usage

Unfortunately the Snowflake SPCS container runtime does not offer primitives within the same container to limit the memory used by particular users. We are investigating approaches for protecting the service from out of memory issues.

For an immediate fix, see the stop and start docs to suspend the Workbench service and restart it.

We suggest resizing your compute pool to prevent this issue from occurring in the future.

Workbench Positron Assistant errors using Snowflake Cortex

When trying to use Positron Assistant with Snowflake Cortex, it is possible that Cortex has not been enabled on your specific account, but is enabled on another account in your organization. You will see an error message like the following.

Snowflake Cross-Region Issue ...

The solution is for an administrator to enable cross region inference. The simplest solution is to enable any region, but read the docs for more specific solutions.

ALTER ACCOUNT SET CORTEX_ENABLED_CROSS_REGION = 'ANY_REGION';

Workbench managed credentials or Connect Snowflake integration not working

If you have AWS/Azure Private Link or an active network policy, you will need to complete additional steps documented in AWS PrivateLink docs, Azure PrivateLink docs, or Network Policy docs.

Viewing Backup Snapshots

There are instances where you may need to view the underlying storage in Posit products in the Posit Team Native App. For Posit Team, we intentionally block root or elevated access on Workbench, Connect, and Package Manager. In order to view the entire filesystem of the products, you must mount a Snowflake snapshot and run it in an SPCS container within your account rather than the Posit Team Native Application.

We provide a bash script to start up a JupyterLab container to inspect the contents of the given snapshots at /data and then properly clean up those resources. The script takes about 2 minutes to start up JupyterLab.

Before running the script make sure to:

Once you have the prerequisites installed, you can run the script. The script will guide you through:

  1. Selecting a Snowflake connection from your configured connections
  2. Entering the database name that contains the snapshots
  3. Selecting a snapshot from the available snapshots (size is automatically detected)

Please review the script before executing. The script will keep JupyterLab running until you press Enter in the command line, at which point it will clean up the compute pool, service, and image repository.

Support

If none of the troubleshooting steps help, please contact support or click on the Support button in the top left of the screen.

Support link

Support link
Back to top