I don't know why you can't write a file to your own home directory. I can't help but wonder if that isn't a symptom of your difficulties. Can you "touch tfile" to create a file in your home directory?
The objective is to see the scheduler output with -v. So another way you can do this is: 1) delete /var/log/fossology.log 2) start the scheduler manually with fossology-scheduler -tv That will start the scheduler normally but with the -v option so we can see more verbose output in the log file. If you are comparing files on each agent machine to the db/web hosting machine, you need to look at more than /etc/fossology. Files are installed in multiple directories (/usr/lib/fossology/, /var/lib, ...). Others have done many more multi system installs than I have. Perhaps they can see something obvious that we are missing. Bob On Nov 23, 2009, at 12:46 AM, Furosh One wrote: I did try that. I cd to the location where the fossology-scheduler is and I also attempted to run from my $HOME directory with the same type of results. I even tried looking at the fossology-scheduler -h options to see if I could try with other options but still no luck. I appreciate you being able to analyze the information needed but we have tons of software and some is of legal confidentiality for the company I work for. We are trying to ensure we are under proper licensing and IP compliance. I beleive we currently are waiting to process about 2-3GB (compressed) of software. We have a up and coming deadline which is why I went directly to 6 machines in the setup. While at work today I compared clear1 (which was not on the last FATAL error log) and did a 'diff' on all files in /etc/fossology/* and compared to clear4 which is one of the ones the scheduler is complaining about and found nothing wrong. The scheduler was generated via script so dont understand how it would be okay on some but failing on 2 hosts. Considering to try to remove a package on the server, then try and reinstall fossology (essentially a reinstall) to see if I get any different results. I installed server with 'apt-get install fossology', should I try to remove and re-install from source (.tgz)??? All clients were 'apt-get install fossology-agent fossology-common' Thanks again!!! On Sun, Nov 22, 2009 at 7:51 PM, Gobeille, Robert <bob.gobei...@hp.com<mailto:bob.gobei...@hp.com>> wrote: Write the file to your home directory. Are you analyzing open source software? If so, would you like me to do it for you (we have a public fossology server)? Bob On Nov 22, 2009, at 7:48 PM, Furosh One wrote: > I can't generate the output needed. The fossology-scheduler is failing with > the following: > > ================================================ > gmarq...@san-clear5:~$ sudo /usr/lib/fossology/fossology-scheduler -tvL my.out > Logfile failure: Permission denied > FATAL: Unable to log to logfile 'my.out' > ================================================ > > I checked permissions on the file (owned by root), I have sudo access, > anything you can think of? > > I'm really sorry to bug you guys because I know you guys can be working on > other more important things but I don't have much options on this. I tried to > come into work on Sunday night to hopefully generate the output so I could > hopefully have some answer that I can try tomorrow Monday morning. > > I'm going to try to check where I can find the "Logfile failure: Permission > denied & FATAL: Unable to log to logile" to see what might cause it to NOT > log to output file... _______________________________________________ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
