[
https://issues.jboss.org/browse/WFLY-4570?page=com.atlassian.jira.plugin....
]
Dennis Gesker updated WFLY-4570:
--------------------------------
Steps to Reproduce:
Set variables in JBOSS_HOME/bin/init.d/wildfly.conf
ln -s JBOSS_HOME/bin/init.d/wildfly.conf /etc/default/wildfly
ln -s JBOSS_HOME/bin/init.d/wildfly-init-debian.sh /etc/init.d/wildfly
cd /etc/init.d
update-rc.d wildfly defaults
permissions and user/group are of course set to wildfly.wildfly
was:
Set variables in JBOSS_HOME/bin/init.d/wildfly.conf
ln -s JBOSS_HOME/bin/init.d/wildfly.conf /etc/default/wildfly
JBOSS_HOME/bin/init.d/wildfly-init-debian.sh /etc/init.d/wildfly
cd /etc/init.d
update-rc.d wildfly defaults
permissions and user/group are of course set to wildfly.wildfly
wildfly-init-debian.sh fails on Ubuntu 15.04
--------------------------------------------
Key: WFLY-4570
URL:
https://issues.jboss.org/browse/WFLY-4570
Project: WildFly
Issue Type: Bug
Components: ConfigAdmin
Affects Versions: 9.0.0.Beta2, 9.0.0.CR1
Environment: Ubuntu 15.04, Oracle JDK_1.8.0_45-b14
Reporter: Dennis Gesker
Assignee: Thomas Diesler
Priority: Minor
Fix For: 9.0.0.CR1
Init script "wildfly-init-debian.sh" fails on Ubuntu 15.04 but standalone.sh
works fine. Env is jdk_1.8.0_45-b14 and wildfly_9.0.0.Beta2. The error returned is:
Failed to start wildfly.service: Unit wildfly.service failed to load: No such file or
directory.
Had no issue with the above script on Ubuntu 14.04 so guessing a change in Ubuntu
("Upstart" Maybe?) But, I'm far from an upstart or bash expert. bash -x
seems to at least create the pid.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)