[jboss-jira] [JBoss JIRA] (WFLY-4044) Wildfly service will not start on fedora 20 - 64 bit

[Marek Goldmann (JIRA)]

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

Marek Goldmann commented on WFLY-4044:
--------------------------------------

I'll look into this.

> Wildfly service will not start on fedora 20 - 64 bit
> ----------------------------------------------------
>
>                 Key: WFLY-4044
>                 URL: https://issues.jboss.org/browse/WFLY-4044
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: Server
>    Affects Versions: 8.1.0.Final
>         Environment: Fedora 20 - updates installed
>            Reporter: Karl Nicholas
>            Assignee: Marek Goldmann
>
> standalone.sh starts wildfly ok but systemctl start service fails:
> [root at localhost system]# yum install wildfly
> Loaded plugins: langpacks, refresh-packagekit
> Package wildfly-8.1.0-3.fc20.noarch already installed and latest version
> Nothing to do
> [root at localhost system]# systemctl start wildfly
> [root at localhost system]# systemctl status wildfly
> wildfly.service - The WildFly Application Server
>    Loaded: loaded (/usr/lib/systemd/system/wildfly.service; disabled)
>    Active: failed (Result: exit-code) since Sat 2014-11-01 15:50:40 PDT; 5s ago
>   Process: 7658 ExecStart=/usr/share/wildfly/bin/launch.sh $WILDFLY_MODE $WILDFLY_CONFIG $WILDFLY_BIND (code=exited, status=1/FAILURE)
>  Main PID: 7658 (code=exited, status=1/FAILURE)
> Nov 01 15:50:39 localhost.localdomain systemd[1]: Started The WildFly Application Server.
> Nov 01 15:50:40 localhost.localdomain systemd[1]: wildfly.service: main process exited, code=exited, status=1/FAILURE
> Nov 01 15:50:40 localhost.localdomain systemd[1]: Unit wildfly.service entered failed state.
> [root at localhost system]



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)