[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | DEC/EDI |
| Notice: | DEC/EDI V2.1 - see note 2002 |
| Moderator: | METSYS::BABER |
|
| Created: | Wed Jun 06 1990 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 3150 |
| Total number of notes: | 13466 |
3076.0. "OBB 2.6 with V3.1" by TAKEOF::BLATTER (Nicolas Blatter @ ZUO) Tue Mar 25 1997 15:20
Hi
I tried to update a OBB 2.5B installation to OBB 2.6.
Server and Client are Unix 3.2B, with DEC/EDI 3.1
If I update OBB I always got on Objectbroker failed.
No errors in the DEC/EDI Log.
As it was working with 2.5B we do not have net problems
or proxy problems.
obbntst -s is working on both sites.
obbntst -A -n ....
is working from the client site but not on the server site.
Hope you can help !!!
Nicolas
Hier the Trace from server and Client.
Server:
asgsap> more OBB000001f60038.log
##
## started server using invocation string /bin/sh -c /tmp/OBB000001f60038.sh
##
trap 'echo exiting;exit' 0 1
cd /usr/users/decedi
if [ -f /usr/users/decedi/.obb_login ]
then
. /usr/users/decedi/.obb_login
fi
rm -f /tmp/OBB000001f60038.sh
/tmp/OBB000001f60038.sh: rm: not found
exec /usr/sbin/decedi_imtd
*** Load Authentication implementation Trusted
FamilyName<3> <TRS>
ImagePath<26> </usr/shlib/libobbsectrs.so>
LibraryName: /usr/shlib/libobbsectrs.so
*** Load Network implementation TCP
FamilyName<5> <TCPIP>
ImagePath<26> </usr/shlib/libobbtrntcp.so>
LibraryName: /usr/shlib/libobbtrntcp.so
--- Setting nonblocking socket : 3
--- Bound to socket: 3
--- Family: 2
--- SType: 1
--- Port: 1093
*** Load Agent implementation OrbV12
FamilyName<3> <OBB>
ImagePath<25> </usr/shlib/libobbagncl.so>
LibraryName: /usr/shlib/libobbagncl.so
--- Connecting to PTIEDI01
--- Port: 62
--- Attempting connect on socket: 4
--- Setting nonblocking socket : 4
*** Queuing Event: Register Implementation.
*** Request Sent: Synchronous Invoke.
*** Method: 65e448ecbd2d.0c.7e.0b.00.00.00.00.00.
** * MethodServerClass: 65e448ecbd2c.0c.7e.0b.00.00.00.00.00
*** Marshalled Buffer: 648
*** Allocated Buffer : 2012
--- SAR: Sending message on socket 4
--- Sending on socket 4
--- Total data length is 648
--- Sending data on socket - len is 648
--- Writing to socket
--- Number of bytes actually sent is 648
--- SAR: Waiting for message on socket 4
--- SAR: Receiving message on socket 4
--- Receiving on socket 4
--- Receving data on socket - len is 20
--- Number of bytes actually received is 20
--- Receving data on socket - len is 100
--- Number of bytes actually received is 100
*** Transport Status: OBB_SUCCESS (s), Successful completion.
*** Operation Status: OBB_SUCCESS (s), Successful completion.
--- Closing socket: 4
--- Accept on the server handle in wait for event: 3
--- Setting nonblocking socket : 5
--- Receiving on socket 5
--- Receving data on socket - len is 20
--- Number of bytes actually received is 20
--- Receving data on socket - len is 448
--- Number of bytes actually received is 448
*** Request Received: Synchronous Invoke.
*** Method: 68eb4b476f3e.0c.70.a9.00.00.00.00.00
*** Implementation Instance ID: 68eeba773e38.0c.70.a9.00.00.00.00.00
*** Deferred Callback Id: 0
@@@ Proxy Lookup:
RemoteHost: tusz1200
RemoteUser: 0
/bin/sh: 2069 Memory fault
Client:
decedi.err
asgsap> more decedi.err
Module : DECEDI_API_FETCH OBB_INV_COMMFAIL (e), Transport level communication failed.
-OBB_INV_DISCONN (e), The connection has been disconnected.
Module : DECEDI_API_TRACK OBB_INV_COMMFAIL (e), Transport level communication failed.
-OBB_INV_DISCONN (e), The connection has been disconnected.
Module : DECEDI_API_TRACK OBB_INV_COMMFAIL (e), Transport level communication failed.
-OBB_INV_DISCONN (e), The connection has been disconnected.
Module : DECEDI_API_TRACK OBB_INV_COMMFAIL (e), Transport level communication failed.
-OBB_INV_DISCONN (e), The connection has been disconnected.
Module : DECEDI_API_TRACK OBB_INV_COMMFAIL (e), Transport level communication failed.
-OBB_INV_DISCONN (e), The connection has been disconnected.
Client trace:
asgsap> more obb_trace.log
Script started on Mon Mar 24 19:09:44 1997
# trade track TTT
*** Load Network implementation TCP
FamilyName<5> <TCPIP>
ImagePath<26> </usr/shlib/libobbtrntcp.so>
LibraryName: /usr/shlib/libobbtrntcp.so
**** Server Instance Selection
*** Load Agent implementation OrbV12
FamilyName<3> <OBB>
ImagePath<25> </usr/shlib/libobbagncl.so>
LibraryName: /usr/shlib/libobbagncl.so
--- Connecting to PTIEDI01
--- Port: 62
--- Attempting connect on socket: 5
--- Setting nonblocking socket : 5
Obtaining Security Key for Client ID 7ba02acf7cdc.02.8a.df.41.6b.00.00.00
Impl ID 65e448ecbd2c.0c.7e.0b.00.00.00.00.00
List of server supported sec. types isn't known yet. Trying client sec types in turn
Number of client supported security types: 1
Trying each of the sectypes from above list
*** Load Authentication implementation Trusted
FamilyName<3> <TRS>
ImagePath<26> </usr/shlib/libobbsectrs.so>
LibraryName: /usr/shlib/libobbsectrs.so
Trying to get security key using Trusted package
Successfully obtained key/esatablished context using security package Trusted
In Marshall Args - # args:11
Arg #:0
In Marshall ObjRef
In Marshall Args - # args:1
Arg #:0
End Marshall Args Successfully. # Args:1
Ending Marshall ObjRef Successfully
Arg #:1
Arg #:2
Arg #:3
In Marshall Args - # args:13
Arg #:0
Arg #:1
Arg #:2
Arg #:3
Arg #:4
Arg #:5
Arg #:6
In Marshall Args - # args:1
Arg #:0
Arg Name: TCP
type:38
valflags:0
argflags:0
Marshalling a string of length:6
End Marshall Args Successfully. # Args:1
Arg #:7
Arg #:8
Arg #:9
Arg #:10
Arg #:11
Arg #:12
End Marshall Args Successfully. # Args:13
Arg #:4
In Marshall Args - # args:0
End Marshall Args Successfully. # Args:0
Arg #:5
Arg #:6
Arg #:7
Arg #:8
Arg #:9
Arg #:10
End Marshall Args Successfully. # Args:11
Signing messsage from Client ID 7ba02acf7cdc.02.8a.df.41.6b.00.00.00
to Impl ID 65e448ecbd2c.0c.7e.0b.00.00.00.00.00
Using Trusted Security package to sign message.
Status of signing message: OBB_SUCCESS (s), Successful completion.
*** Request Sent: Synchronous Invoke.
*** Method: 65e448f20f7c.0c.7e.0b.00.00.00.00.00.
** * MethodServerClass: 65e448ecbd2c.0c.7e.0b.00.00.00.00.00
*** Marshalled Buffer: 544
*** Allocated Buffer : 1900
--- SAR: Sending message on socket 5
--- Sending on socket 5
--- Total data length is 544
--- Sending data on socket - len is 544
--- Writing to socket
--- Number of bytes actually sent is 544
--- SAR: Waiting for message on socket 5
--- SAR: Receiving message on socket 5
--- Receiving on socket 5
--- Receving data on socket - len is 20
--- Number of bytes actually received is 20
--- Receving data on socket - len is 184
--- Number of bytes actually received is 184
*** Transport Status: OBB_SUCCESS (s), Successful completion.
Trying to verify message from client UUID 7ba02acf7cdc.02.8a.df.41.6b.00.00.00
Using Trusted security package to verify signed message
Stauts of verifying signed message: OBB_SUCCESS (s), Successful completion.
In Unmarshall Args - # Args:3
Arg #:0
Type:21
In Unmarshall Args - # Args:0
End Unmarshall Args Successfully - # Args :0
Arg #:1
Type:23
In Unmarshall Args - # Args:0
Arg #:0
In Unmarshall Args - # Args:0
End Unmarshall Args Successfully - # Args :0
Arg #:1
In Unmarshall Args - # Args:0
End Unmarshall Args Successfully - # Args :0
End Unmarshall Args Successfully - # Args :0
Arg #:2
Type:11
End Unmarshall Args Successfully - # Args :3
*** Operation Status: OBB_INV_METHODFAIL (e), Method execution failed.
--- Closing socket: 5
--- Connecting to PTIEDI01
--- Port: 62
--- Attempting connect on socket: 5
--- Setting nonblocking socket : 5
Obtaining Security Key for Client ID 7ba02acf7cdc.02.8a.df.41.6b.00.00.00
Impl ID 65e448ecbd2c.0c.7e.0b.00.00.00.00.00
List of server supported sec. types isn't known yet. Trying client sec types in turn
Number of client supported security types: 1
Trying each of the sectypes from above list
Trying to get security key using Trusted package
Successfully obtained key/esatablished context using security package Trusted
In Marshall Args - # args:11
Arg #:0
In Marshall ObjRef
In Marshall Args - # args:1
Arg #:0
End Marshall Args Successfully. # Args:1
Ending Marshall ObjRef Successfully
Arg #:1
Arg #:2
Arg #:3
In Marshall Args - # args:8
Arg #:0
Arg #:1
Arg #:2
Arg #:3
Arg #:4
In Marshall ObjRef
In Marshall Args - # args:7
Arg #:0
Arg #:1
Arg #:2
Arg #:3
Arg #:4
Arg #:5
Arg #:6
End Marshall Args Successfully. # Args:7
In Marshall Args - # args:10
Arg #:0
Arg #:1
Arg #:2
Arg #:3
Arg #:4
Arg #:5
Arg #:6
Arg #:7
Arg #:8
Arg #:9
End Marshall Args Successfully. # Args:10
Ending Marshall ObjRef Successfully
Arg #:5
Arg #:6
Arg #:7
End Marshall Args Successfully. # Args:8
Arg #:4
In Marshall Args - # args:0
End Marshall Args Successfully. # Args:0
Arg #:5
Arg #:6
Arg #:7
Arg #:8
Arg #:9
Arg #:10
End Marshall Args Successfully. # Args:11
Signing messsage from Client ID 7ba02acf7cdc.02.8a.df.41.6b.00.00.00
to Impl ID 65e448ecbd2c.0c.7e.0b.00.00.00.00.00
Using Trusted Security package to sign message.
Status of signing message: OBB_SUCCESS (s), Successful completion.
*** Request Sent: Synchronous Invoke.
*** Method: 65e448eeadd4.0c.7e.0b.00.00.00.00.00.
** * MethodServerClass: 65e448ecbd2c.0c.7e.0b.00.00.00.00.00
*** Marshalled Buffer: 604
*** Allocated Buffer : 1956
--- SAR: Sending message on socket 5
--- Sending on socket 5
--- Total data length is 604
--- Sending data on socket - len is 604
--- Writing to socket
--- Number of bytes actually sent is 604
--- SAR: Waiting for message on socket 5
--- SAR: Receiving message on socket 5
--- Receiving on socket 5
--- Receving data on socket - len is 20
--- Number of bytes actually received is 20
--- Receving data on socket - len is 88
--- Number of bytes actually received is 88
*** Transport Status: OBB_SUCCESS (s), Successful completion.
Trying to verify message from client UUID 7ba02acf7cdc.02.8a.df.41.6b.00.00.00
Using Trusted security package to verify signed message
Stauts of verifying signed message: OBB_SUCCESS (s), Successful completion.
In Unmarshall Args - # Args:3
Arg #:0
Type:21
In Unmarshall Args - # Args:0
Arg #:0
type:12
valflags:0
argflags:2
Type:12
Arg #:1
type:11
valflags:0
argflags:16777218
Type:11
End Unmarshall Args Successfully - # Args :0
Arg #:1
Type:23
In Unmarshall Args - # Args:0
End Unmarshall Args Successfully - # Args :0
Arg #:2
Type:11
End Unmarshall Args Successfully - # Args :3
*** Operation Status: OBB_SUCCESS (s), Successful completion.
In Marshall Args - # args:11
Arg #:0
In Marshall ObjRef
In Marshall Args - # args:1
Arg #:0
End Marshall Args Successfully. # Args:1
Ending Marshall ObjRef Successfully
Arg #:1
Arg #:2
Arg #:3
In Marshall Args - # args:5
Arg #:0
Arg #:1
Arg #:2
Arg #:3
Arg #:4
End Marshall Args Successfully. # Args:5
Arg #:4
In Marshall Args - # args:0
End Marshall Args Successfully. # Args:0
Arg #:5
Arg #:6
Arg #:7
Arg #:8
Arg #:9
Arg #:10
End Marshall Args Successfully. # Args:11
Signing messsage from Client ID 7ba02acf7cdc.02.8a.df.41.6b.00.00.00
to Impl ID 65e448ecbd2c.0c.7e.0b.00.00.00.00.00
Using Trusted Security package to sign message.
Status of signing message: OBB_SUCCESS (s), Successful completion.
*** Request Sent: Synchronous Invoke.
*** Method: 65e448efbf44.0c.7e.0b.00.00.00.00.00.
** * MethodServerClass: 65e448ecbd2c.0c.7e.0b.00.00.00.00.00
*** Marshalled Buffer: 340
*** Allocated Buffer : 1528
--- SAR: Sending message on socket 5
--- Sending on socket 5
--- Total data length is 340
--- Sending data on socket - len is 340
--- Writing to socket
--- Number of bytes actually sent is 340
--- SAR: Waiting for message on socket 5
--- SAR: Receiving message on socket 5
--- Receiving on socket 5^BM-PM-Y^A@^A(W ^A M-I^B@^AM-pM-^G ^AKj@^AM-dZ ^A q^B@^AM-H0^B@^A^AM-^@p^B@^A
M-I^B@^AM-^H
^AHM-~M-^?^_^AM-^Pd ^AM- 3@^AM-^@^_@^AM-^Xp ^A q^B@^AM-H0^B@^AM-^@p^B@^AHm@^AM-PM-Y^A@^AxM-{ ^A
q^B@^A^BM-|M-^?M-^?`
M-z ^AM-^?
--- Receving data on socket - len is 20
--- Number of bytes actually received is 20
--- Receving data on socket - len is 100
--- Number of bytes actually received is 100
*** Transport Status: OBB_SUCCESS (s), Successful completion.
Trying to verify message from client UUID 7ba02acf7cdc.02.8a.df.41.6b.00.00.00
Using Trusted security package to verify signed message
Stauts of verifying signed message: OBB_SUCCESS (s), Successful completion.
In Unmarshall Args - # Args:3
Arg #:0
Type:21
In Unmarshall Args - # Args:0
Arg #:0
type:11
valflags:0
argflags:2
Type:11
Arg #:1
type:13
valflags:768
argflags:26
Arg #:2
type:11
valflags:0
argflags:16777218
Type:11
End Unmarshall Args Successfully - # Args :0
Arg #:1
Type:23
In Unmarshall Args - # Args:0
End Unmarshall Args Successfully - # Args :0
Arg #:2
Type:11
End Unmarshall Args Successfully - # Args :3
*** Operation Status: OBB_SUCCESS (s), Successful completion.
In Marshall Args - # args:11
Arg #:0
In Marshall ObjRef
In Marshall Args - # args:1
Arg #:0
End Marshall Args Successfully. # Args:1
Ending Marshall ObjRef Successfully
Arg #:1
Arg #:2
Arg #:3
In Marshall Args - # args:5
Arg #:0
Arg #:1
Arg #:2
Arg #:3
Arg #:4
End Marshall Args Successfully. # Args:5
Arg #:4
In Marshall Args - # args:0
End Marshall Args Successfully. # Args:0
Arg #:5
Arg #:6
Arg #:7
Arg #:8
Arg #:9
Arg #:10
End Marshall Args Successfully. # Args:11
Signing messsage from Client ID 7ba02acf7cdc.02.8a.df.41.6b.00.00.00
to Impl ID 65e448ecbd2c.0c.7e.0b.00.00.00.00.00
Using Trusted Security package to sign message.
Status of signing message: OBB_SUCCESS (s), Successful completion.
*** Request Sent: Synchronous Invoke.
*** Method: 65e448efbf44.0c.7e.0b.00.00.00.00.00.
** * MethodServerClass: 65e448ecbd2c.0c.7e.0b.00.00.00.00.00
*** Marshalled Buffer: 340
*** Allocated Buffer : 1528
--- SAR: Sending message on socket 5
--- Sending on socket 5
--- Total data length is 340
--- Sending data on socket - len is 340
--- Writing to socket
--- Number of bytes actually sent is 340
--- SAR: Waiting for message on socket 5
--- SAR: Receiving message on socket 5
--- Receiving on socket 5
--- Receving data on socket - len is 20
--- Number of bytes actually received is 20
--- Receving data on socket - len is 680
--- Number of bytes actually received is 680
*** Transport Status: OBB_SUCCESS (s), Successful completion.
Trying to verify message from client UUID 7ba02acf7cdc.02.8a.df.41.6b.00.00.00
Using Trusted security package to verify signed message
Stauts of verifying signed message: OBB_SUCCESS (s), Successful completion.
In Unmarshall Args - # Args:3
Arg #:0
Type:21
In Unmarshall Args - # Args:0
Arg #:0
type:11
valflags:0
argflags:2
Type:11
Arg #:1
type:13
valflags:256
argflags:26
Type:13
In Unmarshall Args - # Args:0
Arg #:0
type:9
valflags:0
argflags:0
name is ClassId
Dtype length:0
Type:9
Arg #:1
type:9
valflags:0
argflags:0
name is Name
Dtype length:0
Type:9
Arg #:2
type:9
valflags:0
argflags:0
name is InstanceId
Dtype length:0
Type:9
Arg #:3
type:9
valflags:0
argflags:0
name is Annotation
Dtype length:0
Type:9
Arg #:4
type:9
valflags:0
argflags:0
name is TransAddr
Dtype length:0
Type:9
Arg #:5
type:9
valflags:0
argflags:0
name is Username
Dtype length:0
Type:9
Arg #:6
type:9
valflags:0
argflags:0
name is RegTimestamp
Dtype length:0
Type:9
Arg #:7
type:9
valflags:0
argflags:0
name is Node
Dtype length:0
Type:9
Arg #:8
type:11
valflags:0
argflags:0
name is Pid
Dtype length:4
Type:11
Arg #:9
type:11
valflags:0
argflags:0
name is Flags
Dtype length:4
Type:11
Arg #:10
type:14
valflags:512
argflags:0
name is SrvSecPrincipalInfo
Dtype length:0
Arg #:11
type:9
valflags:0
argflags:0
name is CtrlSrvVersion
Dtype length:0
Type:9
End Unmarshall Args Successfully - # Args :0
Arg #:2
type:11
valflags:0
argflags:16777218
Type:11
End Unmarshall Args Successfully - # Args :0
Arg #:1
Type:23
In Unmarshall Args - # Args:0
End Unmarshall Args Successfully - # Args :0
Arg #:2
Type:11
End Unmarshall Args Successfully - # Args :3
*** Operation Status: OBB_SUCCESS (s), Successful completion.
--- Closing socket: 5
--- Connecting to ptiedi01
--- Port: 1093
--- Attempting connect on socket: 5
--- Setting nonblocking socket : 5
Obtaining Security Key for Client ID 7ba02acf7cdc.02.8a.df.41.6b.00.00.00
Impl ID 68eeba773e38.0c.70.a9.00.00.00.00.00
List of server supported sec. types isn't known yet. Trying client sec types in turn
Number of client supported security types: 1
Trying each of the sectypes from above list
Trying to get security key using Trusted package
Successfully obtained key/esatablished context using security package Trusted
MrshLenSequence length:11
MrshLenCommon length:11
MrshLenUDT length:11
UDT length:11
MrshLenSequence length:11
MrshLenCommon length:11
MrshLenUDT length:11
UDT length:11
In Marshall Args - # args:11
Arg #:0
In Marshall ObjRef
In Marshall Args - # args:7
Arg #:0
Arg #:1
Arg #:2
Arg #:3
Arg #:4
Arg #:5
Arg #:6
End Marshall Args Successfully. # Args:7
In Marshall Args - # args:10
Arg #:0
Arg #:1
Arg #:2
Arg #:3
Arg #:4
Arg #:5
Arg #:6
Arg #:7
Arg #:8
Arg #:9
End Marshall Args Successfully. # Args:10
Ending Marshall ObjRef Successfully
Arg #:1
Arg #:2
Arg #:3
In Marshall Args - # args:6
Arg #:0
Marshalling a string of length:4
Arg #:1
In Marshall by Typecode
Starting Marshall Sequence
Ending Marshall Sequence Successfully
Ending Marshall by Typecode Successfully
Arg #:2
Arg #:3
In Marshall by Typecode
Starting Marshall Sequence
Ending Marshall Sequence Successfully
Ending Marshall by Typecode Successfully
Arg #:4
Arg #:5
End Marshall Args Successfully. # Args:6
Arg #:4
In Marshall Args - # args:0
End Marshall Args Successfully. # Args:0
Arg #:5
Arg #:6
Arg #:7
Arg #:8
Arg #:9
Arg #:10
End Marshall Args Successfully. # Args:11
Signing messsage from Client ID 7ba02acf7cdc.02.8a.df.41.6b.00.00.00
to Impl ID 68eeba773e38.0c.70.a9.00.00.00.00.00
Using Trusted Security package to sign message.
Status of signing message: OBB_SUCCESS (s), Successful completion.
*** Request Sent: Synchronous Invoke.
*** Method: 68eb4b476f3e.0c.70.a9.00.00.00.00.00.
** * MethodServerClass: 68eeba773e38.0c.70.a9.00.00.00.00.00
*** Marshalled Buffer: 468
*** Allocated Buffer : 1789
--- SAR: Sending message on socket 5
--- Sending on socket 5
--- Total data length is 468
--- Sending data on socket - len is 468
--- Writing to socket
--- Number of bytes actually sent is 468
--- SAR: Waiting for message on socket 5
--- SAR: Receiving message on socket 5
--- Receiving on socket 5
--- Receving data on socket - len is 20
*** Transport Status: OBB_INV_COMMFAIL (e), Transport level communication failed.
*** Operation Status: OBB_INV_COMMFAIL (e), Transport level communication failed.
--- Closing Client socket: 5
--- Closing socket: 5
ObjectBroker Failure
# exit
# ls
script done on Mon Mar 24 19:09:59 1997
End Marshall Args Successfully. # Args:11
Signing messsage from Client ID 7ba02acf7cdc.02.8a.df.41.6b.00.00.00
ID 65e448ecbd2c.0c.7e.0b.00.00.0.00
Using Trusted Security package to sign^Asage.
Status of signig MM-xM-^?^_^A% Successful completio49
*** Request Sent: Synchronous Invoke.
*** Method: 65e448efbf44.0c.7e
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3076.1 | I remember seeing a warning on installation | SYSTEM::HELLIAR | http://samedi.reo.dec.com/ | Wed Mar 26 1997 15:37 | 10 |
| obbntst does not go via the proxies
'obbntst -A -n' does not exist...I presume you mean obbmsho.
ObjectBroker instalation warns that configuration data MAY be lost on
an upgrade so you may have lost something.
So, start at the beginning and verify obbmsho -A -n works both ways,
and if neccessary add the appropriate proxies.
Graham
|
| 3076.2 | | TAKEOF::BLATTER | Nicolas Blatter @ ZUO | Wed Mar 26 1997 16:08 | 20 |
| Graham
You are right the command was the obbmsho ..
I ve tried many thinks, also reinstalling OBB 2.6
with all the proxy.
I would say that if a proxy would not be correct
that I would got a:
Not authorized to access the EDI Server System
But these is not happenenig.
Also as I sayd the DEC/EDI sees the client, in the log
I can seee the TRADE Command with has been set fromm
the client.
Some more hints ???
Nicolas
|
| 3076.3 | memory fault and hostname | VIRGIN::BILL | BILL is my lastname !!! | Thu Mar 27 1997 08:51 | 19 |
| Nicolas
There are two things which I would check:
I the trace is a memory fault. Try to search a core dump
on the system and find out which process is crashing.
file core... This could give a hint
Another thing to check is the hostname. In the stack the
server is addressed as PTIEDI01 and ptiedi01. Objectbroker
is quite picky about hostnames. My personal unix opinion
is: never use uppercase hostnames.
And maybe you should state the obbmsho -A -n hostname
Cheers
Marco
|
| 3076.4 | OBB V2.7 | NETRIX::"[email protected]" | Nicolas | Tue Apr 08 1997 12:49 | 41 |
| Hi
the customer installed on the Client OBB V2.7 and it Works !!!
I've tried to install it inhouse but if I try to make a DECEDI_CONFIG I get:
1. Configure ACAS
2. Configure ObjectBroker
3. Configure database
4. Modify database users
5. Dump database
6. Load database
7. Manage database
8. Exit Configuration
Select option [8] : 2
Configuring ObjectBroker
Enter the name of the DEC/EDI Server [OBB_LOCAL] :
Will the client local to this server communicate using
ACAS or ObjectBroker (CORBA) interfaces?
1. ACAS
2. CORBA
Enter either 1 or 2 [2] :
...creating repository
OBB_COM_FILCREFAIL (e), Could not create file `OBB000015840001.TMP'.
Error: Couldn't create /var/adm/decedi/decedi_repository.ir
Press <Return> to continue.
I got the same error on the client and the server. Client is now OBB V2.7
(was 2.6), server is now 2.5B (was 2.6). I tried with these configuration
because these is what the customer has.
Any hints ??
Nicolas
[Posted by WWW Notes gateway]
|