By: Robert Roos user 30 Mar 2018 at 4:28 a.m. CDT

8 Responses
Robert Roos gravatar
Steps to reproduce: - Created a VM on LXD: Ubuntu 16.04 (privileged mode) - Clean install of the software - service gluu-server-3.1.2 start seems to work - service gluu-server-3.1.2 login fails with error message: gluu-server-3.1.2 is not running I suspect this is some kind of a permission problem. But Im unsure if this is related to the Gluu default install. A dump of the logs: ``` ''' root@<hidden>:~# systemctl status gluu-server-3.1.2 ● gluu-server-3.1.2.service - LSB: This shell script takes care of starting and stopping Loaded: loaded (/etc/init.d/gluu-server-3.1.2; bad; vendor preset: enabled) Active: active (running) since Fri 2018-03-30 09:06:37 UTC; 1min 26s ago Docs: man:systemd-sysv-generator(8) Process: 294 ExecStart=/etc/init.d/gluu-server-3.1.2 start (code=exited, status=0/SUCCESS) Tasks: 4 Memory: 5.8M CPU: 166ms CGroup: /system.slice/gluu-server-3.1.2.service ├─426 /usr/sbin/rsyslogd └─445 /usr/sbin/cron Mar 30 09:06:35 <hidden> systemd[1]: Starting LSB: This shell script takes care of starting and stopping... Mar 30 09:06:35 <hidden> gluu-server-3.1.2[294]: Starting Gluu server, please wait... Mar 30 09:06:35 <hidden> gluu-server-3.1.2[294]: mount: mount /dev on /opt/gluu-server-3.1.2/dev failed: Permission denied Mar 30 09:06:35 <hidden> gluu-server-3.1.2[294]: mount: /proc is write-protected, mounting read-only Mar 30 09:06:35 <hidden> gluu-server-3.1.2[294]: mount: cannot mount /proc read-only Mar 30 09:06:35 <hidden> gluu-server-3.1.2[294]: mount: /sys/class/net/lo is write-protected, mounting read-only Mar 30 09:06:35 <hidden> gluu-server-3.1.2[294]: mount: cannot mount /sys/class/net/lo read-only Mar 30 09:06:37 localhost systemd[1]: Started LSB: This shell script takes care of starting and stopping. Mar 30 09:06:49 localhost systemd[1]: Started LSB: This shell script takes care of starting and stopping. root@<hidden>:~# service gluu-server-3.1.2 login gluu-server-3.1.2 is not running please start it by running: /etc/init.d/gluu-server-3.1.2 start root@<hidden>:~# Get:3 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB] Get:4 http://archive.ubuntu.com/ubuntu xenial-backports InRelease [102 kB] Get:5 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [744 kB] Get:6 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages [615 kB] Ign:7 https://repo.gluu.org/ubuntu xenial InRelease Hit:8 https://repo.gluu.org/ubuntu xenial Release Fetched 1665 kB in 0s (2161 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following package was automatically installed and is no longer required: libfreetype6 Use 'apt autoremove' to remove it. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root@<hidden>:~# apt autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: libfreetype6 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 928 kB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 46722 files and directories currently installed.) Removing libfreetype6:amd64 (2.6.1-0.1ubuntu2.3) ... Processing triggers for libc-bin (2.23-0ubuntu10) ... root@<hidden>:~# systemctl status gluu-server-3.1.2 ● gluu-server-3.1.2.service - LSB: This shell script takes care of starting and stopping Loaded: loaded (/etc/init.d/gluu-server-3.1.2; bad; vendor preset: enabled) Active: active (running) since Fri 2018-03-30 09:06:37 UTC; 1min 26s ago Docs: man:systemd-sysv-generator(8) Process: 294 ExecStart=/etc/init.d/gluu-server-3.1.2 start (code=exited, status=0/SUCCESS) Tasks: 4 Memory: 5.8M CPU: 166ms CGroup: /system.slice/gluu-server-3.1.2.service ├─426 /usr/sbin/rsyslogd └─445 /usr/sbin/cron Mar 30 09:06:35 <hidden> systemd[1]: Starting LSB: This shell script takes care of starting and stopping... Mar 30 09:06:35 <hidden> gluu-server-3.1.2[294]: Starting Gluu server, please wait... Mar 30 09:06:35 <hidden> gluu-server-3.1.2[294]: mount: mount /dev on /opt/gluu-server-3.1.2/dev failed: Permission denied Mar 30 09:06:35 <hidden> gluu-server-3.1.2[294]: mount: /proc is write-protected, mounting read-only Mar 30 09:06:35 <hidden> gluu-server-3.1.2[294]: mount: cannot mount /proc read-only Mar 30 09:06:35 <hidden> gluu-server-3.1.2[294]: mount: /sys/class/net/lo is write-protected, mounting read-only Mar 30 09:06:35 <hidden> gluu-server-3.1.2[294]: mount: cannot mount /sys/class/net/lo read-only Mar 30 09:06:37 localhost systemd[1]: Started LSB: This shell script takes care of starting and stopping. Mar 30 09:06:49 localhost systemd[1]: Started LSB: This shell script takes care of starting and stopping. root@<hidden>:~# root@<hidden>:~# root@<hidden>:~# service gluu-server-3.1.2 login gluu-server-3.1.2 is not running please start it by running: /etc/init.d/gluu-server-3.1.2 start root@<hidden>:~# clear root@<hidden>:~# journalctl -xe Mar 30 09:06:37 localhost systemd[1]: Starting Update UTMP about System Runlevel Changes... -- Subject: Unit systemd-update-utmp-runlevel.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-update-utmp-runlevel.service has begun starting up. Mar 30 09:06:37 localhost systemd[1]: Failed to reset devices.list on /system.slice/apport.service: Operation not permitted Mar 30 09:06:37 localhost systemd[1]: Failed to reset devices.list on /system.slice/cloud-config.service: Operation not permitted Mar 30 09:06:37 localhost systemd[1]: Failed to reset devices.list on /system.slice/irqbalance.service: Operation not permitted Mar 30 09:06:37 localhost systemd[1]: Failed to reset devices.list on /system.slice/opt-gluu\x2dserver\x2d3.1.2-lib-modules.mount: Operation not permitted Mar 30 09:06:37 localhost systemd[1]: Failed to reset devices.list on /system.slice/opt-gluu\x2dserver\x2d3.1.2-dev-pts.mount: Operation not permitted Mar 30 09:06:37 localhost systemd[1]: Started Update UTMP about System Runlevel Changes. -- Subject: Unit systemd-update-utmp-runlevel.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-update-utmp-runlevel.service has finished starting up. -- -- The start-up result is done. Mar 30 09:06:38 localhost cloud-init[460]: Cloud-init v. 17.2 running 'modules:final' at Fri, 30 Mar 2018 09:06:38 +0000. Up 5.00 seconds. Mar 30 09:06:38 localhost cloud-init[460]: Cloud-init v. 17.2 finished at Fri, 30 Mar 2018 09:06:38 +0000. Datasource DataSourceNoCloud [seed=/var/lib/cloud/ Mar 30 09:06:38 localhost systemd[1]: Started Execute cloud user/final scripts. -- Subject: Unit cloud-final.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit cloud-final.service has finished starting up. -- -- The start-up result is done. Mar 30 09:06:38 localhost systemd[1]: Reached target Cloud-init target. -- Subject: Unit cloud-init.target has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit cloud-init.target has finished starting up. -- -- The start-up result is done. Mar 30 09:06:38 localhost systemd[1]: Startup finished in 4.145s. -- Subject: System start-up is now complete -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- All system services necessary queued for starting at boot have been -- successfully started. Note that this does not mean that the machine is -- now idle as services might still be busy with completing start-up. -- -- Kernel start-up required KERNEL_USEC microseconds. -- -- Initial RAM disk start-up required INITRD_USEC microseconds. -- -- Userspace start-up required 4145055 microseconds. Mar 30 09:06:49 localhost systemd[1]: Started LSB: This shell script takes care of starting and stopping. -- Subject: Unit gluu-server-3.1.2.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit gluu-server-3.1.2.service has finished starting up. -- -- The start-up result is done. lines 879-937/937 (END) ''' ```

