Hi Bruno, WRT the error below: As far as I can tell, this happens when a program tries to call shm_open with no /dev/shm mounted.
Can you check your chroot environment to make sure that it's set up so that it has a /dev/shm? Otherwise I don't think any shared memory open or attach calls will work and this is necessary for postgresql. The FO install directions also suggest increasing the /proc/sys/kernel/shmmax value to 512000000. Let me know if this gets you back on the right track. Sorry it's taken so long to respond. -- Chan Bruno Cornec said on Mon, Feb 16, 2009 at 11:50:21PM +0100: > Then I have issues with the postgresql conf, which is normal as I didn't > finished that part. Will work on that just now. I'm working in an empty chroot to test the fossology install, so I have no previous postgresql install setup. Here is the result of my latest install: *** Checking database connectivity *** ERROR: Unable to connect to the database Connection string: 'dbname=fossology host=localhost user=fossy password=fossy' Connection status: '1' ERROR: Failed to open database ERROR: unable to connect to database, please check /etc/fossology/Db.conf FATAL: shm_open: Function not implemented FATAL: shm_open failed with errno=38 Which seems to come from hte dbcheck command. Anybody can help me create at least a correct basic environment from scratch that could be working ? (Sorry I know a bit more MySQL rather than PostgreSQL for that). Bruno. _______________________________________________ fossology mailing list [email protected] http://fossology.org/mailman/listinfo/fossology

