|
Re: EXTERNAL: Re: [FOSSology] Unpacking .msi Files - Fossology Version 3.8.1
D Frye
Thank you. Here is the URL:
toggle quoted messageShow quoted text
https://ftp.mozilla.org/pub/firefox/releases/84.0/win64/en-US/Firefox%20Setup%2084.0.msi
-----Original Message-----
From: main@lists.fossology.org <main@lists.fossology.org> On Behalf Of Michael C. Jaeger Sent: Thursday, December 31, 2020 6:09 AM To: main@lists.fossology.org Subject: EXTERNAL: Re: [FOSSology] Unpacking .msi Files - Fossology Version 3.8.1 Hi, please help us a little bit with an example file - an URL to it would be great. I do not have a an *.msi file handy right now and I am not sure if it will be better if you could share the file you re having problems with? If you feel that is too much of information revealing to the public, you could send the URL to donwload the file(s) in question directly to my e-mail. Kind regards and if you do not respond earlier, have good start into 2021! - Michael On 30. Dec 2020, at 16:36, D Frye <deborah.l.frye@lmco.com> wrote:
|
|
|
|
Re: Unpacking .msi Files - Fossology Version 3.8.1
Michael C. Jaeger
Hi,
toggle quoted messageShow quoted text
please help us a little bit with an example file - an URL to it would be great. I do not have a an *.msi file handy right now and I am not sure if it will be better if you could share the file you re having problems with? If you feel that is too much of information revealing to the public, you could send the URL to donwload the file(s) in question directly to my e-mail. Kind regards and if you do not respond earlier, have good start into 2021! - Michael
On 30. Dec 2020, at 16:36, D Frye <deborah.l.frye@lmco.com> wrote:
|
|
|
|
FW: Unpacking .msi Files - Fossology Version 3.8.1
D Frye
Everyone was so helpful with the issue of unpacking .deb files in the newer version of Fossology. It looks like there’s also an issue with unpacking .msi files. Has anyone identified a fix for these?
Please let me know.
Thanks – Deb Frye
From: main@... <main@...>
On Behalf Of Frye, Deborah L (US)
Sent: Monday, November 9, 2020 9:19 AM To: main@... Subject: EXTERNAL: Re: [FOSSology] Unpacking Debian Files - Fossology Version 3.8.1
Thanks for the quick find and fix.
Yes, we did change the base system on which Fossology is running. Our Fossology 3.8.1 instance is deployed to a separate server running Ubuntu 18.04 LTS.
Based on your diagnosis, as a workaround we tried changing /etc/mime.types to point 'deb' files back to the previous MIME type of "application/x-debian-package" but still saw the same behavior. Next we will try a custom compiled version that applies your patch.
Thank you for your prompt response!
Deb
Hello Frye,
From what I understood with inconsistency in the unpacking, the deb files were not extracted at all and I tried it on my machine and it didn't work.
It seems like the mimetype of .deb archives was changed (only official document I could find is this https://www.iana.org/assignments/media-types/application/vnd.debian.binary-package). I have created a PR with the new mimetype which you can find here: https://github.com/fossology/fossology/pull/1831
Also, I was wondering did you changed the base system the fossology is running, as there was no change in the code base related to it?
With best regards, Gaurav Mishra From:
main@... <main@...> on behalf of D Frye <deborah.l.frye@...>
Recently upgraded Fossology to Version 3.8.1. Previous version unpacked and scanned Debian files within FOSS packages; however, seems like new version is not consistently unpacking them. Has anyone else run into this?
Any help would be greatly appreciated. Deb Frye Lockheed Martin Corporation Rotary and Mission Systems (RMS) Software License Compliance / F-35 3PC Lead
|
|
|
|
Gsoc 2021
Hey everyone ! Hope u are doing well ! My self Akshay and want to contribute in open source community .As i dont want to be in trapped in learning loops i want to implement what i learn by contributing in open source ...Can anyone here guide me how i start my contribution .
|
|
|
|
Re: Docker Container Restart Problems
flp@...
Just a short update. Checking out the repository and building the containers from source works. I think it should also work with the dockerhub container but I guess I'm missing some essential information to get that work since it's quite annoying to regularily pull the current code.
|
|
|
|
Re: GSoC 2021
Hello Lasal,
Nice to have you here with us! Under FOSSology, we have 3 projects with which we participate in GSoC. Hopefully we will be selected as an organization this year around as well by Google.
I'll give you a brief overview of the projects so you can explore more about them.
With best regards,
Gaurav Mishra
From: main@... <main@...> on behalf of doctor.lasalflair@... <doctor.lasalflair@...>
Sent: 16 November 2020 20:43 To: main@... <main@...> Subject: [FOSSology] GSoC 2021 Hello Everyone!!! I am Lasal Jayawardena and I am very happy to join the community.
I am planning to enter the GSoC 2021 and I want to start contributing. Can anyone give some pointers as to how I can do that?
|
|
|
|
GSoC 2021
doctor.lasalflair@...
Hello Everyone!!! I am Lasal Jayawardena and I am very happy to join the community.
I am planning to enter the GSoC 2021 and I want to start contributing. Can anyone give some pointers as to how I can do that?
|
|
|
|
Re: Unpacking Debian Files - Fossology Version 3.8.1
Hi Deb, Jeremiah
|
|
|
|
Re: Unpacking Debian Files - Fossology Version 3.8.1
Hello Deb,
Yesterday we merged the PR with the fix. You can compile the latest master or pull the latest docker image from Docker hub with the patch.
With best regards, Gaurav Mishra
From: main@... <main@...>
On Behalf Of D Frye
Sent: 09 November 2020 19:49 To: main@... Subject: Re: [FOSSology] Unpacking Debian Files - Fossology Version 3.8.1
Thanks for the quick find and fix.
Yes, we did change the base system on which Fossology is running. Our Fossology 3.8.1 instance is deployed to a separate server running Ubuntu 18.04 LTS.
Based on your diagnosis, as a workaround we tried changing /etc/mime.types to point 'deb' files back to the previous MIME type of "application/x-debian-package" but still saw the same behavior. Next we will try a custom compiled version that applies your patch.
Thank you for your prompt response!
Deb
Hello Frye,
From what I understood with inconsistency in the unpacking, the deb files were not extracted at all and I tried it on my machine and it didn't work.
It seems like the mimetype of .deb archives was changed (only official document I could find is this https://www.iana.org/assignments/media-types/application/vnd.debian.binary-package). I have created a PR with the new mimetype which you can find here: https://github.com/fossology/fossology/pull/1831
Also, I was wondering did you changed the base system the fossology is running, as there was no change in the code base related to it?
With best regards, Gaurav Mishra From:
main@... <main@...> on behalf of D Frye <deborah.l.frye@...>
Recently upgraded Fossology to Version 3.8.1. Previous version unpacked and scanned Debian files within FOSS packages; however, seems like new version is not consistently unpacking them. Has anyone else run into this?
Any help would be greatly appreciated. Deb Frye Lockheed Martin Corporation Rotary and Mission Systems (RMS) Software License Compliance / F-35 3PC Lead
|
|
|
|
Re: Unpacking Debian Files - Fossology Version 3.8.1
D Frye
Thanks for the quick find and fix.
Yes, we did change the base system on which Fossology is running. Our Fossology 3.8.1 instance is deployed to a separate server running Ubuntu 18.04 LTS.
Based on your diagnosis, as a workaround we tried changing /etc/mime.types to point 'deb' files back to the previous MIME type of "application/x-debian-package" but still saw the same behavior. Next we will try a custom compiled version that applies your patch.
Thank you for your prompt response!
Deb
From: main@... <main@...>
On Behalf Of Gaurav Mishra
Sent: Monday, November 9, 2020 4:24 AM To: main@... Subject: EXTERNAL: Re: [FOSSology] Unpacking Debian Files - Fossology Version 3.8.1
Hello Frye,
From what I understood with inconsistency in the unpacking, the deb files were not extracted at all and I tried it on my machine and it didn't work.
It seems like the mimetype of .deb archives was changed (only official document I could find is this https://www.iana.org/assignments/media-types/application/vnd.debian.binary-package). I have created a PR with the new mimetype which you can find here: https://github.com/fossology/fossology/pull/1831
Also, I was wondering did you changed the base system the fossology is running, as there was no change in the code base related to it?
With best regards, Gaurav Mishra From:
main@... <main@...> on behalf of D Frye <deborah.l.frye@...>
Recently upgraded Fossology to Version 3.8.1. Previous version unpacked and scanned Debian files within FOSS packages; however, seems like new version is not consistently unpacking them. Has anyone else run into this?
Any help would be greatly appreciated. Deb Frye Lockheed Martin Corporation Rotary and Mission Systems (RMS) Software License Compliance / F-35 3PC Lead
|
|
|
|
Re: Unpacking Debian Files - Fossology Version 3.8.1
Hello Frye,
From what I understood with inconsistency in the unpacking, the deb files were not extracted at all and I tried it on my machine and it didn't work.
It seems like the mimetype of .deb archives was changed (only official document I could find is this
https://www.iana.org/assignments/media-types/application/vnd.debian.binary-package).
I have created a PR with the new mimetype which you can find here:
https://github.com/fossology/fossology/pull/1831
Also, I was wondering did you changed the base system the fossology is running, as there was no change in the code base related to it?
With best regards,
Gaurav Mishra
From: main@... <main@...> on behalf of D Frye <deborah.l.frye@...>
Sent: 05 November 2020 22:55 To: main@... <main@...> Subject: [FOSSology] Unpacking Debian Files - Fossology Version 3.8.1 Recently upgraded Fossology to Version 3.8.1. Previous version unpacked and scanned Debian files within FOSS packages; however, seems like new version is not consistently unpacking them. Has anyone else run into this?
Any help would be greatly appreciated. Deb Frye Lockheed Martin Corporation Rotary and Mission Systems (RMS) Software License Compliance / F-35 3PC Lead
|
|
|
|
Unpacking Debian Files - Fossology Version 3.8.1
D Frye
Recently upgraded Fossology to Version 3.8.1. Previous version unpacked and scanned Debian files within FOSS packages; however, seems like new version is not consistently unpacking them. Has anyone else run into this?
Any help would be greatly appreciated. Deb Frye Lockheed Martin Corporation Rotary and Mission Systems (RMS) Software License Compliance / F-35 3PC Lead
|
|
|
|
Re: Docker Container Restart Problems
PHP Warning: syntax error, unexpected ')' in/usr/local/etc/fossology/Db.conf on line 4 Did you check the content of the file Db.conf ? -- Nicolas Toussaint - Open Source Expert OBS - Orange Business Services - Lyon, France Tel: +33 608 763 559 On 28/10/2020 13:10, flp via lists.fossology.org wrote: If I downgrade to 9.6 with my docker-compose file, I get the following error:
|
|
|
|
Re: Docker Container Restart Problems
flp@...
If I downgrade to 9.6 with my docker-compose file, I get the following error:
*** Running postinstall for common actions*** *** Creating user and group *** NOTE: group 'fossy' already exists, good. NOTE: user 'fossy' already exists, good. *** Making sure needed dirs exist with right ownership/permissions *** *** clearing file cache *** NOTE: Repository already exists at /srv/fossology/repository NOTE: Running the PostgreSQL vacuum and analyze command can result in a large database performance improvement. We suggest that you either configure postgres to run its autovacuum and autoanalyze daemons, or maintagent -D in a cron job, or run Admin > Maintenance on a regular basis. Admin > Dashboard will show you the last time vacuum and analyze have been run. NOTE: using external DB on host foss-db *** update the database and license_ref table *** PHP Warning: syntax error, unexpected ')' in /usr/local/etc/fossology/Db.conf on line 4 in /usr/local/share/fossology/lib/php/common-sysconfig.php on line 98 PHP Warning: Invalid argument supplied for foreach() in /usr/local/share/fossology/lib/php/common-sysconfig.php on line 103 PHP Notice: Undefined index: user in /usr/local/share/fossology/lib/php/libschema.php on line 520 Old release was 3.0.1 *** Cleaning tables for new constraints *** Table author or agent does not exists, not cleaning! Table author or pfile does not exists, not cleaning! Table bucket_container or bucket_def does not exists, not cleaning! Table bucket_file or bucket_def does not exists, not cleaning! Table bucket_file or pfile does not exists, not cleaning! Table copyright or agent does not exists, not cleaning! Table copyright_decision or pfile does not exists, not cleaning! Table ecc or agent does not exists, not cleaning! Table ecc or pfile does not exists, not cleaning! Table ecc_decision or pfile does not exists, not cleaning! Table highlight_keyword or pfile does not exists, not cleaning! Table keyword or agent does not exists, not cleaning! Table keyword or pfile does not exists, not cleaning! Table keyword_decision or pfile does not exists, not cleaning! Table pkg_deb_req or pkg_deb does not exists, not cleaning! Table pkg_rpm_req or pkg_rpm does not exists, not cleaning! Table report_cache or upload does not exists, not cleaning! Table report_info or upload does not exists, not cleaning! Table reportgen or upload does not exists, not cleaning! Table upload or pfile does not exists, not cleaning! Table upload_clearing_license or upload does not exists, not cleaning! Table obligation_ref does not exists, not cleaning! Table report_info does not exists, not cleaning! Table obligation_ref does not exists, not cleaning! Table group_user_member does not exists, not cleaning! Removed 0 rows from tables with new constraints PHP Notice: Undefined index: user in /usr/local/share/fossology/lib/php/libschema.php on line 520 PHP Warning: pg_query(): Query failed: ERROR: column "group_fk" of relation "license_candidate" already exists in /usr/local/share/fossology/lib/php/Db/Driver/Postgres.php on line 79 [2020-10-28 12:00:24] /usr/local/share/fossology/lib/php/libschema.php.CRITICAL: ERROR: column "group_fk" of relation "license_candidate" already exists [] [] PHP Fatal error: Uncaught Fossology\Lib\Exception: error executing: ALTER TABLE "license_candidate" ADD COLUMN "group_fk" int8 ERROR: column "group_fk" of relation "license_candidate" already exists in /usr/local/share/fossology/lib/php/Db/DbManager.php:144 Stack trace: #0 /usr/local/share/fossology/lib/php/Db/DbManager.php(203): Fossology\Lib\Db\DbManager->checkResult(false, 'ALTER TABLE "li...') #1 /usr/local/share/fossology/lib/php/libschema.php(299): Fossology\Lib\Db\DbManager->queryOnce('ALTER TABLE "li...') #2 /usr/local/share/fossology/lib/php/libschema.php(163): fo_libschema->applyTables(true) #3 /usr/local/lib/fossology/fossinit.php(196): fo_libschema->applySchema('/usr/local/shar...', false, 'fossology', Array) #4 {main} thrown in /usr/local/share/fossology/lib/php/Db/DbManager.php on line 144
|
|
|
|
Re: Docker Container Restart Problems
Hi flp,
toggle quoted messageShow quoted text
I did a quick check on my server, reusing you Dockerfile: - changing to docker-compose version to 3.3 (because I had to) - setting POSTGRES_* variables to fossology / fossy / fossy It looks like the DB container keeps on restarting with Postgres v11, but that does not happen when I downgrade to v9.6 (which is the version I use in production) Hoping it helps a little Nico -- Nicolas Toussaint - Open Source Expert OBS - Orange Business Services - Lyon, France Tel: +33 608 763 559
On 27/10/2020 11:48, Michael C. Jaeger wrote:
|
|
|
|
Re: Docker Container Restart Problems
Michael C. Jaeger
Hello flp,
I am not very familiar with docker, so I do not have a good insight on what you do with your custom docker file cited at the end. I checked out current master and executed docker-compose up and down and up and down with uploading packages in between - > no issues at all.
Would there be any context information (like an old image laying around which is not subject for update) for your setup? Or did you create the docker-compose setup from scratch just based on the attached docker-compose.yml ?
Kind regards, Michael
From: <main@...> on behalf of "flp via lists.fossology.org" <flp=mailbox.org@...>
Hey, *** Running postinstall for common actions*** *** Creating user and group *** NOTE: group 'fossy' already exists, good. NOTE: user 'fossy' already exists, good. *** Making sure needed dirs exist with right ownership/permissions *** *** clearing file cache *** NOTE: Repository already exists at /srv/fossology/repository NOTE: Running the PostgreSQL vacuum and analyze command can result in a large database performance improvement. We suggest that you either configure postgres to run its autovacuum and autoanalyze daemons, or maintagent -D in a cron job, or run Admin > Maintenance on a regular basis. Admin > Dashboard will show you the last time vacuum and analyze have been run. NOTE: using external DB on host foss-db *** update the database and license_ref table *** PHP Warning: syntax error, unexpected ')' in /usr/local/etc/fossology/Db.conf on line 4 in /usr/local/share/fossology/lib/php/common-sysconfig.php on line 96 PHP Warning: Invalid argument supplied for foreach() in /usr/local/share/fossology/lib/php/common-sysconfig.php on line 101 PHP Notice: Undefined index: user in /usr/local/share/fossology/lib/php/libschema.php on line 520 Old release was 3.0.1 *** Cleaning tables for new constraints *** Table author or agent does not exists, not cleaning! Table author or pfile does not exists, not cleaning! Table bucket_container or bucket_def does not exists, not cleaning! Table bucket_file or bucket_def does not exists, not cleaning! Table bucket_file or pfile does not exists, not cleaning! Table copyright or agent does not exists, not cleaning! Table copyright_decision or pfile does not exists, not cleaning! Table ecc or agent does not exists, not cleaning! Table ecc or pfile does not exists, not cleaning! Table ecc_decision or pfile does not exists, not cleaning! Table highlight_keyword or pfile does not exists, not cleaning! Table keyword or agent does not exists, not cleaning! Table keyword or pfile does not exists, not cleaning! Table keyword_decision or pfile does not exists, not cleaning! Table pkg_deb_req or pkg_deb does not exists, not cleaning! Table pkg_rpm_req or pkg_rpm does not exists, not cleaning! Table report_cache or upload does not exists, not cleaning! Table report_info or upload does not exists, not cleaning! Table reportgen or upload does not exists, not cleaning! Table upload or pfile does not exists, not cleaning! Table upload_clearing_license or upload does not exists, not cleaning! Table obligation_ref does not exists, not cleaning! Table report_info does not exists, not cleaning! Table obligation_ref does not exists, not cleaning! Table group_user_member does not exists, not cleaning! Removed 0 rows from tables with new constraints PHP Notice: Undefined index: user in /usr/local/share/fossology/lib/php/libschema.php on line 520 PHP Warning: pg_query(): Query failed: ERROR: column "rf_copyleft" of relation "license_ref" already exists in /usr/local/share/fossology/lib/php/Db/Driver/Postgres.php on line 79 [2020-10-18 21:38:19] /usr/local/share/fossology/lib/php/libschema.php.CRITICAL: ERROR: column "rf_copyleft" of relation "license_ref" already exists [] [] PHP Fatal error: Uncaught Fossology\Lib\Exception: error executing: ALTER TABLE "license_ref" ADD COLUMN "rf_copyleft" bit(1)
ERROR: column "rf_copyleft" of relation "license_ref" already exists in /usr/local/share/fossology/lib/php/Db/DbManager.php:144 Stack trace: #0 /usr/local/share/fossology/lib/php/Db/DbManager.php(203): Fossology\Lib\Db\DbManager->checkResult(false, 'ALTER TABLE "li...') #1 /usr/local/share/fossology/lib/php/libschema.php(299): Fossology\Lib\Db\DbManager->queryOnce('ALTER TABLE "li...') #2 /usr/local/share/fossology/lib/php/libschema.php(161): fo_libschema->applyTables() #3 /usr/local/lib/fossology/fossinit.php(196): fo_libschema->applySchema('/usr/local/shar...', false, 'fossology', Array) #4 {main} thrown in /usr/local/share/fossology/lib/php/Db/DbManager.php on line 144
*** Running postinstall for common actions*** *** Creating user and group *** NOTE: group 'fossy' already exists, good. NOTE: user 'fossy' already exists, good. *** Making sure needed dirs exist with right ownership/permissions *** *** clearing file cache *** NOTE: Repository already exists at /srv/fossology/repository NOTE: Running the PostgreSQL vacuum and analyze command can result in a large database performance improvement. We suggest that you either configure postgres to run its autovacuum and autoanalyze daemons, or maintagent -D in a cron job, or run Admin > Maintenance on a regular basis. Admin > Dashboard will show you the last time vacuum and analyze have been run. NOTE: using external DB on host foss-db *** update the database and license_ref table *** PHP Warning: syntax error, unexpected ')' in /usr/local/etc/fossology/Db.conf on line 4 in /usr/local/share/fossology/lib/php/common-sysconfig.php on line 96 PHP Warning: Invalid argument supplied for foreach() in /usr/local/share/fossology/lib/php/common-sysconfig.php on line 101 PHP Notice: Undefined index: user in /usr/local/share/fossology/lib/php/libschema.php on line 520 Old release was 0 *** Cleaning tables for new constraints *** Table author or agent does not exists, not cleaning! Table author or pfile does not exists, not cleaning! Table bucket_container or bucket_def does not exists, not cleaning! Table bucket_file or bucket_def does not exists, not cleaning! Table bucket_file or pfile does not exists, not cleaning! Table copyright or agent does not exists, not cleaning! Table copyright_decision or pfile does not exists, not cleaning! Table ecc or agent does not exists, not cleaning! Table ecc or pfile does not exists, not cleaning! Table ecc_decision or pfile does not exists, not cleaning! Table highlight_keyword or pfile does not exists, not cleaning! Table keyword or agent does not exists, not cleaning! Table keyword or pfile does not exists, not cleaning! Table keyword_decision or pfile does not exists, not cleaning! Table pkg_deb_req or pkg_deb does not exists, not cleaning! Table pkg_rpm_req or pkg_rpm does not exists, not cleaning! Table report_cache or upload does not exists, not cleaning! Table report_info or upload does not exists, not cleaning! Table reportgen or upload does not exists, not cleaning! Table upload or pfile does not exists, not cleaning! Table upload_clearing_license or upload does not exists, not cleaning! Table obligation_ref does not exists, not cleaning! Table report_info does not exists, not cleaning! Table obligation_ref does not exists, not cleaning! Table group_user_member does not exists, not cleaning! Removed 0 rows from tables with new constraints PHP Notice: Undefined index: user in /usr/local/share/fossology/lib/php/libschema.php on line 520 PHP Warning: pg_query(): Query failed: ERROR: column "option_value" of relation "sysconfig" already exists in /usr/local/share/fossology/lib/php/Db/Driver/Postgres.php on line 79 [2020-10-22 21:49:47] /usr/local/share/fossology/lib/php/libschema.php.CRITICAL: ERROR: column "option_value" of relation "sysconfig" already exists [] [] PHP Fatal error: Uncaught Fossology\Lib\Exception: error executing: ALTER TABLE "sysconfig" ADD COLUMN "option_value" character varying(40) DEFAULT NULL
ERROR: column "option_value" of relation "sysconfig" already exists in /usr/local/share/fossology/lib/php/Db/DbManager.php:144 Stack trace: #0 /usr/local/share/fossology/lib/php/Db/DbManager.php(203): Fossology\Lib\Db\DbManager->checkResult(false, 'ALTER TABLE "sy...') #1 /usr/local/share/fossology/lib/php/libschema.php(299): Fossology\Lib\Db\DbManager->queryOnce('ALTER TABLE "sy...') #2 /usr/local/share/fossology/lib/php/libschema.php(161): fo_libschema->applyTables() #3 /usr/local/lib/fossology/fossinit.php(191): fo_libschema->applySchema('/usr/local/shar...', false, 'fossology', Array) #4 {main} thrown in /usr/local/share/fossology/lib/php/Db/DbManager.php on line 144
|
|
|
|
Docker Container Restart Problems
flp@...
Hey,
I try to run fossology as docker compose cluster. Unfortunately, it always crashes when I need to restart the fossology container (3.7.0, 3.8.1 or 3.9.0-rc2). I end up with the following error in 3.8.1 und 3.9.0: *** Running postinstall for common actions***
*** Creating user and group ***
NOTE: group 'fossy' already exists, good.
NOTE: user 'fossy' already exists, good.
*** Making sure needed dirs exist with right ownership/permissions ***
*** clearing file cache ***
NOTE: Repository already exists at /srv/fossology/repository
NOTE: Running the PostgreSQL vacuum and analyze command can result in a large database performance improvement.
We suggest that you either configure postgres to run its autovacuum and autoanalyze daemons, or maintagent -D in a cron job, or run Admin > Maintenance on a regular basis.
Admin > Dashboard will show you the last time vacuum and analyze have been run.
NOTE: using external DB on host foss-db
*** update the database and license_ref table ***
PHP Warning: syntax error, unexpected ')' in /usr/local/etc/fossology/Db.conf on line 4
in /usr/local/share/fossology/lib/php/common-sysconfig.php on line 96
PHP Warning: Invalid argument supplied for foreach() in /usr/local/share/fossology/lib/php/common-sysconfig.php on line 101
PHP Notice: Undefined index: user in /usr/local/share/fossology/lib/php/libschema.php on line 520
Old release was 3.0.1
*** Cleaning tables for new constraints ***
Table author or agent does not exists, not cleaning!
Table author or pfile does not exists, not cleaning!
Table bucket_container or bucket_def does not exists, not cleaning!
Table bucket_file or bucket_def does not exists, not cleaning!
Table bucket_file or pfile does not exists, not cleaning!
Table copyright or agent does not exists, not cleaning!
Table copyright_decision or pfile does not exists, not cleaning!
Table ecc or agent does not exists, not cleaning!
Table ecc or pfile does not exists, not cleaning!
Table ecc_decision or pfile does not exists, not cleaning!
Table highlight_keyword or pfile does not exists, not cleaning!
Table keyword or agent does not exists, not cleaning!
Table keyword or pfile does not exists, not cleaning!
Table keyword_decision or pfile does not exists, not cleaning!
Table pkg_deb_req or pkg_deb does not exists, not cleaning!
Table pkg_rpm_req or pkg_rpm does not exists, not cleaning!
Table report_cache or upload does not exists, not cleaning!
Table report_info or upload does not exists, not cleaning!
Table reportgen or upload does not exists, not cleaning!
Table upload or pfile does not exists, not cleaning!
Table upload_clearing_license or upload does not exists, not cleaning!
Table obligation_ref does not exists, not cleaning!
Table report_info does not exists, not cleaning!
Table obligation_ref does not exists, not cleaning!
Table group_user_member does not exists, not cleaning!
Removed 0 rows from tables with new constraints
PHP Notice: Undefined index: user in /usr/local/share/fossology/lib/php/libschema.php on line 520
PHP Warning: pg_query(): Query failed: ERROR: column "rf_copyleft" of relation "license_ref" already exists in /usr/local/share/fossology/lib/php/Db/Driver/Postgres.php on line 79
[2020-10-18 21:38:19] /usr/local/share/fossology/lib/php/libschema.php.CRITICAL: ERROR: column "rf_copyleft" of relation "license_ref" already exists [] []
PHP Fatal error: Uncaught Fossology\Lib\Exception: error executing: ALTER TABLE "license_ref" ADD COLUMN "rf_copyleft" bit(1)
ERROR: column "rf_copyleft" of relation "license_ref" already exists in /usr/local/share/fossology/lib/php/Db/DbManager.php:144
Stack trace:
#0 /usr/local/share/fossology/lib/php/Db/DbManager.php(203): Fossology\Lib\Db\DbManager->checkResult(false, 'ALTER TABLE "li...')
#1 /usr/local/share/fossology/lib/php/libschema.php(299): Fossology\Lib\Db\DbManager->queryOnce('ALTER TABLE "li...')
#2 /usr/local/share/fossology/lib/php/libschema.php(161): fo_libschema->applyTables()
#3 /usr/local/lib/fossology/fossinit.php(196): fo_libschema->applySchema('/usr/local/shar...', false, 'fossology', Array)
#4 {main}
thrown in /usr/local/share/fossology/lib/php/Db/DbManager.php on line 144
With 3.7.0 I get the following: *** Running postinstall for common actions***
*** Creating user and group ***
NOTE: group 'fossy' already exists, good.
NOTE: user 'fossy' already exists, good.
*** Making sure needed dirs exist with right ownership/permissions ***
*** clearing file cache ***
NOTE: Repository already exists at /srv/fossology/repository
NOTE: Running the PostgreSQL vacuum and analyze command can result in a large database performance improvement.
We suggest that you either configure postgres to run its autovacuum and autoanalyze daemons, or maintagent -D in a cron job, or run Admin > Maintenance on a regular basis.
Admin > Dashboard will show you the last time vacuum and analyze have been run.
NOTE: using external DB on host foss-db
*** update the database and license_ref table ***
PHP Warning: syntax error, unexpected ')' in /usr/local/etc/fossology/Db.conf on line 4
in /usr/local/share/fossology/lib/php/common-sysconfig.php on line 96
PHP Warning: Invalid argument supplied for foreach() in /usr/local/share/fossology/lib/php/common-sysconfig.php on line 101
PHP Notice: Undefined index: user in /usr/local/share/fossology/lib/php/libschema.php on line 520
Old release was 0
*** Cleaning tables for new constraints ***
Table author or agent does not exists, not cleaning!
Table author or pfile does not exists, not cleaning!
Table bucket_container or bucket_def does not exists, not cleaning!
Table bucket_file or bucket_def does not exists, not cleaning!
Table bucket_file or pfile does not exists, not cleaning!
Table copyright or agent does not exists, not cleaning!
Table copyright_decision or pfile does not exists, not cleaning!
Table ecc or agent does not exists, not cleaning!
Table ecc or pfile does not exists, not cleaning!
Table ecc_decision or pfile does not exists, not cleaning!
Table highlight_keyword or pfile does not exists, not cleaning!
Table keyword or agent does not exists, not cleaning!
Table keyword or pfile does not exists, not cleaning!
Table keyword_decision or pfile does not exists, not cleaning!
Table pkg_deb_req or pkg_deb does not exists, not cleaning!
Table pkg_rpm_req or pkg_rpm does not exists, not cleaning!
Table report_cache or upload does not exists, not cleaning!
Table report_info or upload does not exists, not cleaning!
Table reportgen or upload does not exists, not cleaning!
Table upload or pfile does not exists, not cleaning!
Table upload_clearing_license or upload does not exists, not cleaning!
Table obligation_ref does not exists, not cleaning!
Table report_info does not exists, not cleaning!
Table obligation_ref does not exists, not cleaning!
Table group_user_member does not exists, not cleaning!
Removed 0 rows from tables with new constraints
PHP Notice: Undefined index: user in /usr/local/share/fossology/lib/php/libschema.php on line 520
PHP Warning: pg_query(): Query failed: ERROR: column "option_value" of relation "sysconfig" already exists in /usr/local/share/fossology/lib/php/Db/Driver/Postgres.php on line 79
[2020-10-22 21:49:47] /usr/local/share/fossology/lib/php/libschema.php.CRITICAL: ERROR: column "option_value" of relation "sysconfig" already exists [] []
PHP Fatal error: Uncaught Fossology\Lib\Exception: error executing: ALTER TABLE "sysconfig" ADD COLUMN "option_value" character varying(40) DEFAULT NULL
ERROR: column "option_value" of relation "sysconfig" already exists in /usr/local/share/fossology/lib/php/Db/DbManager.php:144
Stack trace:
#0 /usr/local/share/fossology/lib/php/Db/DbManager.php(203): Fossology\Lib\Db\DbManager->checkResult(false, 'ALTER TABLE "sy...')
#1 /usr/local/share/fossology/lib/php/libschema.php(299): Fossology\Lib\Db\DbManager->queryOnce('ALTER TABLE "sy...')
#2 /usr/local/share/fossology/lib/php/libschema.php(161): fo_libschema->applyTables()
#3 /usr/local/lib/fossology/fossinit.php(191): fo_libschema->applySchema('/usr/local/shar...', false, 'fossology', Array)
#4 {main} thrown in /usr/local/share/fossology/lib/php/Db/DbManager.php on line 144 I'm using fossology with the following compose cluster: version: '3.8' services: foss: image: fossology/fossology:3.9.0-rc2 restart: unless-stopped environment: FOSSOLOGY_DB_HOST: FOSSOLOGY_DB_NAME: FOSSOLOGY_DB_USER: FOSSOLOGY_DB_PASSWORD: volumes: - ./foss-repo:/srv/fossology/repository/ networks: - foss depends_on: - foss-db foss-db: image: postgres:11 restart: unless-stopped environment: POSTGRES_DB: POSTGRES_USER: POSTGRES_PASSWORD: POSTGRES_INITDB_ARGS: '-E SQL_ASCII' volumes: - ./postgres-data:/var/lib/postgresql/data networks: - foss networks: foss: external: name: foss I have no particular experience with Php but it looks like the startup script is always executed within the docker container so I might need to create my own one that does not execute the database script at startup?
|
|
|
|
End of Google Summer of Code - 2020
Shaheem Azmal M MD
Hello Everyone,
We would like to congratulate Darshan, Kaushlendra and Ayush for their contributions to FOSSology community. We are very impressed by the overall quality of their work and organizational skills, keep up the good work and stay in touch with community.
Details of features that were developed in this GSOC-2020.
Project : FOSSology Student Name : Darshan Kansagara Feature Title : Dashboard (Python, influxDB, Grafana) Wiki : https://github.com/darshank15/GSoC_2020_FOSSOlogy/wiki
Project : Atarashi Student Name : Ayush (HastagAB) Feature Title : Accelerating Atarashi Wiki : https://github.com/hastagAB/GSoC-2020
Project : Atarashi Student Name : Kaushlendra Pratap Singh Feature Title : Refurbishing Atarashi Wiki : https://github.com/Kaushl2208/GSoC-2020
We would also like to thank mentors(Michael, Shaheem, Anupam, Gaurav, Nicolas, Aman and Sandeep) for helping students achieve their targets.
Best Regards Shaheem Azmal M MD
|
|
|
|
Re: Not able to upload file >700MB file even after changing values in php.ini file
Michael C. Jaeger
hello,
toggle quoted messageShow quoted text
ja a quick question: if the uploa dis 1.7Gb and the max mem limit is 1.0 GB then this would be the problem. Pls. try setting the mem limit only few GBs above post max size. (something like 2.2 GB, 2.1 GB and and 2.0 GB. And you re right postgresql needs different setting for uploads of 1.7Gb size. I am not sure about work meme of 2GB 8could be also Ok with 256MB), maybe you re not going to use 6GB of maintenance mem. but a good approach is use a tool at first to get you reaosnable settings for the machine youre using: https://pgtune.leopard.in.ua/#/ was a good help for me in the past for tuning postgresql. Please note that you re using this link at your own risk. Kind regards, Michael
On 21. Jul 2020, at 01:12, Praba <dmuthumani@marvell.com> wrote:
|
|
|
|
Not able to upload file >700MB file even after changing values in php.ini file
Praba
Hello,
Just started to work on Fossology tool last few days. I am trying to upload linux5.4.30 component which is around 1.7G and not able to upload the file even after changing “post_max_size” & “upload_max_filesize”. I was able to upload and scan other components less than 700MB.
I have Fossology installed using docker on R640 Dell server. FOSSology version 3.8.0-86-gf0c84e229 (code revision f0c84e)
Below are the details. Please provide details if any modifications are needed.
root@abbf7f77a767:/fossology# cat /etc/php/7.0/apache2/php.ini|grep memory_limit memory_limit = 1002M
root@abbf7f77a767:/fossology# cat /etc/php/7.0/apache2/php.ini|grep post_max_size post_max_size = 4001M
root@abbf7f77a767:/fossology# cat /etc/php/7.0/apache2/php.ini|grep upload_max_filesize upload_max_filesize = 3000M
Also made some tunable and config changes to few files. /etc/sysctl.conf kernel.shmmax=67328311296 kernel.shmall=16437576
root@abbf7f77a767:/fossology# cat /etc/postgresql//9.6/main/postgresql.conf |grep max_connections max_connections = 100 # (change requires restart)
root@abbf7f77a767:/fossology# cat /etc/postgresql//9.6/main/postgresql.conf |grep shared_buffers #shared_buffers = 128MB # min 128kB shared_buffers = 32GB # min 128kB #wal_buffers = -1 # min 32kB, -1 sets based on shared_buffers
root@abbf7f77a767:/fossology# cat /etc/postgresql//9.6/main/postgresql.conf |grep effective_cache_size #effective_cache_size = 4GB effective_cache_size = 10GB
root@abbf7f77a767:/fossology# cat /etc/postgresql//9.6/main/postgresql.conf |grep work_mem #work_mem = 4MB # min 64kB work_mem = 2GB # min 64kB #maintenance_work_mem = 64MB # min 1MB maintenance_work_mem = 6GB # min 1MB #autovacuum_work_mem = -1 # min 1MB, or -1 to use maintenance_work_mem
root@abbf7f77a767:/fossology# cat /etc/postgresql//9.6/main/postgresql.conf |grep maintenance_work_mem #maintenance_work_mem = 64MB # min 1MB maintenance_work_mem = 6GB # min 1MB #autovacuum_work_mem = -1 # min 1MB, or -1 to use maintenance_work_mem
root@abbf7f77a767:/fossology# cat /etc/postgresql//9.6/main/postgresql.conf |grep fsync #fsync = on # flush data to disk for crash safety fsync = on # flush data to disk for crash safety #wal_sync_method = fsync # the default is the first option # fsync # fsync_writethrough #data_sync_retry = off # retry or panic on failure to fsync
root@abbf7f77a767:/fossology# cat /etc/postgresql//9.6/main/postgresql.conf |grep full_page_writes #full_page_writes = on # recover from partial page writes full_page_writes = off # recover from partial page writes
root@abbf7f77a767:/fossology# cat /etc/postgresql//9.6/main/postgresql.conf |grep autovacuum #autovacuum_work_mem = -1 # min 1MB, or -1 to use maintenance_work_mem #autovacuum = on # Enable autovacuum subprocess? 'on' autovacuum = on # Enable autovacuum subprocess? 'on' #log_autovacuum_min_duration = -1 # -1 disables, 0 logs all actions and ..
Thanks!
|
|
|
| 1 - 20 of 55 |