Re: [FOSSology] Unable to login after setup
Hi , Atlast I was able to login. the problem was the permissions in the system for each of the files was not correct. It was a blind action but it worked :-) Lin Laser, Mary wrote: Hello Lin, As Bob mentions below, our 1.1.0 release candidate has just been announced and, so far, it looks very good.If possible, I highly recommend using the latest release. It appears something went wrong during the installation. Did you see any errors during build or install? If you're not sure, it doesn't hurt to re-run it. Did you complete the configuration steps described in the INSTALL doc for PostgreSQL andApache2? If you follow the instructions in the INSTALL doc, you should not need to create the link to get the fossology UI working. Howwere you able toupdate the fossy username? Please check the postgres, fossology and Apache log files for errors/clues indicating why you can't login. Reply to this email with the relevant info. Thanks, Mary From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of Gobeille, Robert Sent: Friday, July 10, 2009 9:38 AM To: Lin Ramachandran Cc: fossology@fossology.org Subject: Re: [FOSSology] Unable to login after setup On Jul 10, 2009, at 5:21 AM, Lin Ramachandran wrote: Hi, I am a bit new to the open source code and all. I have setup Fossology in an Fedora Core 9 machine and it took a whopping nine hours to set it up - had to resolve many decencies and very much to the blogs available I was able to make it run. But now I face a problem that I am not able to login to Fossology using the default username and password : fossy, fossy. I had to create a link to the fossology to get the Web UI of Fossology running, i.e. I created a soft link to the folder /usr/local/share/fossology/www inside /var/www/html ( /var/www/html/fossology - /usr/local/share/fossology/www ) and then I was able to get the UI in the browser. But the problem is that I am not able to login to fossology with the username fossy. I have updated the password of user fossy, but I am still not able to login. When I try to login, it comes back to the same page with the "Home" and the "Help" menu being activated only while all the other menu options are disabled. Hi Lin, It sounds like you have had a terrible experience. Hopefully, with all our install packages in release 1.1, no one else will have to go through this. The 1.1 testing is going very well. I expect an official release around the end of next week. Did you go through the post-install instructions (section 2.2.3 in the INSTALL document)? Places to look to see what is going wrong arethelogfiles(/var/log). Take a look at the postgres, fossology, and apache log files. I'm sure someone on the list with more experience than I with brand new installs will help you. Bob Gobeille b...@fossology.org ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Unable to login after setup
Hi Lin, Glad to hear you got it working finally. See attached email for RPM packages. Mary From: Lin Ramachandran [mailto:lramachand...@tataelxsi.co.in] Sent: Tuesday, July 14, 2009 5:15 AM To: Laser, Mary Cc: Gobeille, Robert; fossology@fossology.org Subject: Re: [FOSSology] Unable to login after setup Hi , Atlast I was able to login. the problem was the permissions in the system for each of the files was not correct. It was a blind action but it worked :-) Lin ---BeginMessage--- Hi all, I have uploaded the CentOS/RHEL RPM packages on Sourceforge and fossology.org. On sourceforge you can download from: https://sourceforge.net/projects/fossology/files/fossology/fossology-1.1.0rc5-0.centos4.i386.rpm/download (centos4/rhel4 i386) https://sourceforge.net/projects/fossology/files/fossology/fossology-1.1.0rc5-0.centos4.x86_64.rpm/download (centos4/rhel4 x86_64) https://sourceforge.net/projects/fossology/files/fossology/fossology-1.1.0rc5-0.centos5.i386.rpm/download (centos5/rhel5 i386) https://sourceforge.net/projects/fossology/files/fossology/fossology-1.1.0rc5-0.centos5.x86_64.rpm/download (centos5/rhel5 x86_64) On fossology.org you can download rpms, srcrpms and develrpms from: http://fossology.org/rpms/1.1.0~rc5/centos/4/ (centos4/rhel4 i386 x86_64) http://fossology.org/rpms/1.1.0~rc5/centos/5/ (centos5/rhel5 i386 x86_64) From Yum install with yum repo at http://fossology.org/rpms/1.1.0~rc5/centos/4/fossology.repo (centos4 i386 x86_64) and http://fossology.org/rpms/1.1.0~rc5/centos/5/fossology.repo (centos5 i386 x86_64) If you install on x86_64 do yum install fossology.x86_64 in order to avoid mixed deps. Any questions feel free let me know. Thanks. Best Regards, Vincent Ma(Ma Dong) Hewlett-Packard Co. IDD: +86 010 6564 5733 Email: dong...@hp.commailto:dong...@hp.com ---End Message--- ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
[FOSSology] FW: 1.1.0RC5 RPM packages available on Sourceforge and fossology.org
Forwarding from Vincent. Mary From: Ma, Dong (vinc...@gdcc-bj-most) Sent: Tuesday, July 14, 2009 5:01 AM Subject: 1.1.0RC5 RPM packages available on Sourceforge and fossology.org Hi all, I have uploaded the CentOS/RHEL RPM packages on Sourceforge and fossology.org. On sourceforge you can download from: https://sourceforge.net/projects/fossology/files/fossology/fossology-1.1.0rc5-0.centos4.i386.rpm/download (centos4/rhel4 i386) https://sourceforge.net/projects/fossology/files/fossology/fossology-1.1.0rc5-0.centos4.x86_64.rpm/download (centos4/rhel4 x86_64) https://sourceforge.net/projects/fossology/files/fossology/fossology-1.1.0rc5-0.centos5.i386.rpm/download (centos5/rhel5 i386) https://sourceforge.net/projects/fossology/files/fossology/fossology-1.1.0rc5-0.centos5.x86_64.rpm/download (centos5/rhel5 x86_64) On fossology.org you can download rpms, srcrpms and develrpms from: http://fossology.org/rpms/1.1.0~rc5/centos/4/ (centos4/rhel4 i386 x86_64) http://fossology.org/rpms/1.1.0~rc5/centos/5/ (centos5/rhel5 i386 x86_64) From Yum install with yum repo at http://fossology.org/rpms/1.1.0~rc5/centos/4/fossology.repo (centos4 i386 x86_64) and http://fossology.org/rpms/1.1.0~rc5/centos/5/fossology.repo (centos5 i386 x86_64) If you install on x86_64 do yum install fossology.x86_64 in order to avoid mixed deps. Any questions feel free let me know. Thanks. Best Regards, Vincent Ma(Ma Dong) ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Delete files
Hello Heinz, The agent responsible for deleing uploads is delagent. You can access it from the UI via Organize - Uploads - Delete Uploaded File. The agent can also be invoked from the command line: la...@mysystem:~/fossology-1.1.0/agents/delagent$mailto:la...@mysystem:~/fossology-1.1.0/agents/delagent$ /usr/local/lib/fossology/agents/delagent -? /usr/local/lib/fossology/agents/delagent: invalid option -- ? Usage: /usr/local/lib/fossology/agents/delagent [options] List or delete uploads. Options -i :: Initialize the DB, then exit. -u :: List uploads IDs. -U # :: Delete upload ID. -l :: List uploads IDs. (same as -u, but goes with -L) -L # :: Delete ALL licenses associated with upload ID. -f :: List folder IDs. -F # :: Delete folder ID and all uploads under this folder. Folder '1' is the default folder. '-F 1' will delete every upload and folder in the navigation tree. -s :: Run from the scheduler. -T :: TEST -- do not update the DB or delete any files (just pretend) -v :: Verbose (-vv for more verbose) As you can see from the usage menu above, you'll need to pass it the upload id. If you know the upload ids for each of the uploads you wish to delete, this would be the way to do it. Bob or Mark may have an easier solution. anyone? Mary From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of heinz.h.hi...@daimler.com Sent: Tuesday, July 14, 2009 6:48 AM To: fossology@fossology.org Subject: [FOSSology] Delete files Hello, We have a lot of single files uploaded into fossology. We have currently about 200 single files on the system and there are in different folders. And now we don't need them any longer and would like to delete them. Do you have any idea how we can delete all of them immediatley? Regards, Heinz If you are not the intended addressee, please inform us immediately that you have received this e-mail in error, and delete it. We thank you for your cooperation. ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Delete files
On the top menu click on Organize Uploads Delete to delete single uploads. Use Organize Folders Delete folder to delete a folder and all the uploads in that folder. There isn't an option to select a list of folders to delete or to delete ALL uploads. Bob Gobeille Sent from my iPhone On Jul 14, 2009, at 6:47 AM, heinz.h.hi...@daimler.com heinz.h.hi...@daimler.com wrote: Hello, We have a lot of single files uploaded into fossology. We have currently about 200 single files on the system and there are in different folders. And now we don't need them any longer and would like to delete them. Do you have any idea how we can delete all of them immediatley? Regards, Heinz If you are not the intended addressee, please inform us immediately that you have received this e-mail in error, and delete it. We thank you for your cooperation. ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Stuck on Licensing
On Jul 14, 2009, at 10:06 AM, Landon Jurgens wrote: Here's what I got from the command date; ps -ef | grep sched Tue Jul 14 04:02:29 EDT 2009 landon 11652 11626 0 04:02 pts/000:00:00 grep sched fossy13841 1 5 Jun30 ? 18:56:34 /usr/lib/fossology/fossology-scheduler -d I think 18:56:34 NOT EQUAL 04:04:29 so the thing is hung. When I restarted it I got all this garbled junk WARNING: nonstandard use of escape in a string literal LINE 2: ', record_update=now(), agent_param='akey=\244063\ a= \480... ^ HINT: Use the escape string syntax for escapes, e.g., E'\r\n'. WARNING: nonstandard use of escape in a string literal LINE 2: ', record_update=now(), agent_param='akey=\244069\ a= \087... ^ HINT: Use the escape string syntax for escapes, e.g., E'\r\n'. WARNING: nonstandard use of escape in a string literal LINE 2: ', record_update=now(), agent_param='akey=\244071\ a= \2A3... ^ HINT: Use the escape string syntax for escapes, e.g., E'\r\n'. These warnings are ok. We have most of them cleaned up in 1.1. They will slow things down because of all the logging, but won't hurt the data. You could change you postgres logging level, in postgresql.conf, to ignore them, if you wish. I didn't know if this made any sense. I'm looking to install 1.1.0 but there isn't an Ubuntu Package for it yet but I think I might try to make one. I think the debian package will probably work. See http://fossology.org/download There are three fossology developers who have been making packages (Bruno, Vincent, and Matt). I'm pretty sure Bruno and Vincent will be making Ubuntu packages, but they may not get to it for another week or so. Bob Gobeille ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Delete files
Mary mentioned delagent. You can try delagent -F 1 if you want to delete ALL uploads. Bob On Jul 14, 2009, at 7:18 AM, Gobeille, Robert wrote: On the top menu click on Organize Uploads Delete to delete single uploads. Use Organize Folders Delete folder to delete a folder and all the uploads in that folder. There isn't an option to select a list of folders to delete or to delete ALL uploads. Bob Gobeille Sent from my iPhone On Jul 14, 2009, at 6:47 AM, heinz.h.hi...@daimler.com heinz.h.hi...@daimler.com wrote: Hello, We have a lot of single files uploaded into fossology. We have currently about 200 single files on the system and there are in different folders. And now we don't need them any longer and would like to delete them. Do you have any idea how we can delete all of them immediatley? Regards, Heinz If you are not the intended addressee, please inform us immediately that you have received this e-mail in error, and delete it. We thank you for your cooperation. ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Unable to login after setup
FYI, we have a script called check.sh that goes through many checks, including permissions, to verify a correct install. No we don't any more. It went away with the buildinstall system rewrite and was replaced by checks in fo-postinstall and the selftest agent. -- Matt Taggart tagg...@fossology.org ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Stuck on Licensing
If there is anything I can do to help with the Ubuntu Packages could someone let me know. I would be interested in keeping the Ubuntu up to date. I think we need a member of Ubuntu's MOTU team to upload the packages to Universe, and people to test and make sure the packages build and work on the Ubuntu releases they care about. If any changes are needed I am happy to make them in the Debian source package so Ubuntu doesn't need an extra diff. -- Matt Taggart tagg...@debian.org ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Scheduler Status page
-Original Message- From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of Gobeille, Robert Sent: Tuesday, July 14, 2009 12:24 PM To: Donohoe, Mark Cc: fossology@fossology.org Subject: Re: [FOSSology] Scheduler Status page So you are proposing that we add notes about all outstanding bugs targeted for 1.1 to the release notes? Sounds reasonable to me. There aren't very many. I think it would be good to get these down to a one liner + url to the bug. Bob On Jul 14, 2009, at 12:16 PM, Donohoe, Mark wrote: Bob, so what should we put in the release notes? It seems like we are going to ship with it in the current state, so it would be good to document in the release notes what the issues are (I'm not sure what they are) Mary? Thoughts on this. Mark Bob, Yes, there are a handful of open bugs that will not get fixed for 1.1. (At least 3 I know of, are license identification issues that should be addressed in 1.2.) As Bob suggests, we should add these to the Known Issues section of the release notes http://fossology.org/release_notes#known_issues. Mary ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Scheduler Status page
On Jul 14, 2009, at 12:46 PM, Laser, Mary wrote: Yes, there are a handful of open bugs that will not get fixed for 1.1. (At least 3 I know of, are license identification issues that should be addressed in 1.2.) As Bob suggests, we should add these to the Known Issues section of the release notes http://fossology.org/release_notes#known_issues . Is someone volunteering to do this? Bob ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Scheduler Status page
-Original Message- On Jul 14, 2009, at 12:46 PM, Laser, Mary wrote: Yes, there are a handful of open bugs that will not get fixed for 1.1. (At least 3 I know of, are license identification issues that should be addressed in 1.2.) As Bob suggests, we should add these to the Known Issues section of the release notes http://fossology.org/release_notes#known_issues . Is someone volunteering to do this? I suggest each bug owner document their bugs in the known issues section. Mary ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
[FOSSology] Fossology 1.1.0 RC5 installation problem: Failed to load default extractor libraries
I am installing Fossology 1.1.0 RC5 on Linux RH 5.1 (see results of 'uname -a' below) Linux rhle51x86 2.6.18-53.el5 #1 SMP Wed Oct 10 16:34:02 EDT 2007 i686 i686 i386 GNU/Linux I used yum to install Fossology. Everything went smoothly. Except that the following error: FATAL: Failed to load default extractor libraries. FATAL: '/usr/lib/fossology/agents/pkgmetagetta -i' failed to initialize I do have libextractor installed from a RPM. [r...@rhle51x86 lib]# ls -l /usr/lib/libextractor* lrwxrwxrwx 1 root root21 Jul 14 16:55 /usr/lib/libextractor - libextractor.so.1.1.1 lrwxrwxrwx 1 root root28 Jul 14 16:40 /usr/lib/libextractor_common.so.0 - libextractor_common.so.0.0.0 -rwxr-xr-x 1 root root 46272 May 29 20:47 /usr/lib/libextractor_common.so.0.0.0 lrwxrwxrwx 1 root root21 Jul 14 16:40 /usr/lib/libextractor.so.1 - libextractor.so.1.1.1 -rwxr-xr-x 1 root root 45276 May 29 20:47 /usr/lib/libextractor.so.1.1.1 Please help. Thank you -- Simon ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
[FOSSology] Fwd: Scheduler hangs
FYI, this is a conversation Neal and I were having that should have gone to the list instead of only me. Forwarded here in case anyone wants to join in. Bob Gobeille Begin forwarded message: From: Bob Gobeille bob.gobei...@hp.com Date: July 14, 2009 1:12:42 PM MDT To: Dr. Neal Krawetz ne...@fossology.org Subject: Re: Scheduler hangs On Jul 14, 2009, at 1:13 PM, Dr. Neal Krawetz wrote: Hi Bob, I just had a thought about detecting and debugging scheduler hangs, as well as a possible workaround. The last I knew... the bug was a signal handling conflict between the DB library and the scheduler. Right now, the scheduler intercepts signals. When sigaction() is called in scheduler.c, there is an optional parameter for storing the old signal handler. I currently ignore the old handler value since I am hijacking the signal handler and have no intention of putting it back. In some new code I added (when testing agents), I save the old sig, set SIG_IGN, and then restore it after giving the agents enough time to die and send their SIG_CHLD. Without this we were reporting unexpected child deaths, when in fact, we wanted to ignore those deaths. However... Try this: - Save the old signal handler. In the scheduler's signal handler, call the original handler before exiting. (if old is not null then call old with same parameters that my signal handler received) - I also set a few signals to SIG_IGN. Instead of ignoring them, create a new signal handler that receives them, does nothing, and calls the old handler. - Occasionally (in the main loop, after the sleep) check to see if the handler is still set the way I set it. If it isn't, then it means that Postgres hijacked my handler. I suspect that Postgres is hijacking interrupts. Between my hijacking and their hijacking, things are getting messed up. If this turns out to be the case, then there is a solution: - Before hijacking any handlers: call the DB and give it a few simple exercises. This will force the SQL library to hijack any interrupts it wants. - Then configure the scheduler's interrupts, holding onto the old handlers. - Have the scheduler pass though all signals to the old handler. Good ideas. I wrote the scheduler watchdog as a hack because the hangs/dies are rare and I thought that diagnosing the problem would be a bitch. Actually, diagnosing the problem would be a good thing to do. ;-) Bob ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Fossology 1.1.0 RC5 installation problem: Failed to load default extractor libraries
On Jul 14, 2009, at 3:01 PM, 西门烧雪 Simon wrote: I am installing Fossology 1.1.0 RC5 on Linux RH 5.1 (see results of 'uname -a' below) Linux rhle51x86 2.6.18-53.el5 #1 SMP Wed Oct 10 16:34:02 EDT 2007 i686 i686 i386 GNU/Linux I used yum to install Fossology. Everything went smoothly. Except that the following error: FATAL: Failed to load default extractor libraries. FATAL: '/usr/lib/fossology/agents/pkgmetagetta -i' failed to initialize I do have libextractor installed from a RPM. [r...@rhle51x86 lib]# ls -l /usr/lib/libextractor* lrwxrwxrwx 1 root root21 Jul 14 16:55 /usr/lib/libextractor - libextractor.so.1.1.1 lrwxrwxrwx 1 root root28 Jul 14 16:40 /usr/lib/libextractor_common.so.0 - libextractor_common.so.0.0.0 -rwxr-xr-x 1 root root 46272 May 29 20:47 /usr/lib/libextractor_common.so.0.0.0 lrwxrwxrwx 1 root root21 Jul 14 16:40 /usr/lib/libextractor.so.1 - libextractor.so.1.1.1 -rwxr-xr-x 1 root root 45276 May 29 20:47 /usr/lib/ libextractor.so.1.1.1 you also need libextractor-devel libextractor is only used by the pkgmeta agent. So if you are only doing license analysis, you could simply skip (probably should skip) running the pkgmettagetta agent. You could also skip the specfile agent. Bob Gobeille ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
