I never had any feedback on this, which is a little disheartening.  In any 
case, we continued to troubleshoot the issue, and it appears there is an 
uninitialized variable in the source code that is causing the error.
The file is immnd_main.c, and the line number is 355.
We added the line: fds[FD_CLM].revents = 0;

This resolved our issue, and we were able to bring up opensaf 5.2.   For the 
record, we were never able to bring up opensaf 5.2, without this fix, on our 
32-bit systems.  We did also test this out on our 64-bit systems, and found 
that we were about 50/50 when staring OpenSAF - sometimes is started, and 
sometimes it failed, without this fix.   Once this fix was applied, both our 
32-bit and 64-bit systems started consistently.

Is there an open ticket for this issue?  Also, with the just announced release 
of OpenSaf 5.2.1, will there be an update to capture this?
How are high-priority fixes applied to OpenSAF?



From: Carroll, James R (US)
Sent: Friday, July 21, 2017 5:07 PM
To: opensaf-users@lists.sourceforge.net
Subject: opensaf 5.2, not starting on 32-bit linux platform


We have recently built and upgraded to opensaf 5.2.  We were previously running 
using opensaf 5.0.
We compiled opensaf as 32-bit applications.  We are running on a 32-bit Redhat 
OS (v6.5).

We have been unable to start opensaf successfully, it appears to be a timing 
issue between IMM and CLM.
The code that is failing appears to be a new feature added to 5.2, reference 
the ticket number below.
The file is immnd_main.c, line number 435, failing on saClmDispatch() call. We 

Ticket Information:
1640 - imm agent changes for integrating IMM with CLMS

Has anyone built opensaf 5.2 as a 32-bit application, and been able to run it 


Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Opensaf-users mailing list

Reply via email to