Menu ▾ ▴

#1864 log: get ER syslog when running logtest 5 2

5.0.1
fixed
nobody
None
defect
log
tests
minor
2016-09-20
2016-06-08
Vu Minh Nguyen
No

When running logtest 5 2 sometimes gets following ER message in syslog:

2016-04-27 02:39:57 SC-1 osaflogd[462]: ER Old log files could not be renamed and closed for stream: safLgStrCfg=saLogNotification,safApp=safLogService
2016-04-27 02:39:57 SC-1 osaflogd[462]: ER Old log files could not be renamed and closed for stream: safLgStrCfg=saLogSystem,safApp=safLogService

The problem is in logtest app - Test case #2 of suite #5.

"logtest 5 2" does following steps:
1) Create xxtest directory
2) Change default logRootDirectory to above directory
3) Change logRootDirectory back to default value
4) Remove all log files in xxtest directory

In step #2 or #3, there is one step to rename the openning log files by appending the closed time to the log file names in IMM apply callback. The problem happens because the step #4 done while LOG service not yet completed IMM apply callback due to #2 or #3.

Can reproduce the problem by making logsv high load while performing logtest 5 2:
1) Open 2 terminals
2) On terminal #1, in loop, using saflogger tool sending log record to alarm stream while on other terminal performing logtest 5 2 in loop.

Related

Tickets: #1864
Wiki: ChangeLog-5.0.1

Discussion

  • Vu Minh Nguyen

    Vu Minh Nguyen - 2016-06-08
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -10,7 +10,7 @@
 3) Change `logRootDirectory` back to default value
 4) **Remove all log files in `xxtest` directory**

-In step #2 or #3, there is one step to rename the openning log files by appending the closed time to the log file names in `IMM apply callback`. The problem happens because the step #4 done while LOG service not yet completed`IMM apply callback` due to #2 or #3.
+In step #2 or #3, there is one step to rename the openning log files by appending the closed time to the log file names in `IMM apply callback`. The problem happens because the step #4 done while LOG service not yet completed `IMM apply callback` due to #2 or #3.

 Can reproduce the problem by making logsv high load while performing `logtest 5 2`:
 1) Open 2 terminals
     

  • Canh Truong

    Canh Truong - 2016-06-17
    • status: unassigned --> assigned
    • assigned_to: Canh Truong
     

  • Canh Truong

    Canh Truong - 2016-06-22
    • status: assigned --> accepted
     

  • Canh Truong

    Canh Truong - 2016-09-16
    • status: accepted --> review
     

  • Vu Minh Nguyen

    Vu Minh Nguyen - 2016-09-20
    • status: review --> fixed
    • assigned_to: Canh Truong --> nobody
    • Milestone: 4.7.2 --> 5.0.1
     

  • Vu Minh Nguyen

    Vu Minh Nguyen - 2016-09-20

    changeset: 8110:3093e3a87a7e
    tag: tip
    parent: 8106:18f09b25f3dd
    user: Canh Van Truong canh.v.truong@dektech.com.au
    date: Tue Sep 20 13:35:59 2016 +0700
    summary: log: fix ER syslog when running logtest 5 2 [#1864]

    changeset: 8109:849706863a78
    branch: opensaf-5.1.x
    parent: 8107:2fe7d71cc3f4
    user: Canh Van Truong canh.v.truong@dektech.com.au
    date: Tue Sep 20 13:35:59 2016 +0700
    summary: log: fix ER syslog when running logtest 5 2 [#1864]

    changeset: 8108:b56c07165af9
    branch: opensaf-5.0.x
    parent: 8093:bcd8675c17b3
    user: Canh Van Truong canh.v.truong@dektech.com.au
    date: Tue Sep 20 13:35:59 2016 +0700
    summary: log: fix ER syslog when running logtest 5 2 [#1864]

     

    Related

    Tickets: #1864

Log in to post a comment.