How to Interpret the log files¶
Scheduler log file¶
the basic layout of the scheduler is:
<date> <time> scheduler [<pid>] :: <message>
The message will depend of the verbosity level that the scheduler is set to.
All notifications will be prepended with "NOTE: ".
All warnings will be prepended with "WARNING: ".
All errors will be prepended with "ERROR: ".
All fatal errors will be prepended with "FATAL: ".
Messages that originate when debugging information is turned on should have some indication as to which file they originated from. Messages that are generated by an agent will be prepended with "JOB[jq_pk].agent_type[pid.host]: ". This information is provided to help users identify where a problem is originating from.
If the 6th bit of verbose it turned on, then there will be several message generated when the configuration is loaded. Agent configuration will resemble this:
2012-02-13 13:33:28 scheduler  :: CONFIG: loading config file /usr/local/etc/fossology/mods-enabled/nomos/nomos.conf 2012-02-13 13:33:28 scheduler  :: CONFIG: added new agent 2012-02-13 13:33:28 scheduler  :: name = nomos 2012-02-13 13:33:28 scheduler  :: command = nomos 2012-02-13 13:33:28 scheduler  :: max = -1 2012-02-13 13:33:28 scheduler  :: special = 0
If you are having problems with an agent running. Make sure that the name is exactly the same as what is entered into the jq_type column of the jobqueue in the database. The command will be used when starting the actual agent process and should work when running the agent via command line. Max is the largest number of concurrently running copies of the agent (-1 means no limit). Special is a bit map, the bits in order from least to most significant bit: EXCLUSIVE, NOEMAIL, NOKILL. EXCLUSIVE means that the agent can not run concurrently with any other agent, including itself. This means that for an agent that uses EXCLUSIVE, max is automatically set to 1. NOEMAIL means that when the agent finishes, it will not send a notification email to the user that queued the job. NOKILL means that the agent will not be killed if it stops communicating with the scheduler.
Host configuration will resemble this:
2012-02-13 16:57:05 scheduler  :: CONFIG: added new host 2012-02-13 16:57:05 scheduler  :: name = localhost 2012-02-13 16:57:05 scheduler  :: address = localhost 2012-02-13 16:57:05 scheduler  :: directory = AGENT_DIR 2012-02-13 16:57:05 scheduler  :: max = 10
If you are having problems with all agents on a specific host, then make sure that this is correct. The name could be anything as long as it is unique. The address needs to be a machine that ssh is able to log into as the user fossy without providing a password. For the machine that the scheduler is running on, make sure that the address is set to "localhost". The AGENT_DIR does not matter for localhost. On all other machines this should be the directory that the scheduler can find the mods-enabled directory on the agent machine. Max is the maximum number of agents that can run on this machine.
Agent log files¶
Currently, this is formatted exactly the same as the scheduler log. This may change in future versions of fossology.