6 Replies Latest reply on Mar 2, 2015 4:06 AM by Manuel Caro

    Random problems with propagation cells

      Share This:

      Sometimes, maybe once or twice per day, some events don´t propagate from secundary cell to main cell. When it happens, I look into mcell.log and I can see:

       

      20131023 074323.063453 mcell: PROPAGATE: BMC-IMC091049E: Operation [4] propagate new event #834300 to pncell_win-pvedubb5phb failed

       

      I often close event in secundary cell, restart patrolagent and the new event propagate without problem.

       

      I modified my mcell.conf with those parameters but I still have this issue:

       

      #DestinationTransportProtocol==co

      #DestinationBufferBaseSize==5000

      #DestinationBufferSizeLimit==0

      #DestinationBufferExpandPercentage==10

      #DestinationBufferReducePercentage==50

      #DestinationBufferReconnectInterval=#1=10,#2=10,=2m

      DestinationBufferKeepWait=36000

      #DestinationBufferKeepSent=#1=3,#2=3,=2m

      DestinationBufferResendCount=10


      Have everyone had this problem?. Have I dismissed any configuration?.

       

      Thans in advance.


       

       

       

        • 1. Re: Random problems with propagation cells

          Hello, Manuel,

           

          What is the value of the MessageBufferResendCount parameter on your mcell.conf?

           

          Also, you may need to turn on tracing to get better information regarding why the propagation failed.  Unfortunately, the message above doesn't give enough info to diagnose.

           

          Carlos.

          1 of 1 people found this helpful
          • 2. Re: Random problems with propagation cells

            Thanks Carlos.

             

            It has thii value (default):

             

            #MessageBufferResendCount=1

             

            Could you tel me how to turn on tracing?

             

            Thanks in avance

            • 3. Re: Random problems with propagation cells

              Hello Manuel,

               

              I have not run into this issue.

              Do you see any error posted on the main cell?

               

              I would open an Issue with BMC Support.

               

              To enable tracing:

              ... in the mcell.conf for the secondary cell, set Trace=Yes

              ... in the mcell.trace for the secondard cell, set ALL ALL stderr

              ... recompile the seconard cell with the trace (-t) option:   mccomp -t manifest.kb
              ... restart the secondary cell.

              .

              Sorry, I wish I had a better answer for you.

              Gib.

              • 4. Re: Random problems with propagation cells

                Hello:

                 

                I have enabled the trace and I have a non-propagate event:

                 

                20131213 103023.080970 mcell: BAROC: BMC-IMC032262V: Upgrade event #301260 @0xa4a45b0 to context Refine

                20131213 103023.080977 mcell: EVTPROC: BMC-IMC090102V: Start refine on event #301260 @0xa4a45b0

                20131213 103023.082632 mcell: EVTPROC: BMC-IMC090116V: Modified slots of event #301260 @0xa4a45b0 to Rule Engine

                20131213 103023.083709 mcell: EVTPROC: BMC-IMC090116V: Modified slots of event #301260 @0xa4a45b0 to Rule Engine

                20131213 103023.084964 mcell: RULES: BMC-IMC110005V: Stop refine event #301260 @0xa4a45b0 : CONT

                20131213 103023.085101 mcell: BAROC: BMC-IMC032262V: Upgrade event #301260 @0xa4a45b0 to context Filter

                20131213 103023.085232 mcell: FILTER: BMC-IMC093102V: Event passed filters

                20131213 103023.085290 mcell: BAROC: BMC-IMC032262V: Upgrade event #301260 @0xa4a45b0 to context Engine

                20131213 103023.085297 mcell: EVTPROC: BMC-IMC090106V: Transfer event #301260 @0xa4a45b0 to Rule Engine

                20131213 103023.085321 mcell: RULES: BMC-IMC110007V: Starting transaction on event #301260 @0xa4a45b0

                20131213 103023.085371 mcell: RULES: BMC-IMC110008V: Analysing event #301260 @0xa4a45b0

                20131213 103023.086740 mcell: BAROC: BMC-IMC032263V: Upgrade data #271292 @0xa5556d8 with mc_udid "mc.SERVER_NET.12aad3af.0" to context Permanent

                 

                20131213 103023.087381 mcell: BAROC: BMC-IMC032262V: Upgrade event #301260 @0xa4a45b0 to context Permanent

                20131213 103023.087561 mcell: RULES: BMC-IMC110009V: Terminating transaction on event #301260 @0xa4a45b0

                20131213 103023.087624 mcell: COLLECT: BMC-IMC103102V: Event #301260 added to collector Active Events of set All Active Events

                20131213 103023.087648 mcell: COLLECT: BMC-IMC103103V: Event #301260 not added to collector of set Intelligent Events

                20131213 103023.087663 mcell: COLLECT: BMC-IMC103102V: Event #301260 added to collector Open of set All Events

                20131213 103023.087675 mcell: COLLECT: BMC-IMC103102V: Event #301260 added to collector Unassigned of set By User

                20131213 103023.087706 mcell: COLLECT: BMC-IMC103102V: Event #301260 added to collector Open of set By Status

                20131213 103023.087715 mcell: COLLECT: BMC-IMC103103V: Event #301260 not added to collector of set MC_Related_Events

                20131213 103023.087765 mcell: COLLECT: BMC-IMC103102V: Event #301260 added to collector Server_Balancer_Aplication of set PATROL

                20131213 103023.087775 mcell: COLLECT: BMC-IMC103103V: Event #301260 not added to collector of set Generated Incidents

                20131213 103023.087782 mcell: COLLECT: BMC-IMC103103V: Event #301260 not added to collector of set MC_SMC_Events

                20131213 103023.087788 mcell: COLLECT: BMC-IMC103103V: Event #301260 not added to collector of set Capacity Events

                20131213 103023.087812 mcell: COLLECT: BMC-IMC103102V: Event #301260 added to collector server_net of set Collector_Windows

                20131213 103023.087823 mcell: COLLECT: BMC-IMC103103V: Event #301260 not added to collector of set Collector_Unix

                20131213 103023.087830 mcell: COLLECT: BMC-IMC103103V: Event #301260 not added to collector of set Collector_BBDD

                20131213 103023.087836 mcell: COLLECT: BMC-IMC103103V: Event #301260 not added to collector of set Collector_COMUNICATIONS

                20131213 103023.087843 mcell: COLLECT: BMC-IMC103103V: Event #301260 not added to collector of set Collector_NO_OPERATION

                20131213 103023.088286 mcell: RULES: BMC-IMC110003V: Propagations [0xa4a45b0,1,['pncell_win-pvedubb5phb'],0xa4a45b0,2,[server_net]]

                20131213 103023.088335 mcell: SERVICE: BMC-IMC050133V: Registering existing destination 1 pncell_win-pvedubb5phb

                20131213 103023.088483 mcell: MESSAGES: BMC-IMC046014V: Send message #8093.2 EVENT [1569]

                20131213 103023.088534 mcell: PROPAGATE: BMC-IMC091101V: Send [11] to destination pncell_win-pvedubb5phb : status=sent

                20131213 103023.088602 mcell: SERVICE: BMC-IMC050053W: Self-connection to Cellserver_net refused

                20131213 103023.088618 mcell: EVTPROC: BMC-IMC090108V: Event #301260 @0xa4a45b0 handled

                 

                 

                 

                 

                 

                20131213 103425.128867 mcell: PROPAGATE: BMC-IMC091049E: Operation [11] propagate new event #301260 to pncell_win-pvedubb5phb failed

                 

                 

                pncell_win-pvedubb5phb is the destination cell.

                 

                 

                I had watched that the cell in server_net only try to propagate the event  ONE time (at 20131213 103425.128867), and no more tries.

                 

                After the 'propagation error' we tried many times the command 'mcontrol (mcontrol -n {cell name} -v prop) in order to PROPAGATE again all 'failed' propagations, but unfortunately without success.

                 

                Is it posibble that MessageBufferResendCount=1 rules over MessageBufferResendCount=10?

                 

                Thanks in advance.

                 

                 

                Best regards.

                • 5. Re: Random problems with propagation cells
                  Alvaro Paronuzzi

                  Hi Manuel Caro

                   

                  I have a similar problem in my BPPM environment. Could you find the cause of this propagation issue in your environment and fix it? If so, I would really appreciate if you could share your experience.

                   

                  Thanks and Regards,

                  Al

                  • 6. Re: Random problems with propagation cells

                    Hi Al,

                     

                    We can´t find the cuase for the issue, so we make a workarround. We execute a schedule task in our windows environment and we look for those events and we force the propagation manually with msend.

                     

                    Best regards.