- 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
~~~~
---
** [tickets:#1864] log: get ER syslog when running logtest 5 2**
**Status:** unassigned
**Milestone:** 4.7.2
**Created:** Wed Jun 08, 2016 02:32 AM UTC by Vu Minh Nguyen
**Last Updated:** Wed Jun 08, 2016 02:32 AM UTC
**Owner:** nobody
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.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
