Logging¶

JetStream server logs to standard out, but installations on some operating systems rely on system facilities for better integration (see below). To stop logging to standard out or customize the log file location, you can use the --log command line parameter.

CentOS 7, Ubuntu 18.04¶

Systemd will handle logging for the processes. Each JetStream service is configured to log into syslog under its service name as the identifier (e.g. jetstream-server). There are a number of ways to look at the logs:

The last few lines are usually shown with the systemctl status command: systemctl status -l jetstream-server

journalctl can be used to view more of the log, if systemd is setup to use journal logging: journalctl -u jetstream-server

The previous command can be used in combination with the -nX flag to show the last X lines (eg. -n20) and the -f flag can be used to tail the log (just like tail -f)

Alternatively, the system log can be tail’d (or grep’d) for JetStream messages. For example: tail -n 40 -f /var/log/messages | grep jetstream (assuming default system configuration where syslog writes to /var/log/messages)

macOS¶

JetStream server will log under /var/log/jetstream-server.log.

Windows¶

JetStream server will log under C:\Program Files\Jet Digital\JetStream Server\log\jetstream-server.log.

The JetStream service also logs to the Windows Event Log. You can open the Event Viewer by navigating to: Start menu ‣ Windows Administrative Tools ‣ Event Viewer. In the Event Viewer, items logged by JetStream will have JetStream as the source.