Middleware that provides libraries, GUI, and code generator to design multi-node (clustered) applications that are highly available, redundant, and scalable. Provides sub-second node and application fault detection and failover, and useful application libraries including distributed hash tables (checkpoint), event, logging, and communications. Implements SA-Forum APIs where applicable. Used anywhere reliability is a must -- like telecom, wireless, defense and enterprise computing. Download stable release with installer from: ftp.openclovis.com
Discription of the Problem
Please look into this below email conversation , this will describe the problem
Mail from ME : TIPC Problem:
While starting the SAF Platform ( i.e. executing asp ) , we were getting error as the TIPC module was not installed.We looked up in the tickets in the GITHUB and found that there were multiple reports of such problem.
In response to the above mail :
You are right, VK. We need to be idiot proof.
Marshall from SAIC figured this out as well, We do have the logs for tipc build failure (like for 1.7.7) and it would be inside logs during the installation directory.But its considered benign and we proceed as we assume (incorrectly) that the end result would be a success since the customer might have tipc with the kernel (2.0 and others and with CONFIG_TIPC enabled).
I agree that these errors need to be transparent and because 1.7.7 tipc (stable version) isn't compatible with recent kernels,
we can probably print an error and walk the user through the possible solutions.
As I mentioned, they can raise a bug and assign it to Minh to get this resolved.
The installation should just work and if it doesn't, the user should be intimated.
In this case, the logs should have the tipc build failure but its ignored as its considered benign before continuing with the installation.
Discription of the Problem Please look into this below email conversation , this will describe the problem
Mail from ME : TIPC Problem: While starting the SAF Platform ( i.e. executing asp ) , we were getting error as the TIPC module was not installed.We looked up in the tickets in the GITHUB and found that there were multiple reports of such problem.
In response to the above mail : You are right, VK. We need to be idiot proof. Marshall from SAIC figured this out as well, We do have the logs for tipc build failure (like for 1.7.7) and it would be inside logs during the installation directory.But its considered benign and we proceed as we assume (incorrectly) that the end result would be a success since the customer might have tipc with the kernel (2.0 and others and with CONFIG_TIPC enabled).
I agree that these errors need to be transparent and because 1.7.7 tipc (stable version) isn't compatible with recent kernels, we can probably print an error and walk the user through the possible solutions.
As I mentioned, they can raise a bug and assign it to Minh to get this resolved.
The installation should just work and if it doesn't, the user should be intimated. In this case, the logs should have the tipc build failure but its ignored as its considered benign before continuing with the installation.
Regards, -Karthick