Log Files#

Below we describe the most relevant log files, how to download them, their contents, and the aspect of the system they are describing.

How to download the log files#

The log files can be downloaded from the Raspberry Shake’s web configuration page. If you cannot access the log files via the web front end for whatever reason, you can still download them directly from the Raspberry Pi computer. On the Raspberry Pi computer, the log files live at /opt/log/ and can be accessed over the network via SSH (Linux) or PuTTY (Windows). For instructions see How to access your Raspberry Shake’s computer via ssh.

Once inside, please run the following commands to collect the log files:

$ myshake
$ tar cf /tmp/rsh.logs.tar /opt/log
$ bzip2 /tmp/rsh.logs.tar

and copy the resulting file, /tmp/rsh.logs.tar.bz2 , using scp (Linux) or WinSCP (Windows) back to your computer, and then post it to the Raspberry Shake Technical Support Forum.

Log file summary#

System Logs

  • myshake.out - containing system information, status of programs, timing, versions, etc., produced once / day

  • mem-usage.out - running history of memory (RAM) usage, produced once / day

  • disk-usage.out - running hsitory of disk usage of directories in /opt, also listing sizes of files in /opt/data, produced once / day

  • gpsd-mgr.out - status of any GPS dongle possibly attached, produced at system start

Program Logs

  • postboot.log - containing output from bootup / initialization sequence and system start

  • upgrade.log - containing output generated by system upgrade program

  • odf_SL_plugin.* - generated by program responsible for generating data; these are, by far, the most important log files relating to the data itself

  • seedlink.log - generated by Seedlink, the local system responsible for converting the data to mini-SEED format and writing to /opt/data

  • rsh-data-producer.log - generated at startup of Docker container rsh-data-producer

  • rsh-data-consumer.log - generated at startup of Docker container rsh-data-consumer

Problem Analysis#

Generally, most problems of the greatest interest are those that ultimately hinder data flow, either locally, or it not being sent to the server. The order of analysis to determine the source of the problem looks something like:

  • Front-End Interface - Home Page System and Program Status

  • postboot.log - any errors generated at system startup appearing here?

  • odf_SL_plugin.err - any errors produced by the data producer program?

As regards understanding which log files are telling you what, this will get you very far. On the other hand, understanding each and every possible error condition that can occur, how it affects the overall system, and how to treat it is indeed a career.

As suggested, when looking at the files and encountering something you don’t understand, it is better to ask specific questions directly when this occurs.

Hopefully this will provide you an “in” to the log files and to the running system they are attempting to describe.