Introduction

The main objective of the BaseAgent is to find, download, upload and serve files. In order to follow what is happening (or has happened earlier), the log file is the obvious source of information (The Log tab). However, the information in the log file can be overwhelming and can occur unstructured, simply because of everything happening in parallel on both the server and client interface.

To help save the day, the Jobs tab will straighten out the log file and organize the information on a 'per-file' basis.

This page is a real-time view of the log file, except that it is only showing what files are being handled. All files are organized in horizontal bars. The bar consists of five elements;

• An arrow showing the direction of the file job; Down for download, up for upload and left for service, this means a file being served to another peering BaseAgent.
• A fileID given to every initiated file job: /file/1, /file/2...
• The relative filename of the file job according to the container on the Front-end Server. File names, 32 characters long (the bright yellow one) is representing the MD5 checksum of a file being served to another Base Agent.
• The source/target of the file job
• An icon representation, symbolizing the type of source or target of the fileJob

Examples

These examples are shown for file jobs on a client computer named DevBlue2;

The downward arrow indicates a download. The color of download file jobs is green (if they succeed). The file being downloaded is the /resources/cistubfiles.zip. The file was found on Devblue2 (itself) and came from the file cache (the recycle-icon).

The upward arrow shows an upload of outbound/pfro.log. Uploads are shown in blue. The file was uploaded to Devtbs2 which is a Front-end Server (the Factory icon).

This is a download file that failed. The arrow is still downwards but the bar is red. All failed file jobs are red, regardless of direction.

Files with a horizontal arrow are files being served to another Base Agent. Not that the file name does not resemble a file path, but rather 32 digits. This is because of Base Agents handling files on MD5 checksums. This means that a Base Agent will request a file from a peer using the MD5 checksum only and that's the reason that the file job is shown with the MD5 checksum instead of a file name. This file was served to Devtbs2 (the share icon).

This is a regular file job of a .kit file to the Adobe Shock Player package being downloaded from the Distribution Server Devwhite, shown with the server rack icon.

This is also a file job requested to a Distribution Server, but unlike the previous file job that succeded, this fileJob was denied. The reason for the file denial is that the Distribution Server is in preload mode and it was being requested to serve a file that wasn't available in the file cache of the Distribution Server. The denial status is returned to the Agent script which will then set the package status to 'Cancelled'. This will ensure that the package is retried on a later Agent Run.

Details

While the list of file jobs is a visual list, representing the file jobs, more details are needed. Each file job is clickable and will show the details of the file job.

The file Job details has a 'view log file' button which is a subset on the overall log file, showing only log entries related to this exact file job. The view has the same features as the general log file. You can 'Auto-scroll' and filter the log in different log levels.