Troubleshooting Posit Team

Advanced

Posit Team is designed to be a fully managed solution.

Debugging

Once configuring the Posit Team Native App for initial use each product’s logs and system health status is available in the management page.

Manage page

User roles granted an appropriate application role can also access product service logs. Run the following Snowflake SQL to grant access:

Snowsight UI

GRANT APPLICATION ROLE POSIT_TEAM.POSIT_TEAM_ADMIN TO ROLE YOUR_USER_ROLE;

Run the following to access individual product service logs:

Snowsight UI

-- controller service logs
SELECT SYSTEM$GET_SERVICE_LOGS('POSIT_TEAM.services.controller', 0, 'controller');
-- 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');

Known issues

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 either POSIT_TEAM_ADMIN or POSIT_TEAM_USER.

Invalid consent request error

Snowflake restricts the roles which can authenticate per their Snowflake Blocked OAuth roles docs. Currently the Workbench Native App authenticates with your default role. This error indicates that your default role is ACCOUNTADMIN, SECURITYADMIN, and/or ORGADMIN. To fix this issue, visit the Snowsight UI and change your default role to something other than these roles.

Invalid Consent Request

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.

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:

• Download the snow cli, docker, and jq
• Configure at least one Snowflake connection using the snow cli. See Snowflake connection configuration docs for more information

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