Kbase P121384: proDebugConfig cannot enable client processes for debugging
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  18/02/2009 |
|
Status: Unverified
SYMPTOM(s):
proDebugConfig cannot enable client processes for debugging
Debugging was previously enabled with proDebugEnable -enable-all
Getting error message: Cannot make process <PID> ready for debugging.
Getting error message: The process id you specified may be invalid, not a Progress 4GL process, is a process from a pre 10.0A release of Progress, is busy and cannot be interrupted or Progress was started before debugging was enabled.
FACT(s) (Environment):
OpenEdge 10.x
Unix
CAUSE:
Bug# OE00135924
CAUSE:
/etc/ProDbgCK contains another DLC entry with a longer name and same root. Example:
/usr1/apps/100b/dlc100b.state=Debugging disabled
/usr1/apps/100b/dlc.state=Debugging enabled
FIX:
Workaround: Edit /etc/proDbgCK so it only contains the OpenEdge DLC paths currently installed on your system.
Follow the fowwing steps to edit /etc/ProDbgCK:
1. log in as root
2. chmod +w /etc/ProDbgCK
3. vi /etc/ProDbgCK
4. make changes in ProDbgCK file
5. save the file from vi and exit vi
6. chmod -w /etc/ProDbgCK
7. check the permissions on the ProDbgCK file with ls -l command. The file must be read only for everyone and owned by root.