hcienginerun.pl -p $Process –> SYSTEM/OS error: -944

Clovertech Forums Cloverleaf hcienginerun.pl -p $Process –> SYSTEM/OS error: -944

  • Creator
    Topic
  • #121398
    roseg
    Participant

      Hello,

      we are experiencing issues when trying to start individual processes on a site using the hcienginerun.pl script.

      We are not running the script in the Cloverleaf environment, but all the necessary environment variables are still present.

      The script call looks as follows:
      <pre>[code]</pre>
      $Process = “g_oru”
      Start-Process -FilePath “$env:HCIROOT\bin\perl.exe” -ArgumentList “-I $env:HCIROOT\lib\perl5 -I $env:HCIROOT\bin $env:HCIROOT\bin\hcienginerun.pl -p $Process”
      <pre>[/code]</pre>
      We also receive the feedback “Process g_oru initiated,” but the process does not actually start.

      In the g_oru.log (..\healthcomm\cloverleaf\cis19.1\integrator\_global\exec\processes\g_oru\), the following error is displayed:
      <pre>[code]</pre>
      prod:prod:INFO/0: g_oru:05/16/2024 09:15:36] Started at Thu May 16 09:15:36 2024
      [prod:prod:INFO/0: g_oru:05/16/2024 09:15:36] Engine process is 2460 on host SERVERHOSTNAME
      [prod:prod:INFO/0: g_oru:05/16/2024 09:15:36] HostMsgIdentifier is 2548358706
      [dbi :dbi :ERR /0: g_oru_cmd:05/16/2024 09:15:36] (-944) ‘RDM Embedded DB error: “SYSTEM/OS error: -944
      [dbi :dbi :ERR /0: g_oru_cmd:–/–/—- –:–:–] TAF-lockmgr synchronization error
      [dbi :dbi :ERR /0: g_oru_cmd:–/–/—- –:–:–] C errno = 0: No error”
      [dbi :dbi :ERR /0: g_oru_cmd:–/–/—- –:–:–] ‘
      PANIC: “(errnum > -900) || (errnum < -976)”
      PANIC: Calling “pti” for thread g_oru_cmd
      —– Scheduler State —–
      Thread Events State Priority Runnable PT Msgs
      0 0 SCHED_IDLE 0 0 0,0,0

      ————– Thread 0 (g_oru_cmd)————–
      ti: 0x000001E27AB876B0
      tid : 0
      HostPthreadId : 0x0000000000000000
      EventList : 0x000001E27AC31A80
      PolledEvents : 0x000001E27AC31D20
      PthreadEvent : 0x000001E27C6B4FB0
      ReadyEvents : 0x000001E27AC31DA0
      CtrlMsgs : 0x000001E27AC31DC0
      UserCtrlMsgs : 0x000001E27AC320E0
      UserDataMsgs : 0x000001E27AC323A0
      StartArgs : 0x0000000000000000
      SchedState : SCHED_IDLE
      SchedPriority : 0
      Killed : 0
      —– Registered Events —–
      el: 0x000001E27AC31A80
      elCount : 2
      elHead: 0x000001E27ABD8220
      elTail: 0x000001E27C7532C0
      ele: 0x000001E27ABD8220
      event: 0x000001E27AB91400
      prev : 0x0
      next : 0x7c7532c0
      ev: 0x7ab91400
      evType : NT_EVENT
      evStrDesc : Tcl Reload Event
      evSocket : 0
      evHandle : 496
      evMsgQue : 0
      evTid : 0
      evState : 0
      evPtMsg : 0x0
      evUserData : 0x0
      evCallBack : 0x848f2350
      evCbShutdown : 0x0
      evRecurFreq : <tvNULL>
      ele: 0x000001E27C7532C0
      event: 0x000001E27C6B4FB0
      prev : 0x7abd8220
      next : 0x0
      ev: 0x7c6b4fb0
      evType : PTHREADS
      evStrDesc : PThreads Event
      evSocket : 0
      evHandle : 0
      evMsgQue : 0
      evTid : 0
      evState : 0
      evPtMsg : 0x0
      evUserData : 0x0
      evCallBack : 0x0
      evCbShutdown : 0x0
      evRecurFreq : <tvNULL>
      —– Polled Events —–
      el: 0x000001E27AC31D20
      elCount : 0
      elHead: 0x0000000000000000
      elTail: 0x0000000000000000
      —– Ready Events —–
      el: 0x000001E27AC31DA0
      elCount : 0
      elHead: 0x0000000000000000
      elTail: 0x0000000000000000
      —– Outstanding Pthread Ctrl Msgs —–
      pmq: 0x000001E27AC31DC0
      Count : 0
      Head : 0x0000000000000000
      Tail : 0x0000000000000000
      —– Outstanding Pthread User Ctrl Msgs —–
      pmq: 0x000001E27AC320E0
      Count : 0
      Head : 0x0000000000000000
      Tail : 0x0000000000000000
      —– Outstanding Pthread User Data Msgs —–
      pmq: 0x000001E27AC323A0
      Count : 0
      Head : 0x0000000000000000
      Tail : 0x0000000000000000

      PANIC: Thread panic—engine going down
      PANIC: assertion ‘(errnum > -900) || (errnum < -976)’ failed at dberr.cpp/57
      <pre>[/code]</pre>
      Unfortunately, we cannot identify the error.

      Can someone help us?

      Thanks for all replies

      Greetings

      • This topic was modified 7 months, 1 week ago by roseg. Reason: BBCodes
    Viewing 1 reply thread
    • Author
      Replies
      • #121400
        Rob Abbott
        Keymaster

          Is the lock manager running?

          Are you starting as a different user than hci (or whoever owns the files in the site/exec/databases directory?

          Try shutting down the site, remove the “rdm.taf” file, and try again.

          If this doesn’t work it’s possible you’re missing some env vars related to the database or RDM.

          Rob Abbott
          Cloverleaf Emeritus

        • #121402
          roseg
          Participant

            Hello Rob,
            thank you for the fast feedback.

            We start the engine right after we start the site daemon. I can’t say for sure whether the Lock Manager is running, where can I check?

            “Are you starting as a different user…”
            Yes, the script is executed under a different user.

            “remove the “rdm.taf”…”
            That worked straight away, but what does rdm.taf do? and would there be another way without deleting files?

            We just noticed during testing that our script to stop the monitor daemon gives the following feedback:
            “Killing hcimonitord

            The syntax of the command is incorrect.
            Unable to invoke hcicmd:

            Despite the feedback, the Monitor Deamon is stopped.
            Maybe we are doing something wrong here that will prevent the processes from starting later?

            We stop the monitor daemon with the following command:
            [code]Start-Process -FilePath “$env:HCIROOT\bin\perl.exe” -ArgumentList “-I $env:HCIROOT\lib\perl5 -I $env:HCIROOT\bin $env:HCIROOT\bin\hcisitectl.pl -k m”[/code]

            Thanks for all replies

            Greetings

        Viewing 1 reply thread
        • You must be logged in to reply to this topic.