Q: The jobs don't seem to be progressing, how do I tell if jobs are being processed?

A: Use 'ps' to see what jobs are currently running:

ps -u fossy -f

  or top: 

top -u fossy

  or fo_cli (use the status command)

On a single server system, with ps or top, you should see fo_scheduler and the agent jobs running and consuming CPU time(especially the agents). If they are then probably nothing is wrong, just be patient.
On a multi-server system you should see fo_scheduler and ssh processes that are running agent tasks on the other servers.

If the scheduler is not running or you don't see the processes you should, look in the scheduler log file (/var/log/fossology/fossology.log for any error messages. This should tell you what went wrong if it was a non-catastrophic (non-segv) scheduler error.

You should also look in the scan log. Go to "Jobs > My Recent Jobs" and click on the left-most number for the scan you believe is having a problem. This will take you to a "Geeky Scan Details" page. On the bottom of the page you can see the agent log.

If there still isn't a clue on what went wrong, you can change the scheduler logging verbosity.

Shut down the scheduler if it is running

sudo /etc/init.d/fossology stop

Edit /etc/init.d/fossology. Change the verbosity in the SCHEDULEROPT variable to 952

SCHEDULEROPT="--daemon --reset --verbose=952"

Then start the scheduler

sudo /etc/init.d/fossology start

This will turn on much more verbosity in the scheduler and agent logs.

Q: What are some common failure causes?

A: There are a few things that can quickly cause failures:
  • Database restart. If connectivity to the database drops for any reason, the scheduler and all agents will fail.
  • Network connectivity. When using FOSSology across remote hosts, a drop in network connectivity can lead to process failures.
  • Bad URLs. The #1 cause of wget_agent failures are bad URLs. As user fossy, try running wget with the provided URL. Bad proxy settings or invalid URLs cause problems. Running the wget command as user fossy quickly shows the problem.

Q: How do I reset a failed job?

A: If this was a result of a scheduler failure, and the job doesn't restart when you restart the scheduler, then just queue it up again with Jobs > Scheduler Agents.

Q: Why do some jobs take so long to finish?

A: Some jobs contain thousands of licenses and thousands of files. It takes time to read and analyze all of them and store the analysis in the DataBase. By examining the show jobs output for your job, you can watch the scan progress.

Factors Influencing Job Performance

  • If much of the code has already been analyzed due to previous uploads of the same code, the job will run much faster.
  • Using as much memory as possible on all servers.
  • The type of server(s) in use. Performance is much improved by the use of separate machines for the agents to run on.
  • Separating out the DataBase to its own machine will also aid in performance.
  • The use of external disk arrays can also help with db and agent performance.