[jboss-jira] [JBoss JIRA] (WFCORE-1381) wildfly-init-debian.sh fails on Ubuntu 15.04

Jorge Solorzano (JIRA) issues at jboss.org
Sat Jun 18 16:58:00 EDT 2016


    [ https://issues.jboss.org/browse/WFCORE-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13254378#comment-13254378 ] 

Jorge Solorzano commented on WFCORE-1381:
-----------------------------------------

It should be noted that the correct way to use it is to copy the init.d and conf files to their respective directories because a symbolic link would create a security exploit should anyone be able to gain the permissions of wildfly and modify $JBOSS_HOME/bin/init.d/wildfly-init-debian.sh.

Please don't make a symbolic link to this files.

I'm going to create a README with the steps to install as a service.


> wildfly-init-debian.sh fails on Ubuntu 15.04
> --------------------------------------------
>
>                 Key: WFCORE-1381
>                 URL: https://issues.jboss.org/browse/WFCORE-1381
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Scripts
>    Affects Versions: 1.0.0.Beta6, 1.0.0.CR1
>         Environment: Ubuntu 15.04, Oracle JDK_1.8.0_45-b14
>            Reporter: Dennis Gesker
>            Priority: Minor
>
> 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.4.11#64026)


More information about the jboss-jira mailing list