On RHEL 7, and the newest version of Rocket's UniVerse (15.+), the installation has two options: install as root or as 'uvadm'.

When installing as 'uvadm', the installation script does not recognize this account even though it is a valid account. It thinks one is logged in as root.

Why is this? I don't want to add uvadm to the root group... as this would create 2 super users so there has to be a different way. I'm looking at the login script to see what it is doing, and I have a support ticket to the vendor.

Wondering if anyone else installing Rocket UniVerse on RHEL has experienced this issue, and how you solved it.

i am assuming you are using KVM
libvert needs to be ran as root or service at startup

Thanks for the answer. I'm not sure if it helps though... the RHEL is a new/fresh install, as is our attempt with UniVerse. KVM means a virtual machine? (Please excuse my ignorance with Linux/VM's, I'm a mainframe guy).

Redirecting to /bin/systemctl status libvert.service
● libvert.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)


I don't know why this service would be relevant to the installation. I'm able to SSH to both a GUI and command-line interface; I'm basically trying to install database software. The install process has two options: root or an administrative user. When I log in as the administrative user, it doesn't acknowledge the user and thinks I'm logged in as root (which is strange). This is preventing me from installing as the user (we want to try installing as "root" to provide more security).

Just an update -

Installing as uvadm requires additional prepwork, since it will not have authority to create the directories needed during the installation!

Solution was to create the directories (2 of them: the home directory and the unishared) with uvadm FIRST. If you cannot create with uvadm, create with root, then change ownership to uvadm:uvadm and give full 777 access. Then, a prudent step is to change the ownership recursively to the temporary installation folder that contains your install files.

This will allow you to complete the install. However, have found that running as uvadm presents addtional issues... UV starts but you cannot log in correctly as uvadm and must "sudo bin/uv" which defeats the whole purpose of running it as uvadm!

Working on solving this new issue... but bottom line is if you are installing this software, don't go with uvadm. Far too many hassles and just do it as root. There are fewer issues down the road too.