Welcome to OCS Inventory NG community support, where you can ask questions and receive answers from other members of the community.

Please ask questions only in English or French.

Release 2.12.3 available

The official documentation can be found on https://wiki.ocsinventory-ng.org. Read it before asking your question.

rôle du "DOWNLOAD_CYCLE_LATENCY"

Bonjour,

Je souhaitais savoir à quoi sert le DOWNLOAD_CYCLE_LATENCY.

Je vous donne mon log du fichier C:\ProgramData\OCS Inventory NG\AgentDownload.txt :

Starting OCS Inventory NG Package Download and Setup Tool on Friday, June 05, 2015 15:19:51.
DOWNLOAD => Running OCS Inventory NG Download Version 2.0.5.0
DOWNLOAD => Using OCS Inventory NG FrameWork Version 2.0.5.0
DOWNLOAD => Using network connection with Communication Server
    COM PROVIDER => Loading Communication Provider <C:\Program Files (x86)\OCS Inventory Agent\ComHTTP.dll>
DOWNLOAD => Using Communication Provider <OCS Inventory NG cURL Communication Provider> Version <2.0.5.0>
DOWNLOAD => Starting new period of 10 cycles
    DOWNLOAD => Flushing package queue
DOWNLOAD => Parsing directory <C:\ProgramData\OCS Inventory NG\Agent\download> for packages
    DOWNLOAD => Verifying package <C:\ProgramData\OCS Inventory NG\Agent\download\1433510139>
DOWNLOAD => Package <1433510139> verified and added to process queue
    DOWNLOAD => Processing packages for cycle 1 on Friday, June 05, 2015 15:19:51

(téléchargment du fragment 1 + connexion au serveur par sans SSL)
    DOWNLOAD => Processing packages for cycle 2 on Friday, June 05, 2015 15:21:02
DOWNLOAD => Downloading package fragment <1433510139-2>
(téléchargment du fragment 2 + connexion au serveur par sans SSL)
    DOWNLOAD => Processing packages for cycle 3 on Friday, June 05, 2015 15:22:12
DOWNLOAD => Downloading package fragment <1433510139-3>
    COM SERVER => Initializing cURL library for getFile
    COM SERVER => Using cURL without server authentication
    COM SERVER => Disabling cURL proxy support
    COM SERVER => Disabling cURL SSL server validation support
    COM SERVER => Sending fileGet request to URL <HTTP://ocs/download/1433510139/1433510139-3>
    COM SERVER => fileGet response received <HTTP Status Code #200>
    COM SERVER => Cleaning cURL library
    DOWNLOAD => Pausing for fragment latency (10 seconds)
    DOWNLOAD => Pausing for cycle latency (60 seconds)
    DOWNLOAD => Processing packages for cycle 4 on Friday, June 05, 2015 15:23:23
DOWNLOAD => Downloading package fragment <1433510139-4>
    COM SERVER => Initializing cURL library for getFile
    COM SERVER => Using cURL without server authentication
    COM SERVER => Disabling cURL proxy support
    COM SERVER => Disabling cURL SSL server validation support
    COM SERVER => Sending fileGet request to URL <HTTP://ocs/download/1433510139/1433510139-4>
    COM SERVER => fileGet response received <HTTP Status Code #200>
    COM SERVER => Cleaning cURL library
    DOWNLOAD => Pausing for fragment latency (10 seconds)
    DOWNLOAD => Pausing for cycle latency (60 seconds)
    DOWNLOAD => Processing packages for cycle 5 on Friday, June 05, 2015 15:24:34
