Handling of ePO client tasks in the local command line
Last Modified: 2023-03-06 14:59:56 Etc/GMT
Affected Products
Languages:
This article is available in the following languages:
Trellix CEO, Bryan Palma, explains the critical need for security that’s always learning.
As per Gartner, "XDR is an emerging technology that can offer improved threat prevention, detection and response."
Trellix announced the establishment of the Trellix Advanced Research Center to advance global threat intelligence.
Trellix Advanced Research Center analyzes threat data on ransomware, nation-states, sectors, vectors, LotL, MITRE ATT&CK techniques, and emails.
After December 1, 2024, please log in to the Thrive Portal for support, knowledge articles, tools, and downloads. For information about using the Thrive Portal, view the Trellix Thrive Portal User Guide.
Handling of ePO client tasks in the local command line
Technical Articles ID:
KB88735
Last Modified: 2023-03-06 14:59:56 Etc/GMT Environment
Endpoint Security for Linux Threat Prevention (ENSLTP) 10.x
Summary
In ENSLTP, ePolicy Orchestrator (ePO) scheduled tasks are listed in the local command line only while the task is running. This behavior is by design. The following example shows how to check the status of tasks from the command line. In this example, a client task named ePO-ODS-Task is running. 2017-02-14 13:05:00.768 (2678.2678) scheduler.Info: Scheduler: Invoking task [ePO-ODS-Task]... 2017-02-14 13:05:00.768 (2678.2678) scheduler.Info: The task ePO-ODS-Task becomes active |Index Task Name Task Type Task Status Last Run | ----------------------------------------------------------------------------------------------------- |1 quick scan ODS Not Started Not Applicable | |2 full scan ODS Not Started Not Applicable | |3 Default Client Update task DAT and Engine Update Completed 13/02/17 15:15:01 UTC | |4 ePO-ODS-Task ODS Running 14/02/17 04:05:00 UTC | ----------------------------------------------------------------------------------------------------- When a client task has finished, the command does not list the task anymore. As shown in the following example, the ePO-ODS-Task client task is no longer listed after it has finished. |Index Task Name Task Type Task Status Last Run | ----------------------------------------------------------------------------------------------------- |1 quick scan ODS Not Started Not Applicable | |2 full scan ODS Not Started Not Applicable | |3 Default Client Update task DAT and Engine Update Completed 13/02/17 15:15:01 UTC | ----------------------------------------------------------------------------------------------------- To view summary information for an ePO on-demand scan task that has finished, locate the log for the task available in the local directory … EVENT = ODS_STOP | NAME = ePO-ODS-Task | TIME = 1487046365 | USER = 0 EVENT = ODS_SUMMARY | Task Name : ePO-ODS-Task Start time : 14/02/17 04:05:01 UTC End time : 14/02/17 04:26:05 UTC Total Requests : 200668 No of files skipped : 47188 No. of Good files : 149454 No. of Cache hit : 4017 No of Files Excluded : 0 No. of Infections : 0 Timeout : 5 ScanError : 4 No of files cleaned : 0 No of files deleted : 0 Time taken : 1264.880372s Engine version : 5800.7501 DAT version : 8437.0 INFO ScanFactory [2876] ODS Scan Manager is shutting down gracefully Affected ProductsLanguages:This article is available in the following languages: |
|