Menu

#3311 imm: PBE logging inconsistent

5.22.06
fixed
None
enhancement
imm
-
major
False
2022-06-02
2022-03-15
No

There are some logging in syslog for PBE but they are inconsistent. It's not easy for troubleshooting.
E.g,
- LOG_WA("Persistent back-end process has apparently died.");
- LOG_NO( "Persistent Back-End capability configured, Pbe file:%s (suffix may get added)",
immnd_cb->mPbeFile);
- LOG_NO("Persistent Back End OI attached, pid: %u", pbe_pid);
- LOG_ER("IMM RELOAD with NO persistent back end => ensure cluster restart by IMMD exit at both SCs, exiting");
.etc,

Should make they consistent.

Related

Tickets: #3311
Wiki: ChangeLog-5.22.06
Wiki: NEWS-5.22.06

Discussion

  • Vu Minh Hoang

    Vu Minh Hoang - 2022-03-15
    • assigned_to: Vu Minh Hoang
     
  • Vu Minh Hoang

    Vu Minh Hoang - 2022-04-28
    • status: unassigned --> fixed
     
  • Vu Minh Hoang

    Vu Minh Hoang - 2022-04-28

    imm: fix PBE logging inconsistent [#3311]

    There are some logging syslog for PBE but they are inconsistent make it hard to troubleshooting
    E.g,
    - LOG_ER("IMM RELOAD with NO persistent back end => ensure cluster restart by IMMD exit at both SCs, exiting");
    - TRACE_5("ERR_TRY_AGAIN: Persistent back end is down");
    - TRACE("Persistent Back-End OI %s is attaching",...);
    Solution is to make all of them to Persistent Back End.

     

    Related

    Tickets: #3311


    Last edit: Vu Minh Hoang 2022-04-28
  • Gary Lee

    Gary Lee - 2022-06-01
    • Component: imm --> unknown
     
  • Gary Lee

    Gary Lee - 2022-06-01
    • Component: unknown --> fm
     
  • Gary Lee

    Gary Lee - 2022-06-02
    • Component: fm --> imm
     

Log in to post a comment.