Menu

#2402 base: "hardening" use of lockfile in opensafd

5.2.RC2
fixed
None
defect
base
-
major
False
2017-05-11
2017-03-29
No

"hardening" use of lockfile in opensafd

Related

Tickets: #2402

Discussion

  • Hans Nordebäck

    Hans Nordebäck - 2017-03-30
    • status: review --> fixed
     
  • Hans Nordebäck

    Hans Nordebäck - 2017-03-30

    changeset: 8739:811a5c573665
    user: Hans Nordeback hans.nordeback@ericsson.com
    date: Thu Mar 30 12:09:26 2017 +0200
    summary: base: "hardening" use of lockfile in opensafd [#2402]

     

    Related

    Tickets: #2402

  • Rafael Odzakow

    Rafael Odzakow - 2017-04-24

    I have seen a issue with the lockfile. Here are some parts from the system log:

    21:59:15 SC-1 opensafd: Starting OpenSAF Services(5.2.0 - 8767:c1cc2a915e72:default) (Using TCP)

    • Reboot command is issued from SC-2:
      21:59:16 SC-2 osafsmfd[599]: NO STEP: Reboot node for removal safAmfNode=SC-1,safAmfCluster=myAmfCluster

    • SC-1 is not finished with the start of opensaf. This line is missing from SC-1: opensafd: OpenSAF services successfully started

    21:59:17 SC-1 opensafd: Stopping OpenSAF Services
    21:59:17 SC-1 opensafd: opensafd start/stop already in progress. Unable to continue
    21:59:17 SC-1 opensafd: To forcefully start/stop OpenSAF remove /var/lock/subsys/opensafd_inprogress
    21:59:17 SC-1 osafamfwd[565]: exiting for shutdown
    21:59:17 SC-1 osafamfnd[487]: NO Shutdown initiated

     
  • Rafael Odzakow

    Rafael Odzakow - 2017-04-24
    • status: fixed --> unassigned
    • Blocker: --> False
     
  • Hans Nordebäck

    Hans Nordebäck - 2017-05-11
    • status: unassigned --> fixed
     

Log in to post a comment.