Bug 1132745 - wildfly will not start after doing 'yum install wildfly' and then 'systemctl start wildfly'
Summary: wildfly will not start after doing 'yum install wildfly' and then 'systemctl ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: wildfly
Version: 20
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Marek Goldmann
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-22 01:42 UTC by Corey Daley
Modified: 2014-10-03 09:31 UTC (History)
1 user (show)

Fixed In Version: wildfly-8.1.0-3.fc20
Clone Of:
: 1173536 (view as bug list)
Environment:
Last Closed: 2014-10-03 09:31:59 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
wildfly server.log for standalone (13.53 KB, text/plain)
2014-08-22 01:42 UTC, Corey Daley 		no flags Details
View All

Description Corey Daley 2014-08-22 01:42:57 UTC 
Created attachment 929398 [details]
wildfly server.log for standalone

Description of problem:
After running 'yum install wildfly' and 'systemctl start wildfly', on a clean install of fedora 20, it does not start, the symlink for a dependency is incorrect.

http://pastebin.com/rWy510Sg (line 100)
The symlink for /usr/share/wildfly/modules/system/layers/base/org/jboss/marshalling/river/main/jboss-marshalling-river.jar is pointing to /usr/share/java/jboss-marshalling-river.jar instead of /usr/share/java/jboss-marshalling/jboss-marshalling-river.jar, fixing this symlink resolves the issue.
Versions installed:
wildfly.noarch                 8.1.0-2.fc20         @updates
jboss-marshalling.noarch       1.4.6-1.fc20         @updates

Version-Release number of selected component (if applicable):
8.1.0-2.fc20

How reproducible:
100%

Steps to Reproduce:
1. yum install wildfly
2.systemctl start wildfly
3.

Actual results:
[root@cdaley-test-1 fedora]# systemctl status wildfly
wildfly.service - The WildFly Application Server
   Loaded: loaded (/usr/lib/systemd/system/wildfly.service; disabled)
   Active: failed (Result: exit-code) since Fri 2014-08-22 01:06:12 UTC; 1s ago
  Process: 29406 ExecStart=/usr/share/wildfly/bin/launch.sh $WILDFLY_MODE $WILDFLY_CONFIG $WILDFLY_BIND (code=exited, status=1/FAILURE)
 Main PID: 29406 (code=exited, status=1/FAILURE)

Aug 22 01:05:51 cdaley-test-1 systemd[1]: Started The WildFly Application Server.
Aug 22 01:06:12 cdaley-test-1 systemd[1]: wildfly.service: main process exited, code=exited, status=1/FAILURE
Aug 22 01:06:12 cdaley-test-1 systemd[1]: Unit wildfly.service entered failed state.

Expected results:
[root@cdaley-test-1 main]# systemctl status wildfly
wildfly.service - The WildFly Application Server
   Loaded: loaded (/usr/lib/systemd/system/wildfly.service; disabled)
   Active: active (running) since Fri 2014-08-22 01:28:04 UTC; 8s ago
 Main PID: 30068 (launch.sh)
   CGroup: /system.slice/wildfly.service
           ├─30068 /bin/sh /usr/share/wildfly/bin/launch.sh standalone standalone.xml 0.0.0.0
           ├─30069 /bin/sh /usr/share/wildfly/bin/standalone.sh -c standalone.xml -b 0.0.0.0
           └─30116 java -D[Standalone] -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=...

Aug 22 01:28:04 cdaley-test-1 systemd[1]: Started The WildFly Application Server.

Additional info:
Comment 1 Marek Goldmann 2014-09-15 07:09:22 UTC 
Have you tried wildfly-8.1.0-3.fc20? It was pushed to stable one day after you reported this bug :)
Comment 2 Marek Goldmann 2014-10-03 09:31:59 UTC 
Closing, this is fixed in wildfly-8.1.0-3.fc20.
Note You need to log in before you can comment on or make changes to this bug.