[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | DECss7 Product Forum |
|
| Moderator: | TAEC::BEATINI |
|
| Created: | Thu Mar 15 1990 |
| Last Modified: | Thu Jun 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 72 |
| Total number of notes: | 176 |
69.0. "@SS7-F-M3_BPGSRES, BEP can't lock its resource ?" by CSC32::COLTER () Fri Jan 31 1997 22:29
CONFIGURATION:
Digital UNIX V3.2D-1 (Rev. 41)
Alphaserver 2100 4/275
1 GB memory
2 21064 CPUs @ 275 MHZ
SS7ANSIPRD253 DECss7 V2.5-3 ANSI Product
SS7ANSIRN253 DECss7 V2.5-3 ANSI Release Notes
SS7HEADERS253 DECss7 V2.5-3 Header Files
SS7STARTUP253 DECss7 V2.5-3 Configure/Startup Procedures
PLATFORM-Z:
For ansi DECss7 version, ansi protocol, TCP/IP transport
FEP List: FEPA01
BEP List: BEPA01 BEPA02
DIR List: LMEA01
Applications List:
BEP BEPA01: MHLR1A MHLR1B
BEP BEPA02: MHLR2A MHLR2B
PROBLEM:
When I try to start the BEP on node BEPA01, the bep and ssnsd fail to
start and the bep_z.log contains:
"DECss7 message from APPLI Z
@SS7-F-M3_BPGSRES, BEP can't lock its resource for global section
Status is : @SS7-F-NOPRIV, no privilege for attempted operation
DECss7 message from APPLI Z
@SS7-E-MG_BEPCREMBX, Error when creating the MGT BEP mailbox
Status is : @SS7-F-IVADDR, invalid media address"
ANALYSIS:
o The BEP and SS7ND processes do not start.
o I created platform_c, using the same parameters as platform_z,
and was able to start the bep successfully.
o I reconfigured platform_z and was still unable to successfully
start it.
o Called Philippe Ravix and he explained that the system was unable
to lock a resource called "ss7_gs_res_bepa01_z".
o I performed a comparison of my system and the customers system
, using the "ipcs -z" command, and determined that BEPA01 seems
to have a ss7 message queue element, that my system does not
contain.
Message Queues:
T ID KEY MODE OWNER GROUP
q 0 1090534378 --rw------- root system
q 1 4949 -Rrw-rw-rw- root daemon
q 2 5000 -Rrw-rw-rw- root daemon
q 3 4500 --rw-rw-rw- ss7 adm
Using "ipcs -a" this expanded to:
T ID KEY MODE OWNER GROUP
q 3 4500 --rw-rw-rw- ss7 adm
CREATOR CGROUP CBYTES QNUM QBYTES LS
ss7 adm 0 0 16384 0
PID LRPID STIME RTIME CTIME
0 no-entry no-entry 16:41:48
o The other portions of the platform function correctly.
FEP List: FEPA01
BEP List: BEPA01 BEPA02
DIR List: LMEA01
o Additional configuration data, probabily not worth a lot:
bepa01:ss7> more /etc/hosts | grep bepa
166.35.251.173 bepa01.rch.mci.com bepa01 # Alpha 2100
166.35.251.176 bepa02.rch.mci.com bepa02 # Alpha 8400
166.35.251.177 bepa02-ft1.rch.mci.com bepa02-ft1 # Alpha 8400
166.35.251.178 bepa02-ft2.rch.mci.com bepa02-ft2 # Alpha 8400
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 69.1 | The problem was an open file in /usr/local/tmp | CSC32::COLTER | | Mon Feb 03 1997 16:45 | 5 |
| This problem was caused by performing a "kill -9 xxxx". It left
/usr/local/tmp/SS7_GS_RES_BEPA01_Z in a faulty state. This problem
remained even though the system rebooted. I had to delete these files
before I was able to successfully perfrom a ss7startup. Thank
you, Francois!
|