Highlighted
Acclaimed Contributor.
Acclaimed Contributor.
830 views

For some reason the scheduler stops working

Jump to solution

There is a schedule named hpclinker4.

I found that sometimes buisness logic stop working. And i see that there is no schedule - hpclinker4

Log about this event (after that this schedule stay in not work state and i have to startit again):

Spoiler
Spoiler

1664( 3464) 01/10/2017 10:55:24 RTE I -Memory : S(1650589362) O(2900428) MAX(1653489790) - MALLOC's Total(97928469)
1664( 3464) 01/10/2017 10:55:26 RTE I [Address ] Symbol(Parm1,Parm2,Parm3,Parm4) +Offset Source module
1664( 3464) 01/10/2017 10:55:26 RTE I 1: [74E3AE7A] memcpy(0x8BAF0058,0x0,0x61FCD090,0x2684AD00) +0x5A C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll-
1664( 3464) 01/10/2017 10:55:26 RTE I 2: [61E85B63] stcopyEx(0x26AD7BC0,0x2C8F4190,0x2684AD00,0x2C8F4188) +0x93 C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\SM.dll-string.cpp-1142
1664( 3464) 01/10/2017 10:55:26 RTE I 3: [61DA1775] dacopyEx(0x26AD7BB8,0x2C8F4188,0x2684AD00,0x314E22C8) +0x285 C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\SM.dll-da.cpp-564
1664( 3464) 01/10/2017 10:55:26 RTE I 4: [61E1E8FD] rcwrt1(0x2689C0C0,0x31431E18,0x2C8F4188,0x314E2260) +0x4D C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\SM.dll-rcche.cpp-878
1664( 3464) 01/10/2017 10:55:26 RTE I 5: [61DADC4E] _getIRText(0x314E2260,0x314E22C8,0x314E23F8,0x2684AD00) +0x11E C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\SM.dll-dbi.cpp-8939
1664( 3464) 01/10/2017 10:55:26 RTE I 6: [61DAFD3E] _getKey(0x33652860,0x2786EBF0,0x2786EB48,0x2786EB8C) +0x10E C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\SM.dll-dbi.cpp-8413
1664( 3464) 01/10/2017 10:55:26 RTE I 7: [61DB134C] _dbOpenCursor(0x314E2260,0x33652860,0x0,0x2686E9B0) +0x25C C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\SM.dll-dbi.cpp-3333
1664( 3464) 01/10/2017 10:55:26 RTE I 8: [61DB2CDB] dbOpenCursorEx(0x314E2260,0x33652860,0x2686E8F0,0x620064D0) +0x2B C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\SM.dll-dbi.cpp-3209
1664( 3464) 01/10/2017 10:55:26 RTE I 9: [61E1556F] _pdbOpenCursor(0xFFFFFFFF,0x2686E8F0,0x620064D0,0x2686E9B0) +0xEF C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\SM.dll-pdb.cpp-1017
1664( 3464) 01/10/2017 10:55:26 RTE I 10: [61E1583C] pdbOpenCursorEx(0x1A79F2E0,0x33652860,0x2686E8F0,0x620064D0) +0x2C C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\SM.dll-pdb.cpp-913
1664( 3464) 01/10/2017 10:55:26 RTE I 11: [61EF6AF9] evslcVar(0x1A79F2E0,0x2686E8D8,0x2686E8F0,0x620064D0) +0x119 C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\SM.dll-evselect.cpp-95
1664( 3464) 01/10/2017 10:55:26 RTE I 12: [61EF6DAE] _doSelect(0x0,0x32,0x2684AD00,0xA) +0x29E C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\SM.dll-evselect.cpp-321
1664( 3464) 01/10/2017 10:55:26 RTE I 13: [61EF6DF6] evslc(0x2686E800,0x2786ED74,0x2684AD00,0x2686E890) +0x36 C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\SM.dll-evselect.cpp-171
1664( 3464) 01/10/2017 10:55:26 RTE I 14: [61EDFE8E] _evalOperator(0x2686E890,0x1,0x2685CE70,0x33338980) +0x16E C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\SM.dll-eval1.cpp-93
1664( 3464) 01/10/2017 10:55:26 RTE I 15: [61EE016B] eval1(0x2686E890,0x0,0x2684AD00,0x2686E110) +0x17B C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\SM.dll-eval1.cpp-232
1664( 3464) 01/10/2017 10:55:26 RTE I 16: [61EDF65A] eval(0x80322AFC,0x0,0x0,0x0) +0x33A C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\SM.dll-eval.cpp-86
1664( 3464) 01/10/2017 10:55:26 RTE I 17: [61EE161C] CallRAD(0x2C35BFA0,0x2C35CB10,0x2C35C750,0x0) +0x57C C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\SM.dll-evcll.cpp-486
1664( 3464) 01/10/2017 10:55:26 RTE I 18: [61D909E3] CDocEngine::startApplication(0x61F833D0,0x2C35CB10,0x2C35C750,0x0) +0xC3 C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\SM.dll-cdoceng.cpp-64
1664( 3464) 01/10/2017 10:55:26 RTE I 19: [61D9119A] CDocEngine::docEngine(0x3148F050,0x3148E6C0,0x26F62540,0x0) +0x13A C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\SM.dll-cdoceng.cpp-407
1664( 3464) 01/10/2017 10:55:27 RTE I 20: [61F1F9D8] datum_Method(0x254B28B0,0x25AF51B0,0x1,0x323410A4) +0xD8 C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\SM.dll-js.cpp-3005
1664( 3464) 01/10/2017 10:55:27 RTE I 21: [61B70081] js_Invoke(0x254B28B0,0x1,0x0,0x0) +0x631 C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\js_1.5rc6a.dll-jsinterp.c-947
1664( 3464) 01/10/2017 10:55:27 RTE I 22: [61B76444] js_Interpret(0x254B28B0,0x2786F1D0,0x2786F278,0x0) +0x5EF4 C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\js_1.5rc6a.dll-jsinterp.c-2979
1664( 3464) 01/10/2017 10:55:27 RTE I 23: [61B700C7] js_Invoke(0x254B28B0,0x0,0x2,0x26987B20) +0x677 C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\js_1.5rc6a.dll-jsinterp.c-964
1664( 3464) 01/10/2017 10:55:27 RTE I 24: [61B70243] js_InternalInvoke(0x0,0x25892B48,0x25AF3F18,0x0) +0xA3 C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\js_1.5rc6a.dll-jsinterp.c-1041
1664( 3464) 01/10/2017 10:55:27 RTE I 25: [61B53839] JS_CallFunction(0x254B28B0,0x25892B48,0x2D89FD98,0x0) +0x29 C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\js_1.5rc6a.dll-jsapi.c-3573
1664( 3464) 01/10/2017 10:55:27 RTE I 26: [61F2AC84] CJsCallable::RawInvoke(0x25892B48,0x0,0x0,0x2786F388) +0x154 C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\SM.dll-js.cpp-6674
1664( 3464) 01/10/2017 10:55:27 RTE I 27: [61F301DC] CJsCallable::Eval(0x2686E0D0,0x2684AE4C,0x2686E0D0,0x1) +0x2C C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\SM.dll-js.cpp-9515
1664( 3464) 01/10/2017 10:55:27 RTE I 28: [61F35F49] CScriptObject::Eval(0x2686E0D0,0xED,0x20,0x2684AD00) +0x129 C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\SM.dll-js.cpp-9709
1664( 3464) 01/10/2017 10:55:27 RTE I 29: [61EE7D0F] evjs(0x26B7A810,0x2686E0B0,0x2684AD00,0x2686E0D0) +0x10F C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\SM.dll-evjs.cpp-81
1664( 3464) 01/10/2017 10:55:27 RTE I 30: [61EDFE8E] _evalOperator(0x2686E0D0,0x1,0x2685CE70,0x2685CE70) +0x16E C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\SM.dll-eval1.cpp-93
1664( 3464) 01/10/2017 10:55:27 RTE I 31: [61EE016B] eval1(0x2686E0D0,0x0,0x2684AD00,0x2A) +0x17B C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\SM.dll-eval1.cpp-232
1664( 3464) 01/10/2017 10:55:27 RTE I 32: [61EECED1] evprc(0x80278510,0x2786F54C,0x2684AD00,0x2686E0B0) +0xE1 C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\SM.dll-evprocess.cpp-93
1664( 3464) 01/10/2017 10:55:27 RTE I 33: [61EDFE8E] _evalOperator(0x2686E0B0,0x1,0x2685CE70,0x26A074C0) +0x16E C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\SM.dll-eval1.cpp-93
1664( 3464) 01/10/2017 10:55:27 RTE I 34: [61EE016B] eval1(0x2686E0B0,0x0,0x2684AD00,0x19EC4400) +0x17B C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\SM.dll-eval1.cpp-232
1664( 3464) 01/10/2017 10:55:27 RTE I 35: [61EDF65A] eval(0x800F9484,0x0,0x0,0x15ACF6C0) +0x33A C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\SM.dll-eval.cpp-86
1664( 3464) 01/10/2017 10:55:27 RTE I 36: [61E87448] symanContinue(0x2786F844,0x19EC4400,0x15ACF6C0,0x15ACF6C8) +0x308 C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\SM.dll-syman.cpp-563
1664( 3464) 01/10/2017 10:55:27 RTE I 37: [61DDE54E] Java_com_hp_ov_sm_server_utility_GenericServerThread_symanContinue(0x19EC4510,0x2786F920,0x2786F91C,0x3359F47) +0x5E C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\SM.dll-genericserverthread.cpp-87
1664( 3464) 01/10/2017 10:55:27 RTE I 38: [03359F47] <not found>(0x0,0x1F80,0x0,0x3350266)
1664( 3464) 01/10/2017 10:55:27 RTE I 39: [6D99FD44] AsyncGetCallTrace(0x2786F9B4,0x2786FB70,0xA,0x15ACF4A8) +0x41354 C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\jre\bin\client\jvm.dll-
1664( 3464) 01/10/2017 10:55:27 RTE I 40: [6D9A049C] AsyncGetCallTrace(0x2786FB68,0x86FA94,0x2786FA98,0x3359210) +0x41AAC C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\jre\bin\client\jvm.dll-
1664( 3464) 01/10/2017 10:55:27 RTE I 41: [6DA2FCF1] JVM_FindSignal(0x6D9A0340,0x2786FB68,0x2786FA94,0x2786FA98) +0x5A891 C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\jre\bin\client\jvm.dll-
1664( 3464) 01/10/2017 10:55:27 RTE I 42: [6D9A0667] AsyncGetCallTrace(0x2786FB68,0x19AECF9C,0x6DB1F1B0,0x6DB1F47C) +0x41C77 C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\jre\bin\client\jvm.dll-
1664( 3464) 01/10/2017 10:55:27 RTE I 43: [6D9A06DD] AsyncGetCallTrace(0x2786FB68,0x19AECF98,0x19AECF9C,0x6DB1F1B0) +0x41CED C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\jre\bin\client\jvm.dll-
1664( 3464) 01/10/2017 10:55:27 RTE I 44: [6D9CA2A0] jio_fprintf(0x19EC4400,0x19EC4400,0x19EC4400,0x19EC4400) +0x140 C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\jre\bin\client\jvm.dll-
1664( 3464) 01/10/2017 10:55:27 RTE I 45: [6DA8DB14] JVM_FindSignal(0x2786FC84,0x2786FC08,0x1,0x1) +0xB86B4 C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\jre\bin\client\jvm.dll-
1664( 3464) 01/10/2017 10:55:27 RTE I 46: [6DA2F96C] JVM_FindSignal(0x19EC4400,0x0,0x0,0x19DA8340) +0x5A50C C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\jre\bin\client\jvm.dll-
1664( 3464) 01/10/2017 10:55:27 RTE I 47: [7C349565] endthreadex(0x19DA8340,0x2786FFD4,0x778C9902,0x19DA8340) +0xA0 C:\Program Files (x86)\HP\Service Manager 9.30\Server\RUN\MSVCR71.dll-
1664( 3464) 01/10/2017 10:55:27 RTE I 48: [7559336A] BaseThreadInitThunk(0x19DA8340,0x501FB413,0x0,0x0) +0x12 C:\Windows\syswow64\kernel32.dll-
1664( 3464) 01/10/2017 10:55:27 RTE I 49: [778C9902] RtlInitializeExceptionChain(0x7C3494F6,0x19DA8340,0xFFFFFFFF,0x779575CC) +0x63 C:\Windows\SysWOW64\ntdll.dll-
1664( 3464) 01/10/2017 10:55:27 RTE I 50: [778C98D5] RtlInitializeExceptionChain(0x7C3494F6,0x19DA8340,0x0,0x34C90000) +0x36 C:\Windows\SysWOW64\ntdll.dll-
1664( 3464) 01/10/2017 10:55:27 RTE I !!! Core Generation is disabled. Ignoring Generate Core Dump Request.
1664( 3464) 01/10/2017 10:55:27 RTE E Caught SCFramework::SCEHException: Win32 Exception: 0xC0000005 (instruction 0x74E3AE7A while reading address 0x00000000)
1664( 3464) 01/10/2017 10:55:27 JRTE I thread: hpclinker4_thread_19 id: 3464 has terminated!
1664( 3464) 01/10/2017 10:55:27 RTE I -Memory : S(1650587818) O(2901972) MAX(1653489790) - MALLOC's Total(97928469)
1664( 3464) 01/10/2017 10:55:27 RTE I ===> Signal 11: User=hpclinker4, Application=sc.get.sla, Panel=select.dept.nme
1664( 3464) 01/10/2017 10:55:27 RTE I RAD thread id 0, last option key 0
1664( 3464) 01/10/2017 10:55:27 RTE I Application trace
1664( 3464) 01/10/2017 10:55:27 RTE I sc.get.sla select.dept.nme
1664( 3464) 01/10/2017 10:55:27 RTE I se.call.process call.rad.1
1664( 3464) 01/10/2017 10:55:27 RTE I se.view.engine call.process
1664( 3464) 01/10/2017 10:55:27 RTE I se.external.action call.engine.1
1664( 3464) 01/10/2017 10:55:27 RTE I ioevents.process.action process.action
1664( 3464) 01/10/2017 10:55:27 RTE I ioevents.process.action process.action line:1
1664( 3464) 01/10/2017 10:55:27 RTE I ioevents.process process.action
1664( 3464) 01/10/2017 10:55:27 RTE I scheduler.process call.app
1664( 3464) 01/10/2017 10:55:27 RTE I scheduler process.class
1664( 3464) 01/10/2017 10:55:27 RTE I Application trace end
1664( 3464) 01/10/2017 10:55:27 RTE I Parameters passed on the command line:
1664( 3464) 01/10/2017 10:55:27 RTE I bg
1664( 3464) 01/10/2017 10:55:27 RTE I Parameters passed from the ini file:
1664( 3464) 01/10/2017 10:55:27 RTE I shared_memory:196000000
1664( 3464) 01/10/2017 10:55:27 RTE I log:../logs/sm.log
1664( 3464) 01/10/2017 10:55:27 RTE I sslConnector:0
1664( 3464) 01/10/2017 10:55:27 RTE I [sqlserver]
1664( 3464) 01/10/2017 10:55:27 RTE I sqldb:sm93
1664( 3464) 01/10/2017 10:55:27 RTE I sqllogin - Value not displayed
1664( 3464) 01/10/2017 10:55:27 RTE I plugin0:kmplugin.dll
1664( 3464) 01/10/2017 10:55:27 RTE I sqldictionary:sqlserver
1664( 3464) 01/10/2017 10:55:27 RTE I threadsperprocess:40
1664( 3464) 01/10/2017 10:55:27 RTE I sessiontimeout:3
1664( 3464) 01/10/2017 10:55:27 RTE I ir_asynchronous:1
1664( 3464) 01/10/2017 10:55:27 RTE I [SSO]
1664( 3464) 01/10/2017 10:55:27 RTE I keystoreFile:server.keystore
1664( 3464) 01/10/2017 10:55:27 RTE I keystorePass - Value not displayed
1664( 3464) 01/10/2017 10:55:27 RTE I ssl_trustedClientsJKS:trustedclients.keystore
1664( 3464) 01/10/2017 10:55:27 RTE I ssl_trustedClientsPwd - Value not displayed
1664( 3464) 01/10/2017 10:55:27 RTE I truststoreFile:cacerts
1664( 3464) 01/10/2017 10:55:27 RTE I truststorePass - Value not displayed
1664( 3464) 01/10/2017 10:55:27 RTE I [URL]
1664( 3464) 01/10/2017 10:55:27 RTE I querysecurity:0
1664( 3464) 01/10/2017 10:55:27 RTE I httpPort:13080
1664( 3464) 01/10/2017 10:55:27 RTE I ir_languagefiles_path:..\irlang
1664( 3464) 01/10/2017 10:55:27 RTE I End of parameters
1664( 3464) 01/10/2017 10:55:27 RTE W Detected locked resource ( probsummary;IM000169169 ). Lock will be released.
1664( 3464) 01/10/2017 10:55:27 RTE W Detected locked resource ( SCHEDULE926586614 ). Lock will be released.
1664( 3464) 01/10/2017 10:55:27 RTE W Detected locked resource ( agent:hpclinker4 ). Lock will be released.
1664( 3464) 01/10/2017 10:55:27 RTE I Thread termination cleanup complete
0 Likes
1 Solution

