[FOSSology] Fossology install fails on Ubuntu
Bob, I was not able to get fossology to run after the initial install. So I have removed fossology with purge command. Now when I try to grep for fossology, I do not get any results. So it is removed. When I try to install it with sudo apt-get install fossology command, it gives error message Following package have unmet dependencies: Fossology: Depends: Fossology-web-single but it is not going to be installed E: broken packages If I try to install Fossology-web-single, then it lists another package that it has dependency, it goes on and on giving list of one package after the other. What is the best way to install fossology? Thanks. Regards, Gurbax Deol 214-567-3311 From: Bob Gobeille [mailto:bob.gobei...@hp.com] Sent: Wednesday, August 04, 2010 4:31 PM To: Deol, Gurbax Subject: Re: Question: Fossology on Ubuntu Hello Gurbax, In the installation you created a website. So you should be able to find it at http://yourhostname/repo/ Did you apt-get install or install from source? Would you mind if we have this conversation on our public mailing list? That way other developers can join. Bob Gobeille On Aug 4, 2010, at 3:05 PM, Deol, Gurbax wrote: Hello Bob, We, at TI, are looking into Fossology as one of the tools that we may want to work with. I managed to install Fossology on Ubuntu. After running into some issues, I seems to be installed. I have been looking at the Fossology website to find out how to invoke this tool. I am not able to do find anything on it. Once the tool is installed, how can I launch it? Thank you so much for all your assistance. Regards, Gurbax Deol Configuration Management Tools Texas Instruments, Inc. gur...@ti.comblocked::mailto:gur...@ti.com 214-567-3311 972-761-5168 Fax ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Fossology install fails on Ubuntu
Hi Gurbax, There are several dependencies for fossology, described on the project website at http://fossology.org/sysadmin_documentation#installation. There is a utility called fo-installdeps we use to install dependencies. You can access it from the source tree at: http://fossology.svn.sourceforge.net/viewvc/fossology/trunk/fossology/utils/fo-installdeps?revision=3388 Mary From: Deol, Gurbax [mailto:gur...@ti.com] Sent: Tuesday, August 17, 2010 9:19 AM To: Gobeille, Robert; Laser, Mary; fossology@fossology.org Subject: Fossology install fails on Ubuntu Bob, I was not able to get fossology to run after the initial install. So I have removed fossology with purge command. Now when I try to grep for fossology, I do not get any results. So it is removed. When I try to install it with sudo apt-get install fossology command, it gives error message Following package have unmet dependencies: Fossology: Depends: Fossology-web-single but it is not going to be installed E: broken packages If I try to install Fossology-web-single, then it lists another package that it has dependency, it goes on and on giving list of one package after the other. What is the best way to install fossology? Thanks. Regards, Gurbax Deol 214-567-3311 From: Bob Gobeille [mailto:bob.gobei...@hp.com] Sent: Wednesday, August 04, 2010 4:31 PM To: Deol, Gurbax Subject: Re: Question: Fossology on Ubuntu Hello Gurbax, In the installation you created a website. So you should be able to find it at http://yourhostname/repo/ Did you apt-get install or install from source? Would you mind if we have this conversation on our public mailing list? That way other developers can join. Bob Gobeille On Aug 4, 2010, at 3:05 PM, Deol, Gurbax wrote: Hello Bob, We, at TI, are looking into Fossology as one of the tools that we may want to work with. I managed to install Fossology on Ubuntu. After running into some issues, I seems to be installed. I have been looking at the Fossology website to find out how to invoke this tool. I am not able to do find anything on it. Once the tool is installed, how can I launch it? Thank you so much for all your assistance. Regards, Gurbax Deol Configuration Management Tools Texas Instruments, Inc. gur...@ti.comblocked::mailto:gur...@ti.com 214-567-3311 972-761-5168 Fax ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Db tables
Hi Matt, It looks like your database was created with the wrong encoding. By default, the postgres package is installed with UTF8 encoding. However, the fossology database cluster must be created with SQL_ASCII encoding. If you do not specify SQL_ASCII, the fossology db cluster will default to the postgres db encoding. This seems the most plausible explanation for your error below. You can check by invoking psql on the command line as user poastgres: postg...@mysys:~$ psql Welcome to psql 8.3.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 postgres=# \encoding SQL_ASCII postgres=# \c fossology You are now connected to database fossology. fossology=# \encoding SQL_ASCII fossology=# If your installation does not match the example above, I suggest you drop the fossology database (drop database fossology) and recreate it by re-running fo-postinstall. Mary -Original Message- From: McIntosh, Matt [mailto:matt_mcint...@mentor.com] Sent: Tuesday, August 17, 2010 11:31 AM To: Laser, Mary Subject: RE: Db tables Mary, This got me further. I'm now getting the below errors in the log. Also, did you see my second email yesterday with the binary display on the web pages? Thanks, -Matt 2010-08-17 10:14:43 scheduler[17680] : Child[7] 'agent=copyright host=localhost ' state=SPAWNED(4) @ Tue Aug 17 10:14:43 2010 2010-08-17 10:14:44 scheduler[17680] : Child[7] 'agent=copyright host=localhost ' state=READY(5) @ Tue Aug 17 10:14:44 2010 2010-08-17 10:14:44 scheduler[17680] : ERROR: In thread 7: DB Access error, returned -1. 2010-08-17 10:14:44 scheduler[17680] : DEBUG[7]: ERROR: DB Access error, returned -1. 2010-08-17 10:14:44 scheduler[17680] : ERROR: In thread 7: DB STATUS: PGRES_FATAL_ERROR 2010-08-17 10:14:44 scheduler[17680] : DEBUG[7]: ERROR: DB STATUS: PGRES_FATAL_ERROR 2010-08-17 10:14:44 scheduler[17680] : ERROR: In thread 7: DB ERRMSG: invalid byte sequence for encoding UTF8: 0x00 2010-08-17 10:14:44 scheduler[17680] : DEBUG[7]: ERROR: DB ERRMSG: invalid byte sequence for encoding UTF8: 0x00 2010-08-17 10:14:44 scheduler[17680] : DEBUG[7]: HINT: This error can also happen if the byte sequence does not match the encoding expected by the server, which is controlled by client_encoding. 2010-08-17 10:14:44 scheduler[17680] : ERROR: In thread 7: sql=INSERT INTO copyright (agent_fk, pfile_fk, copy_startbyte, copy_endbyte, content, hash, type) 2010-08-17 10:14:44 scheduler[17680] : DEBUG[7]: ERROR: sql=INSERT INTO copyright (agent_fk, pfile_fk, copy_startbyte, copy_endbyte, content, hash, type) 2010-08-17 10:14:44 scheduler[17680] : DEBUG[7]: VALUES (24, 19421, 1235, 1276, E'http\:\/\/www\.w3\.org\/TR\/html4\/loose\.dtd\\\^A\000\^N', E'0x781313cb0a6a289b', 'url') 2010-08-17 10:14:44 scheduler[17680] : ERROR: In thread 7: filename=9133AD80C7B6AC5E2880BFD86002DA81006CDB77.3FF4F6DD09C98FC3EF27C C D4531EECCD.6412 2010-08-17 10:14:44 scheduler[17680] : DEBUG[7]: ERROR: filename=9133AD80C7B6AC5E2880BFD86002DA81006CDB77.3FF4F6DD09C98FC3EF27C C D4531EECCD.6412 2010-08-17 10:14:44 scheduler[17680] : FATAL: In thread 7: An error occurred in the main agent loop. Please consult the provided traceback. 2010-08-17 10:14:44 scheduler[17680] : DEBUG[7]: FATAL: An error occurred in the main agent loop. Please consult the provided traceback. 2010-08-17 10:14:44 scheduler[17680] : DEBUG[7]:Traceback (most recent call last): 2010-08-17 10:14:44 scheduler[17680] : DEBUG[7]: File /usr/lib/fossology/agents/copyright/copyright.py, line 284, in agent 2010-08-17 10:14:44 scheduler[17680] : DEBUG[7]: print sys.stdout, 'ERROR: Could not process file.\n\tupload_pk = %s, pfile_pk = %s, pfilename = %s' % (upload_pk, jobs[i]['pfile_pk'], jobs[i]['pfilename']) 2010-08-17 10:14:44 scheduler[17680] : DEBUG[7]:NameError: global name 'jobs' is not defined 2010-08-17 10:14:54 scheduler[17680] : ERROR: Child[7] died prematurely (was state RUNNING, signal was 0) 2010-08-17 10:14:54 scheduler[17680] : Thread 7: 2010-08-17 10:14:54 scheduler[17680] : PID: 17819 2010-08-17 10:14:54 scheduler[17680] : Pipes: in=7-8 / out=10-9 2010-08-17 10:14:54 scheduler[17680] : Attr: 'agent=copyright host=localhost ' 2010-08-17 10:14:54 scheduler[17680] : Command: '/usr/lib/fossology/agents/copyright/run.py --model /usr/share/fossology/model.dat --agent' 2010-08-17 10:14:54 scheduler[17680] : Parm: '5 ' 2010-08-17 10:14:54 scheduler[17680] : Heartbeat: Tue Aug 17 10:14:44 2010 2010-08-17 10:14:54 scheduler[17680] : State: Tue Aug 17 10:14:44 2010 2010-08-17 10:14:54 scheduler[17680] : Status: 6 (RUNNING) 2010-08-17 10:14:54 scheduler[17680] : Spawn: 1 at Tue Aug 17 10:14:43 2010 2010-08-17 10:14:54
[FOSSology] Fossology Install
Mary, Spent too much time trouble shooting it. Since it was a new machine I am setting up, I have un-installed and re-installed Ubuntu OS on my machine. At this point, there is no trace of Fossology. What is the best way to install Fossology without running into issues? Thanks for your support in advance. Regards, Gurbax Deol 214-567-3311 -Original Message- From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of Laser, Mary Sent: Tuesday, August 17, 2010 2:19 PM To: McIntosh, Matt Cc: fossology@fossology.org Subject: Re: [FOSSology] Db tables Hi Matt, It looks like your database was created with the wrong encoding. By default, the postgres package is installed with UTF8 encoding. However, the fossology database cluster must be created with SQL_ASCII encoding. If you do not specify SQL_ASCII, the fossology db cluster will default to the postgres db encoding. This seems the most plausible explanation for your error below. You can check by invoking psql on the command line as user poastgres: postg...@mysys:~$ psql Welcome to psql 8.3.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 postgres=# \encoding SQL_ASCII postgres=# \c fossology You are now connected to database fossology. fossology=# \encoding SQL_ASCII fossology=# If your installation does not match the example above, I suggest you drop the fossology database (drop database fossology) and recreate it by re-running fo-postinstall. Mary -Original Message- From: McIntosh, Matt [mailto:matt_mcint...@mentor.com] Sent: Tuesday, August 17, 2010 11:31 AM To: Laser, Mary Subject: RE: Db tables Mary, This got me further. I'm now getting the below errors in the log. Also, did you see my second email yesterday with the binary display on the web pages? Thanks, -Matt 2010-08-17 10:14:43 scheduler[17680] : Child[7] 'agent=copyright host=localhost ' state=SPAWNED(4) @ Tue Aug 17 10:14:43 2010 2010-08-17 10:14:44 scheduler[17680] : Child[7] 'agent=copyright host=localhost ' state=READY(5) @ Tue Aug 17 10:14:44 2010 2010-08-17 10:14:44 scheduler[17680] : ERROR: In thread 7: DB Access error, returned -1. 2010-08-17 10:14:44 scheduler[17680] : DEBUG[7]: ERROR: DB Access error, returned -1. 2010-08-17 10:14:44 scheduler[17680] : ERROR: In thread 7: DB STATUS: PGRES_FATAL_ERROR 2010-08-17 10:14:44 scheduler[17680] : DEBUG[7]: ERROR: DB STATUS: PGRES_FATAL_ERROR 2010-08-17 10:14:44 scheduler[17680] : ERROR: In thread 7: DB ERRMSG: invalid byte sequence for encoding UTF8: 0x00 2010-08-17 10:14:44 scheduler[17680] : DEBUG[7]: ERROR: DB ERRMSG: invalid byte sequence for encoding UTF8: 0x00 2010-08-17 10:14:44 scheduler[17680] : DEBUG[7]: HINT: This error can also happen if the byte sequence does not match the encoding expected by the server, which is controlled by client_encoding. 2010-08-17 10:14:44 scheduler[17680] : ERROR: In thread 7: sql=INSERT INTO copyright (agent_fk, pfile_fk, copy_startbyte, copy_endbyte, content, hash, type) 2010-08-17 10:14:44 scheduler[17680] : DEBUG[7]: ERROR: sql=INSERT INTO copyright (agent_fk, pfile_fk, copy_startbyte, copy_endbyte, content, hash, type) 2010-08-17 10:14:44 scheduler[17680] : DEBUG[7]: VALUES (24, 19421, 1235, 1276, E'http\:\/\/www\.w3\.org\/TR\/html4\/loose\.dtd\\\^A\000\^N', E'0x781313cb0a6a289b', 'url') 2010-08-17 10:14:44 scheduler[17680] : ERROR: In thread 7: filename=9133AD80C7B6AC5E2880BFD86002DA81006CDB77.3FF4F6DD09C98FC3EF27 C C D4531EECCD.6412 2010-08-17 10:14:44 scheduler[17680] : DEBUG[7]: ERROR: filename=9133AD80C7B6AC5E2880BFD86002DA81006CDB77.3FF4F6DD09C98FC3EF27 C C D4531EECCD.6412 2010-08-17 10:14:44 scheduler[17680] : FATAL: In thread 7: An error occurred in the main agent loop. Please consult the provided traceback. 2010-08-17 10:14:44 scheduler[17680] : DEBUG[7]: FATAL: An error occurred in the main agent loop. Please consult the provided traceback. 2010-08-17 10:14:44 scheduler[17680] : DEBUG[7]:Traceback (most recent call last): 2010-08-17 10:14:44 scheduler[17680] : DEBUG[7]: File /usr/lib/fossology/agents/copyright/copyright.py, line 284, in agent 2010-08-17 10:14:44 scheduler[17680] : DEBUG[7]: print sys.stdout, 'ERROR: Could not process file.\n\tupload_pk = %s, pfile_pk = %s, pfilename = %s' % (upload_pk, jobs[i]['pfile_pk'], jobs[i]['pfilename']) 2010-08-17 10:14:44 scheduler[17680] : DEBUG[7]:NameError: global name 'jobs' is not defined 2010-08-17 10:14:54 scheduler[17680] : ERROR: Child[7] died prematurely (was state RUNNING, signal was 0) 2010-08-17 10:14:54 scheduler[17680] : Thread 7: 2010-08-17 10:14:54 scheduler[17680] : PID: 17819 2010-08-17 10:14:54 scheduler[17680] : Pipes: in=7-8 / out=10-9
Re: [FOSSology] Fossology Install
Gurbax, I think the best thing to do now is provide the info taggart requested What distribution (name and version) are you using and what apt source are you using to get the packages? You shouldn't be having all these issues so with the above info we can at least test the release/disto combination. Bob Gobeille On Aug 17, 2010, at 3:01 PM, Deol, Gurbax wrote: Mary, Spent too much time trouble shooting it. Since it was a new machine I am setting up, I have un-installed and re-installed Ubuntu OS on my machine. At this point, there is no trace of Fossology. What is the best way to install Fossology without running into issues? Thanks for your support in advance. ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
