By: Mark Slaats user 20 Dec 2017 at 12:37 p.m. CST

9 Responses
Mark Slaats gravatar
Hi, I am currently new to the Gluu server and I wanted to start the server but that did not work. I installed Gluu on a CentOS7 container with the latest updates installed. It has the recommended resources which I found here: https://gluu.org/docs/ce/installation-guide/ I installed Gluu as they documented it here (Followed CentOS): https://gluu.org/docs/ce/installation-guide/install/ ```bash yum update yum upgrade yum install wget wget https://repo.gluu.org/centos/Gluu-centos7.repo -O /etc/yum.repos.d/Gluu.repo wget https://repo.gluu.org/centos/RPM-GPG-KEY-GLUU -O /etc/pki/rpm-gpg/RPM-GPG-KEY-GLUU rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-GLUU yum clean all yum update yum install gluu-server-3.1.1 /sbin/gluu-serverd-3.1.1 enable /sbin/gluu-serverd-3.1.1 start ``` After I tried the last command (/sbin/gluu-serverd-3.1.1 start) it gave me an error. This is what my systemctl told me: ``` ● systemd-nspawn@gluu_server_3.1.1.service - Container gluu_server_3.1.1 Loaded: loaded (/usr/lib/systemd/system/systemd-nspawn@gluu_server_3.1.1.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2017-12-19 16:05:51 UTC; 7min ago Docs: man:systemd-nspawn(1) Process: 832 ExecStart=/usr/bin/systemd-nspawn --quiet --boot --link-journal=try-guest --machine=%I (code=exited, status=1/FAILURE) Main PID: 832 (code=exited, status=1/FAILURE) Status: "Terminating..." Dec 19 16:05:51 openid systemd[1]: Starting Container gluu_server_3.1.1... Dec 19 16:05:51 openid systemd-nspawn[832]: MS_SLAVE|MS_REC failed: Permission denied Dec 19 16:05:51 openid systemd-nspawn[832]: Failed to register machine: Interrupted system call Dec 19 16:05:51 openid systemd[1]: systemd-nspawn@gluu_server_3.1.1.service: main process exited, code=exited, status=1/FAILURE Dec 19 16:05:51 openid systemd[1]: Failed to start Container gluu_server_3.1.1. Dec 19 16:05:51 openid systemd[1]: Unit systemd-nspawn@gluu_server_3.1.1.service entered failed state. Dec 19 16:05:51 openid systemd[1]: systemd-nspawn@gluu_server_3.1.1.service failed. ``` It tells me something about permission denied. However I do not have sudo inside the container. So I installed that and tried it again with the same error occuring. Last but not least my full journal: https://pastebin.com/9Dr5dvHn

By Aliaksandr Samuseu staff 20 Dec 2017 at 5:03 p.m. CST

Aliaksandr Samuseu gravatar
Hi, MS. >However I do not have sudo inside the container It's not about `sudo` specifically, it's just you must run all install and management commands as "root" user when you are dealing with Gluu. Please confirm the next before we'll proceed further: 1. You are issuing all those commands as "root" 2. SElinux is disabled there; you can check with `# getenforce`

By Mark Slaats user 20 Dec 2017 at 5:13 p.m. CST

Mark Slaats gravatar
Thanks for the reply, If I do getenforce it tells me that it is disabled. So I started looking on how to enable it on CentOS 7 and they tell me that I have to have a file called /etc/sysconfig/selinux or /etc/selinux/config (https://www.centos.org/docs/5/html/5.1/Deployment_Guide/sec-sel-enable-disable.html). However I don't have either of those files. Another approach would be using # setenforce 1 but that does not work it returns me setenforce: SELinux is disabled. Do you have any idea how I need to enable it?

By Aliaksandr Samuseu staff 20 Dec 2017 at 5:18 p.m. CST

Aliaksandr Samuseu gravatar
>If I do getenforce it tells me that it is disabled. So I started looking on how to enable it on CentOS 7 Sorry, you got me wrong, perhaps - it must stay disabled (we mention this in system requirement docs). Gluu isn't compatible with SELinux atm. Please make sure you are logged in as root there, then. I would also try to remove Gluu completely (including any lingering files under `/opt`), restart the vm, and re-try all install steps again.

By Mark Slaats user 20 Dec 2017 at 5:22 p.m. CST

Mark Slaats gravatar
All right my bad, should have known that. So to give you some more info, I am running a CentOS 7 container on which I am logged on as a root user and every command I execute is as the root. Now we can conclude that SELinux is disabled so that is not a problem either. And I already retryed installing it all over again and I got exactly the same error. I hope this gives you some more context.

By Aliaksandr Samuseu staff 20 Dec 2017 at 5:29 p.m. CST

Aliaksandr Samuseu gravatar
Thanks for clarification. >I am running a CentOS 7 container This didn't catch my eye before. We often refer to Gluu's chroot environment as container, but it seems to me you may mean something else. What kind of "container" is it? Something like Docker, KVM etc?

By Mark Slaats user 20 Dec 2017 at 5:35 p.m. CST

Mark Slaats gravatar
It is a container in Proxmox Virtual Environment 5.1-36 with the latest updates. Proxmox works roughly the same as docker it only has a built in managing website which I really like :) And if I take a look at the use of the resources I gave it (2 cores, 4GB RAM and 50GB diskspace) it doesn't use anything at all (because it is not able to start the Gluu server. Maybe my complete journal (https://pastebin.com/9Dr5dvHn) could give you a hand?

By Aliaksandr Samuseu staff 20 Dec 2017 at 5:41 p.m. CST

Aliaksandr Samuseu gravatar
>It is a container in Proxmox Virtual Environment 5.1-36 with the latest updates. Proxmox works roughly the same as docker I believe our answer to questions regarding support of Docker is still "work in progress, officially not supported". I'll try to ask around, may be we need to put some note to docs regarding this. For now, I would suggest to resort to some basic environment, like an good old plain vm software (VirtualBox is a solid option)

By Mark Slaats user 20 Dec 2017 at 5:44 p.m. CST

Mark Slaats gravatar
Thanks a lot, I really appreciate it, I will try that tomorrow (Dutch guy here haha) and keep you up to date if VirtualBox does or does not work :)

By Mark Slaats user 22 Dec 2017 at 6:28 a.m. CST

Mark Slaats gravatar
Thanks a lot for your help, I tried to install it under a CentOS7 in the latest Virtualbox and it works with SELinux disabled. So my conclusion is that I cannot visualize it in Proxmox. Thanks a lot for your help^^