Here is my fossology.conf root@oo95sw01 [/usr/local/etc/fossology] # cat fossology.conf ; basic Scheduer.conf for the version 2.0 of the scheduler ; this is a simple key-value configuration file ; should have two groups ; FOSSOLOGY: basic configurations ; HOSTS: a list of host used by fossology ; REPOSITORY: sets the repo information
[FOSSOLOGY] port = 24693 address = localhost ; REPLACEMENT for Depth.conf depth = 3 ; REPLACEMENT for RepPath.conf path = /opt/OSS/fossology/repository ; REPLACEMENT for Proxy.conf ; proxy settings that will be used by fossology agents ; examples: http_proxy= http://px73tste.opr.statefarm.org:8000 ftp_proxy = http://px73tste.opr.statefarm.org:8000 ;no_proxy = localhost,10.1.2.3 ; REPLACEMENT for Hosts.conf ; set up the set of hosts available to analyze files. If there is an entry ; for localhost it will be read, if there isn't one then it is assumed that ; localhost cannot host any agents. A man of -1 does not indicate that a ; host can have as many agents running as necessary, (i.e. there should always ; be a max on the number of agents for a particular host). [HOSTS] localhost = localhost AGENT_DIR 10 [REPOSITORY] localhost[] = * 00 ff [DIRECTORIES] ; Project Name and Group ; Do not change after installation since PROJECT and PROJECTGROUP is used in installation ; directory names and ownership. ; Use PREFIX to install multiple copies of FOSSology. PROJECT=fossology PROJECTGROUP=fossy ; base of the program data tree PREFIX=/usr/local ; executable programs that users run BINDIR=$PREFIX/bin ; executable programs that sysadmins run SBINDIR=$PREFIX/sbin ; object code libraries LIBDIR=$PREFIX/lib ; header files INCLUDEDIR=$PREFIX/include ; executables/libraries that only our project uses LIBEXECDIR=$PREFIX/lib/$PROJECT ; non-arch-specific data DATAROOTDIR=$PREFIX/share ; non-arch-dependent program data MODDIR=$DATAROOTDIR/$PROJECT ; local state LOCALSTATEDIR=/var/local ; project local state PROJECTSTATEDIR=$LOCALSTATEDIR/lib/$PROJECT ; project logdir LOGDIR=/var/log/$PROJECT ; section that allows fossology to send email notifications to users when their ; job has successfully finished. Both the header and footer for the email are ; in text files in the fossology system configuration directory (the same ; directory that contains this file). The subject is simply the subject that ; will be used in the email notification. [EMAILNOTIFY] header = sampleheader.txt footer = samplefooter.txt subject = FOSSology scan complete client = /usr/bin/mailx Valerie _______________________ valerie duncan open source stewardship team<http://sfnet.opr.statefarm.org/content/sysoss/index.shtml> Mobile: 406.633.5099 Desk: 406.655.4132 "Stay strong and wait for signs" ...craig johnson From: Laser, Mary [mailto:[email protected]] Sent: Wednesday, November 07, 2012 1:14 PM To: Valerie Duncan; [email protected] Subject: RE: unable to access email For the database? Or the repository? Database: postgresql.conf Repository: fossology.conf Mary From: Valerie Duncan [mailto:[email protected]]<mailto:[mailto:[email protected]]> Sent: Wednesday, November 07, 2012 12:56 PM To: Laser, Mary; [email protected]<mailto:[email protected]> Cc: Valerie Duncan Subject: RE: unable to access email Fossy failed this morning with the message file system full. In the dashboard I saw the following: /dev/mapper/vg00-lvol3 950.74 MB (996,925,440) 1007.89 MB (1,056,858,112) 100% Instead of writing to / it should be writing to a different location. Where do I set this configuration? Valerie _______________________ valerie duncan open source stewardship team<http://sfnet.opr.statefarm.org/content/sysoss/index.shtml> Mobile: 406.633.5099 Desk: 406.655.4132 "Stay strong and wait for signs" ...craig johnson From: Laser, Mary [mailto:[email protected]]<mailto:[mailto:[email protected]]> Sent: Tuesday, November 06, 2012 10:01 AM To: Valerie Duncan; [email protected]<mailto:[email protected]> Subject: RE: unable to access email Please look in the postgres log file for additional info about this message: 2012-11-01 12:13:13 scheduler [30100] :: ERROR postgresql error: Default location for the log file is /var/log/postgresql/. Mary Laser The FOSSology Project http://fossology.org<http://fossology.org/> From: [email protected]<mailto:[email protected]> [mailto:[email protected]]<mailto:[mailto:[email protected]]> On Behalf Of Valerie Duncan Sent: Tuesday, November 06, 2012 9:45 AM To: [email protected]<mailto:[email protected]> Cc: Valerie Duncan Subject: [FOSSology] unable to access email Hello. Fossology failed this morning for some reason I cannot ascertain. A tail of fossology.log shows this: 2012-11-01 12:13:13 scheduler [30100] :: ERROR database.c.486: unable to access email info for job 1586 2012-11-01 12:13:13 scheduler [30100] :: ERROR postgresql error: 2012-11-01 12:13:27 scheduler [30100] :: ERROR database.c.486: unable to access email info for job 1587 2012-11-01 12:13:27 scheduler [30100] :: ERROR postgresql error: 2012-11-06 10:24:20 scheduler [30613] :: NOTE: ***************************************************************** 2012-11-06 10:24:20 scheduler [30613] :: NOTE: *** FOSSology scheduler started *** 2012-11-06 10:24:20 scheduler [30613] :: NOTE: *** pid: 30613 *** 2012-11-06 10:24:20 scheduler [30613] :: NOTE: *** verbose: 1 *** 2012-11-06 10:24:20 scheduler [30613] :: NOTE: *** config: /usr/local/etc/fossology *** 2012-11-06 10:24:20 scheduler [30613] :: NOTE: ***************************************************************** Fossology has been running w/o issue since the last server reboot Sept 27. Can you provide suggestions on what might be causing the email info errors? No one is receiving emails alerting them to completed scans although I have them checked for email notifications. Any help you can provide is appreciated. SpottedOtter _______________________ "Stay strong and wait for signs" ...craig johnson
_______________________________________________ fossology mailing list [email protected] http://lists.fossology.org/mailman/listinfo/fossology
