Hi Vu, Is current opensaf-4.7.x (4.7.0-1) and default (5.0.M0-1 ) in-service upgrade working for you ?
-AVM On 3/3/2016 2:32 PM, A V Mahesh wrote: > Hi Vu, > > You just take > > (5.0.M0-1 ) : hg clone http://hg.code.sf.net/p/opensaf/staging & `hg > update default` > (4.7.0-1) : `hg clone http://hg.code.sf.net/p/opensaf/staging` & `hg > update opensaf-4.7.x` > > Bring 4.7.0-1) node as Active , then try to bring 5.0.M0-1 node > as Standby , you will see the problem always reproducible. > > - AVM > > > On 3/3/2016 1:36 PM, Vu Minh Nguyen wrote: >> Hi Mahesh, >> >> What is the changeset number of default (5.0.M0-1 ) that you were using? >> And can you send me the trace log of osaflogd on standby node? >> >> Thanks. >> >> Regards, Vu. >>> -----Original Message----- >>> From: A V Mahesh [mailto:mahesh.va...@oracle.com] >>> Sent: Thursday, March 03, 2016 2:53 PM >>> To: opensaf-devel@lists.sourceforge.net >>> Subject: [devel] current opensaf-4.7.x (4.7.0-1) and default >>> (5.0.M0-1 ) >> in-service >>> upgrade is not working >>> >>> Hi All, >>> >>> With current opensaf-4.7.x (4.7.0-1) and default (5.0.M0-1 ) >>> in-service upgrade is not working >>> the default (5.0.M0-1 ) Node is not able to joining cluster as Standby >>> with following error : >>> >>> ================================================================== >>> =============================================== >>> >>> Mar 3 13:16:28 SC-1 osafimmnd[12072]: NO NODE STATE-> >>> IMM_NODE_W_AVAILABLE >>> Mar 3 13:16:28 SC-1 osafimmnd[12072]: NO SERVER STATE: >>> IMM_SERVER_SYNC_PENDING --> IMM_SERVER_SYNC_CLIENT >>> Mar 3 13:16:28 SC-1 osafimmd[12061]: NO SBY: New Epoch for IMMND >>> process at node 2020f old epoch: 2 new epoch:3 >>> Mar 3 13:16:28 SC-1 osafimmd[12061]: NO IMMND coord at 2020f >>> Mar 3 13:16:28 SC-1 osafimmnd[12072]: NO NODE STATE-> >>> IMM_NODE_FULLY_AVAILABLE 2676 >>> Mar 3 13:16:28 SC-1 osafimmnd[12072]: NO RepositoryInitModeT is >>> SA_IMM_INIT_FROM_FILE >>> Mar 3 13:16:28 SC-1 osafimmnd[12072]: WA IMM Access Control mode is >>> DISABLED! >>> Mar 3 13:16:28 SC-1 osafimmnd[12072]: NO Epoch set to 3 in ImmModel >>> Mar 3 13:16:28 SC-1 osafimmd[12061]: NO SBY: New Epoch for IMMND >>> process at node 2010f old epoch: 0 new epoch:3 >>> Mar 3 13:16:28 SC-1 osafimmnd[12072]: NO SERVER STATE: >>> IMM_SERVER_SYNC_CLIENT --> IMM SERVER READY >>> Mar 3 13:16:28 SC-1 osaflogd[12082]: Started >>> Mar 3 13:16:28 SC-1 osaflogd[12082]: NO LOGSV_DATA_GROUPNAME not >>> found >>> Mar 3 13:16:28 SC-1 osaflogd[12082]: NO LOG root directory is: >>> "/var/log/opensaf/saflog" >>> Mar 3 13:16:28 SC-1 osaflogd[12082]: NO LOG data group is: "" >>> Mar 3 13:16:28 SC-1 osaflogd[12082]: NO LGS_MBCSV_VERSION = 5 >>> Mar 3 13:16:28 SC-1 osafntfd[12093]: Started >>> Mar 3 13:16:29 SC-1 osafntfd[12093]: WA saLogStreamOpen_2 returns try >>> again, retries... >>> >>> ================================================================== >>> =============================================== >>> >>> >>> -AVM >>> >>> --------------------------------------------------------------------------- >>> >> --- >>> Site24x7 APM Insight: Get Deep Visibility into Application Performance >>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month >>> Monitor end-to-end web transactions and take corrective actions now >>> Troubleshoot faster and improve end-user experience. Signup Now! >>> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 >>> _______________________________________________ >>> Opensaf-devel mailing list >>> Opensaf-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/opensaf-devel > ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval _______________________________________________ Opensaf-devel mailing list Opensaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-devel