By Thomas Gasmyr Mougang staff 30 Mar 2018 at 4:38 a.m. CDT

Thomas Gasmyr Mougang gravatar
Hi **Robert**, If the Gluu service is not configured to start at boot time then you have to start it before login in. ``` #service gluu-server-3.1.2 start #service gluu-server-3.1.2 login ``` Note that the log file you have provided aren't readable. Thanks, Gasmyr

By Robert Roos user 30 Mar 2018 at 6 a.m. CDT

Robert Roos gravatar
Just changed the markup of the logs. The service **gluu-server-3.1.2** seems to be started. But the service gluu-server-3.1.2 login command doesnt seem to recognise that the server is running.

By Mohib Zico staff 30 Mar 2018 at 8:17 a.m. CDT

Mohib Zico gravatar
FYI.. I think we haven't tested Gluu Server in any LXD. If you want to run it real quick in your own computer... I would suggest to go with VMWare/Virtualbox VMs.

By Robert Roos user 30 Mar 2018 at 11:28 a.m. CDT

Robert Roos gravatar
Oh thats a pity. Is there a way to further troubleshoot this issue? E.g. certain logs/files to look at?

By Thomas Gasmyr Mougang staff 02 Apr 2018 at 12:20 a.m. CDT

Thomas Gasmyr Mougang gravatar
Hi **Robert**, You can start with the permission issue mentioned in the log and move forward. Thanks, Gasmyr.

By Mohib Zico staff 02 Apr 2018 at 1:51 a.m. CDT

Mohib Zico gravatar
Yes.. and [here](https://gluu.org/docs/ce/3.1.2/operation/logs/) is documentation on logs; please let us know if it's not clear to you; we will update doc if required.

By Thomas Gasmyr Mougang staff 06 Apr 2018 at 1:10 a.m. CDT

Thomas Gasmyr Mougang gravatar
Hello **Robert**, Any update about that issue? We are going to close this ticket tomorrow due to inactivity. Feel free to reopen it if required. Thanks, Gasmyr

By Robert Roos user 06 Apr 2018 at 8:46 a.m. CDT

Robert Roos gravatar
Hi Gasmyr, you can close the ticket. I am going to conduct the further investigation on my own.