If StreamLab or s-Dashboard does not seem to be connecting to s-Server, you may have started components in an incorrect order. Components need to be started as follows: 1) s-Server 2) webAgent 3) s-Dashboard and StreamLab.
You may need to configure ports. Port requirements for all components are summarized at Managing Ports for Guavus SQLstream.
s-Server requires Java Development Kit 8 or higher. The installer should either find your system’s installation of JDK, or install OpenJDK on your system. If this does not work, you may need to start the installer using the following command.
sudo JAVA_HOME=<the location of your JAVA_HOME> ./SQLstream-sServer-X.Y.Z-x64.run
This tells your installer the location of JAVA_HOME
If you are experiencing either of these problems, you may need to contact SQLstream technical support. It may be useful to consult /etc/sqlstream/environment. This might allow you to see, for example, that JAVA_HOME is set incorrectly, or that other environment variables are problematic.
You may also find useful information in your system’s syslog (often located in /var/log/syslog or /var/log/messages). You will usually need sudo/root access to view your syslog. The link http://www.cyberciti.biz/faq/linux-log-files-location-and-how-do-i-view-logs-files/ has some information on syslogs.
If you have installed a new version of s-Server, you may notice that it is throttling (performing at a lower level of throughput), as described in the topic SQLstream s-Server Licensing. When you install a new version of s-Server, you will need to move the license file from the old installation’s $SQLSTREAM_HOME to the new installation’s $SQLSTREAM_HOME. Purchased licenses are managed by a file in $SQLSTREAM_HOME, the installation directory for s-Server, such as /opt/sqlstream/<%VERSION%>.XXX/s-Server/.
If your initial installation is behind a firewall, you will need to set a Linux environment variable called https_proxy in order to access the license server.
You do so with a command along the following lines:
Note: http_proxy will not work. Also, SQLstream does not support a username and password in the proxy variable.
In some cases, you may have modified aspen.custom.properties in your old installation of s-Server. You will need to move this file from the old installation directory to the new installation directory before you uninstall the old version. Some users may have also modified bin/defineAspenRuntime.sh and need to move this file as well.
s-Server requires OpenSSL to run. All Linux distributions should include OpenSSL by default. If for some reason your installation does not include OpenSSL, you will need to install it.