Need help with other JFrog products?
Using a third-party log collector
To use an external log collector that requires a separate user for Distribution (e.g. Sumologic, Splunk), you can adjust the permissions on the
$DISTRIBUTION_DATA/logs folder to allow the the log collection service to perform read operations on the generated log files as follows:
- Add the log collection service user to the relevant group if needed (the user and group that installed and started Distribution)
Apply the user and group permissions as needed on the
Adjust the group read inheritance permissions setgid bit using:
This will cause the generated log files to inherit the folder's group permissions.
The Distribution Linux installation follows standard conventions and installs Distribution in the following folders:
The installation script will prompt you for an optional alternative location.
Distribution will rotate and compress old log files.
Log configuration files
PostgreSQL home directory
Redis home directory
The installation instructions for all of the supported flavors of Linux are the same. As a pre-requisite, you must have Java 8 installed.
Note: In all of the instructions below, replace the <linux-flavor> place-holder with one of centos, debian, ubuntu or redhat according to the flavor of Linux on which you are operating.
Extract the downloaded installation archive
Run the installation script
(If you are not running as "root", prepend the following command with "sudo")
Using External Databases
JFrog Distribution uses several databases for different features of its operation.
Distribution gives you the option of using your own PostgreSQL database if you have these already installed and in use in your organization.
For more details, please refer to Using External Databases.
Upgrading on Linux
For instructions on how to upgrade an existing installation, please refer to Upgrading Distribution.
Interacting with the Linux Installer
Make sure Distribution fully started
Verify all the required Distribution components and connected databases are up and running using the following command:
Use the below command to start all Distribution components:
It is also possible to exclude the 'all' flag which will make the script run or check only for the running Distribution services (without the databases) as follows:
The installation script offers facilities for maintenance. Run the following commands as "root" or prepend them with "sudo".
<command> can take one of the following values:
|Start the service|
|Stop the service|
|Restart the service|
|Display the service status (e.g. running, stopped...)|
|Displays version information for each service|
|Deploy the service (only available for the distribution service)|
|Remove the service (only available for the distribution service)|
<target> Optional. When omitted, the command only applies to the Distribution service.
|Apply the command to all services|