Hello, maybe soon ready by Anupam:
https://github.com/fossology/fossology/pull/1122 Or, you could try the last release, 3.3.0 where we did not see the errors. Kind regards, Michael > On 19.06.2018, at 17:02, Stephanie Mehltretter <[email protected]> > wrote: > > Hey, > thanks for the answer. Restarting the scheduler as you mentioned help me for > the first time. Unfortunately I have to do a more complex license scan until > next Thuesday and have to review toe licenses my self and generate a reviewed > report out of them. At the moment this is not possible because of the bugs in > the scheduler. Would it be possible to produce a bug fix soon? > > Thank you so much! > Yours sincerely, > Stephanie > > Am 18.06.18 um 14:03 schrieb Michael C. Jaeger: >> Hello, >> >> looks like we have an unfortunate time with the scheduler the past days. >> >> Regarding the apache message: I am not sure if this indicates a serious >> problem. As far as I know the server name should be set by admin of the >> machine (in this case your vagrant machine) and if it is not set, then this >> message arrives. >> >> FOSSology is a server application therefore some admin tasks may be >> necessary to fully set this up. >> >> It seems like the scheduler crashes and then is not starting again. However >> the start can be triggered at restart of the machine, so that it is why it >> returns when you issue vagrant to reprovision >> >> You could do >> · “vagrant ssh” (being in the directory from where you executed the >> other vagrant commands) to log into the machine directly >> · once logged in, either try to “sudo service fossology >> graceful-stop” and “sudo service fossology stop” (or “sudo service fossology >> restart”) >> · see htop or top what it is doing >> >> Any other than that, the scheduler might require an investigation why it is >> stopping, maybe it is a general error. >> >> Kind regards, Michael >> >> >> >> From: [email protected] [mailto:[email protected]] On Behalf >> Of Stephanie Mehltretter >> Sent: Montag, 18. Juni 2018 12:07 >> To: [email protected] >> Subject: [FOSSology] Flossology bugs: upload and unified report tasks are >> not executed in vagrant vm >> >> Hello, >> I am new to Flossology and have installed the software using vagrant and >> Virtualbox. The installation worked fine and I can use a Fossology instance >> onhttp://localhost:8081/repo/. In the terminal I got the warning that " >> default: AH00558: apache2: Could not reliably determine the server's fully >> qualified domain name, using 10.0.2.15. Set the 'ServerName' directive >> globally to suppress this message". >> >> BUG 1: >> >> The problem is that the unified report only can be downloaded after >> executing a vagrant reload in the Terminal! >> >> My steps are the following: >> >> 1) upload via version control system the project >> "https://github.com/laravel/framework" (works - see attachement) >> >> 2) under the tab "browse" click on the project and select "export unified >> report" >> >> --> in the job list 29 new jobs show up doing a unified report. ALL of those >> jobs stay yellow until you type "vagrant reload" in the terminal. >> >> Then you can go to the job list and see blue yellow and gree jobs and you >> can download the generated report! >> >> By the way, pausing or canceling a job results in the error added in the >> attachement. >> >> >> >> BUG 2: >> >> - if you follow the steps mentioned before and then upload a new project to >> be analysed, the upload jobs will stay yellow even if you do vagrant reload. >> I have been waiting for the upload for over 2 hours even if the project is >> not very big (react js of facebook). >> >> How to handle this bug? >> >> >> >> I hope all the screenshow are helpful. >> >> Could you please help me, how to avoid the problem or fix it in the vagrant >> container? >> >> Thank you so much! >> >> Sincerely, >> >> Stephanie Mehltretter >> >> >> > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#14): https://lists.fossology.org/g/main/message/14 Mute This Topic: https://lists.fossology.org/mt/22401775/21656 Group Owner: [email protected] Unsubscribe: https://lists.fossology.org/g/main/leave/2477038/1225511528/xyzzy [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
