System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

Error in logon balancing routine (rc=82, err=7);

Manuales
Super Advisor

Error in logon balancing routine (rc=82, err=7);


Hi ...
this is the issue:
- SAP was running in the system: OSF1 server3 V4.0 878 alpha
- the application was down
- a disk was changed
- the server was started
- but now SAP can not be started
- when i started the SAP processes they are started but they are down litle by litle ...

i had this issue in the past and the solution was to reset the semaphores and the shared memory and it was solved, but now these semaphores and semaphores are cleaned but the processes can not be started .... well, they are started for about 2 minutes but after these 2 minutes they are down by themselve ...

when i logon to SAP from GUI there is a problem:
Error in logon balancing routine (rc=82, err=7);
Logon group 'XXXXXX' not found - check spelling and case sensitivity

i go to unix system and the processes are not running .... it sems sap processes are killed
the question is: why the processes are being killed?
who is killing the processes ..


if i go to a the log:

bisap3:bp1adm 30> cat dev_disp



---------------------------------------------------

trc file: "dev_disp", trc level: 1, release: "31I"

---------------------------------------------------



Tue Dec 9 12:56:30 2008

***LOG Q00=> DpSapEnvInit, DPStart (00 8004) [dpxxdisp 0795]



relno 31I

patchlevel 710

compiled on OSF1 V4.0 878 alpha

compiled at Apr 12 2003 05:49:28

pid 8004



Profile configuration error detected, use temporary corrected setup

Shared Pool 10: ipc/shm_psize_10 = 4000000 (too small)

Shared Pool 10: (smaller than default 12000000)

Shared Pool 10: (default size assumed 12000000)

MBUF state OFF

MBUF opmode USE

client 0 initializing ....

InitFreeList

block size is 1024 kByte.

EsIUnamFileMapInit: ES base = 0x4800000

EsIOsInit: Extended Memory 1024 MB allocated

1023 blocks reserved for free list.

ES initialized.



Tue Dec 9 12:56:31 2008

***LOG Q0K=> DpMsAttach, mscon ( bisap3) [dpxxdisp 6637]

MBUF set hwid_state to HWID_PENDING

MBUF state PREPARED

MBUF component UP

MBUF set hwid_state to SAP_O_K (S1353317685 )



Tue Dec 9 12:57:11 2008

*** ERROR => W0 (pid 8009) died [dpxxdisp 8564]

*** ERROR => W2 (pid 8013) died [dpxxdisp 8564]



Tue Dec 9 12:57:31 2008

*** ERROR => W1 (pid 8010) died [dpxxdisp 8564]

*** ERROR => W12 (pid 8029) died [dpxxdisp 8564]



Tue Dec 9 12:57:51 2008

*** ERROR => W14 (pid 8035) died [dpxxdisp 8564]



Tue Dec 9 12:58:11 2008

*** ERROR => W17 (pid 8042) died [dpxxdisp 8564]

my types changed after wp death/restart 0x3f --> 0x1f



Tue Dec 9 12:58:31 2008

*** ERROR => W3 (pid 8014) died [dpxxdisp 8564]

*** ERROR => W4 (pid 8017) died [dpxxdisp 8564]

my types changed after wp death/restart 0x1f --> 0x1e



Tue Dec 9 12:58:51 2008

*** ERROR => W5 (pid 8018) died [dpxxdisp 8564]



Tue Dec 9 12:59:11 2008

*** ERROR => W7 (pid 8022) died [dpxxdisp 8564]

*** ERROR => W8 (pid 8023) died [dpxxdisp 8564]

bisap3:bp1adm 31>

========================================================================
bisap3:bp1adm 68> cat stderr2

(6160) New Child Process created.

(6160) Starting local Command:

Command: dw.sapBP1_DVEBMGS00

pf=/usr/sap/BP1/SYS/profile/BP1_DVEBMGS00

*** WARNING => pfclock may be badly adjusted (109362)

*** WARNING => pfclock may be badly adjusted (244)



***

*** work process W0 died => tskh_init: ThIPCInit

*** WARNING => pfclock may be badly adjusted (284840)



***

*** work process W2 died => tskh_init: ThIPCInit

*** WARNING => pfclock may be badly adjusted (109081)



***

*** work process W5 died => tskh_init: ThIPCInit

*** WARNING => pfclock may be badly adjusted (109087)



***

*** work process W6 died => tskh_init: ThIPCInit

*** WARNING => pfclock may be badly adjusted (109070)



***

*** work process W9 died => tskh_init: ThIPCInit

*** WARNING => pfclock may be badly adjusted (284841)



***

*** work process W10 died => tskh_init: ThIPCInit

*** WARNING => pfclock may be badly adjusted (248)



***

*** work process W11 died => tskh_init: ThIPCInit

*** WARNING => pfclock may be badly adjusted (109618)



***

*** work process W1 died => tskh_init: ThIPCInit

*** WARNING => pfclock may be badly adjusted (89)



***

*** work process W3 died => tskh_init: ThIPCInit

*** WARNING => pfclock may be badly adjusted (109085)



***

*** work process W4 died => tskh_init: ThIPCInit




Any idea why system do this?
1 REPLY
Hein van den Heuvel
Honored Contributor

Re: Error in logon balancing routine (rc=82, err=7);

I see you X posted in an SAP forum.
Good, because I think pfclock is an SAP kernel module, not a Tru64 thing.


https://forums.sdn.sap.com/click.jspa?searchID=19730435&messageID=6683697

I don't see an SAP kernel version/patch version?

I suspect that the stop/restart made the system pick up a new setting, possibly not related to the new disk.

I'd check stuff like /etc/services, /etc/hosts, DNS settings.
It the sap message switch available?


You show dev_disp, from the dispatch process.
That is more or less the driver.
It observes it chidren are dying.
Maybe the child logs for the worker processes like dev_w0 have more data?

And since the word 'clock' is in there, I suppose you want to check timezones and daylight saving effects?
Is this a 1-node setup, or several?

The database came back up nicely?

What was on the replaced disk?
OS stuff? SAp directories? DB files?


Good luck,
Hein.