Hi Gurbax, Did you try to uninstall the previous (1.1.0) version of fossology? If so, it does not appear to have worked. Note the message in your log file in #2 below : Scheduler started. Build version: 1.1.0, exported.
Error #1 is most likely a symptom of an incomplete uninstall/install. Error #3 is a due to mis-configuration of Postgresql. Note the HINT about the SHMMAX kernel parameter. An incomplete uninstall of a package combined with a source install of 1.2.0 will leave pieces of both versions on your system! A very bad, mixed up configuration. Please verify apt-get remove successfully removes the 1.1.0 version before you try to install 1.2.1 from source. Mary > -----Original Message----- > From: Deol, Gurbax [mailto:gur...@ti.com] > Sent: Tuesday, October 19, 2010 4:12 PM > To: Donohoe, Mark; Laser, Mary > Cc: Causey, William; fossology@fossology.org > Subject: RE: [FOSSology] Installing fossology on a Ubuntu karmic koala > (9.10) machine > > Mark, Mary, > > We followed the instructions provided in your email, but are running > into the following issues: > > 1. This command does not run, error message is that this file is not > found: > sudo fo-postinstall > po.out 2>&1 > > 2. The following command errors out too: > sudo /usr/lib/fossology/fossology-scheduler -t -L stdout > 2010-10-19 17:10:09 scheduler[30586] : Scheduler started. Build > version: 1.1.0, exported. > > 2010-10-19 17:10:09 scheduler[30586] : *** Scheduler started, PID 30586 > *** > ERROR: Unable to connect to the database > Connection string: 'dbname=fossology host=localhost user=fossy > password=fossy' > Connection status: '1' > 2010-10-19 17:10:09 scheduler[30586] : FATAL: Unable to connect to > database. Exiting. > > 3. then I try to start the database and get another error message: > > sudo /etc/init.d/postgresql-8.3 start > * Starting PostgreSQL 8.3 database server > * The PostgreSQL server failed to start. Please check the log output: > 2010-10-19 16:17:53 CDT 4cbe0b01.7639LOG: could not load root > certificate file "root.crt": No such file or directory > 2010-10-19 16:17:53 CDT 4cbe0b01.7639DETAIL: Will not verify client > certificates. > 2010-10-19 16:17:53 CDT 4cbe0b01.7639FATAL: could not create shared > memory segment: Invalid argument > 2010-10-19 16:17:53 CDT 4cbe0b01.7639DETAIL: Failed system call was > shmget(key=5432001, size=268632064, 03600). > 2010-10-19 16:17:53 CDT 4cbe0b01.7639HINT: This error usually means > that PostgreSQL's request for a shared memory segment exceeded your > kernel's SHMMAX parameter. You can either reduce the request size or > reconfigure the kernel with larger SHMMAX. To reduce the request size > (currently 268632064 bytes), reduce PostgreSQL's shared_buffers > parameter (currently 32000) and/or its max_connections parameter > (currently 43). > If the request size is already small, it's possible that it is less > than your kernel's SHMMIN parameter, in which case raising the request > size or reconfiguring SHMMIN is called for. > The PostgreSQL documentation contains more information about shared > memory configuration. > > Thanks for all your support. > > -gurbax > _______________________________________________ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
