cancel
Showing results for 
Search instead for 
Did you mean: 

SNC not working after an upgrade from RHEL5 to RHEL6

former_member55246
Discoverer
0 Kudos

Need some help on how to fix a SNC after upgrading from a Red Hat Enterprise Linux 5 to 6. We copied all the file systems we had from 5. The pop up message from the sapgui is the usual "SAP System Message: S".

server ticket is good (klist)...

57> klist
Ticket cache: FILE:/tmp/krb5cc_276
Default principal: host/xxxxx

Valid starting          Expires                   Service principal
04/26/13 09:56:43  04/26/13 19:56:44  krbtgt/xxxxx

From the work logs...

(SNC is identified)

N Thu Apr 25 11:39:23 2013

N  SncInit(): Initializing Secure Network Communication (SNC)

N        AMD/Intel x86_64 with Linux (st,ascii,SAP_UC/size_t/void* = 16/64/64)

N  SncInit():   found snc/data_protection/max=3, using 3 (Privacy Level)

N  SncInit():   found snc/data_protection/min=3, using 3 (Privacy Level)

N  SncInit():   found snc/data_protection/use=3, using 3 (Privacy Level)

N  SncInit(): found  snc/gssapi_lib=/lib64/libgssapi_krb5.so.2

N

N Thu Apr 25 11:39:24 2013

N    File "/lib64/libgssapi_krb5.so.2" dynamically loaded as GSS-API v2 library.

N    The internal Adapter for the loaded GSS-API mechanism identifies as:

N    Internal SNC-Adapter (Rev 1.0) to Kerberos 5/GSS-API v2

N

N Thu Apr 25 11:39:25 2013

N  SncInit():   found snc/identity/as=s:host@sap-smp-01.oit.duke.edu

N

N Thu Apr 25 11:39:26 2013

N  SncInit(): Accepting  Credentials available, lifetime=1193046h 28m 14s

N  SncInit(): Initiating Credentials available, lifetime=09h 58m 38s

M  SNC (Secure Network Communication) enabled

On the server side, SNC is loaded and everthing looks good. However, when a client tries to connect to the system, we get this error...

(SNC error when user tries to log in)

N Fri Apr 26 10:06:59 2013

N  *** ERROR => SncPEstablishContext()==SNCERR_GSSAPI  [sncxxall.c 3357]

N        GSS-API(maj): No credentials were supplied, or the credentials were unavailable or inaccessible

N      Unable to establish the security context

N  <<- SncProcessInput()==SNCERR_GSSAPI

M  *** ERROR => ThSncIn: SncProcessInput (SNCERR_GSSAPI) [thxxsnc.c    1034]

M  {root-id=005056BB5EFA1EE2ABCF51EFF911CCFC}_{conn-id=00000000000000000000000000000000}_0

M  *** ERROR => ThSncIn: SncProcessInput [thxxsnc.c    1039]

M  {root-id=005056BB5EFA1EE2ABCF51EFF911CCFC}_{conn-id=00000000000000000000000000000000}_0

M  in_ThErrHandle: 1

M  *** ERROR => ThSncIn: SncProcessInput (step 4, th_errno 44, action 1, level 1) [thxxhead.c   11329]

M  {root-id=005056BB5EFA1EE2ABCF51EFF911CCFC}_{conn-id=00000000000000000000000000000000}_0

M  DpVmcGetVmByTmAdm: no VM found for T44/M0/I0 (locked VMs ignored)

M

Additional Info:

Kernel 720 p300

Oracle 11

We have looked around trying to figure out if we miss something. Hopefully somone else had this problem before after an upgrade and will be kind enough to share the information.

Thanks,

Fernando

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

There are others having the same problem. See the linked discussion thread. The basic problem is that you have used a unsupported method and now it doesn't work anymore. The supported method is NWSSO or a certified 3rd party solution.

http://scn.sap.com/thread/3348422