locked
some theoretics explanations needed RRS feed

  • Question

  • Good day everyone.

    i have to make some custom MP for monitoring some application.

    i create one DS for powershell script, one Probe Action for on demand detection, one Monitor Type 2 state.

    i use many monitors with different PS Scripts to monitor diferent properties of application.

    in production i freqently got this error

    can it be because that i use one monitor type with all monitors?

    should i create one Monitor type for each monitor? should i create one DS for each Monitor type?

    what best parctice to make custom MP with several (about 10) PS Scripted Monitors on loaded system?

    AND one more question.

    on examples i saw that PropertyBag Object can contains many objects or values.

    how can it be used except just output those on alert string or monitor description ?

    Error description:

    The PowerShell script failed with below exception
    
    System.Management.Automation.Runspaces.InvalidPipelineStateException:
    Cannot invoke pipeline because it has been invoked earlier.
    at System.Management.Automation.Runspaces.PipelineBase.CoreInvoke
    (IEnumerable input, Boolean syncCall)
    at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable
    input)
    at System.Management.Automation.Runspaces.Pipeline.Invoke()
    at
    Microsoft.EnterpriseManagement.Modules.PowerShell.RunspaceController.RunScript
    (String scriptName, String scriptBody, Dictionary`2 parameters,
    PowerShellOutputType outputType, Int32 serializationDepth, IModuleDebug
    iModuleDebug)
    
    
    
    Script Name: chkDiagSvc.ps1
    
    
    One or more workflows were affected by this.
    
    
    Workflow name: ITeco.HPDiagnostics.ServerServiceMonitor
    
    ------------------------------------------------------------------------------
    The PowerShell script failed with below exception
    
    System.Management.Automation.Runspaces.InvalidPipelineStateException:
    Cannot invoke pipeline because it has been invoked earlier.
    at System.Management.Automation.Runspaces.PipelineBase.CoreInvoke
    (IEnumerable input, Boolean syncCall)
    at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable
    input)
    at System.Management.Automation.Runspaces.Pipeline.Invoke()
    at
    Microsoft.EnterpriseManagement.Modules.PowerShell.RunspaceController.RunScript
    (String scriptName, String scriptBody, Dictionary`2 parameters,
    PowerShellOutputType outputType, Int32 serializationDepth, IModuleDebug
    iModuleDebug)
    
    
    
    Script Name: DiagPortsDisc.ps1
    
    
    One or more workflows were affected by this.
    
    
    Workflow name: ITeco.HPDiagnostics.Ports.Discovery
    
    -------------------------------------------------------------------------
    The PowerShell script failed with below exception
    
    System.Management.Automation.Runspaces.InvalidPipelineStateException:
    Cannot invoke pipeline because it has been invoked earlier.
    at System.Management.Automation.Runspaces.PipelineBase.CoreInvoke
    (IEnumerable input, Boolean syncCall)
    at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable
    input)
    at System.Management.Automation.Runspaces.Pipeline.Invoke()
    at
    Microsoft.EnterpriseManagement.Modules.PowerShell.RunspaceController.RunScript
    (String scriptName, String scriptBody, Dictionary`2 parameters,
    PowerShellOutputType outputType, Int32 serializationDepth, IModuleDebug
    iModuleDebug)
    
    
    
    Script Name: chkXML.ps1
    
    
    One or more workflows were affected by this.
    
    
    Workflow name: ITeco.HPDiagnostics.xmlServerStateMonitor
    

    Thursday, January 22, 2015 9:41 AM

All replies