Description

In a rare case, jlaunchd fails to turn on sampling process when a new configuration related to inline-jflow configuration is pushed. The commit completes but "show system process extensive" does not list sampling.

Symptoms

The commit is successful, but the following error is reported in the log:

Apr  3 12:10:39  r1 mgd[57131]: %INTERACT-6-UI_COMMIT_PROGRESS: Commit operation in progress: cannot signal 'Traffic sampling control process', signal 1, no pid
Apr  3 12:10:39  r1 mgd[57131]: %INTERACT-6-UI_COMMIT_PROGRESS: Commit operation in progress:  notifying rmopd(25)

Also, 'show system process extensive' does not list the samplings.

Solution

In a rare case, jlaunchd fails to turn on the sampling process when a new configuration related to inline-jflow configuration is pushed.

This can happen if multiple mgd sessions are running and the sampling is turned on for the first time.

Below is an example of the new inline-jlfow configuration which causes the issue:

[edit groups]
  ABC { ... }
  IFCS-SAMPLING {
      interfaces {
          <ae*> {
              unit <*> {
                  family mpls {
                      filter {
                          input MPLS-SAMPLE;
                          output MPLS-SAMPLE;
                      }
                  }
              }
          }
      }
  }
[edit chassis]
  apply-groups [ FPCS-SAMPLING-TABLE-SIZE FPCS-SAMPLING-INSTANCE ];
[edit]
  services {
      flow-monitoring {
          version-ipfix {
              template INLINE-FLOW-MPLS-TEMPL {
                  mpls-ipv4-template {
                      label-position [ 1 2 3 ];
                  }
              }
          }
      }
  }
[edit interfaces]
  apply-groups IFCS-SAMPLING;
[edit forwarding-options]
   sampling {
       instance {
           INLINE-FLOW {
               input {
                   rate 5000;
                   run-length 0;
                   max-packets-per-second 20000;
               }
               family mpls {
                   output {
                       flow-server 142.95.80.91 {
                           port 9996;
                           version-ipfix {
                               template {
                                   INLINE-FLOW-MPLS-TEMPL;
                               }
                           }
                       }
                       inline-jflow {
                           source-address 142.93.140.13;
                       }
                   }
               }
           }
       }
   }
[edit firewall]
    family mpls {
        filter MPLS-SAMPLE {
            term default {
                then {
                    count mpls-in;
                    sample;
                    accept;
                }
            }
        }
    }

The issue is recovered by executing 'commit full'.

The following logs appear when the new process is initiated after the 'commit full'.

Apr  3 14:14:59  man50-br-cor-r2 mgd[56110]: %INTERACT-6-UI_COMMIT_PROGRESS: Commit operation in progress: cannot signal 'Traffic sampling control process', signal 1, no pid
Apr  3 14:14:59  man50-br-cor-r2 mgd[56110]: %INTERACT-6-UI_COMMIT_PROGRESS: Commit operation in progress: signaling 'Sampling route record process', pid 56606, signal 1, status 0 with notification errors disabled