ONYX - 9.0 - KB - Nettoyage des fichiers du Spooler/en

Différence entre versions

De MappingDoc
(Page créée avec « *Deleting all the jobs (whatever status) with an expired retention time: »)
 
(27 révisions intermédiaires par le même utilisateur non affichées)
Ligne 4 : Ligne 4 :
  
 
==Clearing jobs==
 
==Clearing jobs==
===Per retention time===
+
===As per retention time===
 
All the jobs in the Spooler have a specific attribute: the retention time (in days). The solution uses this attribute to clear the "expired" jobs in the Spooler, in other words, those with an exceeded retention time.
 
All the jobs in the Spooler have a specific attribute: the retention time (in days). The solution uses this attribute to clear the "expired" jobs in the Spooler, in other words, those with an exceeded retention time.
  
Ligne 15 : Ligne 15 :
 
Windows: <code>E:\MappingWindows\Applications\map_cron.exe –date</code>
 
Windows: <code>E:\MappingWindows\Applications\map_cron.exe –date</code>
  
*Deleting all the jobs (whatever status) with an expired retention time:
+
*Deleting all the jobs (no matter their status) with an expired retention time:
  
 
Linux: <code>/apps/mapping/bin/map_cron –dateall</code>
 
Linux: <code>/apps/mapping/bin/map_cron –dateall</code>
Ligne 21 : Ligne 21 :
 
Windows: <code>E:\MappingWindows\Applications\map_cron.exe –dateall</code>
 
Windows: <code>E:\MappingWindows\Applications\map_cron.exe –dateall</code>
  
===Par filtres de nettoyage===
+
===As per clearing filters===
Pour nettoyer le Spooler de certains travaux, une méthode plus fine consiste à utiliser des filtres de sélection des travaux à supprimer. Cinq filtres sont disponibles :
+
One method to clear the Spooler of jobs consists in using filters to select the jobs to delete. Five filters are available:
  
- Par type de file d’attente : point d’entrée (<FONT color="blue"> -entry</FONT>) ou file d’attente d’impression (<FONT color="blue"> -queue</FONT>)
+
- As per type of queue: input point (<FONT color="blue"> -entry</FONT>) or print queue (<FONT color="blue"> -queue</FONT>)
  
