[tickets] [opensaf:tickets] #1864 log: get ER syslog when running logtest 5 2
- **status**: review --> fixed - **assigned_to**: Canh Truong --> nobody - **Milestone**: 4.7.2 --> 5.0.1 - **Comment**: changeset: 8110:3093e3a87a7e tag: tip parent: 8106:18f09b25f3dd user:Canh Van Truong 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 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 date:Tue Sep 20 13:35:59 2016 +0700 summary: log: fix ER syslog when running logtest 5 2 [#1864] --- ** [tickets:#1864] log: get ER syslog when running logtest 5 2** **Status:** fixed **Milestone:** 5.0.1 **Created:** Wed Jun 08, 2016 02:32 AM UTC by Vu Minh Nguyen **Last Updated:** Fri Sep 16, 2016 09:39 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 opensaf-tickets@lists.sourceforge.net 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.-- ___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1864 log: get ER syslog when running logtest 5 2
- **status**: accepted --> review --- ** [tickets:#1864] log: get ER syslog when running logtest 5 2** **Status:** review **Milestone:** 4.7.2 **Created:** Wed Jun 08, 2016 02:32 AM UTC by Vu Minh Nguyen **Last Updated:** Wed Jun 22, 2016 11:18 AM UTC **Owner:** Canh Truong 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 opensaf-tickets@lists.sourceforge.net 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.-- ___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1864 log: get ER syslog when running logtest 5 2
- **status**: assigned --> accepted --- ** [tickets:#1864] log: get ER syslog when running logtest 5 2** **Status:** accepted **Milestone:** 4.7.2 **Created:** Wed Jun 08, 2016 02:32 AM UTC by Vu Minh Nguyen **Last Updated:** Fri Jun 17, 2016 06:15 AM UTC **Owner:** Canh Truong 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 opensaf-tickets@lists.sourceforge.net 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.-- Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1864 log: get ER syslog when running logtest 5 2
- **status**: unassigned --> assigned - **assigned_to**: Canh Truong --- ** [tickets:#1864] log: get ER syslog when running logtest 5 2** **Status:** assigned **Milestone:** 4.7.2 **Created:** Wed Jun 08, 2016 02:32 AM UTC by Vu Minh Nguyen **Last Updated:** Wed Jun 08, 2016 02:38 AM UTC **Owner:** Canh Truong 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 opensaf-tickets@lists.sourceforge.net 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. http://sdm.link/zohomanageengine___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1864 log: get ER syslog when running logtest 5 2
- 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 opensaf-tickets@lists.sourceforge.net 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 Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1864 log: get ER syslog when running logtest 5 2
--- ** [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 opensaf-tickets@lists.sourceforge.net 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 Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
