Kbase P74131: Can not start webspeed broker when using customized protermcap
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
9/19/2008 |
|
Status: Verified
SYMPTOM(s):
Can not start WebSpeed broker
Broker starts if the initial agents to start is set to 0
Can not add WebSpeed agents after broker with zero agents starts
Can start _progres with no errors by the same user
Can manually start server from java process, cutting the command from broker log
get process ID
completed
wsbroker1 is not responding to a ping (8307)
Error 8307 seen in cmdplugin.dat
Installing service pack 9.1D08 does not fix the problem
Using tusc to trace agent start up shows the process is trying to output promsg "C o u l d n o t f i n d t e r m i n a l t y p e i n f i l e ( 1 4 6 )"
FACT(s) (Environment):
HP-UX 11 64-bit
WebSpeed 3.1D
CAUSE:
The TERM environment variable is set to em320w and the protermcap pointed to by PROTERMCAP environment variable contains only this entry, this does not affect regular _progres session, however webspeed can not start with this setting
FIX:
Reset TERM to a supported terminal in regular protermcap, and point PROTERMCAP to a regular protermcap file from normal progress installation