Managing Collibra services on Linux

If you have installed Collibra Data Governance Center as a root user on a Linux system, the following items are also installed:

• The Collibra Agent service
• The Collibra Management Console service
• An extra user: collibra. The extra user is necessary to run the Collibra DGC software, however you cannot sign in to Collibra DGC with this user.

To manage the Collibra DGC services, use the default service management tool of your operating system:

service collibra-agent <command>
service collibra-console <command>

You can use the following commands to control the services:

• start
• stop
• restart
• status

Note  The services are automatically started after a restart of a node. However, on some operating systems, it is possible that the agent and console service do not start automatically because the OS does not allow them to be installed as system service. In that situation, you have to manually start the services as described above after a restart of the node

If you have installed Collibra Data Governance Center as a non-root user on Linux, there are no services added to the Linux services list.

You have to manage the Collibra services manually or install them afterwards.

Similar to the installation with the root user, you can only manage the agent and Collibra Console services. The other services in an environment are then managed via the Collibra Console user interface.

In the installation directory, by default ~/collibra, you find each Collibra DGC service as a separate directory:

• agent
• console

Each of these directories has a bin directory, which contains the script to manage these services.

By default, you have to start these services manually after the restart of the node.

Run the script

• agent: ./agent <command>
• console: ./console <command>

Tip If you use the install command, the service is added as daemon, which can then be configured to start with the start of your operating system.

Commands

Command	Description
console	Start in the current console.
start	Start in the background as a daemon process.
stop	Stop if running as a daemon or in another console.
restart	Stop if running and then start.
condrestart	Restart only if already running.
status	Display the current status.
install	Install the service as daemon and manage further through the operating system's service management.
remove	Remove the service from the node.
dump	Request a Java thread dump if running.