- **status**: review --> fixed
- **assigned_to**: Canh Truong --> nobody
---
** [tickets:#3052] log: Update document for ticket #3022 and #3046**
**Status:** fixed
**Milestone:** 5.19.07
**Created:** Mon Jun 17, 2019 10:56 AM UTC by Canh Truong
**Last Updated:** Thu Jul 11, 2019 04:46 AM
changeset: 243:98a830708434
tag: tip
user: Canh Van Truong
date: Thu Jul 11 11:43:33 2019 +0700
summary: log: update LOG PR for OpenSAF 5.19.07 [#3052]
---
** [tickets:#3052] log: Update document for ticket #3022 and #3046**
**Status:** review
**Milestone:** 5.19.07
**Created:** Mon Jun 17,
- **status**: review --> fixed
- **assigned_to**: Canh Truong --> nobody
---
** [tickets:#3056] log: Update try again for admin operation in logtest 6 49,
50**
**Status:** fixed
**Milestone:** 5.19.07
**Created:** Wed Jun 26, 2019 07:22 AM UTC by Canh Truong
**Last Updated:** Wed Jul 10,
commit f60f0388969846307e148096df9cd4cc06bb707b (HEAD -> develop,
origin/develop, ticket-3056)
Author: Canh Van Truong
Date: Wed Jul 10 17:33:15 2019 +0700
log: Update the try again for admin operation [#3056]
The logtest 6 49 and logtest 6 50 failed because the admin
operation
- **Type**: defect --> enhancement
---
** [tickets:#3052] log: Update document for ticket #3022 and #3046**
**Status:** review
**Milestone:** 5.19.06
**Created:** Mon Jun 17, 2019 10:56 AM UTC by Canh Truong
**Last Updated:** Mon Jun 17, 2019 11:09 AM UTC
**Owner:** Canh Truong
Update the
- **status**: accepted --> duplicate
- **assigned_to**: Canh Truong --> nobody
- **Comment**:
Duplicated with #3056
---
** [tickets:#3031] log: Updated document for enhancement in ticket #3022**
**Status:** duplicate
**Milestone:** 5.19.06
**Created:** Wed Apr 17, 2019 08:54 AM UTC by Canh
- **status**: accepted --> review
---
** [tickets:#3056] log: Update try again for admin operation in logtest 6 49,
50**
**Status:** review
**Milestone:** 5.19.06
**Created:** Wed Jun 26, 2019 07:22 AM UTC by Canh Truong
**Last Updated:** Wed Jun 26, 2019 07:22 AM UTC
**Owner:** Canh Truong
---
** [tickets:#3056] log: Update try again for admin operation in logtest 6 49,
50**
**Status:** accepted
**Milestone:** 5.19.06
**Created:** Wed Jun 26, 2019 07:22 AM UTC by Canh Truong
**Last Updated:** Wed Jun 26, 2019 07:22 AM UTC
**Owner:** Canh Truong
The test case logtest 6 49,
commit 68efc6010fda86d62300a687bbd8c52cba232479 (HEAD -> develop,
origin/develop, ticket-3046)
Author: Canh Van Truong
Date: Tue Jun 18 18:14:08 2019 +0700
log: Delete the older file without closing current log file via admin
operation [#3046]
Improve the enhancement of ticket
- **status**: accepted --> review
---
** [tickets:#3052] log: Update document for ticket #3022 and #3046**
**Status:** review
**Milestone:** 5.19.06
**Created:** Mon Jun 17, 2019 10:56 AM UTC by Canh Truong
**Last Updated:** Mon Jun 17, 2019 10:56 AM UTC
**Owner:** Canh Truong
Update the
---
** [tickets:#3052] log: Update document for ticket #3022 and #3046**
**Status:** accepted
**Milestone:** 5.19.06
**Created:** Mon Jun 17, 2019 10:56 AM UTC by Canh Truong
**Last Updated:** Mon Jun 17, 2019 10:56 AM UTC
**Owner:** Canh Truong
Update the new feature in
- **status**: unassigned --> fixed
- **Comment**:
commit 8742197dee4c0afe3ff84a13312dd2ba59e9e785 (HEAD -> develop,
origin/develop, ticket-3045)
Author: Canh Van Truong
Date: Fri Jun 7 16:52:04 2019 +0700
log: fix to remove the cfg file when log file rotation [#3045]
If the
- Description has changed:
Diff:
--- old
+++ new
@@ -1,4 +1,4 @@
Remove some log files after the priod time but the current of log file is not
closed.
It is useful if user doesn't want the log file exist after some days. The
current log file may be empty or don't have too much log
- **assigned_to**: Canh Truong
---
** [tickets:#3046] log: clean up number of older log file without closing
current log file**
**Status:** unassigned
**Milestone:** 5.19.06
**Created:** Wed May 29, 2019 08:50 AM UTC by Canh Truong
**Last Updated:** Wed May 29, 2019 08:50 AM UTC
**Owner:**
---
** [tickets:#3046] log: clean up number of older log file without closing
current log file**
**Status:** unassigned
**Milestone:** 5.19.06
**Created:** Wed May 29, 2019 08:50 AM UTC by Canh Truong
**Last Updated:** Wed May 29, 2019 08:50 AM UTC
**Owner:** nobody
Remove some log files
- Description has changed:
Diff:
--- old
+++ new
@@ -1,6 +1,12 @@
when log file is rotated, the oldest log files are deleted to make sure the
number log files is less than "maxFilesRotated". The oldest cfg is also
checked and deleted.
-If oldest cfg file is deleted fail, log service
- Description has changed:
Diff:
--- old
+++ new
@@ -21,8 +21,7 @@
rc = (cfg_files - failed);
}
}
- }
...
}
-The "cfgolddate" is not alway equal with "logolddate" if the deleting of cfg
fail in previous or the closing cfg/log file in old day and creating new
---
** [tickets:#3045] log: the cfg file never be removed **
**Status:** unassigned
**Milestone:** 5.19.06
**Created:** Tue May 28, 2019 04:27 AM UTC by Canh Truong
**Last Updated:** Tue May 28, 2019 04:27 AM UTC
**Owner:** nobody
when log file is rotated, the oldest log files are deleted
---
** [tickets:#3037] osaf: lost connectivity to consensus due to timeout**
**Status:** accepted
**Milestone:** 5.19.06
**Created:** Fri May 10, 2019 07:52 AM UTC by Canh Truong
**Last Updated:** Fri May 10, 2019 07:52 AM UTC
**Owner:** Canh Truong
The watch command return with lost
- **status**: accepted --> fixed
---
** [tickets:#3026] log: number of log file more than
"saLogStreamMaxFilesRotated"**
**Status:** fixed
**Milestone:** 5.19.06
**Created:** Thu Mar 28, 2019 11:26 AM UTC by Canh Truong
**Last Updated:** Tue Apr 23, 2019 05:10 AM UTC
**Owner:** Canh Truong
The fixes is included in #3022[
3022](https://sourceforge.net/p/opensaf/tickets/3022/)
---
** [tickets:#3026] log: number of log file more than
"saLogStreamMaxFilesRotated"**
**Status:** accepted
**Milestone:** 5.19.06
**Created:** Thu Mar 28, 2019 11:26 AM UTC by Canh Truong
**Last
- **status**: accepted --> fixed
---
** [tickets:#3025] log: logd always create new log file at standby in case
split file system**
**Status:** fixed
**Milestone:** 5.19.06
**Labels:** #3022
**Created:** Thu Mar 28, 2019 09:58 AM UTC by Canh Truong
**Last Updated:** Tue Apr 23, 2019 05:09
the fixes is included in #3022
---
** [tickets:#3025] log: logd always create new log file at standby in case
split file system**
**Status:** accepted
**Milestone:** 5.19.06
**Created:** Thu Mar 28, 2019 09:58 AM UTC by Canh Truong
**Last Updated:** Thu Mar 28, 2019 11:26 AM UTC
**Owner:**
- **labels**: --> #3022
---
** [tickets:#3025] log: logd always create new log file at standby in case
split file system**
**Status:** accepted
**Milestone:** 5.19.06
**Labels:** #3022
**Created:** Thu Mar 28, 2019 09:58 AM UTC by Canh Truong
**Last Updated:** Tue Apr 23, 2019 05:08 AM UTC
- **status**: review --> fixed
- **assigned_to**: Canh Truong --> nobody
---
** [tickets:#3022] log: Rotate log file base on admin operation**
**Status:** fixed
**Milestone:** 5.19.06
**Created:** Wed Mar 20, 2019 07:58 AM UTC by Canh Truong
**Last Updated:** Tue Apr 23, 2019 05:07 AM UTC
commit 7916ac316e86478c621c8359cf2aca4886288a38 (HEAD -> develop,
origin/develop, ticket-3022)
Author: Canh Van Truong
Date: Tue Apr 23 11:50:03 2019 +0700
log: Rotate log file via admin operation [#3022]
In some cases the Users want to rotate log file at the time althouth
the
commit e6cf94a9b03ab4542bb84a0172806f4f2fb86530 (HEAD -> develop,
origin/develop, ticket-3032)
Author: thuan.tran
Date: Thu Apr 18 13:41:46 2019 +0700
amf: fix container sample build failure [#3032]
---
** [tickets:#3032] amf: sample build failure**
**Status:** fixed
**Milestone:**
---
** [tickets:#3031] log: Updated document for enhancement in ticket #3022**
**Status:** accepted
**Milestone:** 5.19.06
**Created:** Wed Apr 17, 2019 08:54 AM UTC by Canh Truong
**Last Updated:** Wed Apr 17, 2019 08:54 AM UTC
**Owner:** Canh Truong
The enhancement for log file rotation
- **status**: accepted --> review
---
** [tickets:#3022] log: Rotate log file base on admin operation**
**Status:** review
**Milestone:** 5.19.06
**Created:** Wed Mar 20, 2019 07:58 AM UTC by Canh Truong
**Last Updated:** Wed Mar 27, 2019 08:21 AM UTC
**Owner:** Canh Truong
The rotation of
- **status**: fixed --> unassigned
- **Comment**:
The fix should be reverted because it always make the standby reboot when the
cold sync happen after the checkpoint of reopening stream.
---
** [tickets:#3018] log: logd crash due to well known stream has numOpeners = 0**
**Status:**
- **status**: review --> fixed
- **assigned_to**: Canh Truong --> nobody
---
** [tickets:#3018] log: logd crash due to well known stream has numOpeners = 0**
**Status:** fixed
**Milestone:** 5.19.06
**Created:** Thu Mar 14, 2019 09:37 AM UTC by Canh Truong
**Last Updated:** Mon Apr 01, 2019
commit 1cca4b16b4cf2060c7b7e6d18b9d279188d90dd6 (HEAD -> develop,
origin/develop, ticket-3018)
Author: canht32
Date: Mon Apr 1 17:16:30 2019 +0700
log: fix logd crash due to well known stream has numOpeners=0 [#3018]
If client closes stream is successful in active node but it cannot
---
** [tickets:#3026] log: number of log file more than
"saLogStreamMaxFilesRotated"**
**Status:** unassigned
**Milestone:** 5.19.06
**Created:** Thu Mar 28, 2019 11:26 AM UTC by Canh Truong
**Last Updated:** Thu Mar 28, 2019 11:26 AM UTC
**Owner:** nobody
When changing the attribute of
- **Component**: unknown --> log
- **Part**: - --> d
- **Priority**: major --> minor
---
** [tickets:#3025] log: logd always create new log file at standby in case
split file system**
**Status:** accepted
**Milestone:** 5.19.06
**Created:** Thu Mar 28, 2019 09:58 AM UTC by Canh Truong
**Last
- Description has changed:
Diff:
--- old
+++ new
@@ -2,4 +2,4 @@
1/ logd always create new log file at standby node if changing the attribute
of the stream although it doesn't need create new one.
e.g. changing the attribute "saLogStreamSeverityFilter". There is no new log
file on
- **status**: accepted --> review
---
** [tickets:#3018] log: logd crash due to well known stream has numOpeners = 0**
**Status:** review
**Milestone:** 5.19.06
**Created:** Thu Mar 14, 2019 09:37 AM UTC by Canh Truong
**Last Updated:** Tue Mar 26, 2019 06:25 AM UTC
**Owner:** Canh Truong
- Description has changed:
Diff:
--- old
+++ new
@@ -1,2 +1,2 @@
The rotation of log file can be done by trigger of admin operation.
-The admin operation can be done for global object in log service
(logConfig=1,safApp=safLogService)
+The admin operation can be done for each stream
I guess following is steps of the condition for the crash:
1/Current "numOpeners" of one well known stream = 2. This mean that just one
client open this stream. LOGD get close that stream request from client. The
closing stream is successful on active node. But checkpoiting to standby
have
- **status**: review --> accepted
---
** [tickets:#3018] log: logd crash due to well known stream has numOpeners = 0**
**Status:** accepted
**Milestone:** 5.19.03
**Created:** Thu Mar 14, 2019 09:37 AM UTC by Canh Truong
**Last Updated:** Fri Mar 15, 2019 02:40 AM UTC
**Owner:** Canh Truong
---
** [tickets:#3022] log: Rotate log file base on admin operation**
**Status:** unassigned
**Milestone:** 5.19.03
**Created:** Wed Mar 20, 2019 07:58 AM UTC by Canh Truong
**Last Updated:** Wed Mar 20, 2019 07:58 AM UTC
**Owner:** nobody
The rotation of log file can be done by trigger of
- **status**: review --> fixed
- **assigned_to**: Canh Truong --> nobody
---
** [tickets:#2984] dtm: dtm close socket due to duplication of add node IP
info**
**Status:** fixed
**Milestone:** 5.19.03
**Created:** Thu Dec 13, 2018 05:05 AM UTC by Canh Truong
**Last Updated:** Fri Mar 15,
- **status**: accepted --> review
---
** [tickets:#3018] log: logd crash due to well known stream has numOpeners = 0**
**Status:** review
**Milestone:** 5.19.03
**Created:** Thu Mar 14, 2019 09:37 AM UTC by Canh Truong
**Last Updated:** Thu Mar 14, 2019 09:37 AM UTC
**Owner:** Canh Truong
---
** [tickets:#3018] log: logd crash due to well known stream has numOpeners = 0**
**Status:** accepted
**Milestone:** 5.19.03
**Created:** Thu Mar 14, 2019 09:37 AM UTC by Canh Truong
**Last Updated:** Thu Mar 14, 2019 09:37 AM UTC
**Owner:** Canh Truong
osaflogd[14677]:
- **status**: review --> fixed
- **assigned_to**: Canh Truong --> nobody
- **Comment**:
commit 89c579247b5b43122301b248433b319054178b58 (HEAD -> develop,
origin/develop)
Author: Canh Van Truong
Date: Thu Feb 28 10:50:42 2019 +0700
log: fix last value of
- Description has changed:
Diff:
--- old
+++ new
@@ -1,4 +1,3 @@
-
After removing value
"saLogSystem_dest;UNIX_SOCKET;/var/run/stream/CMW_saLogSystem.sock" from
logRecordDestinationConfiguration of logConfig=1 successfully
SC-2-1:~ # immlist logConfig=1,safApp=safLogService
-
---
** [tickets:#3014] log: The value of logRecordDestinationConfiguration is not
deleted in lgd**
**Status:** accepted
**Milestone:** 5.19.03
**Created:** Thu Feb 28, 2019 03:33 AM UTC by Canh Truong
**Last Updated:** Thu Feb 28, 2019 03:33 AM UTC
**Owner:** Canh Truong
After removing
---
** [tickets:#3000] rde: rdegetrole timeout in rda**
**Status:** unassigned
**Milestone:** 5.19.03
**Created:** Wed Jan 16, 2019 07:58 AM UTC by Canh Truong
**Last Updated:** Wed Jan 16, 2019 07:58 AM UTC
**Owner:** nobody
In the "rdegetrole" command or set role ..., rda send the geting
- **status**: accepted --> review
- **Type**: defect --> enhancement
---
** [tickets:#2994] ntf: update document for limit of logger buffer**
**Status:** review
**Milestone:** 5.19.03
**Created:** Wed Jan 09, 2019 09:11 AM UTC by Canh Truong
**Last Updated:** Wed Jan 09, 2019 09:25 PM UTC
- **status**: accepted --> unassigned
- **assigned_to**: Canh Truong --> nobody
---
** [tickets:#2992] rde: Having two instances of rded that watch they key**
**Status:** unassigned
**Milestone:** 5.18.12
**Created:** Thu Jan 03, 2019 06:11 AM UTC by Minh Hon Chau
**Last Updated:** Tue Jan
- **status**: unassigned --> accepted
- **assigned_to**: Canh Truong
---
** [tickets:#2992] rde: Having two instances of rded that watch they key**
**Status:** accepted
**Milestone:** 5.18.12
**Created:** Thu Jan 03, 2019 06:11 AM UTC by Minh Hon Chau
**Last Updated:** Thu Jan 03, 2019 06:11
- **status**: review --> fixed
- **assigned_to**: Canh Truong --> nobody
---
** [tickets:#2990] log: ER in syslog after returning the response to agent
failed**
**Status:** fixed
**Milestone:** 5.18.12
**Created:** Thu Dec 27, 2018 07:06 AM UTC by Canh Truong
**Last Updated:** Fri Dec 28,
commit 29fbd0c6839f350444835c121a279075eecd3cdc (HEAD -> develop,
origin/develop)
Author: Canh Van Truong
Date: Thu Dec 27 14:42:09 2018 +0700
log: Update level of printout info in syslog from ER to WA [#2990]
---
** [tickets:#2990] log: ER in syslog after returning the response to
- **summary**: log: ER in syslog after returning the response to agent --> log:
ER in syslog after returning the response to agent failed
---
** [tickets:#2990] log: ER in syslog after returning the response to agent
failed**
**Status:** review
**Milestone:** 5.18.12
**Created:** Thu Dec
- **status**: unassigned --> review
---
** [tickets:#2984] dtm: dtm close socket due to duplication of add node IP
info**
**Status:** review
**Milestone:** 5.18.12
**Created:** Thu Dec 13, 2018 05:05 AM UTC by Canh Truong
**Last Updated:** Thu Dec 27, 2018 08:41 AM UTC
**Owner:** Canh Truong
- **assigned_to**: Canh Truong
---
** [tickets:#2984] dtm: dtm close socket due to duplication of add node IP
info**
**Status:** unassigned
**Milestone:** 5.18.12
**Created:** Thu Dec 13, 2018 05:05 AM UTC by Canh Truong
**Last Updated:** Fri Dec 14, 2018 02:35 AM UTC
**Owner:** Canh Truong
- **status**: accepted --> review
---
** [tickets:#2990] log: ER in syslog after returning the response to agent**
**Status:** review
**Milestone:** 5.18.12
**Created:** Thu Dec 27, 2018 07:06 AM UTC by Canh Truong
**Last Updated:** Thu Dec 27, 2018 07:07 AM UTC
**Owner:** Canh Truong
- **Component**: unknown --> log
---
** [tickets:#2990] log: ER in syslog after returning the response to agent**
**Status:** accepted
**Milestone:** 5.18.12
**Created:** Thu Dec 27, 2018 07:06 AM UTC by Canh Truong
**Last Updated:** Thu Dec 27, 2018 07:06 AM UTC
**Owner:** Canh Truong
---
** [tickets:#2990] log: ER in syslog after returning the response to agent**
**Status:** accepted
**Milestone:** 5.18.12
**Created:** Thu Dec 27, 2018 07:06 AM UTC by Canh Truong
**Last Updated:** Thu Dec 27, 2018 07:06 AM UTC
**Owner:** Canh Truong
2018-12-13 20:00:31.818 SC-1
- Description has changed:
Diff:
--- old
+++ new
@@ -1,10 +1,10 @@
The situation of issue:
-1/ Stanby SC2 is restart. When SC2 is up, SC2's dtm send broadcast msg to
all nodes (dtmscb->multicast->Send(); ) . PL4 receive this msg and start to
connect to create communication sock with
---
** [tickets:#2984] dtm: dtm close socket due to duplication of add node IP
info**
**Status:** unassigned
**Milestone:** 5.18.12
**Created:** Thu Dec 13, 2018 05:05 AM UTC by Canh Truong
**Last Updated:** Thu Dec 13, 2018 05:05 AM UTC
**Owner:** nobody
The situation of issue:
1/ Stanby
- Description has changed:
Diff:
--- old
+++ new
@@ -7,4 +7,4 @@
+ Take time to write all notificaion in the very big list
-During NTFD is delayed, a lot of request come to and be pushed in mbx. if
NTFD doesn't handle the request on time, the request is timeout.
+During NTFD is
- **status**: accepted --> review
---
** [tickets:#2973] ntf: NTFD send the response the client (MDS DEST) fail
because the MDS dest disconnected**
**Status:** review
**Milestone:** 5.18.12
**Created:** Fri Nov 23, 2018 11:49 AM UTC by Canh Truong
**Last Updated:** Wed Dec 05, 2018 04:33 AM
- **status**: invalid --> assigned
---
** [tickets:#2961] ntf: saNtfNotificationSend take time due to write to log
file error with try again**
**Status:** assigned
**Milestone:** 5.18.12
**Created:** Thu Nov 15, 2018 06:52 AM UTC by Canh Truong
**Last Updated:** Tue Dec 04, 2018 08:22 AM UTC
- **summary**: ntf: saNtfNotificationSend take a lot of time and may timeout
--> ntf: saNtfNotificationSend take time due to write to log file error with
try again
- Description has changed:
Diff:
--- old
+++ new
@@ -1 +1,10 @@
-Ntf need to write all notification in the queue to the log
- Description has changed:
Diff:
--- old
+++ new
@@ -1,3 +1,3 @@
When the sending notification request come to NTFD , they are put in the mbx
to wait for being processed. if client of these request is down, MDS thread
receive the event down and also put to mbx.
-The priority of
- Description has changed:
Diff:
--- old
+++ new
@@ -1,3 +1,3 @@
When the sending notification request come to NTFD , they are put in the mbx
to wait for being processed. if client of these request is down, MDS thread
receive the event down and also put to mbx.
-The priority of
---
** [tickets:#2973] ntf: NCSMDS_DOWN event is delayed to send to main thread**
**Status:** accepted
**Milestone:** 5.18.12
**Created:** Fri Nov 23, 2018 11:49 AM UTC by Canh Truong
**Last Updated:** Fri Nov 23, 2018 11:49 AM UTC
**Owner:** Canh Truong
When the sending notification
- Description has changed:
Diff:
--- old
+++ new
@@ -1,2 +1 @@
-
-Ntf need to write all notification in the queue to the log file, if there are
some notification in the queue. But in meanwhile, ntf get write callback with
writting notification fail with TRY_AGAIN error , it push this
- Description has changed:
Diff:
--- old
+++ new
@@ -1,6 +1,7 @@
Summary issue:
Config cluster with 5 SCs.
-- starting cluster: SC5 is active, SC4 standby and [SC1-SC3] is quiesced. SC1
and SC2 are promoting those nodes to become ACTIVE (by rde component). SC5 is
answering the
---
** [tickets:#2948] rde: race between quiesced node and standby node become
active node**
**Status:** unassigned
**Milestone:** 5.18.12
**Created:** Mon Oct 29, 2018 10:48 AM UTC by Canh Truong
**Last Updated:** Mon Oct 29, 2018 10:48 AM UTC
**Owner:** nobody
Summary issue:
Config
- **status**: review --> unassigned
- **assigned_to**: Canh Truong --> nobody
---
** [tickets:#2445] log: reorganize headers and implementation**
**Status:** unassigned
**Milestone:** 5.18.12
**Created:** Fri Apr 28, 2017 08:28 AM UTC by Vu Minh Nguyen
**Last Updated:** Sat Sep 29, 2018
- Description has changed:
Diff:
--- old
+++ new
@@ -46,5 +46,5 @@
perceivedSeverity = SA_NTF_SEVERITY_WARNING
-There are 3 notifications that happens before the eventtime =
1536740946933049001, but it is still read while the result should be no
notification with this command.
- **status**: accepted --> review
---
** [tickets:#2925] ntf: NtfReader create the list of notification with
searchcriteria is not correct**
**Status:** review
**Milestone:** 5.18.09
**Created:** Thu Sep 13, 2018 04:05 AM UTC by Canh Truong
**Last Updated:** Thu Sep 13, 2018 04:05 AM UTC
---
** [tickets:#2925] ntf: NtfReader create the list of notification with
searchcriteria is not correct**
**Status:** accepted
**Milestone:** 5.18.09
**Created:** Thu Sep 13, 2018 04:05 AM UTC by Canh Truong
**Last Updated:** Thu Sep 13, 2018 04:05 AM UTC
**Owner:** Canh Truong
Produce
- **status**: review --> fixed
- **assigned_to**: Canh Truong --> nobody
- **Comment**:
commit 1315ade5d2223ecb22cc3076da00d4cee09ec7f7 (HEAD -> develop,
origin/develop)
Author: Canh Van Truong
Date: Thu Aug 23 14:31:47 2018 +0700
log: fix timeout when deleting configuration stream
---
** [tickets:#2765] base: try_again_decorator is wrong for initialize API**
**Status:** unassigned
**Milestone:** 5.18.01
**Created:** Mon Jan 22, 2018 07:49 AM UTC by Canh Truong
**Last Updated:** Mon Jan 22, 2018 07:49 AM UTC
**Owner:** nobody
When doing try-again for Initialize api,
---
** [tickets:#2764] log: update saflogtest to limit time when handling try again
for ack of write log records**
**Status:** accepted
**Milestone:** 5.18.01
**Created:** Mon Jan 22, 2018 07:46 AM UTC by Canh Truong
**Last Updated:** Mon Jan 22, 2018 07:46 AM UTC
**Owner:** Canh Truong
- **status**: unassigned --> invalid
- **Blocker**: --> False
- **Comment**:
The node name is included in log record with token @Cq now. So I set this
ticket to invalid.
---
** [tickets:#631] LOG: add possibilty to log originating hostname**
**Status:** invalid
**Milestone:** future
- **status**: assigned --> review
---
** [tickets:#2752] log: not reject creating log streams with same file name in
same CCB**
**Status:** review
**Milestone:** 5.18.01
**Created:** Thu Dec 28, 2017 01:51 PM UTC by Vu Minh Nguyen
**Last Updated:** Wed Jan 03, 2018 10:02 AM UTC
**Owner:**
- **status**: unassigned --> invalid
- **Comment**:
The returned error has been changed. So I set it to be invalid
---
** [tickets:#1242] LOG: Incorrect error return in filehandling function**
**Status:** invalid
**Milestone:** future
**Created:** Wed Jan 21, 2015 04:06 PM UTC by elunlen
In case 2 streams are created in the same CCB, ccb_completed callback is called
2 times to verify the parameters then ccb_apply_create callbacks is called 2
time to create 2 new streams. Log service verifies stream file name by checking
if the file name is duplicated with any exist streams.
- **status**: unassigned --> assigned
- **assigned_to**: Canh Truong
---
** [tickets:#2752] log: not reject creating log streams with same file name in
same CCB**
**Status:** assigned
**Milestone:** 5.18.01
**Created:** Thu Dec 28, 2017 01:51 PM UTC by Vu Minh Nguyen
**Last Updated:** Fri
- **status**: accepted --> review
---
** [tickets:#2747] ntf: ntfd abort with theNtfAdmin is NULL**
**Status:** review
**Milestone:** 5.18.01
**Created:** Thu Dec 21, 2017 09:42 AM UTC by Canh Truong
**Last Updated:** Thu Dec 21, 2017 09:42 AM UTC
**Owner:** Canh Truong
2017-12-21
---
** [tickets:#2747] ntf: ntfd abort with theNtfAdmin is NULL**
**Status:** accepted
**Milestone:** 5.18.01
**Created:** Thu Dec 21, 2017 09:42 AM UTC by Canh Truong
**Last Updated:** Thu Dec 21, 2017 09:42 AM UTC
**Owner:** Canh Truong
2017-12-21 01:08:23.207 SC-1 osafsmfnd[347]: NO MDS
Hi
The maxinum charaters of file name in log 255 characters, but maximum
characters of stream name is greater than 255 characters. In case, we use
stream name with size > 255 characters and file name < 255 characters (with
option -f ) is still valid. (Test case logtest 13 5)
For the local
Hi Srinivas,
1/ For longDN, file name may be greater 255 characters
2/ variable 'tmpDn' is defined in local and "saAisNameLend(tmpDn,
);" make put the local pointer to "logStreamName". So when
saflogger use "logStreamName", The pointer that was contained in
"logStreamName" may be invalid
---
---
** [tickets:#2733] ntf: NTFD has unexpectedly crashed due to ntfimcnd exit**
**Status:** unassigned
**Milestone:** 5.18.01
**Created:** Thu Dec 07, 2017 11:38 AM UTC by Canh Truong
**Last Updated:** Thu Dec 07, 2017 11:38 AM UTC
**Owner:** nobody
When the cluster is started, NTFD has
- **status**: accepted --> review
---
** [tickets:#2705] ntf: ntfd remove client in standby node while not finalize
in active node**
**Status:** review
**Milestone:** 5.18.01
**Created:** Mon Nov 27, 2017 07:32 AM UTC by Canh Truong
**Last Updated:** Thu Nov 30, 2017 02:46 AM UTC
**Owner:**
- **status**: unassigned --> accepted
- **assigned_to**: Canh Truong
---
** [tickets:#2705] ntf: ntfd remove client in standby node while not finalize
in active node**
**Status:** accepted
**Milestone:** 5.18.01
**Created:** Mon Nov 27, 2017 07:32 AM UTC by Canh Truong
**Last Updated:** Mon
- Description has changed:
Diff:
--- old
+++ new
@@ -7,8 +7,8 @@
At the end of step 2, the NCSMDS_DOWN event will be send to both active and
standby node.
-- In active node, mds thread send this request to ntfd through mailbox. ntfd
receive this request to process this event and
- **status**: accepted --> review
---
** [tickets:#2700] log: coredump when stop cluster**
**Status:** review
**Milestone:** 5.18.01
**Created:** Wed Nov 22, 2017 08:43 AM UTC by Canh Truong
**Last Updated:** Thu Nov 23, 2017 09:25 AM UTC
**Owner:** Canh Truong
**Attachments:**
-
- **status**: assigned --> accepted
---
** [tickets:#2700] log: coredump when stop cluster**
**Status:** accepted
**Milestone:** 5.18.01
**Created:** Wed Nov 22, 2017 08:43 AM UTC by Canh Truong
**Last Updated:** Wed Nov 22, 2017 09:10 AM UTC
**Owner:** Canh Truong
**Attachments:**
-
- **status**: unassigned --> assigned
- **assigned_to**: Canh Truong
---
** [tickets:#2700] log: coredump when stop cluster**
**Status:** assigned
**Milestone:** 5.18.01
**Created:** Wed Nov 22, 2017 08:43 AM UTC by Canh Truong
**Last Updated:** Wed Nov 22, 2017 08:43 AM UTC
**Owner:** Canh
---
** [tickets:#2700] log: coredump when stop cluster**
**Status:** unassigned
**Milestone:** 5.18.01
**Created:** Wed Nov 22, 2017 08:43 AM UTC by Canh Truong
**Last Updated:** Wed Nov 22, 2017 08:43 AM UTC
**Owner:** nobody
**Attachments:**
-
- **status**: accepted --> duplicate
- **assigned_to**: Canh Truong --> nobody
- **Blocker**: --> False
- **Milestone**: 5.17.08 --> future
- **Comment**:
The ER already converted to WA in other ticket
---
** [tickets:#1888] log: ER in syslog if changing attribute of stream after
writing
- **status**: accepted --> invalid
- **assigned_to**: Canh Truong --> nobody
- **Blocker**: --> False
- **Milestone**: 5.17.08 --> future
- **Comment**:
Discuss with Lennart and get the point: "
The logMaxLogrecsize can be found in the log service configuration object but
the
- **status**: unassigned --> invalid
- **Blocker**: --> False
- **Comment**:
>From the log PR document, section 3.5.2.2:
*"After the deletion of the value of this attribute, the ownership of all
current log files won't be changed and behavior will be kept as previous, i.e:
new opened log file
- **status**: assigned --> invalid
- **assigned_to**: Canh Truong --> nobody
- **Blocker**: --> False
- **Comment**:
The user has to make sure that the group name and group id are created the same
in both node
---
** [tickets:#1730] LOG: group ownership of log file is not correct after
- **status**: accepted --> review
---
** [tickets:#2670] log: log agent may crash after recovery fails in log api**
**Status:** review
**Milestone:** 5.18.01
**Created:** Tue Nov 07, 2017 03:21 AM UTC by Canh Truong
**Last Updated:** Tue Nov 07, 2017 03:21 AM UTC
**Owner:** Canh Truong
In
---
** [tickets:#2670] log: log agent may crash after recovery fails in log api**
**Status:** accepted
**Milestone:** 5.18.01
**Created:** Tue Nov 07, 2017 03:21 AM UTC by Canh Truong
**Last Updated:** Tue Nov 07, 2017 03:21 AM UTC
**Owner:** Canh Truong
In log api, the client is deleted
1 - 100 of 124 matches
Mail list logo
