Common Problems In Studio

This article was written for version 2.3.1 of Core. Click here for the most recent version of the help center.

Find solutions to common problems reported through Studio’s system state module.

1. SDF Configuration does not match physical configuration

The most common issue with replay is that the SDF file─psync.sdf─does not match the physical configuration of the PolySync Core system.

Use this checklist to validate the existing configuration matches the SDF Configuration

  1. Use the license tool to see what PolySync Core IP address is set
    • $ polysync-license-tool
    • ...
    • `IP Address: ‘’
  2. Compare the IP address printed above with the SDF, using the Configurator
    • $ polysync-core-sdf-configurator
    • In the menu bar, select File -> Open
    • Navigate to the directory $HOME/.local/share/polysync/rnr_logs/, containing all logfile sessions on each host
    • Open the psync.sdf in the logfile session that is reporting errors during replay
    • Ensure the Interface Address field in the Configurator matches the IP Address from the license tool output
    • If there is more than one host defined in the SDF, this is the cause of error and you must consolidate all nodes to a single host

2. Missing manager error

Missing manager error

This is fixed by starting the manager, which can be done from the command line:

$ sudo service polysync-core-manager start

Studio will automatically detect when the manager starts, and system state will update to look similar to this:

Missing manager error recovery

In distributed systems, it’s required that the PolySync Core manager is running on each host defined in the SDF .

Ensure the system is in the standby mode by clicking the standby button.

3. Missing nodes error

Missing nodes error

3.1 Hardware mode

  1. Toggle nodes into standby mode
  2. Toggle nodes back into hardware mode

The nodes will reinitialize their connection with the hardware devices and sensors. If one or more nodes are still in an error state, check Studio’s console module.

The console contains debug and error messages from all nodes. Debug messages provide context for the issue, and the error messages can indicate what potential solutions exist.

3.1.1 Debugging nodes in an error state

If a node is observed in an error state but the rest of the system is working well, it’s best to remove unnecessary components from the system and debug the system one component at a time.

Stop all nodes by clicking the standby button.

Start the mishaving node by itself on the command line and observe errors reported.

Utilize the setup and configuration steps in the supported sensors articles to ensure the SDF Configuration is valid.

3.2 Replay mode

First reselect the logfile session for playback to ensure the issue was not related to a loading-timeout issue.

  1. Toggle nodes into standby mode
  2. Reselect the logfile session from the playlist
  3. Playback will begin and nodes show up in system state with the blue replay status

Missing nodes error recovery

If one or modes remain in an error state, close Studio and use the manager to stop all other nodes and clean the environment.

$ polysync-core-manager -f 

Now the system is in a clean state. Restart the manager and start Studio to replay a logfile sesion:

$ polysync-core-manager
$ polysync-core-studio