| 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 |
7 Hi, We are having some resource problems starting up a second REALM in a development system ( OpenVMS ). It looks like the AMS_SERVER is having problem with insufficient virtual memory. What system or process parameter should we increase and about how much ? Regards, Fredrik REALM log 0002599 97/04/11 08:14:36 4b36 BSTR_CLI: 0002600 97/04/11 08:14:42 4f51 CE: S-BSTR_S_COM_START: Start (BASEStar Open 2.0 (Rev. 1), Mar 13 1996, 16:54:20) 0002601 97/04/11 08:14:43 5155 CNS: S-BSTR_S_COM_START: Start �:F�����0͵ 0002602 97/04/11 08:14:50 3656 GOM_SERVER: I-BSTR_S_GOM_SERVER_START: GOM Server starting up (BASEStar Open 2.0 (Rev. 1), Mar 13 1996, 17:43:16) 0002603 97/04/11 08:14:52 3656 GOM_SERVER: I-BSTR_S_GOM_SNP_LOAD: Load snapshot file: objects=DATATYPE; access_key=SNAPSHOT; database=BSTR$SNAPSHOT; version=1 0002604 97/04/11 08:15:10 3656 GOM_SERVER: I-BSTR_S_GOM_SNP_LOAD: Load snapshot file: objects=DOMAIN; access_key=SNAPSHOT; database=BSTR$SNAPSHOT; version=1 0002605 97/04/11 08:15:13 3656 GOM_SERVER: I-BSTR_S_GOM_SNP_LOAD: Load snapshot file: objects=DEVICE; access_key=SNAPSHOT; database=BSTR$SNAPSHOT; version=1 0002606 97/04/11 08:15:13 4e58 TCP_RCM: S-BSTR_S_COM_START: Start (BASEStar Open 2.0 (Rev. 1), Jul 12 1994, 13:24:12) 0002607 97/04/11 08:15:19 4e59 AMS_SERVER: I-BSTR_S_AMS_AMSSTART: AMS SERVER starting for realm 'KLECS_1F (BASEStar Open 2.0 (Rev. 1), Mar 13 1996, 17:18:41)' 0002608 97/04/11 08:15:26 4e59 AMS_SERVER: I-BSTR_S_AMS_CLILOAD: LOAD CONFIGURATION request: -t SNAPSHOT -a BSTR$SNAPSHOT -v 1 0002610 97/04/11 08:19:13 4e59 AMS_SERVER: F-BSTR_S_COM_LNS_FDBERROR: Internal FDB error 0002611 97/04/11 08:19:13 4e59 AMS_SERVER: W-BSTR_S_AMS_NET_PART: #### NETWORK PARTITIONING: AMS_SERVER restarted #### 0002612 97/04/11 08:19:13 4e59 AMS_SERVER: I-BSTR_S_AMS_AMSSHUT: AMS SERVER shutting 0002613 97/04/11 08:19:19 5163 AMS_SERVER: I-BSTR_S_AMS_AMSSTART: AMS SERVER starting for realm 'KLECS_1F (BASEStar Open 2.0 (Rev. 1), Mar 13 1996, 17:18:41)' BASESTARNODE.LOG 0002739 97/04/11 09:42:58 126 LNSSR: F-BSTR_S_FDB_INSVIRMEM: Insufficient virtual memory
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 587.1 | LNSSR's pgflquo | IMPERO::SERRA | Volumeappalla! | Fri Apr 11 1997 16:06 | 50 |
Hello,
>> It looks like the AMS_SERVER is having problem with insufficient
>> virtual memory.
Not exactly. The process having virtual memory problem is
actually the B* Lock & Name Server (LNSSR_BSTR):
LNSSR: F-BSTR_S_FDB_INSVIRMEM: Insufficient virtual memory
It happens that the problem arises while the AMS Server of the
2nd realm is exchanging information with LNSSR, who returns
an error to AMS, who in turn logs the error on the realm
logfile:
AMS_SERVER: F-BSTR_S_COM_LNS_FDBERROR: Internal FDB error
^^^
>> What system or process parameter should we increase and about how
>> much ?
You should increase LNSSR_BSTR's process "Paging file quota":
whose default value is 30000.
If you edit the bstr_bin:com_start_lns.com file, you'll see
near the bottom the "run" command for the LNSHM process
(LNSSR's parent process):
$ run /detach -
/ast_limit = 100 -
...
/page_file = 30000 -
...
Try to increase the "page_file" value of, say, 10 or 20000,
then do a bstr_node_shut / bstr_node_start.
If it is still not enough, put some more and repeat.
The right value depends on the volume of B* objects
configurations of the two combined realms.
Since it's the first time I see this kind of problem allow me
a question: do you realms configs have an awful lot of objects
such as array/structure_datatypes, domains, vmds, actors,
activities, programs ? Only objects of these classes are made
known to LNSSR, so there must be a large number of them to make
memory troubles to LNSSR.
- Beppe -
| |||||