PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 04/23/2017 9:06 AM by  Aamir
killing looping lacobrts processes in LSF9 help
 13 Replies
Sort:
You are not authorized to post a reply.
Author Messages
FrankH
Lawson Admin
Mcgraw-Hill
Basic Member
(15 points)
Basic Member
Posts:7


Send Message:

--
07/12/2010 2:22 PM
    All-
    We were about to go live on LSF9 when we came across this problem that hung users in HR11. This is in the latm.log..
    latm (RmExecTPPrc): WARNING: Looping program detected, HRUAT, HR11
    Mon Jul 12 11:05:42 2010: latm (RmExecTPPrc): Killing looping lacobrts process, Pid=24482
    Mon Jul 12 11:05:42 2010: Terminating process, 24482

    After about 6 hours on the system users in portal or lid would hang and get the above msg. We have had vendors and Lawson troubleshooting this and can not get it resolved. It is keeping us from going live.

    TIA
    Frank H
    subba
    Private
    Private
    New Member
    (7 points)
    New Member
    Posts:3


    Send Message:

    --
    07/13/2010 12:05 PM
    Frank,
    I feel it is due to LSF9.0 security issue .See same eror you getting with Security turn off or turn security debug flag on and see which security rule causing this.

    Thanks,
    Subba
    Jimmy Chiu
    System Analyst
    Federal Government
    Veteran Member
    (1858 points)
    Veteran Member
    Posts:632


    Send Message:

    --
    07/13/2010 12:48 PM
    I would do this and see if it will help just temporarily.

    Edit your %lawdir%\system\latm.cfg

    OPENTIMEOUT 600
    LOOPTIMEOUT 30

    A reboot is required after the changes. Then wait and see if it will pop the errors.
    Tony Conway
    Private
    Private
    Basic Member
    (27 points)
    Basic Member
    Posts:9


    Send Message:

    --
    07/14/2010 2:18 AM

    Posted By Jimmy Chiu on 07/13/2010 12:48 PM
    I would do this and see if it will help just temporarily.

    Edit your %lawdir%\system\latm.cfg

    OPENTIMEOUT 600
    LOOPTIMEOUT 30

    A reboot is required after the changes. Then wait and see if it will pop the errors.


    If I'm not mistaken, a reboot is not required. tmcontrol -rc should reinitialise those settings.
    Tony Conway
    Private
    Private
    Basic Member
    (27 points)
    Basic Member
    Posts:9


    Send Message:

    --
    07/14/2010 2:25 AM

    Posted By Jimmy Chiu on 07/13/2010 12:48 PM
    I would do this and see if it will help just temporarily.

    Edit your %lawdir%\system\latm.cfg

    OPENTIMEOUT 600
    LOOPTIMEOUT 30

    A reboot is required after the changes. Then wait and see if it will pop the errors.


    If I'm not mistaken, a reboot is not required. tmcontrol -rc should reinitialise those settings.
    FrankH
    Lawson Admin
    Mcgraw-Hill
    Basic Member
    (15 points)
    Basic Member
    Posts:7


    Send Message:

    --
    07/14/2010 9:59 AM
    We tried changing OPENTIMEOUT and LOOPTIMEOUT and this didn't solve the problem. We applied 2 JT's and the "killing looping lacobrts" message went away, but we now have a new error....see below. The users get on and test and it took 24hrs to get it to fail and get this new message. Any ideas?

    TIA
    Frank
    INFORMATION FROM THE LATM.LOG

    Program Code = PR05 , DataArea/DataID = HRPROD
    Tue Jul 13 15:20:25 2010: ERROR: Stopped due to a signal 9
    Tue Jul 13 15:20:25 2010: SIGNAL: Kill

    Wed Jul 14 09:12:07 2010: latm (PrcTPCrash): Received death notification of lacobrts, Uid=14, Pid=9943
    Wed Jul 14 09:12:07 2010: Program Code = HR11 , DataArea/DataID = HRPROD
    Wed Jul 14 09:12:07 2010: ERROR: Stopped due to a signal 13
    Wed Jul 14 09:12:07 2010: SIGNAL: Write on a pipe with no one to read it

    lacobrts timed out waiting for OPEN message
    lacobrts timed out waiting for OPEN message
    lacobrts timed out waiting for OPEN message
    FrankH
    Lawson Admin
    Mcgraw-Hill
    Basic Member
    (15 points)
    Basic Member
    Posts:7


    Send Message:

    --
    07/14/2010 10:00 AM
    We tried turning off security and still get the errors.
    jknox
    Private
    Private
    Basic Member
    (13 points)
    Basic Member
    Posts:5


    Send Message:

    --
    02/18/2011 12:41 PM
    Posted By FrankH on 07/14/2010 09:59 AM
    We tried changing OPENTIMEOUT and LOOPTIMEOUT and this didn't solve the problem. We applied 2 JT's and the "killing looping lacobrts" message went away, but we now have a new error....see below. The users get on and test and it took 24hrs to get it to fail and get this new message. Any ideas?

    TIA
    Frank
    INFORMATION FROM THE LATM.LOG

    Program Code = PR05 , DataArea/DataID = HRPROD
    Tue Jul 13 15:20:25 2010: ERROR: Stopped due to a signal 9
    Tue Jul 13 15:20:25 2010: SIGNAL: Kill

    Wed Jul 14 09:12:07 2010: latm (PrcTPCrash): Received death notification of lacobrts, Uid=14, Pid=9943
    Wed Jul 14 09:12:07 2010: Program Code = HR11 , DataArea/DataID = HRPROD
    Wed Jul 14 09:12:07 2010: ERROR: Stopped due to a signal 13
    Wed Jul 14 09:12:07 2010: SIGNAL: Write on a pipe with no one to read it

    lacobrts timed out waiting for OPEN message
    lacobrts timed out waiting for OPEN message
    lacobrts timed out waiting for OPEN message

    What JTs did you apply?  We are seeing this same error in out latm log.
    John Cunningham
    Private
    Private
    Advanced Member
    (73 points)
    Advanced Member
    Posts:31


    Send Message:

    --
    02/22/2011 1:11 PM
    What version of Lawson are you on?  Are you on AIX or Windows?  Does it only happen in HR11?
    Matt Sherwood
    Private
    Private
    Basic Member
    (35 points)
    Basic Member
    Posts:13


    Send Message:

    --
    02/22/2011 1:25 PM
    Did Lawson have you trace the program? compile HR11

    qcompile -T prod hr hr11

    compile invokes

    lstinvk -qT prod hr11

    When the program times out the trace will be within the lacobrts log.

    Usually I would set the looptimeout to 60 seconds so you don't have to sit there and wait.

    I'm guessing Lawson has already taken you through this process, but wanted to throw it out there if they have not.

    Srini Rao
    Private
    Private
    Veteran Member
    (287 points)
    Veteran Member
    Posts:133


    Send Message:

    --
    06/02/2011 6:43 PM
    We are planning to upgrade to MSP5 and ESP7 , did Lawson addressed this issue?
    shaurav
    analyst
    ccf
    New Member
    (3 points)
    New Member
    Posts:1


    Send Message:

    --
    02/07/2012 8:40 PM
    Anyone have any updates on this issue? We are getting this issue about once a week mostly on HR11 and PA52
    brooke
    Private
    Private
    (49 points)
    Posts:21


    Send Message:

    --
    11/18/2015 8:47 AM
    We are having a similar issue with an upload to LP31 - only in test but it is preventing us from moving forward with this user on Lawson security - when we get this error lawson security hangs hangs the entire system - it kills lacobrts - we have to manually kill every process to restart - did you get a solution?
    Aamir
    IT Analyst
    Private
    New Member
    (3 points)
    New Member
    Posts:1


    Send Message:

    --
    04/23/2017 9:06 AM
    Can anyone please help me on how to enable and disable the security flag? I am using Lawson Insight Desktop(LID) version 7.3.3.0.
    One of my customize screen starts clocking if I update my stuff through it.
    The problem and logs are just similar to the one that has been sent/pasted in the original query.
    Appreciate your response!
    You are not authorized to post a reply.