Regarding AMF logging; The amfnd process is responsible for this logging and is by default set to allow NOTICE (and higher) level messages. On the default level NOTICE, only service unit and service instance events are logged. It was concluded to produce too much logs if the component and CSI level was logged at NOTICE. The component level lifecycle and service instance events are logged at INFO level.
So by changing the filtered logging level from NOTICE to INFO you would get more events logged. This can be done either in amfnd.conf (persistently) or in runtime with a "pkill -hup amfnd" on the host in question. /Hans On 2015-01-27 00:58, santosh satapathy wrote: > Hi, > > In one instance, doing a lock after unlock-in assigns QUIESCED state to the > SI but not to the individual components it contains. Is this behavior > correct? > > Jan 26 15:51:33 node1 osafamfnd[23468]: NO Assigning > 'safSi=testsu,safApp=TestApp' ACTIVE to > 'safSu=testsu,safSg=testsu,safApp=TestApp' > Jan 26 15:52:16 node1 osafamfnd[23468]: NO Assigned > 'safSi=testsu,safApp=TestApp' ACTIVE to > 'safSu=testsu,safSg=testsu,safApp=TestApp' > > > Jan 26 15:52:34 node1 osafamfnd[23468]: NO Assigning > 'safSi=testsu,safApp=TestApp' QUIESCED to > 'safSu=testsu,safSg=testsu,safApp=TestApp' > Jan 26 15:52:34 node1 osafamfnd[23468]: NO Assigned > 'safSi=testsu,safApp=TestApp' QUIESCED to > 'safSu=testsu,safSg=testsu,safApp=TestApp' > ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Opensaf-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-users
