Here's the continuation of my experience installing FOSSology on RHEL5.3.
his section covers
the configuration tasks and gotchas that occurred after successfully building
FOSSology (make).
Unless noted, all of the default file locations were accepted. I performed the
procedure as described in the INSTALL file. I will only note where the process
deviated from this file or where I think the directions contained there can be
improved. (Where possible, I reference steps here with the section number.)
2.1.4 Postgresql
----------------
Config file is at /var/lib/pgsql/data/postgresql.conf
Can configure postgresql service to start at boot by default with
# chkconfig postgresql on
Can start postgresql service with
# service postgresql start
2.1.5 PHP
---------
Config file is at /etc/php.ini
I had to add a line to /etc/php.ini
allow_call_time_pass_reference = On
to avoid PHP warning messages when running FOSSology. This was with 5.1.6-23
2.1.6 Apache
------------
This is probably somewhat dependent on site conventions and whether the system
will be hosting other websites besides FOSSology, but I'll relate what I
did to get it working with FOSSology being the only and default web site served.
Config file is at /etc/httpd/conf/httpd.conf
Software uses apachectl instead of apache2ctl
Added website to the httpd.conf file as a VirtualHost with the
following segment:
NameVirtualHost *
<VirtualHost *>
ServerAdmin r...@localhost
DocumentRoot /usr/local/share/fossology/www/
LogLevel warn
ErrorLog /var/log/httpd/error_log
CustomLog /var/log/httpd/access_log combined
<Directory "/">
AllowOverride None
Options FollowSymLinks MultiViews
php_flag display_errors on
php_value error_reporting 2039
</Directory>
</VirtualHost>
2.2.3 Post-Install
------------------
RHEL5 Apache does not have www-data user. I had to add user httpd to
the fossy group by hand.
The useradd command shown to add the fossy user is wrong. Something
failed later on
because fossy needs a real shell (not /bin/false as shown in the command).
In Step 2B, the need to su to user postgres before running psql should
be highlighted
better by showing it as an actual command immediately prior to the psql command.
pg_hba.conf is in /var/lib/pgsql/data. To get it to work, I had to add
another line besides
local all all md5
I also needed to add
host all all 127.0.0.1/32 md5
to get it to work. Don't know why it wanted to use IPv4 instead of Unix domain.
SELinux
-------
People who use SELinux will have to make some configuration changes to give
FOSSology the proper permissions to do its thing. An exact description of those
changes is probably beyond the scope of the INSTALL file. But a suggested course
of action is to temporarily run SELinux in Permissive mode and take note of what
events are flagged and need to be corrected. Note that some things may
appear to be
working initially, but you won't really know all the gotchas until you start
uploading and analyzing packages. My first uploads scheduled a bunch of jobs,
which completed, but were unable to do their work, because SELinux was blocking
their actions.
Takeaway here is that if you're running SELinux and some part of FOSSology
doesn't seem to be working correctly, you probably want to check the SELinux
log to see if you need to tweak permissions, etc.
Other suggestions
-----------------
It might be nice to have a troubleshooting section, particularly when it comes
to the correct permissions for various directories. It may have been pilot
error, but I problems with permissions on the repository directory, Db.conf,
and the /var/log/fossology.
_______________________________________________
fossology mailing list
[email protected]
http://fossology.org/mailman/listinfo/fossology