DOWNLOAD => Downloading package fragment <1433510139-5>
    COM SERVER => Initializing cURL library for getFile
    COM SERVER => Using cURL without server authentication
    COM SERVER => Disabling cURL proxy support
    COM SERVER => Disabling cURL SSL server validation support
    COM SERVER => Sending fileGet request to URL <HTTP://ocs/download/1433510139/1433510139-5>
    COM SERVER => fileGet response received <HTTP Status Code #200>
    COM SERVER => Cleaning cURL library
    DOWNLOAD => Pausing for fragment latency (10 seconds)
    DOWNLOAD => Pausing for cycle latency (60 seconds)
    DOWNLOAD => Processing packages for cycle 6 on Friday, June 05, 2015 15:25:44
DOWNLOAD => Building package <1433510139>
    PACKAGE => Verifying fragment files of package <1433510139>
    PACKAGE => Checking free disk space for package <1433510139>
    PACKAGE => Building ZIP for package <1433510139>
    PACKAGE => Verifying ZIP signature for package <1433510139>
    DOWNLOAD => Package <1433510139> built successfully
DOWNLOAD => Executing action <EXECUTE> for package <1433510139>
    PACKAGE => Executing command <msiexec /i Firefox-38.0.1-ach.msi /qn> for package <1433510139>
    PACKAGE => Package <1433510139> successfully executed. Command exit code is <0>
DOWNLOAD => Sending result code <SUCCESS> for package <1433510139>
    DID_CHECK => Read DeviceID <X8635-2015-06-05-09-50-35> and MACs <A0:48:1C:9B:36:BF> in file <ocsinventory.dat>
    COM SERVER => Initializing cURL library for sendRequest
    COM SERVER => Using cURL without server authentication
    COM SERVER => Disabling cURL proxy support
    COM SERVER => Disabling cURL SSL server validation support
    COM SERVER => Sending HTTP Post request to URL <http://10.1.100.66/ocsinventory>
    COM SERVER => HTTP Post response received <HTTP Status Code #200>
    COM SERVER => Cleaning cURL library
    DOWNLOAD => Result code request successfully sent
    DOWNLOAD => Pausing for fragment latency (10 seconds)
    DOWNLOAD => Pausing for cycle latency (60 seconds)
    DOWNLOAD => Processing packages for cycle 7 on Friday, June 05, 2015 15:27:51
    DOWNLOAD => Pausing for cycle latency (60 seconds)
    DOWNLOAD => Processing packages for cycle 8 on Friday, June 05, 2015 15:28:51
    DOWNLOAD => Pausing for cycle latency (60 seconds)
    DOWNLOAD => Processing packages for cycle 9 on Friday, June 05, 2015 15:29:51
    DOWNLOAD => Pausing for cycle latency (60 seconds)
    DOWNLOAD => Processing packages for cycle 10 on Friday, June 05, 2015 15:30:51
    DOWNLOAD => Pausing for cycle latency (60 seconds)
    DOWNLOAD => Pausing for period latency (1 seconds)
DOWNLOAD => Starting new period of 10 cycles
    DOWNLOAD => Flushing package queue
DOWNLOAD => Parsing directory <C:\ProgramData\OCS Inventory NG\Agent\download> for packages
DOWNLOAD => No package found, exiting
DOWNLOAD => Unloading communication provider
DOWNLOAD => Execution duration: 00:12:02.

En faite je souhaitaite savoir à quoi servent les cycles 7/8/9/10 car ils s'enchainent les uns après les autres sans aucune action effectués entre chaque..

Savez-vous le but de ces cycles ??

Merci

in OCS Inventory NG server for Unix by (2k points)

2 Answers

0 votes
Bonjour,

J'ai tout documenté ici : http://wiki.ocsinventory-ng.org/index.php/Documentation:Teledeploy/fr

Et le shéma détaillé : http://wiki.ocsinventory-ng.org/index.php/File:SCHEMA_TELEDEPLOY_detail.jpg

Donc c'est le temps écoulé entre 2 cycles.
by (180 points)
0 votes
D'accord, je vais baisser la valeur de mes DCL, DFL et DPL car ils sont trop élevés, ce qui peut engendrer des erreurs de déploiement.
by (2k points)
 
Powered by Question2Answer
...