Probe Doesn’t Start

The possible reasons why a probe does not start are described below:

  1. There is no connection with a server. Stable connection to a server part is a necessary requirement for successful registration of the probe on the server (in case the cloud Boro service is used, Internet connection is required). After registration is completed, the probe is not sensitive to the connection loss and is using a buffer for the collection and further transfer of the statistical data. A list of possible errors which might occur while setting up connection with a server:

    • In the monitor.cfg file, the “server” field contains an incorrect server address and/or port;

    • Unstable connection to a server (try to restart);

    • You are using a proxy server for connection to the server part, however it is not specified (or is incorrect) in the monitor.cfg file, or the string is “commented out”;

    • Firewall (Brandmauer) restricts the application access to the local network or to the Internet. In Windows allow the streamMonitor.exe using private and public networks (set “private” and “public” checkboxes in Windows firewall).

  2. You have made certain amendments breaking the JSON format regulations in the monitor.cfg file or added data which is not compatible with the data structure specified at monitor.cfg. Moreover, please note, that the monitor.cfg file must be saved in utf-8. Generally, in case any problem occurs with a config file parsing errors appear in a console log. This is the first sign proving that there are some problems with the monitor.cfg. file. The solution of the problem:

    • Try to find errors in a file (it is difficult for the beginners);

    • Download the archive file again using your personal account and place the new unchanged monitor.cfg file in a folder which you used to start the probe initially. However, please note, in this case you will lose all the probe’s settings and task lists since the last stop of the probe. You will have to name a probe again and, if necessary, set up a proxy server and add tasks to the launched probe using a web-interface.

    Note

    We strongly recommend using saving/downloading configuration at the server, so that you can avoid problems while editing the monitor.cfg file, and you will always have a configuration backup.

  3. Possibly, certain libraries were deleted or damaged in the application folder. Download the archive again, replace the monitor.cfg file and the authkey.pub file with your own files. It is advisable to copy a hidden file .stored.cache, thus providing that there will be no second record with the same probe’s name.

  4. You are probably trying to start a very old version of the probe. Try to download a new version using your personal account, then edit (or replace with the old one) the monitor.cfg file and restart the probe.

  5. You are using an old version of Linux OS. You need the support of glibc-2.17 or later.