Kbase P103084: Problem starting AdminServer due to WRKDIR environment variable not being set
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
22/09/2005 |
|
Status: Unverified
FACT(s) (Environment):
UNIX
SYMPTOM(s):
Cannot start the AdminServer because of permissions errors.
proadsv -start fails with permission errors
Has permissions to create and update files in the current working directory.
Other users can start the AdminServer without errors
The WRKDIR environment variable for this user is not set.
CAUSE:
The WRKDIR environment variable for this user is not set and. The user also does not have sufficient permissions to update the admserv.log in the working directory.
FIX:
1. Change permissions on the working directory that was specified during the Progress Installation process. If an admserv.log file also exists in this directory you may need to change the permissions associated with it.
a. Reference $DLC/installd.ini to determine the directory / path name specified for WRKDIR when the installation was performed.
b. As root use the command: chmod 755 <directory or path name associated with the WRKDIR environment variable identified in the $DLC/installd.ini file>
c. As root use the command: chmod 755 to the admserv.log file if one exists in the directory or path name identified in b.
2. If you do not want to change permissions of pre-existing WRKDIR or admserv.log file, then change the WRKDIR environment variable to point to a different location. This can be done by typing the following at a UNIX Bourne or Korn sell.
WRKDIR=<new working directory>;export WRKDIR