Description of problem: # systemctl status jetty ● jetty.service - Jetty Web Application Server Loaded: loaded (/usr/lib/systemd/system/jetty.service; disabled) Active: failed (Result: exit-code) since Sun 2014-10-05 12:43:04 CEST; 15s ago Process: 3453 ExecStart=/usr/share/jetty/bin/jetty.sh (code=exited, status=1/FAILURE) Main PID: 3453 (code=exited, status=1/FAILURE) # /usr/share/jetty/bin/jetty.sh Starting Jetty: Error: Unable to access jarfile /usr/share/jetty/start.jar If jvm exited with Out of Memory Error it is quite likely that your SELinux policy doesn't allow execmem access for the JVM. To solve this problem, use: setsebool -P httpd_execmem 1 to allow execmem acces for processes in the httpd domain. Please bear in mind that this might affect other processess. For more information see httpd_selinux(8). I think the file /usr/share/jetty/start.jar is missing in the rpm! A symlink # ls -ld /usr/share/jetty/start.jar lrwxrwxrwx 1 root root 35 Jun 13 12:25 /usr/share/jetty/start.jar -> lib/jetty-start-9.2.1.v20140609.jar another symlink # ls -ld /usr/share/jetty/lib/jetty-start-9.2.1.v20140609.jar lrwxrwxrwx 1 root root 37 Jun 13 12:25 /usr/share/jetty/lib/jetty-start-9.2.1.v20140609.jar -> /usr/share/java/jetty/jetty-start.jar but no start.jar: # ls -ld /usr/share/java/jetty/jetty* -rw-r--r-- 1 root root 78556 Jun 13 12:26 /usr/share/java/jetty/jetty-annotations.jar -rw-r--r-- 1 root root 221091 Jun 13 12:26 /usr/share/java/jetty/jetty-client.jar -rw-r--r-- 1 root root 15725 Jun 13 12:26 /usr/share/java/jetty/jetty-continuation.jar -rw-r--r-- 1 root root 49161 Jun 13 12:26 /usr/share/java/jetty/jetty-deploy.jar -rw-r--r-- 1 root root 103355 Jun 13 12:26 /usr/share/java/jetty/jetty-http.jar -rw-r--r-- 1 root root 103221 Jun 13 12:26 /usr/share/java/jetty/jetty-io.jar -rw-r--r-- 1 root root 37290 Jun 13 12:26 /usr/share/java/jetty/jetty-jaas.jar -rw-r--r-- 1 root root 21816 Jun 13 12:26 /usr/share/java/jetty/jetty-jmx.jar -rw-r--r-- 1 root root 41008 Jun 13 12:26 /usr/share/java/jetty/jetty-jndi.jar -rw-r--r-- 1 root root 53505 Jun 13 12:26 /usr/share/java/jetty/jetty-plus.jar -rw-r--r-- 1 root root 49794 Jun 13 12:26 /usr/share/java/jetty/jetty-proxy.jar -rw-r--r-- 1 root root 28044 Jun 13 12:26 /usr/share/java/jetty/jetty-rewrite.jar -rw-r--r-- 1 root root 95562 Jun 13 12:26 /usr/share/java/jetty/jetty-security.jar -rw-r--r-- 1 root root 405386 Jun 13 12:26 /usr/share/java/jetty/jetty-server.jar -rw-r--r-- 1 root root 111063 Jun 13 12:26 /usr/share/java/jetty/jetty-servlet.jar -rw-r--r-- 1 root root 117785 Jun 13 12:26 /usr/share/java/jetty/jetty-servlets.jar -rw-r--r-- 1 root root 339742 Jun 13 12:26 /usr/share/java/jetty/jetty-util.jar -rw-r--r-- 1 root root 106262 Jun 13 12:26 /usr/share/java/jetty/jetty-webapp.jar -rw-r--r-- 1 root root 43867 Jun 13 12:26 /usr/share/java/jetty/jetty-xml.jar Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
jetty-9.2.1-2.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/jetty-9.2.1-2.fc21
Package jetty-9.2.1-2.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing jetty-9.2.1-2.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-12786/jetty-9.2.1-2.fc21 then log in and leave karma (feedback).
There seems to be much more dangling symlinks than just jetty-start. $ rpm -q jetty jetty-9.2.1-2.fc21.noarch $ find /usr/share/jetty/lib/ -type l ! -exec test -e {} \; -print /usr/share/jetty/lib/jetty-util-ajax-9.2.1.v20140609.jar /usr/share/jetty/lib/jetty-monitor-9.2.1.v20140609.jar /usr/share/jetty/lib/jetty-jaspi-9.2.1.v20140609.jar /usr/share/jetty/lib/jetty-spring-9.2.1.v20140609.jar /usr/share/jetty/lib/jetty-maven-plugin-9.2.1.v20140609.jar /usr/share/jetty/lib/jetty-websocket-9.2.1.v20140609.jar /usr/share/jetty/lib/jetty-nosql-9.2.1.v20140609.jar /usr/share/jetty/lib/websocket/javax-websocket-server-impl-9.2.1.v20140609.jar /usr/share/jetty/lib/websocket/javax-websocket-client-impl-9.2.1.v20140609.jar /usr/share/jetty/lib/jetty-jspc-maven-plugin-9.2.1.v20140609.jar /usr/share/jetty/lib/jetty-jsp-9.2.1.v20140609.jar /usr/share/jetty/lib/jetty-http-spi-9.2.1.v20140609.jar /usr/share/jetty/lib/jetty-ant-9.2.1.v20140609.jar /usr/share/jetty/lib/jetty-osgi-9.2.1.v20140609.jar
jetty-9.2.1-2.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
Problems still persist with exactly the same error message as originally noted. This is not the first time I have come across errors with the jetty package (previously it was a broken shell script). Please actually test the packages, I'm sure it's part of the standard build and publishing process.
(In reply to Gustav van der Merwe from comment #5) > Problems still persist with exactly the same error message as originally > noted. This is not the first time I have come across errors with the jetty > package (previously it was a broken shell script). > > Please actually test the packages, I'm sure it's part of the standard build > and publishing process. It's fixed in f21, but there was some problem when propagating it to rawhide which seemingly was fixed after f22 branching. So I assume you're using f22, otherwise you're hitting some unrelated problem as I just tested it in f21 and it started. I'll backport the fix to f22, sorry about that.
Actually, this is with FC21...
(In reply to Gustav van der Merwe from comment #7) > Actually, this is with FC21... That's weird. Can you post the exact version of jetty package you're using and the whole output of the command?
I moved forward with tomcat and jetty is now uninstalled from the server. The version was: Version : 9.2.1 Release : 3.fc21 The command sequence was systemctl start jetty and then systemctl status jetty (or looking in the journal) giving the same error as above.