[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference tuxedo::dce-products

Title:DCE Product Information
Notice:Kit Info - See 2.*-4.*
Moderator:TUXEDO::MAZZAFERRO
Created:Fri Jun 26 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2269
Total number of notes:10003

2168.0. "sec_login_setup_identity hanging on dce 2.0a" by CAMINO::MCDERMOTT () Fri Feb 21 1997 16:58

    Hi,
    
    I'm on Unix 4.0b and dce 2.0a.
    
    The call, sec_login_setup_identity, is hanging.  I've checked
    the input args to the call and there fine. This same code performs
    correctly on Unix 3.2g and DCE 1.3b ECO1.  After hanging on the 
    this call for about a half hour in the debugger, I did a control-C
    to get back to the dbx prompt, here's the tstack trace:
    
    dbx) tstack
    
    Thread 0x3:
       0 __recvmsg(0x3ff8055d0c8, 0x3ffc008ae28, 0x3ff805aad58,
    0x325acbb9817d, 0x300000b2a80) [0x3ff8010c32c]
    
    Thread 0x7:
       0 (noname)() [0x120000000]
    
    Thread 0xa:
       0 nxm_idle(0x1, 0x140006278, 0x3ffc0188b70, 0x140006210,
    0x3ff80572724) [0x3ff8053ea8c]
       1 vpIdle(0x3ff80572724, 0x3ffc01877f0, 0x3ff8056d5b4, 0x140006210,
    0x3ffc0182ca8) [0x3ff8057a790]
       2 (unknown)() [0x3ff8056d5b0]
       3 thdBase(0x0, 0x0, 0x0, 0x1, 0x45586732) [0x3ff80574714]
    
    Thread 0xc:
       0 msg_receive_trap(0x14001b680, 0x400, 0x3ff8056e2fc, 0x0,
    0x3ffc01877f0) [0x3ff8053ea40]
       1 msg_receive(0x3ffc01877f0, 0x3ffc0188c50, 0x7, 0x500,
    0x3ffc018a120) [0x3ff80535200]
       2 (unknown)() [0x3ff8056cc9c]
       3 thdBase(0x0, 0x0, 0x0, 0x1, 0x45586732) [0x3ff80574714]
    
    Thread 0xe:
    >  0 nxm_idle(0x0, 0x0, 0x3ff8057bf4c, 0x3ffc018a988, 0x3ffc018a988)
    [0x3ff8053ea88]
       1 (unknown)() [0x3ff8057c078]
       2 (unknown)() [0x3ff8057b460]
       3 msg_receive(0x0, 0x3ffc018ac10, 0x0, 0x0, 0x3ffc018a988)
    [0x3ff80535200]
    
    Thread 0x10:
    >  0 nxm_idle(0x0, 0x0, 0x3ff8057bf4c, 0x3ffc018a988, 0x3ffc018a988)
    [0x3ff8053ea88]
       1 (unknown)() [0x3ff8057c078]
       2 (unknown)() [0x3ff8057b460]
       3 msg_receive(0x0, 0x3ffc018ac10, 0x0, 0x0, 0x3ffc018a988)
    [0x3ff80535200]
    
    Thread 0x12:
    >  0 nxm_idle(0x0, 0x0, 0x3ff8057bf4c, 0x3ffc018a988, 0x3ffc018a988)
    [0x3ff8053ea88]
       1 (unknown)() [0x3ff8057c078]
       2 (unknown)() [0x3ff8057b460]
       3 msg_receive(0x0, 0x3ffc018ac10, 0x0, 0x0, 0x3ffc018a988)
    [0x3ff80535200]
    
     Any ideas would be very appreciated.
    
     thanks
                                                  
T.RTitleUserPersonal
Name
DateLines
2168.1one more thingCAMINO::MCDERMOTTSat Feb 22 1997 15:412
BTW, the thread that called sec_login_setup_identity is thread 0xa.
Its called from main.
2168.2secd ok ?NETRIX::"[email protected]"Marco BillMon Feb 24 1997 09:2516
Was the rest of the cell servers working ?

- secd and cdsd, cdsadv on the servers ?

- cdsadv and dced on your system ?

- was dce_login working on your system ?

- dcecp -c secval status

- dcecp -c server ping /.:/subsys/dce/sec/master

- is this always reproducible ?

/Marco
[Posted by WWW Notes gateway]
2168.3dce appears to be okCAMINO::MCDERMOTTMon Feb 24 1997 11:487
    Hi,
    
    DCE is up and functioning correctly, before and after the hang.
    I can do a dce_login successfully and all dce processes are 
    up and running.
    
    The hang happens almost 100% of the time.
2168.4Re: sec_login_setup_identity hanging on dce 2.0aQUABBI::"[email protected]"Mon Feb 24 1997 13:3126
In article <[email protected]>, [email protected] writes:
|>Title: sec_login_setup_identity hanging on dce 2.0a
|>    I'm on Unix 4.0b and dce 2.0a.

|>    The call, sec_login_setup_identity, is hanging.  I've checked
|>    the input args to the call and there fine. This same code performs
|>    correctly on Unix 3.2g and DCE 1.3b ECO1.  After hanging on the 
|>    this call for about a half hour in the debugger, I did a control-C

	Hi,
	   Could you please check to see if the application is being linked
	properly.  You should be specifying -threads flag instead of
	-pthread used previously in the Digital UNIX V3.x environment.
	The -threads is *required* for DCE applications to run under
	the POSIX 1003.4a Draft 4 implementation.  You may also need to
	modify the portion of the code that handles signals for the
	application process.

							- Mustie

--
Mustafizur Rahman                           E-Mail: [email protected]
Project Leader, DCE for Digital UNIX         Phone: (508) 486-5150
Digital Equipment Corporation, Littleton, MA   FAX: (508) 486-7417
[posted by Notes-News gateway]
2168.5already using -threadsCAMINO::MCDERMOTTMon Feb 24 1997 14:0315
    I'm already compiling with the -threads flag. I'm linking with
    the libraries described in the unix 4.0 version of "Guide to
    Decthreads" appendix A:
    
    "If using the cma or 1003.4a Draft 4 interfaces, you would use the
    following: 
    
    ld <...> -lpthreads -lpthread -lmach -lexc -lc"
    
    
    
    I put -ldce in front of -lpthreads.
    
    Greg