Accepted Solutions
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: For some reason the scheduler stops working

Jump to solution

They will restart any of the schedulers listed in the info.startup record.

View solution in original post

9 Replies
Highlighted
Acclaimed Contributor.. Acclaimed Contributor..
Acclaimed Contributor..

Re: For some reason the scheduler stops working

Jump to solution

Well, the long string of what looks like garbage is a memory dump I think, but the part that gives a clue is the line:

signal 11: User=hpclinker4, Application=sc.get.sla, Panel=select.dept.nme

The select.dept.nme panel in the sc.get.sla RAD application just performs a search of the department table based on the data passed in.  I'm not sure what you have that schedule process doing (I'm not familiar with any OOB schedulers by that name) but if it's using the data in an IM ticket (listed in your error message) and trying to do something to it, then there's some piece of data in that IM ticket that isn't what your background process expects, and it generates the singal 11, which terminates the process.

You can have the system automatically restart this process if you add it to the startup schedulers that anubis runs.

Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: For some reason the scheduler stops working

Jump to solution

Hello.

Can you explain more detail how can i do that (step by step).

As i can see there is scheduler "anubis", but there is no such record in "info" table (looks like this named - agent record)

unfortunately the help file is extremely useless

0 Likes
Highlighted
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: For some reason the scheduler stops working

Jump to solution

Does it work for SM 9.3x ?

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: For some reason the scheduler stops working

Jump to solution
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: For some reason the scheduler stops working

Jump to solution

Yes, that's what i talking about - this help is useless.

Let's see:

Create an anubis agent record

To create an anubis agent record:

  1. Type the following command into the HPE Service Manager command line, and press Enter:

    info

     The info.startup.g form opens.

  2. Type or select the anubis agent record information.
  3. Click Add.
    Service Manager adds the Information record.

===============

about 2. - where exactly I have to write (or even select) anubis agent record  information

If just in TYPE field need to type word - anubis and then Add. Is this enough - create such record only with type=anubis and empty all other fields ?

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: For some reason the scheduler stops working

Jump to solution

I remember just winging it.  Mirror it off the problem or alert info record.

Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: For some reason the scheduler stops working

Jump to solution

Ok.

 

What exactly schedulers or agents will anubis restart ?

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: For some reason the scheduler stops working

Jump to solution

They will restart any of the schedulers listed in the info.startup record.

View solution in original post

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.