Linux VS AIX. Panic Can open Smat.

Clovertech Forums Cloverleaf Linux VS AIX. Panic Can open Smat.

  • Creator
    Topic
  • #118977
    John Hamilton
    Participant

      Ok I have to convert from AIX to Linux.
      The problem is that occasionally  when starting the process it panics with can’t open the Smat file.   Has anyone else had this problem ?

      Running
      Cloverleaf 20.1.1.
      RedHat Kernel Release:
      Linux 4.18.0-305.3.1.el8_4.x86_64 x86_64

      The only way to get it started is to do the whole shutdown region cleanup with removing the MonitorShememory, rdm.taf and database cleanup.
      Anyone else having this problem>
      I have set tall the file limits to match or exceed what I had on AIX.

      I am able to open the smat files in the GUI so they are there and have data.

      Snip of the error.

      [pd :open:ERR /0: Ghh:06/18/2021 09:41:31] Unable to open sqlite db Gh
      h.out
      [pd :open:ERR /0: Ghh:06/18/2021 09:41:31] Internal Init failed for SM
      AT Ghh.out
      [pd :open:ERR /0: Ghh:06/18/2021 09:41:31] Initializing secondary for
      Ghh.out when not present
      [pd :wrte:ERR /0: Ghh:06/18/2021 09:41:31] Error 2 while opening FS Te
      st file for Ghh.out SMAT
      [pd :open:ERR /0: Ghh:06/18/2021 09:41:31] Unable to open sqlite db Gh
      h.out
      [pd :open:ERR /0: Ghh:06/18/2021 09:41:31] Internal Init failed for SM
      AT Ghh.out
      [pd :open:ERR /0: Ghh:06/18/2021 09:41:31] Init on secondary failed fo
      r SMAT Ghh.out
      [pd :open:ERR /0: Ghh:06/18/2021 09:41:31] Error in saving outbound SM
      AT messages in ‘Ghh.out’
      PANIC: “smat != __null”
      PANIC: Calling “pti” for thread 912704_cmd
      —– Scheduler State —–
      Thread Events State Priority Runnable PT Msgs
      0 0 SCHED_IDLE 0 0 0,0,0

    Viewing 2 reply threads
    • Author
      Replies
      • #118978
        David Barr
        Participant

          Have you tried running lsof to see if there’s a process accessing the file? Are there lock files that need to be removed?

        • #118980
          John Hamilton
          Participant

            Not yet as it is working right now.  I will when it fails again.

          • #119085
            gdksc
            Participant

              Started looking at this with John (OP).  Noticed that the “current working directory” for a similar error showed up as “/proc”, which is incorrect.  The smatdb files are not in /proc,. should never be in /proc.  Hence the “errno 2” of file not found, etc.

              Any indications why one of these would try to startup with “current working directory” as /proc?

          Viewing 2 reply threads
          • You must be logged in to reply to this topic.