Page tree
Skip to end of metadata
Go to start of metadata

This topic provides several instructions for carrying out Jethro Manager activities.

Service Management

To stop Jethro Manager from working, run:

service jethromng stop

To start Jethro Manager, run:

service jethromng start

To restart Jethro Manager (stop and then start), run:

service jethromng restart

To check if the service is up:

service jethromng status

To see which Jethro Manager version is running:

service jethromng version

Common Error Handling

If Jethro Manager stops functioning properly, the following steps might provide a quick solution:

  1. Sign in as user jethro or user root, and run the following command to restart the service on the Jethro Manager machine:

    service jethromng restart
  2. Empty the site's cache on Google Chrome:

    1. Click F12 (or CTRL+Shift+I)
    2. Click and hold the Reload button to open the menu displayed below:
       
    3. Click Empty Cache and Hard Reload.
       
  3. If you're getting 'connection refused' error in the browser when trying to browse to Jethro Manager, ensure there's no firewall policy blocking communication. Both the port (9100 by default) and the host/IP address should be allowed through your firewall.

Logs

The logs for Jethro Manager can be found at: /var/log/jethro/jethromng/

There are two types of log files:

  • jethromng.log - General log file. By default it includes only information level messages and errors.
  • jethromng.error.log - Errors only. This file won't be created if no errors were found.
Log file life-cycle

New log files are created once they reach 5Mb. Up to 10 log files (of each type) are kept before the oldest log files are being overwritten.

For example:
once jethromng.log reaches 5Mb, it will be renamed jethromng1.log and a new empty jethromng.log file will be created.
Once jethromng.log will reach 5Mb again, jethromng1.log will be renamed jethromng2.log and jethromng.log will be renamed jethromng1.log - and so on until 10 log files are created, afterwhich the oldest log file will be overwritten.

Ubuntu 14.04

On ubuntu 14.04 there's a known issue in which the Jethro Manager service does not auto-start once installation completes, because some of its files become owned by the root account instead of the install_user ('jethro' by default).
To overcome this and start the service, perform these actions after the installation:

  1. login as root.

  2. Perform these commands in a terminal: 

    service jethromng stop
    pkill PM2
    chmod 777 /opt/jethro/jethromng/jethromng.out
    chown -R jethro.jethro /opt/jethro/jethromng/pm2
    chown jethro.jethro /opt/jethro/jethromng/jethromng.config
    su - jethro
    service jethromng start
  3. If you wish to start the Jethro Manager service with a different user and/or group, replace 'jethro.jethro' in line #3 above with the need user name and group name respetively.

Contacting Jethro Support

For any question or feedback you may have, contact our support team: support@jethrodata.com.

  • No labels