Solution
When either the SystemLink server or the external PostgreSQL database server is rebooted, certain services will temporarily go offline. This behavior is expected and can be mitigated depending on how your test systems are configured.
Reboot Scenarios and Behavior
1. External PostgreSQL server rebooted (SystemLink Server active)
- Expected behavior:
- The TestMonitor and PostgreSQL Database services will go offline.
- These services will remain down until they successfully reconnect to the PostgreSQL server.
- User action:
- Monitor service status via NI SystemLink Server Configuration.
- Once the database is back online, verify that services reconnect automatically.
2. SystemLink server rebooted (PostgreSQL active)
- Expected behavior:
- All SystemLink services will go offline during the reboot.
- Upon restart, services will come back sequentially, restoring full functionality.
- User action:
- After reboot, confirm that all services are running via the NI SystemLink Server Configuration.
Impact to test data being sent to SystemLink
- If uploading data from TestStand, using TestStand’s Store and Forward setting set to Always:
- No data loss will occur during either type of outage.
- Data will be cached locally and forwarded once the connection is restored.
- If streaming live data to SystemLink services:
- Streams will fail during the outage, and data loss may occur.
To summarize, when either the database server or the SystemLink server is rebooted, the database will be unavailable. This means that if you are streaming live data to SystemLink, the streams will fail while the servers are down. However, if you are sending data from TestStand, enabling the Store and Forward setting ensures that data is buffered locally and sent once the connection is restored.