Kbase P48564: Starting Webspeed broker causes error 8109 in the broker log
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
17/10/2003 |
|
Status: Unverified
FACT(s) (Environment):
SCO UnixWare 7.1.1
FACT(s) (Environment):
WebSpeed 3.1D
SYMPTOM(s):
Starting Webspeed broker causes error 8109 in the broker log file when AdminServer and NameServer run.
The NameServer does not start when AdminServer and WebSpeed broker run fine.
When broker dies it gives the following error:
main>(Oct 16, 2003 08:46:04:960) /usr/wrk/logs/wsbroker1.broker.log opened.
main>(Oct 16, 2003 08:46:05:090) ERROR : Configured maxSrvrInstance (10) exceeds maximum licensed servers (2). (8453)
main>(Oct 16, 2003 08:46:05:100) ubroker version: v91D (09-Apr-02) (8038)
L-3002>(Oct 16, 2003 08:46:05:330) Started listener thread: L-3002 (8043)
L-3002>Starting 2 server threads ... (8053)
S-0001>(Oct 16, 2003 08:46:05:400) Started server thread: S-0001. (8101)
S-0002>(Oct 16, 2003 08:46:05:490) Started server thread: S-0002. (8101)
S-0001>Server exec error : Resource temporarily unavailable (8109)
S-0001>(Oct 16, 2003 08:46:05:610) ERROR: cannot start server. (8100)
S-0002>Server exec error : Resource temporarily unavailable (8109)
S-0002>(Oct 16, 2003 08:46:06:600) ERROR: cannot start server. (8100)
L-3002>(Oct 16, 2003 08:46:07:630) Exception unbinding broker (not bound) : wsbroker1 (8525)
main>(Oct 16, 2003 08:46:08:640) ubroker v91D (09-Apr-02) done. (8041)
main>(Oct 16, 2003 08:46:08:640) Log Closed
When NameServer does not start it give the following errors upon executing nsman command:
Unable to connect to NameServer (8289)
Unable to find NameServer (8281)
The AdminServer starts fine.
If the broker is started before the NameServer, the NameServer does not start or vise versa.
While starting the server got an error stating "DIMM slot had an error on reboot"
DIMM means dual in-line memory module.
Changing the physical memory stick in the server resolved the Dimm error, hence, all the processes such as AdminServer, NameServer and the WebSpeed broker ran fine afterward.
CAUSE:
The bad physical memory installed in the machine caused the resource issue.
FIX:
Change the Physical memory stick in the server.