If the scheduler dies, the fo_watchdog should restart it, but it can
take upto 10 minutes.
Since this problem is more than 10 minutes old, I'm guessing that
fo_watchdog keeps starting the scheduler, and the scheduler keeps dying.
You can test the scheduler with the command:
fossology-scheduler -TL stdout
Could you send me the output of this command?
If you installed from a package (rpm, debian) then fossology-scheduler
should be in /usr/lib/fossology.
If you installed from a tarball, it should be in /usr/local/lib/
fossology
Bob Gobeille
On Jul 20, 2009, at 9:55 AM, [email protected] wrote:
Hello,
I tried uploading the file just through the UI and when I view the
job queue, it shows a list of jobs but none are scheduled. I went
to the O/S it was installed on and executed the following command
and it did not show the scheduler executing:
ps -ef | grep foss
postgres 2889 2867 0 10:22 ? 00:00:00 postgres: fossy
fossology 127.0.0.1(53107) idle
postgres 2890 2867 0 10:22 ? 00:00:00 postgres: fossy
fossology 127.0.0.1(53108) idle
postgres 2891 2867 0 10:22 ? 00:00:00 postgres: fossy
fossology 127.0.0.1(53109) idle
postgres 2893 2867 0 10:22 ? 00:00:00 postgres: fossy
fossology 127.0.0.1(53110) idle
postgres 3041 2867 0 10:36 ? 00:00:00 postgres: fossy
fossology 127.0.0.1(57025) idle
postgres 4998 2867 0 11:33 ? 00:00:00 postgres: fossy
fossology 127.0.0.1(43112) idle
postgres 8578 2867 0 11:26 ? 00:00:00 postgres: fossy
fossology 127.0.0.1(58243) idle
fossy 9630 1 0 11:33 ? 00:00:00 /usr/lib/fossology/
fo_watchdog
postgres 9632 2867 0 11:33 ? 00:00:00 postgres: fossy
fossology 127.0.0.1(43115) idle
root 27348 2745 0 11:41 pts/1 00:00:00 grep foss
postgres 29075 2867 0 11:31 ? 00:00:00 postgres: fossy
fossology 127.0.0.1(43107) idle
_______________________________________________
fossology mailing list
[email protected]
http://fossology.org/mailman/listinfo/fossology
