| Title: | BASEstar Open Multiplatform Application Framework |
| Notice: | Kit pointers: see topic 3 |
| Moderator: | VARESE::CORBETTA |
| Created: | Tue Oct 02 1990 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 607 |
| Total number of notes: | 1971 |
We have a situation at a customer site (ERICSSON) where there has been some network problems. A lot of nodes had to be rebooted but the B* system which consists of two nodes, didn't have to be rebooted. The B* system executes on the primary node and if single B* components have to be restarted they are restarted on the primary node. Only if the whole B* system goes down it will be restarted on the other node. However, after some time we got the message: PC_SERVER: ... No more room for new hosts: MAX IS HOSTS=16; TASKS=64 Since there are two additional PC-servers it seems that there is no load balance between them. It looks like only one is working. The ACTOR for the PC-servers have been restarted but it didn't help. - Is LSN involved in the assigning of PC-clients to a PC-server ? - Is there any good way to restart the PC-servers to make them split the workload without restarting B* ? Regards Michael
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 571.1 | IMPERO::SERRA | We allow more rock'n'roll | Thu Mar 06 1997 10:41 | 45 | |
Are you talking about B* 2.0 on Alpha VMS, right ?
>> The ACTOR for the PC-servers have been restarted but it didn't help.
Do *all* your PC-servers belong to the actor, or do you have
also the "default" one, that is, the one which starts at realm's
startup ?
Do you mean that even after a PC-servers' actor termination/startup
client PCs attempt always to connect to the *same* PC-server as they
did before ? Do you get the "No more room for new hosts ..."
message immediately (i.e. as soon as the 1st PC attempts to connect
after actor's restart) or when the Nth PC is switched on ?
>> Is LSN involved in the assigning of PC-clients to a PC-server ?
Yes, LNS plays a main role in this.
>> Is there any good way to restart the PC-servers to make them split
>> the workload without restarting B* ?
Mmmmm ... try this, but I cannot guarantee it'll work,
therefore, do it in a moment when a possible total B* shutdown
wouldn't be a disaster for the customer :
- terminate PC-servers actor
- shut down the whole B* environment (bstr_node_shut -h) on the
"backup" (or "secondary") node, i.e. the node where the no
application component is running.
- restart PC-servers actor then see if the problem still happens.
If so, your only chance is to shutdown B* on the primary node too
and then restart everything.
If you can mail me or post here B* realm and node logfiles from both
systems, they'll be welcome.
- Beppe -
| |||||
| 571.2 | Restarted BASEstar on the primary node | SWETSC::LONNGREN | Thu Mar 06 1997 17:25 | 32 | |
Hello Beppe !
- Yes it's B* V2.0 on Alpha.
The customer got an opurtunity to restart B* on the primary node and
after that it works fine.
However it would be interesting to hear your comments on your
questions that I have answered below.
>>> Do *all* your PC-servers belong to the actor, or do you have
also the "default" one, that is, the one which starts at realm's
startup ?
- No ,only the two additional PC-servers belongs to a separate actor.
The "default" one is still started when the realm is started.
>>> Do you mean that even after a PC-servers' actor termination/startup
client PCs attempt always to connect to the *same* PC-server as they
did before ? Do you get the "No more room for new hosts ..."
message immediately (i.e. as soon as the 1st PC attempts to connect
after actor's restart) or when the Nth PC is switched on ?
- Well, as far as we know we got the "No more room for new hosts ..."
message immediately after restarting the actor.
If we get this problem again we will try your suggestion about stopping
B* on the BACKUPnode and if that doesn't help I'll send you the logfiles.
- Thanks Michael
| |||||
| 571.3 | all PC-servers under the actor | IMPERO::SERRA | Volumeappalla! | Fri Mar 07 1997 12:14 | 13 |
>> No, only the two additional PC-servers belongs to a separate actor.
>> The "default" one is still started when the realm is started.
I'd suggest to get rid of the "default" one and replace it with
a third "actor-controlled" PC-server.
You may have a look at reply 110.7 of BASESTAROPEN_QAR to see
how to avoid PC-server starting at realm startup.
- Beppe -
| |||||
| 571.4 | V3.1 way | VARESE::BLASI | Thu Mar 27 1997 18:12 | 9 | |
> You may have a look at reply 110.7 of BASESTAROPEN_QAR to see
> how to avoid PC-server starting at realm startup.
In V3.1 bstr_realm_start_node will have a new parameter (-nocs)
to do just this: to avoid PC-server starting at realm startup.
Lorenzo
| |||||