2.1.11. Linux groups used by components

The following table lists the users and groups requird for files managed by the components. For more information on components, see Section 3.2.1.3, Component.

Componentuser/group
Networkingowner='root' group='root'
System loggingowner='root' group='root'
Host configurationowner='root' group='root'
Management Accessowner='root' group='velanft'
Management Serverowner='root' group='vms'
Management Agentowner='root' group='root'
Application-level Gatewayowner='root' group='vela'
Licencesowner='root' group='vas' group='vcf' group='vela' group='vms'
Package sourcesowner='root' group='root'
Date and timeowner='root' group='root'
Authentication Serverowner='root' group='vas'
Content Filteringowner='root' group='vcf'
Availability Checkerowner='root' group='root'
VPNowner='root' group='root' group='velanft'
Nftablesowner='root' group='velanft'
DNSowner='root' group='root'
ModSecurityowner='root' group='root'
systemd-coredump configurationowner='root' group='root'
URL filter black and white listsowner='root' group='vela'
Keepalivedowner='root' group='root' group='velanft'

Table 2.1. Linux users and groups

Note

These groups will be created once the relevant components are installed on the host. If you try to upload a component to the host from MC before installing the corresponding package on the affected node, then the following example error message will be shown: Set owner='root' group='vas' mode='100640': group not found. The given group does not exist on target host.