Hello,
Thanks for the feedback.
We have "straced" the selftest agent and find an issue in the
directories names. It's now fixed.
When fossology is started, we have another error now:
2009-02-19 16:45:44 scheduler[11818] : Log opened
2009-02-19 16:45:44 scheduler[11818] : *** Scheduler started
2009-02-19 16:45:44 scheduler[11818] : Child[0] 'agent=wget host=localhost
' state=FREE(1) @ Thu Feb 19 16:45:44 2009
2009-02-19 16:45:44 scheduler[11818] : Child[1] 'agent=unpack
host=localhost ' state=FREE(1) @ Thu Feb 19 16:45:44 2009
2009-02-19 16:45:44 scheduler[11818] : Child[2] 'agent=adj2nest
host=localhost ' state=FREE(1) @ Thu Feb 19 16:45:44 2009
2009-02-19 16:45:44 scheduler[11818] : Child[3] 'agent=filter_license
host=localhost ' state=FREE(1) @ Thu Feb 19 16:45:44 2009
2009-02-19 16:45:44 scheduler[11818] : Child[4] 'agent=license
host=localhost ' state=FREE(1) @ Thu Feb 19 16:45:44 2009
2009-02-19 16:45:44 scheduler[11818] : Child[5] 'agent=licinspect
host=localhost ' state=FREE(1) @ Thu Feb 19 16:45:44 2009
2009-02-19 16:45:44 scheduler[11818] : Child[6] 'agent=mimetype
host=localhost ' state=FREE(1) @ Thu Feb 19 16:45:44 2009
2009-02-19 16:45:44 scheduler[11818] : Child[7] 'agent=specagent
host=localhost ' state=FREE(1) @ Thu Feb 19 16:45:44 2009
2009-02-19 16:45:44 scheduler[11818] : Child[8] 'agent=filter_clean
host=localhost ' state=FREE(1) @ Thu Feb 19 16:45:44 2009
2009-02-19 16:45:44 scheduler[11818] : Child[9] 'agent=delagent
host=localhost ' state=FREE(1) @ Thu Feb 19 16:45:44 2009
2009-02-19 16:45:44 scheduler[11818] : Child[10] 'agent=sqlagent
host=localhost ' state=FREE(1) @ Thu Feb 19 16:45:44 2009
2009-02-19 16:45:44 scheduler[11818] : Child[11] 'agent=sqlagenthost
host=localhost ' state=FREE(1) @ Thu Feb 19 16:45:44 2009
2009-02-19 16:45:44 scheduler[11818] : Child[12] 'agent=pkgmetagetta
host=localhost ' state=FREE(1) @ Thu Feb 19 16:45:44 2009
2009-02-19 16:45:44 scheduler[11818] : Child[13] 'agent=fosscp_agent
host=localhost ' state=FREE(1) @ Thu Feb 19 16:45:44 2009
2009-02-19 16:45:44 scheduler[11818] : Child[14] 'agent=selftest
host=localhost ' state=FREE(1) @ Thu Feb 19 16:45:44 2009
2009-02-19 16:45:44 scheduler[11818] : FATAL: Unable to generate test
data: 'echo 'test' | /srv/fossology/lib/fossy_test/agents/selftest -g -s'.
2009-02-19 16:45:44 scheduler[11818] : FATAL: Inconsistent agent(s)
detected.
When connecting to the DB, we didn't see any agent table ?
The DB has been dropped and recreated with the script sql script,
but the agent table is still not there.
Any idea ?
Thanks in advance,
Christian Sterpin - ICSD System & Hardware Administration
Ext: 32303
[email protected]
19.02.2009 12:05
To
[email protected]
cc
[email protected], [email protected],
[email protected]
Subject
Re: [FOSSology] Installation problem
Christian,
Start from here...
http://www.postgresql.org/docs/8.1/interactive/client-authentication.html
I would still say it is more of a postgres config problem than fossology
directly.
As far as logging goes....
postgres should be somewhere like:
/var/log/postgresql/postgresql-8.1-main.log
(for an 8.1 install)
scheduler log....
/var/log/fossology/fossology.log
Please also just reverify all of this from the INSTALL has been done
correctly...
2.2.3 Detailed Post-Install Instructions
------------------------------------------
If you prefer to do these steps by hand or are curious of what the
fo-postinstall script is doing, continue reading, otherwise skip to
step 2.2.4.
1) Setting up Users and Groups
You are expected to already have a "postgres" user as part of the
system postgresql install, and a "www-data" user as part of the
apache2 install.
FOSSology requires a system user and a system group both named
"fossy".
The /etc/passwd entries for these user should look
something like (Note: your uid & gid values may be different):
fossy:x:1001:1001:FOSSology:/srv/fossology:/bin/bash
and the /etc/group entry
fossy:x:1001:fossy
On a system with the useradd and groupadd commands (all LSB systems
including Debian, Fedora, etc) you can create the above system user
and group with the following commands as root:
groupadd fossy
useradd -c FOSSology -d /srv/fossology -g fossy -s /bin/false fossy
Alternatively, you can use the adduser command:
adduser --gecos "FOSSology" --home /srv/fossology --system --group fossy
2) Setting up the database
A sample database schema file can be found either on the installed system
at /usr/local/lib/fossology/test.d/fossologyinit.sql or in the tarball at
fossology-<version>/db/fossologyinit.sql. This will create the
database when it is read in. It will also create an owner for the
database "fossy" and owner's password "fossy". For security reasons,
please change this password, after the database is created, using
the alter command. Here are the steps:
Check to see the database server is running
A) Ensure that postgresql is running using this command:
/etc/init.d/postgresql-8.1 status
Version Cluster Port Status Owner Data directory Log
file
8.1 main 5432 online postgres /var/lib/postgresql/8.1/main \
/var/log/postgresql/postgresql-8.1-main.log
If the status reported is "online", you can proceed to the next step.
If the status is "down", use this command to start postgres:
/etc/init.d/postgresql-8.1 start
You should see the following message:
Starting PostgreSQL 8.1 database server: main.
B) The default database and owner is created by reading in the
fossologyinit.sql file of sql statements to define the database schema.
You must be logged in as user postgres to create the database schema
and define the owner. As root, you can su to user postgres (su
postgres) and then run the psql command:
psql < fossologyinit.sql
C) If any steps fail, check the postgres log file for errors:
/var/log/postgresql/postgresql-8.1-main.log
D) Make sure /etc/postgresql/8.1/main/pg_hba.conf is configured
correctly to allow your connection. This file controls: which hosts
are allowed to connect, how clients are authenticated, which
PostgreSQL user names they can use, which databases they can access.
As a starting point, you will need something like the following for
local connections:
# local DATABASE USER METHOD [OPTION]
local all all md5
See
http://www.postgresql.org/docs/current/static/client-authentication.html
for detailed information.
If you do need to edit it then restart postgresql so the changes take
effect:
/etc/init.d/postgresql-<version> restart
E) Once the database is defined, verify connection with
psql -d fossology -U fossy
use the default password "fossy". You should connect and see the
following:
Welcome to psql 8.1.9, the PostgreSQL interactive terminal.
Type: \copyright for distribution terms
\h for help with SQL commands
\? for help with psql commands
\g or terminate with semicolon to execute query
\q to quit
fossology=>
If so then you successfully connected. Type \q to quit.
F) If any steps fail, check the postgres log file for errors:
/var/log/postgresql/postgresql-8.1-main.log
2.2.4 Checking the Default Configuration Files
------------------------------------------------
On a fresh install you start with default versions of configuration
files that contain reasonable defaults (where possible), or some files
are generated via the post install script. You need to review and edit
where needed.
A) /usr/local/etc/fossology/RepPath.conf
This is the path to the fossology repository. The repository can
be a mount point, and should be a large disk space. If you plan to
analyze ISOs, then consider a terabyte of disk or larger. For more
discussion of this topic see the INSTALL.multi file and user
documents on the website. If you change this file you may need
to setup the new repo or run the fo-postinstall script to do it.
B) /usr/local/etc/fossology/Hosts.conf
This file determines how the file repository is split across
hosts, the default is a single machine. For more into see the
INSTALL.multi file.
C) /usr/local/etc/fossology/Proxy.conf
If you need to use a proxy to access the internet, you can use this
file to tell the different parts of fossology that need internet
access which proxy to use.
D) /usr/local/etc/fossology/Depth.conf
This file is magic, do not touch unless you are a wizard.
E) /usr/local/etc/fossology/Db.conf
This file is the information needed to access the database. It's
ownership and permissions should be root:fossy 660 so that
only root and people in the fossy group can read it. On a fresh
install it contains the default database password, you should
really change that here and in postgresql.
F) /usr/local/etc/fossology/Scheduler.conf
This file tells the scheduler how to send out work to the agents.
It is generated by the mkschedconf utility. You can run
/usr/local/lib/fossology/mkschedconf -h
for help on using that utility. For more information on the
scheduler config file format, see
http://fossology.org/docs/scheduler#configuring_the_scheduler
2.2.5 Start the Scheduler
---------------------------
As root, start the scheduler with:
/etc/init.d/fossology start
The scheduler logs to /var/log/fossology/fossology.log by default, you
can look there for scheduler activity or errors.
Sorry but I am not in a location where I can gain access to my own
installation for a few days.
Sincerely,
Shay Stowe
Pramerica Systems Ireland Limited is a private company limited by shares
incorporated and registered in the Republic of Ireland with registered
number 319900 and registered office at 6th Floor, South Bank House, Barrow
Street,
Dublin 4, Ireland.
[email protected]
Sent by: [email protected]
Thu 02/19/2009 10:34 AM
To
[email protected]
cc
[email protected], [email protected],
[email protected]
Subject
Re: [FOSSology] Installation problem
Hello,
Thanks for the tip, but we still have the same problem.
Is there any option to have more verbose logs ?
Thanks in advance,
Christian Sterpin - ICSD System & Hardware Administration
Ext: 32303
[email protected]
18.02.2009 11:54
To
[email protected]
cc
[email protected], [email protected],
[email protected]
Subject
Re: [FOSSology] Installation problem
Christian,
Don't reinstall - not necessary, the problem is as you correctly
identified is with the postgres pg_hba.conf
I am not a postgres expert but had similar problems on an Ubuntu install
.....
Try this for starters and try and isolate down to your IPv4, then maybe
switch on and off sections to see where the problem occurs
(Remembering to restart postgres between changes)
I am assuming apache has been set up to just run localhost so that
http://localhost/repo/
brings you to the fossology instance.
##################################################
# "local" is for Unix domain socket connections only
#local all all trust
# IPv4 local connections:
host all all 127.0.0.1/32 trust
# IPv6 local connections:
#host all all ::1/128 trust
##################################################
The postgres site has some good documentation in order to configure this
later on - but I assume you want to try and get this running.
Hope this helps, as I said no expert but just from my installation
experience.
Sincerely,
Shay Stowe
Pramerica Systems Ireland Limited is a private company limited by shares
incorporated and registered in the Republic of Ireland with registered
number 319900 and registered office at 6th Floor, South Bank House, Barrow
Street,
Dublin 4, Ireland.
[email protected]
Sent by: [email protected]
Wed 02/18/2009 10:24 AM
To
[email protected]
cc
[email protected]
Subject
[FOSSology] Installation problem
Hello,
Here is a problem we encounter after the installation of fossology.
(on a RHEL 5.2 x86_64)
By start of scheduler:
2009-02-13 10:53:47 scheduler[11317] : *** Scheduler started
2009-02-13 10:53:47 scheduler[11317] : FATAL: Unable to connect to
database
Db.conf:
------------
dbname=fossology;
host=localhost;
user=fossy;
password=fossy;
------------
DB instance is up and running:
--------------------------
[fo...@reikland ~]$ psql -d fossology -h localhost -U fossy -W
Password for user fossy:
Welcome to psql 8.1.11, the PostgreSQL interactive terminal.
Type: \copyright for distribution terms
\h for help with SQL commands
\? for help with psql commands
\g or terminate with semicolon to execute query
\q to quit
fossology=>
--------------------
Following a suggestion from Mary Laser, the following was done:
I have changed all "trust" to "md5" in following part of pg_hba.conf and
restarted postgresql.
##################################################
# "local" is for Unix domain socket connections only
local all all trust
# IPv4 local connections:
host all all 127.0.0.1/32 trust
# IPv6 local connections:
host all all ::1/128 trust
##################################################
Then i tryed to restart scheduler again. Those changes had no effect, the
scheduler still fails. However the postgresql log file does not consists
mentioning of "apachedb" anymore.
Any further ideas ? should i drop the db and reinstall fossology again ?
Would it help ?
Thanks in advance,
Christian Sterpin - ICSD System & Hardware Administration
Ext: 32303
----------------------------------------------------------------------------
Clearstream Services S.A.
42 Avenue JF Kennedy, L-1855 Luxembourg
Société anonyme is organised with limited liability
in the Grand Duchy of Luxembourg R.C.S. Luxembourg B 60911.
Visit us at http://www.clearstream.com IMPORTANT MESSAGE Internet
communications are not secure and therefore Clearstream International does
not accept legal responsibility for the contents of this message. The
information contained in this e-mail is confidential and may be legally
privileged. It is intended solely for the addressee. If you are not the
intended recipient, any disclosure, copying, distribution or any action
taken or omitted to be taken in reliance on it, is prohibited and may be
unlawful. Any views expressed in this e-mail are those of the individual
sender, except where the sender specifically states them to be the views
of Clearstream International or of any of its affiliates or subsidiaries.
Legally required information for business correspondence/ Gesetzliche
Pflichtangaben fuer Geschaeftskorrespondenz:
http://deutsche-boerse.com/letterhead END OF DISCLAIMER
_______________________________________________
fossology mailing list
[email protected]
http://fossology.org/mailman/listinfo/fossology
----------------------------------------------------------------------------
Clearstream Services S.A.
42 Avenue JF Kennedy, L-1855 Luxembourg
Société anonyme is organised with limited liability
in the Grand Duchy of Luxembourg R.C.S. Luxembourg B 60911.
Visit us at http://www.clearstream.com IMPORTANT MESSAGE Internet
communications are not secure and therefore Clearstream International does
not accept legal responsibility for the contents of this message. The
information contained in this e-mail is confidential and may be legally
privileged. It is intended solely for the addressee. If you are not the
intended recipient, any disclosure, copying, distribution or any action
taken or omitted to be taken in reliance on it, is prohibited and may be
unlawful. Any views expressed in this e-mail are those of the individual
sender, except where the sender specifically states them to be the views
of Clearstream International or of any of its affiliates or subsidiaries.
Legally required information for business correspondence/ Gesetzliche
Pflichtangaben fuer Geschaeftskorrespondenz:
http://deutsche-boerse.com/letterhead END OF DISCLAIMER
_______________________________________________
fossology mailing list
[email protected]
http://fossology.org/mailman/listinfo/fossology
----------------------------------------------------------------------------
Clearstream Services S.A.
42 Avenue JF Kennedy, L-1855 Luxembourg
Société anonyme is organised with limited liability
in the Grand Duchy of Luxembourg R.C.S. Luxembourg B 60911.
-----------------------------------------
Visit us at http://www.clearstream.com
IMPORTANT MESSAGE
Internet communications are not secure and therefore Clearstream
International does not accept legal responsibility for the contents
of this message.
The information contained in this e-mail is confidential and may be
legally privileged. It is intended solely for the addressee. If you
are not the intended recipient, any disclosure, copying,
distribution or any action taken or omitted to be taken in reliance
on it, is prohibited and may be unlawful. Any views expressed in
this e-mail are those of the individual sender, except where the
sender specifically states them to be the views of Clearstream
International or of any of its affiliates or subsidiaries.
Legally required information for business correspondence/
Gesetzliche Pflichtangaben fuer Geschaeftskorrespondenz:
http://deutsche-boerse.com/letterhead
END OF DISCLAIMER_______________________________________________
fossology mailing list
[email protected]
http://fossology.org/mailman/listinfo/fossology
