Description of problem:
Small edge case that might deserve a knowledgebase entry.
If the JBoss AS is run as root - via run.sh or jbossas-run - before the jbossas
service is ever run, then the server.log and boot.log files will be owned by
root. If the jbossas service is subsequently run, the startup will fail with an
jbossas startup has timed out, process still running
The correct error cause (permission failure on server.log) is written to the
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. After install, start up jbossas as root, then stop
2. Then attempt to start jbossas service
Error "jbossas startup has timed out, process still running" is written to
stdout. Actual file permission error is written to console log.
Change in direction - instead of KB article - needs a change to the startup script to report an error
if its logs cannot be written.
The init script has been updated with a check to see if server.log is writable
before starting the server. The fix will be in the next respin.
Fixed for the next respin.
In StacksV1-re20070110.0 (jbossas-4.0.5-1.el4s1.4) - the user sees this:
[root@cheddar all]# service jbossas start
Starting jbossas: [FAILED]
Logfile /var/log/jbossas/all/server.log exists but not writable by jboss.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.