Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1062950 - wildfly service doesn't start up
Summary: wildfly service doesn't start up
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: wildfly
Version: 20
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Marek Goldmann
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-09 06:26 UTC by Ellis Seiker
Modified: 2014-02-09 07:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-09 07:12:43 UTC


Attachments (Terms of Use)

Description Ellis Seiker 2014-02-09 06:26:27 UTC
Description of problem:
sudo systemctl start wildfly.service doesn't work

Version-Release number of selected component (if applicable):
$ sudo rpm -q wildfly
wildfly-8.0.0-0.17.CR1.fc20.noarch

Steps to Reproduce:
1.$ sudo systemctl start wildfly.service
2.$ systemctl status wildfly.service -l

Actual results:
wildfly.service - The WildFly Application Server
   Loaded: loaded (/usr/lib/systemd/system/wildfly.service; disabled)
   Active: failed (Result: exit-code) since 일 2014-02-09 15:15:04 KST; 2s ago
  Process: 14701 ExecStart=/usr/share/wildfly/bin/launch.sh $WILDFLY_MODE $WILDFLY_CONFIG $WILDFLY_BIND (code=exited, status=1/FAILURE)
 Main PID: 14701 (code=exited, status=1/FAILURE)

 2월 09 15:15:03 systemd[1]: Started The WildFly Application Server.
 2월 09 15:15:04 systemd[1]: wildfly.service: main process exited, code=exited, status=1/FAILURE
 2월 09 15:15:04 systemd[1]: Unit wildfly.service entered failed state.


Expected results:
wildfly service starts and listens port 8080 and 9990

Additional info:
running standalone.sh or launch.sh works
result of standalone.sh:

$ sudo ./bin/standalone.sh
=========================================================================

  JBoss Bootstrap Environment

  JBOSS_HOME: /usr/share/wildfly

  JAVA: java

  JAVA_OPTS:  -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true

=========================================================================

15:24:08,812 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.0.Beta3
15:24:09,030 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.0.Beta1
15:24:09,104 INFO  [org.jboss.as] (MSC service thread 1-6) JBAS015899: WildFly 8.0.0.CR1 "WildFly" starting
15:24:09,965 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found TwitForge.war in deployment directory. To trigger deployment create a file called TwitForge.war.dodeploy
15:24:09,980 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
15:24:09,983 INFO  [org.xnio] (MSC service thread 1-9) XNIO version 3.2.0.Beta3
15:24:09,990 INFO  [org.xnio.nio] (MSC service thread 1-9) XNIO NIO Implementation Version 3.2.0.Beta3
15:24:10,006 INFO  [org.jboss.remoting] (MSC service thread 1-9) JBoss Remoting version 4.0.0.Beta1
15:24:10,019 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 33) JBAS010280: Activating Infinispan subsystem.
15:24:10,030 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 41) JBAS011800: Activating Naming Subsystem
15:24:10,047 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 46) JBAS013171: Activating Security Subsystem
15:24:10,059 INFO  [org.jboss.as.security] (MSC service thread 1-8) JBAS013170: Current PicketBox version=4.0.18.Final
15:24:10,061 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 39) JBAS012615: Activated the following JSF Implementations: [main]
15:24:10,062 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 50) JBAS015537: Activating WebServices Extension
15:24:10,066 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-15) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.2.Final)
15:24:10,097 INFO  [org.jboss.as.naming] (MSC service thread 1-14) JBAS011802: Starting Naming Service
15:24:10,101 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-7) JBAS015400: Bound mail session [java:jboss/mail/Default]
15:24:10,127 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-14) JBAS017502: Undertow 1.0.0.Beta30 starting
15:24:10,127 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 49) JBAS017502: Undertow 1.0.0.Beta30 starting
15:24:10,128 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 28) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
15:24:10,142 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-6) JBAS010417: Started Driver service with driver-name = h2
15:24:10,290 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-9) JBAS017525: Started server default-server.
15:24:10,293 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 49) JBAS017527: Creating file handler for path /usr/share/wildfly/welcome-content
15:24:10,301 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017531: Host default-host starting
15:24:10,479 WARN  [org.jboss.as.webservices] (ServerService Thread Pool -- 50) JBAS015506: Cannot load WS deployment aspects from /META-INF/stack-specific-deployment-aspects.xml
15:24:10,548 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) JBAS017519: Undertow HTTP listener default listening on /127.0.0.1:8080
15:24:10,567 INFO  [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.2.0.Final
15:24:10,646 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
15:24:10,675 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-11) JBAS015012: Started FileSystemDeploymentService for directory /usr/share/wildfly/standalone/deployments
15:24:10,677 ERROR [org.jboss.as.domain.http.api.undertow] (MSC service thread 1-3) JBAS015102: Unable to load console module for slot main, disabling console
15:24:10,677 INFO  [org.jboss.as.remoting] (MSC service thread 1-6) JBAS017100: Listening on 127.0.0.1:9999
15:24:10,873 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
15:24:10,873 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
15:24:10,874 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.0.0.CR1 "WildFly" started in 2315ms - Started 184 of 232 services (78 services are lazy, passive or on-demand)

Comment 1 Ellis Seiker 2014-02-09 07:12:43 UTC
My old config files were owned by my account, not wildfly. That's why they wildfly service couldn't be started. sorry


Note You need to log in before you can comment on or make changes to this bug.