Re: [Dspace-tech] Failing compilation on debian lenny, PostgreSQL 8.3.12, libpg-java 8.2-504-2, java version 1.6.0_20, tomcat 5.5
shame one me :/ the schema was wrong... thanks again Tim, regards, K On 14 January 2011 16:27, Tim Donohue tdono...@duraspace.org wrote: Kocisky, DSpace should be finding those columns from the Database table itself. I noticed from your other email that you had this setting in dspace.cfg: db.schema = dspace So, I'm assuming you are working in a PostgreSQL database that is using multiple schemas. Is the table being created under the proper schema? So, rather than it being created under the public schema (which I think is the default), it should be appearing under the dspace schema for you. Also, did you create this dspace schema in your database? If not, then your 'db.schema' setting may be causing these problems. By default, the dspace.cfg has the 'db.schema' setting commented out (which tells DSpace you want to use the default schema in Postgres). If you uncomment this setting, and give it a value, then you must first *create* that Schema in your database (as DSpace doesn't have permissions to create the schema for you, just as it doesn't create the database for you). Hopefully this helps, - Tim On 1/13/2011 10:38 AM, Kocisky wrote: Tim, you are right, i miss that, thanks! below further details: On 11 January 2011 18:17, Tim Donohuetdono...@duraspace.org wrote: Kocisky, Actually those logs are helpful. It shows me that for some reason your install process is not able to load data into your 'bitstreamformatregistry' table. Can you check to make sure this table is created properly in your DB? It should be created with the following columns: bitstream_format_id integer NOT NULL, mimetype character varying(256), short_description character varying(128), description text, support_level integer, internal boolean yes the table is in the db as you reported You also may want to look at your PostgreSQL log files, to see if it has reported any errors. the postgresql-8.3-main.log report these errors: 2011-01-13 11:08:04 EST NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index bi_item_pkey for table bi_item 2011-01-13 11:08:04 EST NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index bi_withdrawn_pkey for table bi_withdrawn 2011-01-13 11:08:04 EST NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index bi_2_dis_pkey for table bi_2_dis 2011-01-13 11:08:04 EST NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index bi_2_dmap_pkey for table bi_2_dmap 2011-01-13 11:08:04 EST NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index bi_4_dis_pkey for table bi_4_dis 2011-01-13 11:08:04 EST NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index bi_4_dmap_pkey for table bi_4_dmap 2011-01-13 11:08:04 EST LOG: unexpected EOF on client connection 2011-01-13 11:08:04 EST LOG: unexpected EOF on client connection 2011-01-13 11:08:05 EST ERROR: relation bi_1 does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_1 LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_1_dis does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_1_dis LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_2 does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_2 LIMIT 1 2011-01-13 11:08:05 EST NOTICE: drop cascades to constraint bi_2_dmap_distinct_id_fkey on table bi_2_dmap 2011-01-13 11:08:05 EST ERROR: relation bi_3 does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_3 LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_3_dis does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_3_dis LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_4 does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_4 LIMIT 1 2011-01-13 11:08:05 EST NOTICE: drop cascades to constraint bi_4_dmap_distinct_id_fkey on table bi_4_dmap 2011-01-13 11:08:05 EST ERROR: relation bi_5 does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_5 LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_5_dis does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_5_dis LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_6 does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_6 LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_6_dis does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_6_dis LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_7 does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_7 LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_7_dis does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_7_dis LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_8 does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_8 LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_8_dis does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_8_dis LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_9 does not exist 2011-01-13 11:08:05 EST STATEMENT:
Re: [Dspace-tech] Failing compilation on debian lenny, PostgreSQL 8.3.12, libpg-java 8.2-504-2, java version 1.6.0_20, tomcat 5.5
Kocisky, DSpace should be finding those columns from the Database table itself. I noticed from your other email that you had this setting in dspace.cfg: db.schema = dspace So, I'm assuming you are working in a PostgreSQL database that is using multiple schemas. Is the table being created under the proper schema? So, rather than it being created under the public schema (which I think is the default), it should be appearing under the dspace schema for you. Also, did you create this dspace schema in your database? If not, then your 'db.schema' setting may be causing these problems. By default, the dspace.cfg has the 'db.schema' setting commented out (which tells DSpace you want to use the default schema in Postgres). If you uncomment this setting, and give it a value, then you must first *create* that Schema in your database (as DSpace doesn't have permissions to create the schema for you, just as it doesn't create the database for you). Hopefully this helps, - Tim On 1/13/2011 10:38 AM, Kocisky wrote: Tim, you are right, i miss that, thanks! below further details: On 11 January 2011 18:17, Tim Donohuetdono...@duraspace.org wrote: Kocisky, Actually those logs are helpful. It shows me that for some reason your install process is not able to load data into your 'bitstreamformatregistry' table. Can you check to make sure this table is created properly in your DB? It should be created with the following columns: bitstream_format_id integer NOT NULL, mimetype character varying(256), short_description character varying(128), description text, support_level integer, internal boolean yes the table is in the db as you reported You also may want to look at your PostgreSQL log files, to see if it has reported any errors. the postgresql-8.3-main.log report these errors: 2011-01-13 11:08:04 EST NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index bi_item_pkey for table bi_item 2011-01-13 11:08:04 EST NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index bi_withdrawn_pkey for table bi_withdrawn 2011-01-13 11:08:04 EST NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index bi_2_dis_pkey for table bi_2_dis 2011-01-13 11:08:04 EST NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index bi_2_dmap_pkey for table bi_2_dmap 2011-01-13 11:08:04 EST NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index bi_4_dis_pkey for table bi_4_dis 2011-01-13 11:08:04 EST NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index bi_4_dmap_pkey for table bi_4_dmap 2011-01-13 11:08:04 EST LOG: unexpected EOF on client connection 2011-01-13 11:08:04 EST LOG: unexpected EOF on client connection 2011-01-13 11:08:05 EST ERROR: relation bi_1 does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_1 LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_1_dis does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_1_dis LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_2 does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_2 LIMIT 1 2011-01-13 11:08:05 EST NOTICE: drop cascades to constraint bi_2_dmap_distinct_id_fkey on table bi_2_dmap 2011-01-13 11:08:05 EST ERROR: relation bi_3 does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_3 LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_3_dis does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_3_dis LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_4 does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_4 LIMIT 1 2011-01-13 11:08:05 EST NOTICE: drop cascades to constraint bi_4_dmap_distinct_id_fkey on table bi_4_dmap 2011-01-13 11:08:05 EST ERROR: relation bi_5 does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_5 LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_5_dis does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_5_dis LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_6 does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_6 LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_6_dis does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_6_dis LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_7 does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_7 LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_7_dis does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_7_dis LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_8 does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_8 LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_8_dis does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_8_dis LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_9 does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_9 LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_9_dis does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_9_dis
Re: [Dspace-tech] Failing compilation on debian lenny, PostgreSQL 8.3.12, libpg-java 8.2-504-2, java version 1.6.0_20, tomcat 5.5
Tim, you are right, i miss that, thanks! below further details: On 11 January 2011 18:17, Tim Donohue tdono...@duraspace.org wrote: Kocisky, Actually those logs are helpful. It shows me that for some reason your install process is not able to load data into your 'bitstreamformatregistry' table. Can you check to make sure this table is created properly in your DB? It should be created with the following columns: bitstream_format_id integer NOT NULL, mimetype character varying(256), short_description character varying(128), description text, support_level integer, internal boolean yes the table is in the db as you reported You also may want to look at your PostgreSQL log files, to see if it has reported any errors. the postgresql-8.3-main.log report these errors: 2011-01-13 11:08:04 EST NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index bi_item_pkey for table bi_item 2011-01-13 11:08:04 EST NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index bi_withdrawn_pkey for table bi_withdrawn 2011-01-13 11:08:04 EST NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index bi_2_dis_pkey for table bi_2_dis 2011-01-13 11:08:04 EST NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index bi_2_dmap_pkey for table bi_2_dmap 2011-01-13 11:08:04 EST NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index bi_4_dis_pkey for table bi_4_dis 2011-01-13 11:08:04 EST NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index bi_4_dmap_pkey for table bi_4_dmap 2011-01-13 11:08:04 EST LOG: unexpected EOF on client connection 2011-01-13 11:08:04 EST LOG: unexpected EOF on client connection 2011-01-13 11:08:05 EST ERROR: relation bi_1 does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_1 LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_1_dis does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_1_dis LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_2 does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_2 LIMIT 1 2011-01-13 11:08:05 EST NOTICE: drop cascades to constraint bi_2_dmap_distinct_id_fkey on table bi_2_dmap 2011-01-13 11:08:05 EST ERROR: relation bi_3 does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_3 LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_3_dis does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_3_dis LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_4 does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_4 LIMIT 1 2011-01-13 11:08:05 EST NOTICE: drop cascades to constraint bi_4_dmap_distinct_id_fkey on table bi_4_dmap 2011-01-13 11:08:05 EST ERROR: relation bi_5 does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_5 LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_5_dis does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_5_dis LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_6 does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_6 LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_6_dis does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_6_dis LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_7 does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_7 LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_7_dis does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_7_dis LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_8 does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_8 LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_8_dis does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_8_dis LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_9 does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_9 LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_9_dis does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_9_dis LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_10 does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_10 LIMIT 1 2011-01-13 11:08:05 EST ERROR: relation bi_10_dis does not exist 2011-01-13 11:08:05 EST STATEMENT: SELECT * FROM bi_10_dis LIMIT 1 2011-01-13 11:08:05 EST NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index bi_item_pkey for table bi_item 2011-01-13 11:08:05 EST NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index bi_withdrawn_pkey for table bi_withdrawn 2011-01-13 11:08:05 EST NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index bi_2_dis_pkey for table bi_2_dis 2011-01-13 11:08:05 EST NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index bi_2_dmap_pkey for table bi_2_dmap 2011-01-13 11:08:05 EST NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index bi_4_dis_pkey for table bi_4_dis 2011-01-13 11:08:05 EST NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index bi_4_dmap_pkey for table bi_4_dmap 2011-01-13 11:08:05 EST LOG: unexpected EOF on client connection 2011-01-13 11:08:05 EST LOG:
Re: [Dspace-tech] Failing compilation on debian lenny, PostgreSQL 8.3.12, libpg-java 8.2-504-2, java version 1.6.0_20, tomcat 5.5
Hi Tim, thank you for your reply, i've followed your suggestions but didn't got many results, see below: DSpace 1.7 actually comes packaged with the PostgreSQL JDBC driver it needs to use. You do not need to install a separate JDBC driver (in fact, you may want to remove what you installed, to make sure it doesn't cause any conflicts). great, i've removed that package The full installation prerequisites instructions are at: https://wiki.duraspace.org/display/DSDOC/Installation i was following the doc in the pkg, thanks also for this ! Also be aware that you will need Maven 2.2.x or above to properly build DSpace 1.7.0. We've discovered an error in builds with Maven 2.0.x -- see the above link for more details (look under the prerequisites software section) i'm now using apache-maven 3.0.1 but have the same syntax problem, see below Your version of Maven actually may be part of the problem. After the Maven build, it seems you don't receive a full summary of all modules being built properly. Double check that you are running 'mvn package' from the [dspace-src]/dspace/ directory. The results of a successful build should report similar to this (notice how many more modules were built -- you only had 8 listed in your logs below): maybe i have less packages because i'm not compiling the source but the slim package with pre-compiled modules? here the last build with maven version: [INFO] Copying 1394 files to /home/user/Desktop/dspace-1.7.0-release/dspace/target/dspace-1.7.0-build.dir [INFO] [INFO] Reactor Summary: [INFO] [INFO] DSpace Addon Modules .. SUCCESS [0.385s] [INFO] DSpace XML-UI (Manakin) :: Web Application SUCCESS [7.276s] [INFO] DSpace LNI :: Web Application . SUCCESS [4.203s] [INFO] DSpace OAI :: Web Application . SUCCESS [4.589s] [INFO] DSpace JSP-UI :: Web Application .. SUCCESS [5.691s] [INFO] DSpace SWORD :: Web Application ... SUCCESS [4.986s] [INFO] DSpace SOLR :: Web Application SUCCESS [10.092s] [INFO] DSpace Assembly and Configuration . SUCCESS [44.539s] [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 1:22.092s [INFO] Finished at: Tue Jan 11 15:12:14 EST 2011 [INFO] Final Memory: 10M/26M [INFO] dev:/home/user/Desktop/dspace-1.7.0-release/dspace# cd /home/user/Desktop/dspace-1.7.0-release/dspace/target/dspace-1.7.0-build.dir dev:/home/user/Desktop/dspace-1.7.0-release/dspace/target/dspace-1.7.0-build.dir# ls bin build.xml CHANGES config docs etc KNOWN_BUGS lib LICENSE README solr webapps dev:/home/user/Desktop/dspace-1.7.0-release/dspace/target/dspace-1.7.0-build.dir# ant fresh_install Buildfile: build.xml init_installation: init_configs: [copy] Copying 1 file to /usr/local/dspace/config test_database: [java] 2011-01-11 15:12:49,705 INFO org.dspace.core.ConfigurationManager @ Loading system provided config property (-Ddspace.configuration): config/dspace.cfg [java] 2011-01-11 15:12:49,724 INFO org.dspace.core.ConfigurationManager @ Using default log4j provided log configuration,if unintended, check your dspace.cfg for (log.init.config) [java] [java] Attempting to connect to database: [java] - URL: jdbc:postgresql://localhost:5432/dspace [java] - Driver: org.postgresql.Driver [java] - Username: postgres [java] - Password: zsx [java] - Schema: dspace [java] [java] Testing connection... [java] Connected successfully! [java] setup_database: [java] 2011-01-11 15:12:51,258 INFO org.dspace.core.ConfigurationManager @ Loading system provided config property (-Ddspace.configuration): config/dspace.cfg [java] 2011-01-11 15:12:51,264 INFO org.dspace.core.ConfigurationManager @ Using default log4j provided log configuration,if unintended, check your dspace.cfg for (log.init.config) [java] 2011-01-11 15:12:51,264 INFO org.dspace.storage.rdbms.InitializeDatabase @ Initializing Database [java] 2011-01-11 15:13:01,503 INFO org.dspace.core.ConfigurationManager @ Loading system provided config property (-Ddspace.configuration): config/dspace.cfg [java] 2011-01-11 15:13:01,509 INFO org.dspace.core.ConfigurationManager @ Using default log4j provided log configuration,if unintended, check your dspace.cfg for (log.init.config) [java] Started: 1294776781495 [java] Ended: 1294776782197 [java] Elapsed time: 0 secs (702 msecs) load_registries: [java] 2011-01-11 15:13:02,426 INFO org.dspace.core.ConfigurationManager @ Loading system provided config property (-Ddspace.configuration): config/dspace.cfg [java]
Re: [Dspace-tech] Failing compilation on debian lenny, PostgreSQL 8.3.12, libpg-java 8.2-504-2, java version 1.6.0_20, tomcat 5.5
Hi Kocisky, Your Maven build part is working properly. I didn't notice you were using the 'dspace-1.7.0-release' version (which has pre-compiled code, and therefore responds as having built fewer modules). I had thought you were still using the 'dspace-1.7.0-src-release' version. Here's something else you can try: (1) From [dspace-src]/dspace/ run this command: 'mvn clean package' (WARNING: this will first delete the entire /target/dspace-1.7.0-build.dir , before it rebuilds DSpace.) (2) After DSpace has been rebuilt, edit the following configuration file: [dspace-src]/dspace/target/dspace-1.7.0-build.dir/config/log4j-console.properties In that text file, temporarily change the following line: log4j.rootCategory=INFO, A1 Replace INFO with DEBUG like this: log4j.rootCategory=DEBUG, A1 This changes the logging mode to debug. That means that the DSpace installer will now report a lot more information to you about what is going on while DSpace is being installed. (3) Finally, re-run the 'ant fresh_install' command. This time, you should see a ton of extra information be logged to your command line (since you are now in debug mode). Once it errors out again, please email us the lines just *before* that error message. This time, those lines should include extra information on what is happening and what exact command the install process is failing on. Hopefully this extra information can help us figure out what could be going wrong in your DSpace installation. - Tim On 1/11/2011 2:31 PM, Kocisky wrote: Hi Tim, thank you for your reply, i've followed your suggestions but didn't got many results, see below: DSpace 1.7 actually comes packaged with the PostgreSQL JDBC driver it needs to use. You do not need to install a separate JDBC driver (in fact, you may want to remove what you installed, to make sure it doesn't cause any conflicts). great, i've removed that package The full installation prerequisites instructions are at: https://wiki.duraspace.org/display/DSDOC/Installation i was following the doc in the pkg, thanks also for this ! Also be aware that you will need Maven 2.2.x or above to properly build DSpace 1.7.0. We've discovered an error in builds with Maven 2.0.x -- see the above link for more details (look under the prerequisites software section) i'm now using apache-maven 3.0.1 but have the same syntax problem, see below Your version of Maven actually may be part of the problem. After the Maven build, it seems you don't receive a full summary of all modules being built properly. Double check that you are running 'mvn package' from the [dspace-src]/dspace/ directory. The results of a successful build should report similar to this (notice how many more modules were built -- you only had 8 listed in your logs below): maybe i have less packages because i'm not compiling the source but the slim package with pre-compiled modules? here the last build with maven version: [INFO] Copying 1394 files to /home/user/Desktop/dspace-1.7.0-release/dspace/target/dspace-1.7.0-build.dir [INFO] [INFO] Reactor Summary: [INFO] [INFO] DSpace Addon Modules .. SUCCESS [0.385s] [INFO] DSpace XML-UI (Manakin) :: Web Application SUCCESS [7.276s] [INFO] DSpace LNI :: Web Application . SUCCESS [4.203s] [INFO] DSpace OAI :: Web Application . SUCCESS [4.589s] [INFO] DSpace JSP-UI :: Web Application .. SUCCESS [5.691s] [INFO] DSpace SWORD :: Web Application ... SUCCESS [4.986s] [INFO] DSpace SOLR :: Web Application SUCCESS [10.092s] [INFO] DSpace Assembly and Configuration . SUCCESS [44.539s] [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 1:22.092s [INFO] Finished at: Tue Jan 11 15:12:14 EST 2011 [INFO] Final Memory: 10M/26M [INFO] dev:/home/user/Desktop/dspace-1.7.0-release/dspace# cd /home/user/Desktop/dspace-1.7.0-release/dspace/target/dspace-1.7.0-build.dir dev:/home/user/Desktop/dspace-1.7.0-release/dspace/target/dspace-1.7.0-build.dir# ls bin build.xmlCHANGES config docs etc KNOWN_BUGS lib LICENSE README solr webapps dev:/home/user/Desktop/dspace-1.7.0-release/dspace/target/dspace-1.7.0-build.dir# ant fresh_install Buildfile: build.xml init_installation: init_configs: [copy] Copying 1 file to /usr/local/dspace/config test_database: [java] 2011-01-11 15:12:49,705 INFO org.dspace.core.ConfigurationManager @ Loading system provided config property (-Ddspace.configuration): config/dspace.cfg [java] 2011-01-11 15:12:49,724 INFO
Re: [Dspace-tech] Failing compilation on debian lenny, PostgreSQL 8.3.12, libpg-java 8.2-504-2, java version 1.6.0_20, tomcat 5.5
Tim, i think that the DEBUG flag is not helping us much, in the mean while i've tried also to update ant to 1.8.2 but nothing... should we enable other debug flags? maybe in org.postgresql.util package ? thank you, K [java] 2011-01-11 17:19:37,432 DEBUG org.dspace.storage.rdbms.DatabaseManager @ Running query CREATE INDEX bi_4_dis_value_idx ON bi_4_dis(value) with parameters: [java] 2011-01-11 17:19:37,433 DEBUG org.dspace.storage.rdbms.DatabaseManager @ Running query CREATE INDEX bi_4_dis_uvalue_idx ON bi_4_dis(UPPER(value)) with parameters: [java] 2011-01-11 17:19:37,435 DEBUG org.dspace.storage.rdbms.DatabaseManager @ Running query CREATE INDEX bi_4_dmap_item_id_idx ON bi_4_dmap(item_id) with parameters: [java] 2011-01-11 17:19:37,436 DEBUG org.dspace.storage.rdbms.DatabaseManager @ Running query CREATE INDEX bi_4_dmap_dist_idx ON bi_4_dmap(distinct_id) with parameters: [java] Started: 1294784376950 [java] Ended: 1294784377438 [java] Elapsed time: 0 secs (488 msecs) load_registries: [java] 2011-01-11 17:19:38,273 INFO org.dspace.core.ConfigurationManager @ Loading system provided config property (-Ddspace.configuration): config/dspace.cfg [java] 2011-01-11 17:19:38,281 INFO org.dspace.core.ConfigurationManager @ Using default log4j provided log configuration,if unintended, check your dspace.cfg for (log.init.config) [java] 2011-01-11 17:19:39,283 DEBUG org.dspace.storage.rdbms.DatabaseManager @ Running query INSERT INTO bitstreamformatregistry ( ) VALUES ( ) RETURNING null [java] 2011-01-11 17:19:39,292 FATAL org.dspace.administer.RegistryLoader @ anonymous::error_loading_registries: [java] org.postgresql.util.PSQLException: ERROR: syntax error at or near ) [java] at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:1531) [java] at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1313) [java] at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:188) [java] at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:452) [java] at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:354) [java] at org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:258) [java] at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) [java] at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) [java] at org.apache.commons.dbcp.DelegatingPreparedStatement.executeError: [java] - ERROR: syntax error at or near ) [java] Query(DelegatingPreparedStatement.java:96) [java] at org.dspace.storage.rdbms.DatabaseManager.doInsertPostgres(DatabaseManager.java:1755) [java] at org.dspace.storage.rdbms.DatabaseManager.insert(DatabaseManager.java:675) [java] at org.dspace.storage.rdbms.DatabaseManager.create(DatabaseManager.java:451) [java] at org.dspace.content.BitstreamFormat.create(BitstreamFormat.java:403) [java] at org.dspace.administer.RegistryLoader.loadFormat(RegistryLoader.java:172) [java] at org.dspace.administer.RegistryLoader.loadBitstreamFormats(RegistryLoader.java:138) [java] at org.dspace.administer.RegistryLoader.main(RegistryLoader.java:75) BUILD FAILED /home/user/Desktop/dspace-1.7.0-src-release/dspace/target/dspace-1.7.0-build.dir/build.xml:809: Java returned: 1 Total time: 13 seconds On 11 January 2011 16:31, Tim Donohue tdono...@duraspace.org wrote: Hi Kocisky, Your Maven build part is working properly. I didn't notice you were using the 'dspace-1.7.0-release' version (which has pre-compiled code, and therefore responds as having built fewer modules). I had thought you were still using the 'dspace-1.7.0-src-release' version. Here's something else you can try: (1) From [dspace-src]/dspace/ run this command: 'mvn clean package' (WARNING: this will first delete the entire /target/dspace-1.7.0-build.dir , before it rebuilds DSpace.) (2) After DSpace has been rebuilt, edit the following configuration file: [dspace-src]/dspace/target/dspace-1.7.0-build.dir/config/log4j-console.properties In that text file, temporarily change the following line: log4j.rootCategory=INFO, A1 Replace INFO with DEBUG like this: log4j.rootCategory=DEBUG, A1 This changes the logging mode to debug. That means that the DSpace installer will now report a lot more information to you about what is going on while DSpace is being installed. (3) Finally, re-run the 'ant fresh_install' command. This time, you should see a ton of extra information be logged to your command line (since you are now in debug mode). Once it errors out again, please email us the lines just *before* that error message. This time, those lines should
Re: [Dspace-tech] Failing compilation on debian lenny, PostgreSQL 8.3.12, libpg-java 8.2-504-2, java version 1.6.0_20, tomcat 5.5
Kocisky,
Actually those logs are helpful. It shows me that for some reason your
install process is not able to load data into your
'bitstreamformatregistry' table.
Can you check to make sure this table is created properly in your DB?
It should be created with the following columns:
bitstream_format_id integer NOT NULL,
mimetype character varying(256),
short_description character varying(128),
description text,
support_level integer,
internal boolean
You also may want to look at your PostgreSQL log files, to see if it has
reported any errors.
From your logged output, it looks like DSpace is not able to determine
the columns in this 'bitstreamformatregistry' table. That's why you see:
[java] 2011-01-11 17:19:39,283 DEBUG
org.dspace.storage.rdbms.DatabaseManager @ Running query INSERT INTO
bitstreamformatregistry ( ) VALUES ( ) RETURNING null
In a successful install, you should instead see a long listing of
similar INSERT queries, which look like this:
[java] 2011-01-11 16:58:27,896 DEBUG
org.dspace.storage.rdbms.DatabaseManager @ Running query INSERT INTO
bitstreamformatregistry (
mimetype,short_description,description,support_level,bitstream_format_id,internal)
VALUES ( ?,?,?,?,getnextid('bitstreamformatregistry'),?) RETURNING
bitstream_format_id
These insert queries should be run for *every* entry in the
dspace/config/registries/bitstream-formats.xml file. Unfortunately,
your install process is erroring out on the first insert, which likely
means something may be wrong with your database or your database (db.*)
settings in the dspace.cfg.
Let us know what you find out!
- Tim
On 1/11/2011 4:35 PM, Kocisky wrote:
Tim, i think that the DEBUG flag is not helping us much, in the mean
while i've tried also to update ant to 1.8.2 but nothing...
should we enable other debug flags? maybe in org.postgresql.util package ?
thank you,
K
[java] 2011-01-11 17:19:37,432 DEBUG
org.dspace.storage.rdbms.DatabaseManager @ Running query CREATE INDEX
bi_4_dis_value_idx ON bi_4_dis(value) with parameters:
[java] 2011-01-11 17:19:37,433 DEBUG
org.dspace.storage.rdbms.DatabaseManager @ Running query CREATE INDEX
bi_4_dis_uvalue_idx ON bi_4_dis(UPPER(value)) with parameters:
[java] 2011-01-11 17:19:37,435 DEBUG
org.dspace.storage.rdbms.DatabaseManager @ Running query CREATE INDEX
bi_4_dmap_item_id_idx ON bi_4_dmap(item_id) with parameters:
[java] 2011-01-11 17:19:37,436 DEBUG
org.dspace.storage.rdbms.DatabaseManager @ Running query CREATE INDEX
bi_4_dmap_dist_idx ON bi_4_dmap(distinct_id) with parameters:
[java] Started: 1294784376950
[java] Ended: 1294784377438
[java] Elapsed time: 0 secs (488 msecs)
load_registries:
[java] 2011-01-11 17:19:38,273 INFO
org.dspace.core.ConfigurationManager @ Loading system provided config
property (-Ddspace.configuration): config/dspace.cfg
[java] 2011-01-11 17:19:38,281 INFO
org.dspace.core.ConfigurationManager @ Using default log4j provided
log configuration,if unintended, check your dspace.cfg for
(log.init.config)
[java] 2011-01-11 17:19:39,283 DEBUG
org.dspace.storage.rdbms.DatabaseManager @ Running query INSERT INTO
bitstreamformatregistry ( ) VALUES ( ) RETURNING null
[java] 2011-01-11 17:19:39,292 FATAL
org.dspace.administer.RegistryLoader @
anonymous::error_loading_registries:
[java] org.postgresql.util.PSQLException: ERROR: syntax error at
or near )
[java] at
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:1531)
[java] at
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1313)
[java] at
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:188)
[java] at
org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:452)
[java] at
org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:354)
[java] at
org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:258)
[java] at
org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
[java] at
org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
[java] at
org.apache.commons.dbcp.DelegatingPreparedStatement.executeError:
[java] - ERROR: syntax error at or near )
[java] Query(DelegatingPreparedStatement.java:96)
[java] at
org.dspace.storage.rdbms.DatabaseManager.doInsertPostgres(DatabaseManager.java:1755)
[java] at
org.dspace.storage.rdbms.DatabaseManager.insert(DatabaseManager.java:675)
[java] at
org.dspace.storage.rdbms.DatabaseManager.create(DatabaseManager.java:451)
[java] at
org.dspace.content.BitstreamFormat.create(BitstreamFormat.java:403)
[java] at
Re: [Dspace-tech] Failing compilation on debian lenny, PostgreSQL 8.3.12, libpg-java 8.2-504-2, java version 1.6.0_20, tomcat 5.5
Kocisky, I'm actually at a loss for what exactly could be causing this problem (and unfortunately I don't have a Debian server and am not as familiar with Debian). Are you running Oracle's (Sun's) Java? You need to make sure you are running that version of Java, and not the one that comes with Debian. Also, through the power of Google, I found this nice reference for installing DSpace on Debian 5 (Lenny): http://rspproject.wordpress.com/2010/11/10/installing-dspace-on-debian-5/ So, that blog post may be helpful to resolve your issues. You may want to double check you've installed all the Prerequisities for DSpace 1.7, similar to how it is detailed in that posting. Hopefully that is of some help, or perhaps someone else on this list is more familiar with Debian than I. Good luck, - Tim On 1/7/2011 9:52 AM, Kocisky wrote: below the important part: [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 5 minutes 5 seconds [INFO] Finished at: Fri Jan 07 09:46:00 EST 2011 [INFO] Final Memory: 84M/203M [INFO] dev:/home/user/Desktop/dspace-1.7.0-src-release/dspace# cd /home/user/Desktop/dspace-1.7.0-src-release/dspace/target/dspace-1.7.0-build.dir dev:/home/user/Desktop/dspace-1.7.0-src-release/dspace/target/dspace-1.7.0-build.dir# ant fresh_install Buildfile: build.xml init_installation: [mkdir] Created dir: /usr/local/dspace_src/bin [mkdir] Created dir: /usr/local/dspace_src/config [mkdir] Created dir: /usr/local/dspace_src/lib [mkdir] Created dir: /usr/local/dspace_src/etc [mkdir] Created dir: /usr/local/dspace_src/webapps [mkdir] Created dir: /usr/local/dspace_src/exports [mkdir] Created dir: /usr/local/dspace_src/exports/download [mkdir] Created dir: /usr/local/dspace_src/assetstore [mkdir] Created dir: /usr/local/dspace_src/handle-server [mkdir] Created dir: /usr/local/dspace_src/search [mkdir] Created dir: /usr/local/dspace_src/log [mkdir] Created dir: /usr/local/dspace_src/upload [mkdir] Created dir: /usr/local/dspace_src/reports [mkdir] Created dir: /usr/local/dspace_src/solr init_configs: [copy] Copying 61 files to /usr/local/dspace_src/config [copy] Copying 1 file to /usr/local/dspace_src/config test_database: [java] 2011-01-07 09:46:35,471 INFO org.dspace.core.ConfigurationManager @ Loading system provided config property (-Ddspace.configuration): config/dspace.cfg [java] 2011-01-07 09:46:35,477 INFO org.dspace.core.ConfigurationManager @ Using default log4j provided log configuration,if unintended, check your dspace.cfg for (log.init.config) [java] [java] Attempting to connect to database: [java] - URL: jdbc:postgresql://localhost:5432/dspace [java] - Driver: org.postgresql.Driver [java] - Username: postgres [java] - Password: zsx [java] - Schema: dspace [java] [java] Testing connection... [java] Connected successfully! [java] setup_database: [java] 2011-01-07 09:46:36,156 INFO org.dspace.core.ConfigurationManager @ Loading system provided config property (-Ddspace.configuration): config/dspace.cfg [java] 2011-01-07 09:46:36,162 INFO org.dspace.core.ConfigurationManager @ Using default log4j provided log configuration,if unintended, check your dspace.cfg for (log.init.config) [java] 2011-01-07 09:46:36,162 INFO org.dspace.storage.rdbms.InitializeDatabase @ Initializing Database [java] 2011-01-07 09:46:43,759 INFO org.dspace.core.ConfigurationManager @ Loading system provided config property (-Ddspace.configuration): config/dspace.cfg [java] 2011-01-07 09:46:43,765 INFO org.dspace.core.ConfigurationManager @ Using default log4j provided log configuration,if unintended, check your dspace.cfg for (log.init.config) [java] Started: 1294411603751 [java] Ended: 1294411604212 [java] Elapsed time: 0 secs (461 msecs) load_registries: [java] 2011-01-07 09:46:44,518 INFO org.dspace.core.ConfigurationManager @ Loading system provided config property (-Ddspace.configuration): config/dspace.cfg [java] 2011-01-07 09:46:44,524 INFO org.dspace.core.ConfigurationManager @ Using default log4j provided log configuration,if unintended, check your dspace.cfg for (log.init.config) [java] 2011-01-07 09:46:45,215 FATAL org.dspace.administer.RegistryLoader @ anonymous::error_loading_registries: [java] org.postgresql.util.PSQLException: ERROR: syntax error at or near ) [java] at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:1531)
