Red Hat Bugzilla – Bug 983781
Installing JBoss Datagrid as a service
Last modified: 2013-12-18 09:01:33 EST
Description of problem:
JBoss Datagrid version 6.1 contains a bin/init.d folder. The folder contains a script that can be used to install Datagrid as a service on unix systems, but the script seems to be for jboss-as, not jboss-datagrid. Also, I could not find any section on installing jboss datagrid as a service.
Version-Release number of selected component (if applicable):
Look in bin/init.d folder
Steps to Reproduce:
So I am not able to start JDG Server as service
[root@vchepQA /]# systemctl start infinispan-server.service
Job failed. See system journal and 'systemctl status' for details.
[Status of service]
infinispan-server.service - SYSV: Infinispan Server
Loaded: loaded (/etc/rc.d/init.d/infinispan-server)
Active: failed (Result: resources) since Thu, 19 Sep 2013 09:56:21 +0200; 2min 7s ago
Process: 9722 ExecStart=/etc/rc.d/init.d/infinispan-server start (code=exited, status=0/SUCCESS)
Main PID: 8990
[Log from /var/log/messages]
Sep 19 09:56:21 vchepQA systemd: PID file /var/run/infinispan-server/infinispan-server-standalone.pid not readable (yet?) after start.
[PID of server]
[root@vchepQA /]# lsof -t -i:8080
9785 <<< SO server is started properly and listening
[But there is NO PID file created!!!]
[root@vchepQA /]# ll /var/run/infinispan-server/
[Problems in script infinispan-server.sh]
1. start()__line__(101) if JDG started, there is "grep 'Infinispan Server.*started in' $ISPN_SERVER_CONSOLE_LOG > /dev/null"
I think should be "grep JBoss Data Grid.* started"
2. standalone.sh does not contain variables like LAUNCH_ISPN_SERVER_IN_BACKGROUND=1 so there is NO need to do %s/JBOSS_/ISPN_SERVER_/g because it does not help if you EXPORT variables and DO NOT use them inside standalone.sh
The grep command could be universal. Something like grep '.*started.*in.*ms' . I tried this and it worked well for all JDG, ISPN server and EAP, started with or without errors. Just a tip...
Martin Gencur <firstname.lastname@example.org> updated the status of jira ISPN-3327 to Reopened
Martin Gencur <email@example.com> made a comment on jira ISPN-3327
Looks like this issue should be reopened.