Kbase 19584: adminserver failing to start with different user in 9.0B
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/10/2000 |
|
This knowledge base with discuss possible reasons for the adminserver
failing to start or re-start with a different user. Also, this can be
seen when proadsv -start command appears to be hanging.
One error is that the ads0.exp file is growing exponentially while the
proadsv -start command appears to hang. In the ads0.exp file the
following messages may appear:
Exception at Fri Mar 10 10:34:42 CET 2000:
java.io.FileNotFoundException
Message (excp): admserv.log
Stack Trace:
java.io.FileNotFoundException: admserv.log
at java.lang.Exception.<init>(Compiled Code)
at java.io.IOException.<init>(Compiled Code)
<snip>
This error indicates that it cannot find the admserv.log file. One
possible reason for this is because the adminserver has been started
previously by a different user. For example, if you start the
adminserver as root then the log files take the ownership of root.
Therefore, when you try to restart the adminserver as another user
then this user does not have the rights to read the log file.
In version 9.1A the following error message is shown in this case:
ERROR! Process being taken down because exception log is inaccessible.
The solution is to backup (if needed) and remove the log files in the
working directory. At this point you should be able to re-start the
adminserver as a different user. Alternatively you can change
ownership and permissions on the log files.
Kbase #19584
(tca 03/10/2000)