- Par date : absolue (travaux plus anciens que tel jour, argument <FONT color="blue"> -before_date:JJ/MM/AAAA</FONT>) ou relative (travaux de plus de N jours
+
- As per date: absolute (jobs older than a given day, argument <FONT color="blue"> -before_date:JJ/MM/AAAA</FONT>) or relative (jobs of more than N days
 
(<FONT color="blue"> -relative_date:d/m/y</FONT>)
 
(<FONT color="blue"> -relative_date:d/m/y</FONT>)
  
- Par utilisateur propriétaire :argument <FONT color="blue"> -user:XXXX</FONT>
+
- As per owner user: argument <FONT color="blue"> -user:XXXX</FONT>
  
- Par état des travaux : argument <FONT color="blue"> -state:XXXX</FONT> (ready, saved, held, error)
+
- As per job status: argument <FONT color="blue"> -state:XXXX</FONT> (ready, saved, held, error)
  
- Par nom de file d’attente : argument <FONT color="blue"> -queue_name:XXXX</FONT>
+
- As per queue name: argument <FONT color="blue"> -queue_name:XXXX</FONT>
  
  
Voici quelques exemples d’utilisation :
+
Here are some examples:
  
*Suppression de tous les spools :
+
*To delete all the spooled files:
  
 
  map_cron –cleanspool
 
  map_cron –cleanspool
  
*Suppression des spools de l’utilisateur mapadmin :
+
*To delete spooled files owned by the mapadmin user:
  
 
  map_cron -cleanspool -user:mapadmin
 
  map_cron -cleanspool -user:mapadmin
  
*Suppression des spools conservés de l’utilisateur mapadmin :
+
*To delete spooled files kept by the mapadmin user:
  
 
  map_cron -cleanspool -user:mapadmin -state:saved
 
  map_cron -cleanspool -user:mapadmin -state:saved
  
*Suppression des spools conservés, de l’utilisateur mapadmin, dans les points d'entrée :
+
*To delete spooled files kept by the mapadmin user, in the input points:
  
 
  map_cron -cleanspool -user:mapadmin -state:saved -entry
 
  map_cron -cleanspool -user:mapadmin -state:saved -entry
  
*Suppression des spools conservés, de l’utilisateur mapadmin, dans les points d'entrée, dont la date est antérieure au 19 janvier 2018 :
+
*To delete spooled files kept by the mapadmin user, in the input points, which have a date prior to the 19th of January 2018:
  
 
  map_cron -cleanspool -user:mapadmin -state:saved -entry -before_date:19/01/2018
 
  map_cron -cleanspool -user:mapadmin -state:saved -entry -before_date:19/01/2018
  
*Suppression des spools conservés, de l’utilisateur mapadmin, dans les points d'entrée, de plus de 10 jours :
+
*To delete spooled files kept by the mapadmin user, in the input points, which are older than 10 days:
  
 
  map_cron -cleanspool -user:mapadmin -state:saved -entry -relative_date:10/0/0
 
  map_cron -cleanspool -user:mapadmin -state:saved -entry -relative_date:10/0/0
  
*Suppression des spools conservés, de l’utilisateur mapadmin, de plus de 10 jours, dans le point d'entréemon_entry :
+
**To delete spooled files kept by the mapadmin user, which are older than 10 days, in the mon_entry input point:
  
 
  map_cron -cleanspool -user:mapadmin -state:saved -entry -relative_date:10/0/0 -queue_name:mon_entry
 
  map_cron -cleanspool -user:mapadmin -state:saved -entry -relative_date:10/0/0 -queue_name:mon_entry
  
  
Remarque:
+
Note:
  
Pour fonctionner, l’exécution de ces commandes de nettoyage des travaux doit se faire avec le Spooler ONYX Server en état de marche. En effet, seul le Spooler peut interagir avec ses travaux alors que les commandes précédentes envoient des requêtes de suppression au Spooler.
+
For them to be carried out be correctly, these clearing commands must be run as the ONYX Server Spooler is also running. Only the Spooler can interact with its jobs, the previous commands can only send deletion queries to the Spooler.
  
  
==Épuration des journaux d’événements==
+
==Clearing logs==
  
La commande <FONT color="blue"> map_cron </FONT> permet également de nettoyer les fichiers correspondants aux journaux d’événements d'ONYX Server. Des options permettent de conserver, pour historique, des archives des journaux d’événements avant leur suppression.
+
The <FONT color="blue"> map_cron </FONT> clears the files corresponding to ONYX Server logs. Options can be set to keep archives of the logs before they are deleted, to keep them as history.
  
*Création d’une archive (ZIP) des journaux avant suppression :
+
*Creating an archive (ZIP) of the logs before deleting them:
  
 
Linux: <code>/apps/mapping/bin/<FONT color="blue"> map_cron -cleanlog </FONT></code>
 
Linux: <code>/apps/mapping/bin/<FONT color="blue"> map_cron -cleanlog </FONT></code>
Ligne 82 : Ligne 82 :
 
Windows: <code>E:\MappingWindows\Applications\<FONT color="blue"> map_cron.exe -cleanlog </FONT></code>
 
Windows: <code>E:\MappingWindows\Applications\<FONT color="blue"> map_cron.exe -cleanlog </FONT></code>
  
L’archive est conservée par défaut à la racine du répertoire des logs Onyx Server (variable PATH_LOG de la configuration), nommée en fonction de la date/heure d’exécution de la commande.
+
The archive is kept by default at the root of the Onyx Server logs folder (PATH_LOG variable of the configuration) and named according to the date/hour on which the command was run.
  
*Suppression des journaux sans sauvegarde :
+
*Deleting logs without backup:
  
 
Linux: <code>/apps/mapping/bin/<FONT color="blue">map_cron -cleanlog -delete</FONT></code>
 
Linux: <code>/apps/mapping/bin/<FONT color="blue">map_cron -cleanlog -delete</FONT></code>
Ligne 90 : Ligne 90 :
 
Windows: <code>E:\MappingWindows\Applications\<FONT color="blue">map_cron.exe -cleanlog -delete</FONT></code>
 
Windows: <code>E:\MappingWindows\Applications\<FONT color="blue">map_cron.exe -cleanlog -delete</FONT></code>
  
==Épuration des statistiques==
+
==Clearing statistics==
  
Sur le même principe que précédemment, les fichiers correspondants aux statistiques et rapports d’utilisation d'ONYX Server peuvent être nettoyés :
+
Following the same principle as previously, the files corresponding to statistics and ONYX Server usage reports can be cleared:
  
 
Linux: <code>/apps/mapping/bin/<FONT color="blue"> map_cron -cleanstats [ -delete ]</FONT></code>
 
Linux: <code>/apps/mapping/bin/<FONT color="blue"> map_cron -cleanstats [ -delete ]</FONT></code>
  
 
Windows: <code>E:\MappingWindows\Applications\<FONT color="blue"> map_cron.exe -cleanstats [ -delete ]</FONT></code>
 
Windows: <code>E:\MappingWindows\Applications\<FONT color="blue"> map_cron.exe -cleanstats [ -delete ]</FONT></code>

Version actuelle datée du 30 août 2019 à 13:21

Autres langues :
English • ‎français

Introduction

ONYX Server normally creates and keeps a certain number of files which we advise you regularly clear: kept jobs, logs, statistics. This can be done using an ONYX Server command: map_cron.

Clearing jobs

As per retention time

All the jobs in the Spooler have a specific attribute: the retention time (in days). The solution uses this attribute to clear the "expired" jobs in the Spooler, in other words, those with an exceeded retention time.

There are two ONYX Server commands which serve this purpose:

  • Deleting all the jobs kept (which were processed and kept) with an expired retention time:

Linux: /apps/mapping/bin/map_cron –date

Windows: E:\MappingWindows\Applications\map_cron.exe –date

  • Deleting all the jobs (no matter their status) with an expired retention time:

Linux: /apps/mapping/bin/map_cron –dateall

Windows: E:\MappingWindows\Applications\map_cron.exe –dateall

As per clearing filters

One method to clear the Spooler of jobs consists in using filters to select the jobs to delete. Five filters are available:

- As per type of queue: input point ( -entry) or print queue ( -queue)

- As per date: absolute (jobs older than a given day, argument -before_date:JJ/MM/AAAA) or relative (jobs of more than N days ( -relative_date:d/m/y)

- As per owner user: argument -user:XXXX

- As per job status: argument -state:XXXX (ready, saved, held, error)

- As per queue name: argument -queue_name:XXXX


Here are some examples:

  • To delete all the spooled files:
map_cron –cleanspool
  • To delete spooled files owned by the mapadmin user:
map_cron -cleanspool -user:mapadmin
  • To delete spooled files kept by the mapadmin user:
map_cron -cleanspool -user:mapadmin -state:saved
  • To delete spooled files kept by the mapadmin user, in the input points:
map_cron -cleanspool -user:mapadmin -state:saved -entry
  • To delete spooled files kept by the mapadmin user, in the input points, which have a date prior to the 19th of January 2018:
map_cron -cleanspool -user:mapadmin -state:saved -entry -before_date:19/01/2018
  • To delete spooled files kept by the mapadmin user, in the input points, which are older than 10 days:
map_cron -cleanspool -user:mapadmin -state:saved -entry -relative_date:10/0/0
    • To delete spooled files kept by the mapadmin user, which are older than 10 days, in the mon_entry input point:
map_cron -cleanspool -user:mapadmin -state:saved -entry -relative_date:10/0/0 -queue_name:mon_entry


Note:

For them to be carried out be correctly, these clearing commands must be run as the ONYX Server Spooler is also running. Only the Spooler can interact with its jobs, the previous commands can only send deletion queries to the Spooler.


Clearing logs

The map_cron clears the files corresponding to ONYX Server logs. Options can be set to keep archives of the logs before they are deleted, to keep them as history.

  • Creating an archive (ZIP) of the logs before deleting them:

Linux: /apps/mapping/bin/ map_cron -cleanlog

Windows: E:\MappingWindows\Applications\ map_cron.exe -cleanlog

The archive is kept by default at the root of the Onyx Server logs folder (PATH_LOG variable of the configuration) and named according to the date/hour on which the command was run.

  • Deleting logs without backup:

Linux: /apps/mapping/bin/map_cron -cleanlog -delete

Windows: E:\MappingWindows\Applications\map_cron.exe -cleanlog -delete

Clearing statistics

Following the same principle as previously, the files corresponding to statistics and ONYX Server usage reports can be cleared:

Linux: /apps/mapping/bin/ map_cron -cleanstats [ -delete ]

Windows: E:\MappingWindows\Applications\ map_cron.exe -cleanstats [ -delete ]