- **Comment**:

Tried to reproduce with chengeset 8611 anf 6.1.0 GCC by running 2N application 
campaign.
I did not observe any crash.



---

** [tickets:#2004] SMF: smfd crashed when triggered campaign with gcc 6.1**

**Status:** unassigned
**Milestone:** 5.0.2
**Created:** Tue Sep 06, 2016 08:35 AM UTC by Madhurika Koppula
**Last Updated:** Thu Jan 05, 2017 06:48 AM UTC
**Owner:** nobody
**Attachments:**

- [smf.tgz](https://sourceforge.net/p/opensaf/tickets/2004/attachment/smf.tgz) 
(1.6 MB; application/octet-stream)


**Environment Details:**

OS : Suse 64bit
Changeset : 7997 ( 5.1.FC)
Setup : 4 nodes ( 2 controllers and 2 payloads with headless feature disabled & 
1PBE enabled ).
GCC version : 6.1

**Note: Crash not observed with gcc 4.8 compiled rpms**

**summary:**

smfd got crashed due to segfault on active controller.

**Steps followed & Observed behaviour:**

Test SGupgrade of 2N model with valid configurations.

**Observations:**

Active controller went for reboot due to avadown for smfd.

Below is the snippet of syslog on active controller:

Sep  6 11:52:19 SLES-M-SLOT-1 osafsmfd[3745]: NO 
SmfProcedureThread::getImmProcedure, IMM data for procedure 
safSmfProc=amfClusterProc-1,safSmfCampaign=Campaign2,safApp=safSmfService not 
found
Sep  6 11:52:19 SLES-M-SLOT-1 osafimmnd[3661]: NO Implementer connected: 20 
(safSmfProc1) <662, 2010f>
Sep  6 11:52:19 SLES-M-SLOT-1 osafsmfd[3745]: NO PROC: Start upgrade procedure 
safSmfProc=amfClusterProc-1
Sep  6 11:52:19 SLES-M-SLOT-1 osafsmfd[3745]: NO PROC: Start procedure init 
actions

Sep  6 11:52:19 SLES-M-SLOT-1 osafamfnd[3726]: NO 
'safComp=SMF,safSu=SC-1,safSg=2N,safApp=OpenSAF' faulted due to 'avaDown' : 
Recovery is 'nodeFailfast'

**Sep  6 11:52:19 SLES-M-SLOT-1 osafamfnd[3726]: ER 
safComp=SMF,safSu=SC-1,safSg=2N,safApp=OpenSAF Faulted due to:avaDown Recovery 
is:nodeFailfast**

Sep  6 11:52:19 SLES-M-SLOT-1 osafamfnd[3726]: Rebooting OpenSAF NodeId = 
131343 EE Name = , Reason: Component faulted: recovery is node failfast, 
OwnNodeId = 131343, SupervisionTime = 60

Below is the snippet of osafsmfd trace on active controller:
============================================================================
Sep  6 11:52:19.808986 osafsmfd [3745:SmfUpgradeProcedure.cc:0741] TR 
SmfUpgradeProcedure::calculateRollingSteps:calculateRollingSteps new SW install 
step added safSmfStep=0003 (with no act/deact unit) for node 
safAmfNode=PL-4,safAmfCluster=myAmfCluster
Sep  6 11:52:19.808995 osafsmfd [3745:SmfUpgradeProcedure.cc:1876] >> 
addStepModifications
Sep  6 11:52:19.809002 osafsmfd [3745:SmfUpgradeProcedure.cc:1931] >> 
addStepModificationsNode
Sep  6 11:52:19.809008 osafsmfd [3745:imma_om_api.c:0160] >> saImmOmInitialize
Sep  6 11:52:19.809015 osafsmfd [3745:imma_om_api.c:0186] TR OM client version 
A.2.1
Sep  6 11:52:19.809021 osafsmfd [3745:imma_om_api.c:0228] >> initialize_common
Sep  6 11:52:19.809026 osafsmfd [3745:imma_init.c:0275] >> imma_startup: use 
count 1
Sep  6 11:52:19.809032 osafsmfd [3745:imma_init.c:0298] << imma_startup: use 
count 2
Sep  6 11:52:19.809040 osafsmfd [3745:imma_om_api.c:0246] T2 IMMA library 
syncronous timeout set to:30000
Sep  6 11:52:19.809263 osafsmfd [3745:imma_om_api.c:0349] T1 Trying to add OM 
client id:727 node:2010f
Sep  6 11:52:19.809280 osafsmfd [3745:imma_om_api.c:0442] << initialize_common
Sep  6 11:52:19.809287 osafsmfd [3745:imma_om_api.c:0214] << saImmOmInitialize
Sep  6 11:52:19.809293 osafsmfd [3745:imma_om_api.c:0931] >> 
saImmOmAdminOwnerInitialize
Sep  6 11:52:19.811060 osafsmfd [3745:imma_om_api.c:1143] T1 Admin owner init 
successful
Sep  6 11:52:19.811076 osafsmfd [3745:imma_om_api.c:1144] << 
saImmOmAdminOwnerInitialize
Sep  6 11:52:19.811083 osafsmfd [3745:imma_om_api.c:5528] >> 
saImmOmAccessorInitialize
Sep  6 11:52:19.811091 osafsmfd [3745:imma_om_api.c:5626] << 
saImmOmAccessorInitialize
Sep  6 12:21:09.873661 osafsmfd [2421:ncs_main_pub.c:0220] TR
NCS:PROCESS_ID=2421

Attachments:
Active Controller:
1)syslog
2)osafsmfd, osafsmfnd traces.
3)osafimmnd traces.



---

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

Reply via email to