By: Jay Kumar user 19 Jan 2018 at 8:14 a.m. CST

3 Responses
Jay Kumar gravatar
Hi Gluu Team, We recently installed the latest version of Gluu server 3.1.2 as per the steps mentioned on this page: https://gluu.org/docs/ce/installation-guide/install/ ). We ran the following commands to install the Gluu: 1. echo "deb https://repo.gluu.org/debian/ stable main" > /etc/apt/sources.list.d/gluu-repo.list 2. curl https://repo.gluu.org/debian/gluu-apt.key | apt-key add - 3. apt-get update 4. apt-get install gluu-server-3.1.2 And, it installed successfully. But when we are trying to start the Gluu server with this command "service gluu-server-3.1.2 start", it gives the error mentioned below: **Error: **Job for gluu-server-3.1.2.service failed because the control process exited with error code. See "systemctl status gluu-server-3.1.2.service" and "journalctl -xe" for details. Kindly look into the issue and suggest what could be the reason for this error. Thanks!

By Thomas Gasmyr Mougang staff 19 Jan 2018 at 9:01 a.m. CST

Thomas Gasmyr Mougang gravatar
Hi Kumar, I hope you are doing well. Kindly go through the following steps in order to get more in side about what is happening. - Run the below commands as an admin user,the command will fail as you described above. ``` #service gluu-server-3.1.2 ``` - Run theses two commands and check the result. ``` #systemctl status gluu-server-3.1.2.service > gluu-status.txt #journalctl -xe > gluu-startjournal.txt ``` Check the content of theses two files and you will get more details about your issue. If after that you still need help, just provide us with the logs files and stay tuned if we need more information. Thanks

By Thomas Gasmyr Mougang staff 21 Jan 2018 at 1:06 p.m. CST

Thomas Gasmyr Mougang gravatar
Hi Kumar, I hope you are doing well. I assume that your issue has been fixed. If not, let us help you. By the way the ticket is schedule for deletion tomorrow for inactivity reason.

By Jay Kumar user 22 Jan 2018 at 3:08 a.m. CST

Jay Kumar gravatar
Hi Thomas , This issue has been fixed after rebooting our server. Thanks!