DX Unified Infrastructure Management

  • 1.  Best practice for Robot Inactive alerts

    Posted Jan 12, 2017 09:21 AM

    Hi Guys,

     

    We know that because of communication issue between hub and robot we receive the robot inactive alert.

     

    In my case, alert is closed and now Windows and network team is saying that there was no issue from platform level or from network level. Alerts are no more on the console now.

     

    How do i can find the root cause now?

     

    below are some lines from the controller.log file from couple of servers.

     

    Jan  2 06:00:29:739 [1476] Controller:  Loglevel = 0, Logfile = controller.log
    Jan  2 06:00:29:755 [1476] Controller:  Running as user SYSTEM
    Jan  2 06:00:29:755 [1476] Controller: -----
    Jan  2 06:00:29:755 [1476] Controller: Stopping processes from previous run
    Jan  2 06:00:29:755 [1476] Controller: ProcessControl: Sending ^C signal to spooler (2960)...
    Jan  2 06:00:29:755 [1476] Controller: ProcessControl: Unable to send stop signal to process spooler (2960)
    Jan  2 06:00:29:755 [1476] Controller: ProcessControl: Process 2960 not found
    Jan  2 06:00:29:755 [1476] Controller: ProcessControl: Sending ^C signal to processes (5652)...
    Jan  2 06:00:29:755 [1476] Controller: ProcessControl: Unable to send stop signal to process processes (5652)
    Jan  2 06:00:29:755 [1476] Controller: ProcessControl: Process 5652 not found
    Jan  2 06:00:29:755 [1476] Controller: ProcessControl: Sending ^C signal to ntservices (3748)...
    Jan  2 06:00:29:755 [1476] Controller: ProcessControl: Unable to send stop signal to process ntservices (3748)
    Jan  2 06:00:29:755 [1476] Controller: ProcessControl: Process 3748 not found
    Jan  2 06:00:29:755 [1476] Controller: ProcessControl: Sending ^C signal to ntevl (3356)...
    Jan  2 06:00:29:755 [1476] Controller: ProcessControl: Unable to send stop signal to process ntevl (3356)
    Jan  2 06:00:29:755 [1476] Controller: ProcessControl: Process 3356 not found
    Jan  2 06:00:29:755 [1476] Controller: ProcessControl: Sending ^C signal to hdb (6888)...
    Jan  2 06:00:29:755 [1476] Controller: ProcessControl: Unable to send stop signal to process hdb (6888)
    Jan  2 06:00:29:755 [1476] Controller: ProcessControl: Process 6888 not found
    Jan  2 06:00:29:755 [1476] Controller: ProcessControl: Sending ^C signal to cdm (4468)...
    Jan  2 06:00:29:755 [1476] Controller: ProcessControl: Unable to send stop signal to process cdm (4468)
    Jan  2 06:00:29:755 [1476] Controller: ProcessControl: Process 4468 not found
    Jan  2 06:00:29:755 [1476] Controller: Controller on "HOSTNAME" port 48000 started

     

    Regards,

    IK



  • 2.  Re: Best practice for Robot Inactive alerts

    Broadcom Employee
    Posted Jan 12, 2017 09:27 AM

    with loglevel 0 logs from the time of the issue you will probably not be able to tell.

    You would also need loglevel 3 hubs logs form the same time as the alarms actually come from the hub and not the robot.

    Could possibly check the windows event logs and see if the process was stopped or other issue were happening at the time.



  • 3.  Re: Best practice for Robot Inactive alerts

    Posted Jan 13, 2017 08:39 AM