[tickets] [opensaf:tickets] #682 LOG: New Active reboots when coordinator IMMND is killed in the middle of switchover

2017-12-11 Thread Srinivas Siva Mangipudy via Opensaf-tickets 
- **status**: unassigned --> assigned
- **assigned_to**: Srinivas Siva Mangipudy
- **Blocker**:  --> False



---

** [tickets:#682] LOG: New Active reboots when coordinator IMMND is killed in 
the middle of switchover**

**Status:** assigned
**Milestone:** future
**Created:** Fri Dec 20, 2013 05:27 AM UTC by Sirisha Alla
**Last Updated:** Tue Sep 20, 2016 06:04 PM UTC
**Owner:** Srinivas Siva Mangipudy
**Attachments:**

- 
[logs.tar.bz2](https://sourceforge.net/p/opensaf/tickets/682/attachment/logs.tar.bz2)
 (4.3 MB; application/x-bzip)
- 
[tic682.tgz](https://sourceforge.net/p/opensaf/tickets/682/attachment/tic682.tgz)
 (208.3 kB; application/x-compressed-tar)


The issue is observed on changeset 4733 + #220 patches corresponding to cs 4741 
and cs 4742. The test setup is a 4 node SLES 64bit VMs.The setup is single PBE 
enabled loaded with 25k objects.

SC-2(SLES-64BIT-SLOT2) is Active and IMMND coordinator is hosted on 
SC-1(SLES-64BIT-SLOT1). Controller Switchover is initiated and immnd is killed 
on SC-1. SC-1 went for reboot because of the csi set callback timeout of logd.

/var/log/messages of SC-1 and SC-2 corresponding to the above mentioned steps :

SC-2:

Dec 19 17:21:36 SLES-64BIT-SLOT2 osafamfd[3609]: NO safSi=SC-2N,safApp=OpenSAF 
Swap initiated
Dec 19 17:21:36 SLES-64BIT-SLOT2 osafamfnd[3619]: NO Assigning 
'safSi=SC-2N,safApp=OpenSAF' QUIESCED to 'safSu=SC-2,safSg=2N,safApp=OpenSAF'
Dec 19 17:21:36 SLES-64BIT-SLOT2 osafimmnd[3554]: NO Implementer disconnected 
18 <320, 2020f> (safMsgGrpService)
Dec 19 17:21:36 SLES-64BIT-SLOT2 osafimmnd[3554]: NO implementer for class 
'SaSmfCampaign' is released => class extent is UNSAFE
Dec 19 17:21:36 SLES-64BIT-SLOT2 osafimmnd[3554]: NO Implementer disconnected 
22 <319, 2020f> (safEvtService)
Dec 19 17:21:36 SLES-64BIT-SLOT2 osafimmnd[3554]: NO Implementer disconnected 
23 <3, 2020f> (safLogService)
Dec 19 17:21:36 SLES-64BIT-SLOT2 osafimmnd[3554]: NO implementer for class 
'OpenSafSmfConfig' is released => class extent is UNSAFE
Dec 19 17:21:36 SLES-64BIT-SLOT2 osafimmnd[3554]: NO implementer for class 
'SaSmfSwBundle' is released => class extent is UNSAFE
Dec 19 17:21:36 SLES-64BIT-SLOT2 osafimmnd[3554]: NO Implementer disconnected 
24 <298, 2020f> (safSmfService)
Dec 19 17:21:37 SLES-64BIT-SLOT2 osafimmnd[3554]: NO IDec 19 17:21:38 

SC-1:

SLES-64BIT-SLOT1 osafimmnd[3498]: NO Implementer disconnected 18 <0, 2020f> 
(safMsgGrpService)
Dec 19 17:21:38 SLES-64BIT-SLOT1 osafimmnd[3498]: NO implementer for class 
'SaSmfCampaign' is released => class extent is UNSAFE
Dec 19 17:21:38 SLES-64BIT-SLOT1 osafimmnd[3498]: NO Implementer disconnected 
22 <0, 2020f> (safEvtService)
Dec 19 17:21:38 SLES-64BIT-SLOT1 osafimmnd[3498]: NO Implementer disconnected 
23 <0, 2020f> (safLogService)
Dec 19 17:21:38 SLES-64BIT-SLOT1 osafimmnd[3498]: NO implementer for class 
'OpenSafSmfConfig' is released => class extent is UNSAFE
Dec 19 17:21:38 SLES-64BIT-SLOT1 osafimmnd[3498]: NO implementer for class 
'SaSmfSwBundle' is released => class extent is UNSAFE
Dec 19 17:21:38 SLES-64BIT-SLOT1 osafimmnd[3498]: NO Implementer disconnected 
24 <0, 2020f> (safSmfService)
Dec 19 17:21:39 SLES-64BIT-SLOT1 osafimmnd[3498]: NO Implementer disconnected 
20 <0, 2020f> (safLckService)
Dec 19 17:21:39 SLES-64BIT-SLOT1 osafimmnd[3498]: NO Implementer disconnected 
19 <0, 2020f> (safCheckPointService)
Dec 19 17:21:39 SLES-64BIT-SLOT1 osafimmnd[3498]: NO Implementer disconnected 
21 <0, 2020f> (safClmService)
Dec 19 17:21:39 SLES-64BIT-SLOT1 osafimmpbed: WA PBE lost contact with parent 
IMMND - Exiting
Dec 19 17:21:39 SLES-64BIT-SLOT1 osafamfnd[3578]: NO 
'safComp=IMMND,safSu=SC-1,safSg=NoRed,safApp=OpenSAF' faulted due to 'avaDown' 
: Recovery is 'componentRestart'
Dec 19 17:21:39 SLES-64BIT-SLOT1 osafntfimcnd[3829]: ER saImmOiDispatch() Fail 
SA_AIS_ERR_BAD_HANDLE (9)
Dec 19 17:21:39 SLES-64BIT-SLOT1 osafamfd[3565]: NO Re-initializing with IMM
Dec 19 17:21:39 SLES-64BIT-SLOT1 osafimmd[3488]: NO IMMND coord at 2020f
mplementer disconnected 20 <303, 2020f> (safLckService)
..

Dec 19 17:21:49 SLES-64BIT-SLOT1 osafimmnd[3953]: NO Implementer connected: 40 
(OpenSafImmPBE) <0, 2020f>
Dec 19 17:21:49 SLES-64BIT-SLOT1 osafamfd[3565]: NO Finished re-initializing 
with IMM
Dec 19 17:21:50 SLES-64BIT-SLOT1 osafimmnd[3953]: NO PBE-OI established on 
other SC. Dumping incrementally to file imm.db
Dec 19 17:23:40 SLES-64BIT-SLOT1 osafamfnd[3578]: NO 
'safComp=LOG,safSu=SC-1,safSg=2N,safApp=OpenSAF' faulted due to 
'csiSetcallbackTimeout' : Recovery is 'nodeFailfast'
Dec 19 17:23:40 SLES-64BIT-SLOT1 osafamfnd[3578]: ER 
safComp=LOG,safSu=SC-1,safSg=2N,safApp=OpenSAF Faulted due 
to:csiSetcallbackTimeout Recovery is:nodeFailfast
Dec 19 17:23:40 SLES-64BIT-SLOT1 osafamfnd[3578]: Rebooting OpenSAF NodeId = 
131343 EE Name = , Reason: Component faulted: recovery is node failfast, 
OwnNodeId = 131343, SupervisionTime = 60
Dec 19 17:23:40 SLES-64BIT-SLOT1 opensaf_reboot: Rebooting local node;

[tickets] [opensaf:tickets] #2736 dtm: Add option to osaflog for specifying log directory

2017-12-11 Thread Anders Widell via Opensaf-tickets 



---

** [tickets:#2736] dtm: Add option to osaflog for specifying log directory**

**Status:** unassigned
**Milestone:** 5.18.01
**Created:** Mon Dec 11, 2017 02:02 PM UTC by Anders Widell
**Last Updated:** Mon Dec 11, 2017 02:02 PM UTC
**Owner:** nobody


Add an option --logdir that makes it possible to specify the directory where 
the command shall search for log files. This makes it possible to use the 
command offline. Since the option is supposed to be used offline, the --flush 
option shall not be impled when using the --logdir option.

Also, add a --help option for printing command help.


---

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.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2709 dtm: Support pretty-printing log messages using the osaflog command

2017-12-11 Thread Anders Widell via Opensaf-tickets 
- **status**: review --> fixed
- **Comment**:

commit 5a539d23583a19a521b2f946391d9b557dce5296 (HEAD -> develop, 
origin/develop)
Author: Anders Widell 
Date:   Mon Dec 11 12:40:54 2017 +0100

dtm: Support pretty-printing OpenSAF logs using the osaflog command [#2709]

Add support to the osaflog command for parsing and pretty-printing the 
OpenSAF
log messages. Initially, we only support simple pretty-printing by removing
information which is not frequently needed when reading the logs. In future
ticket(s), we can also add support for filtering log messages.

The following example command will print the MDS log:

osaflog mds.log




---

** [tickets:#2709] dtm: Support pretty-printing log messages using the osaflog 
command**

**Status:** fixed
**Milestone:** 5.18.01
**Created:** Tue Nov 28, 2017 04:07 PM UTC by Anders Widell
**Last Updated:** Fri Dec 01, 2017 09:56 AM UTC
**Owner:** Anders Widell


Add support to the osaflog command for parsing and pretty-printing the OpenSAF 
log messages. Initially, we can support pretty-printing to remove information 
which is not frequently needed when reading the logs. In future ticket(s), we 
can also add support for filtering log messages.


---

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.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2646 dtm: Add a tool for syncing log messages to disk

2017-12-11 Thread Anders Widell via Opensaf-tickets 
- **status**: accepted --> fixed
- **Comment**:

commit 77d30164c9c934e0eb323acb0655a24faebd1df1 (HEAD -> develop, 
origin/develop, ticket-2646)
Author: Anders Widell 
Date:   Mon Dec 11 10:49:42 2017 +0100

osaf: Flush OpenSAF internal log entries before rebooting [#2646]

Flush log entries in the OpenSAF internal log server from memory to disk 
before
rebooting the local node, to prevent loss of log messages.

commit 8e45a519b8f607b45093e9d69d0de39120332e26
Author: Anders Widell 
Date:   Mon Dec 11 10:49:42 2017 +0100

dtm: Add flush command for writing buffered log messages to disk [#2646]

Add a new protocol message that can be recevied on the UNIX socket, that 
causes
osaftransportd to write all buffered log messages from memory to disk.

commit 0668553762b6ee21b5f9d684fd922bccb063cfe6
Author: Anders Widell 
Date:   Mon Dec 11 10:49:42 2017 +0100

base: Add support for recvfrom and sendto operations on UnixSocket [#2646]

Add new UnixSocket methods for sending and receiving with a sockaddr_un 
address
parameter. Also add support for abstract UNIX socket addresses and for 
providing
a raw sockaddr_un address to UnixSocket.




---

** [tickets:#2646] dtm: Add a tool for syncing log messages to disk**

**Status:** fixed
**Milestone:** 5.18.01
**Created:** Thu Oct 19, 2017 11:20 AM UTC by Anders Widell
**Last Updated:** Mon Nov 20, 2017 03:51 PM UTC
**Owner:** Anders Widell


Add a command-line tool that can flush and sync all log streams to disk. Use 
this tool in the opensaf_reboot script before rebooting.


---

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.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2726 smf: Smfnd does not protect global variables used in more than one thread

2017-12-11 Thread elunlen via Opensaf-tickets 
- **status**: accepted --> assigned



---

** [tickets:#2726] smf: Smfnd does not protect global variables used in more 
than one thread**

**Status:** assigned
**Milestone:** 5.18.01
**Created:** Mon Dec 04, 2017 11:29 AM UTC by elunlen
**Last Updated:** Mon Dec 04, 2017 11:29 AM UTC
**Owner:** elunlen


Several global variables (cb structure) are handled both in the main thread and 
in the mds thread but no mutex is used for protection. Make handling of global 
variables thread safe


---

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.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets