[Openais] Problems with OpenAis version 0.81

[Cohen-Sason Daniel-BDC021]

Hi Steve.

Thanks for the quick response!
I'm sorry, but I forgot to attach the log I generated.

My hostname is CENTOS, and I set this name at the saAmfNodeClmNode
directive (Should it be at the safAmfNode?)

I'm also logged in as root with root group.

I verified and all the 3 files are executables with 755.

I tried to change the timeouts to 5000 and it didn't help.

Attached please find the fixed configuration files and the log.

Hope this will be help you to find out the problem.

Thanks,

Daniel.


-----Original Message-----
From: Steven Dake [mailto:sdake at redhat.com] 
Sent: Wednesday, September 12, 2007 9:14 PM
To: Cohen-Sason Daniel-BDC021
Cc: openais at lists.osdl.org
Subject: Re: [Openais] Problems with OpenAis version 0.81

Without logs it is difficult to tell what went wrong.

I would verify the following things:

You a node that has name service resolution to CENTOS.  That is required
by the "safAmfNode = AMF1" directive.  If this doesn't match, testamf1
will never be started.  Put some kind of log output in testamf1 to
verify it is actually started by AMF.  If it isn't started, this is
likely the cause of the problem.

verify:
you have mode 755 clc_cli_script in /tmp/aisexample
you have mode 755 openais-instantiate in /tmp/aisexample
you have mode 755 testamf1 in /tmp/aisexample

I have noticed sometimes the default time values shipped in amf.conf do
not work very well with some applications resulting in false positive
failure detections.  Try changing them as follows:

                             saAmfCompDefaultClcCliTimeout = 5000
                             saAmfCompDefaultCallbackTimeOut = 5000     
                             saAmfHealthcheckPeriod = 5000

please send the log file generated by AIS.

Regards
-steve

On Wed, 2007-09-12 at 08:45 +0300, Cohen-Sason Daniel-BDC021 wrote:
> Hello
> 
> 
>  
> 
> We, at Motorola, are trying to upgrade to Ver 0.81 from Ver 0.70.
> 
>  
> 
> The reason why we do it is because we encounter an unstable behavior
> with 0.70, and hope that 0.81 will be better.
> 
>  
> 
> I first started by trying to run the "amfexample1", but for some
> reason, the readiness states of the components are always becoming
> OUT_OF_SERVICE (after I run: ./aisexec -f).
> 
>  
> 
> I followed the steps which are described in README.AMF.
> 
>  
> 
> I also noticed the bindnetaddr should be set, or the instantiation
> won't even start.
> 
>  
> 
> Attached please find the log and the configuration files
> from /tmp/aisexample folder.
> 
>  
> 
> I really hope you can help us.
> 
>  
> 
> Please advice,
> 
>  
> 
> Daniel
> 
> ________________
> Daniel Cohen-Sason
> MCIL, Design Center, Public Safety.
> Multi-Net-Mobility (MNM).
> Office:  +972-3-5658548 
> Private: +972-57-5658548 (8548)
> 
> Daniel.Cohen at motorola.com
> "The significant problems we have cannot be solved at the same level
> of thinking with which we created them." [Albert Einstein]
> 
> 
>  
> 
> 
> _______________________________________________
> Openais mailing list
> Openais at lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/openais

-------------- next part --------------
A non-text attachment was scrubbed...
Name: amf.conf
Type: application/octet-stream
Size: 5251 bytes
Desc: amf.conf
Url : http://lists.linux-foundation.org/pipermail/openais/attachments/20070913/0e83d884/amf-0001.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: openais.conf
Type: application/octet-stream
Size: 469 bytes
Desc: openais.conf
Url : http://lists.linux-foundation.org/pipermail/openais/attachments/20070913/0e83d884/openais-0002.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: openais.log
Type: application/octet-stream
Size: 31801 bytes
Desc: openais.log
Url : http://lists.linux-foundation.org/pipermail/openais/attachments/20070913/0e83d884/openais-0003.obj