Ok, I did # ant clean_database # ant fresh_install
Now I have BUILD SUCCESSFUL Thanks. Maybe finally I can run this thing! :) Bill Page. On Fri, Aug 12, 2011 at 5:00 PM, Bill Page <[email protected]> wrote: > Tim, > > Thanks for the suggested work-round. This time, after copying the > file and running 'ant fresh_install' the 2nd time, I get error > messages concerning "duplicate keys". This is how the build ends: > > load_registries: > [java] 2011-08-12 16:26:06,902 INFO > org.dspace.core.ConfigurationManager @ Loading system provided config > property (-Ddspace.configuration): config/dspace.cfg > [java] 2011-08-12 16:26:06,910 INFO > org.dspace.core.ConfigurationManager @ Using default log4j provided > log configuration,if unintended, check your dspace.cfg for > (log.init.config) > [java] 2011-08-12 16:26:07,371 INFO > org.dspace.content.BitstreamFormat @ > anonymous::create_bitstream_format:bitstream_format_id=76 > [java] 2011-08-12 16:26:07,381 INFO > org.dspace.content.BitstreamFormat @ > anonymous::update_bitstream_format:bitstream_format_id=76 > [java] 2011-08-12 16:26:07,386 FATAL > org.dspace.administer.RegistryLoader @ > anonymous::error_loading_registries: > [java] org.postgresql.util.PSQLException: ERROR: duplicate key > value violates unique constraint > "bitstreamformatregistry_short_description_key" > [java] Detail: Key (short_description)=(Unknown) already exists. > [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.executeUpdate(AbstractJdbc2Statement.java:308) > [java] at > org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) > [java] at > org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) > [java] at > org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) > [java] at > org.dspace.storage.rdbms.DatabaseManager.executeUpdate(DatabaseManager.java:1315) > [java] at > org.dspace.storage.rdbms.DatabaseManager.update(DatabaseManager.java:729) > [java] at > org.dspace.content.BitstreamFormat.update(BitstreamFormat.java:601) > [java] at > org.dspace.administer.RegistryLoader.loadFormat(RegistryLoader.java:183) > [java] at > org.dspace.administer.RegistryLoader.loadBitstreamFormats(RegistryLoader.java:138) > [java] at > org.dspace.administer.RegistryLoader.main(RegistryLoader.java:75) > [java] Error: > [java] - ERROR: duplicate key value violates unique constraint > "bitstreamformatregistry_short_description_key" > [java] Detail: Key (short_description)=(Unknown) already exists. > > BUILD FAILED > /home/page/dspace-1.7.2-src-release/dspace/target/dspace-1.7.2-build.dir/build.xml:809: > Java returned: 1 > > Total time: 7 seconds > page@linux-am71:~/dspace-1.7.2-src-release/dspace/target/dspace-1.7.2-build.dir> > > ---- > > Should I be doing something other than fresh_install? > > Regards, > Bill Page. > > On Fri, Aug 12, 2011 at 3:05 PM, Tim Donohue <[email protected]> wrote: >> Hi Bill, >> >> On 8/11/2011 4:39 PM, Bill Page wrote: >>> >>> Tim Donohue, >>> >>> Thank you for your comments and suggestions. >>> >>> Yes, I did configure a proxy for maven as a necessary first step, but >>> in our situation the proxy is very strict. HTTP and FTP download >>> requests of any files that are known to be potential threat vectors >>> (i.e which might contain malicious code) are automatically processed >>> by something called "McAfee Web Gateway" and require a dialogue with >>> the user to successfully complete the download. I am in a situation >>> where I can only argue with these security measures on a special >>> case-by-case basis. After a little arm twisting I did manage to get >>> repo1.maven.org added as an exception. This allows me to at least >>> complete the 'maven -U package' process. >> >> That's good to hear. >> >>> Besides the large size (about 250 Mbytes), is there some reason why >>> there is no optional download of DSpace that has this maven build >>> process pre-completed? Is there some critical architecture or >>> machine-dependent processing about this step? For example, would it >>> necessarily be limited to specific version of java etc.? >> >> There are a few reasons we still distribute everything via Maven, rather >> than just packaging up a bit downloadable zip. One reason is that Maven is >> actually helpful if people wish to customize their DSpace install (which >> many do), as one can more easily separate their custom code from the >> out-of-the-box DSpace code. It also helps simplify upgrades (to a point) >> because of this code separation. Finally, it can also allow us to >> pre-configure the dspace.cfg configuration file with things like Oracle DB >> or PostgreSQL DB specific settings (this is a minor feature though). >> >> That being said, a downloadable zip file may be of use to sites that don't >> want to customize DSpace at all (or have very minimal customizations which >> they want to keep track of on their own). >> >> So, it may be worth the developers reanalyzing whether there are situations >> where a downloadable zip could be useful, rather than building via Maven. >> >>> As you say, >>> later I will have to copy the result of this step to another machine >>> that is completely isolated from the Internet. Do I have to make sure >>> that the environment is identical between the build and target >>> machines? >> >> No, they don't need to be identical. Technically you could build DSpace on a >> Windows machine and copy it to a Linux machine and it all should still work >> fine. It'd probably be best to have the same version of Java on them though. >> Beyond that, just follow the normal prerequisites: >> https://wiki.duraspace.org/display/DSDOC/Installation >> >>> But now I find I am stuck again during the install. Is there some way >>> that I can avoid 'update_geolite'? What is the purpose of >>> 'update_geolite'? >> >> Ugh. This is a known bug, which we're working on fixing in 1.8.0: >> https://jira.duraspace.org/browse/DS-878 >> >> Essentially, that script is attempting to download the "GeoLiteCity.data.gz" >> data file, which is used by the DSpace statistics engine to help determine >> where hits/downloads are coming from (what country, etc). Unfortunately, if >> that file fails to download or times out, then the install process fails. >> This will be fixed in 1.8.0. >> >> In the meantime, you can get around this by manually installing the file >> into DSpace: >> >> (1) Download file from: >> http://geolite.maxmind.com/download/geoip/database/GeoLiteCity.dat.gz >> (2) Unzip the file, which will create a file named "GeoLiteCity.dat" >> (3) Manually copy this file to the folder [dspace]/config/ (where [dspace] >> is the location where you are installing DSpace, i.e. the 'dspace.dir' value >> in your dspace.cfg) >> (4) Rerun 'ant fresh_install'. This time, it should skip over the >> 'update_geolite' step, as it will see that the >> [dspace]/config/GeoLiteCity.dat file already exists. >> >> Sorry about this issue. As you can tell, DSpace currently is not very well >> tailored to installation from a machine with no internet access. >> >> - Tim >> > ------------------------------------------------------------------------------ FREE DOWNLOAD - uberSVN with Social Coding for Subversion. Subversion made easy with a complete admin console. Easy to use, easy to manage, easy to install, easy to extend. Get a Free download of the new open ALM Subversion platform now. http://p.sf.net/sfu/wandisco-dev2dev _______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
