Re: [dspace-tech] Build Fail after running ant fresh_install see attached

[Claudia Jürgen]

Hello Mutowongi,

you still got the dspace.dir not properly set, or rather set twice.
Remove the wrong one (dspace.dir = /dspace)  or comment it out.

Hope this helps

Claudia Jürgen



Am 23.02.2017 um 08:32 schrieb Mutowongi:

# Windows note: Please remember to use forward slashes for all paths (e.g. 
C:/dspace)
dspace.dir = /dspace


dspace.dir = C:/dspace


--
Claudia Juergen
Eldorado

Technische Universität Dortmund
Universitätsbibliothek
Vogelpothsweg 76
44227 Dortmund

Tel.: +49 231-755 40 43
Fax: +49 231-755 40 32
claudia.juer...@tu-dortmund.de
www.ub.tu-dortmund.de

Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie ist 
ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für diese 
E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender und 
vernichten Sie diese Mail. Vielen Dank.
Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen 
ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher Schriftform 
(mit eigenhändiger Unterschrift) oder durch Übermittlung eines solchen 
Schriftstücks per Telefax erfolgen.

Important note: The information included in this e-mail is confidential. It is 
solely intended for the recipient. If you are not the intended recipient of 
this e-mail please contact the sender and delete this message. Thank you. 
Without prejudice of e-mail correspondence, our statements are only legally 
binding when they are made in the conventional written form (with personal 
signature) or when such documents are sent by fax.

--
You received this message because you are subscribed to the Google Groups "DSpace 
Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Re: d space BUILD FAILED see attached document

[Mutowongi]

thanks but stilling am facing another build fail see new post sent by me

On Wednesday, February 22, 2017 at 1:37:17 PM UTC+2, Claudia Jürgen wrote:
>
> Hello Mutowongi, 
>
> you seem to have an error in 
> your local.cfg see 
>
> https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace/config/local.cfg.EXAMPLE#L31
>  
> check your settings of "dspace.dir". 
> Even for Windows you need to  use forward slashes. So assuming you 
> created an installation directory at C:\DSpace 
> the setting would be 
> dspace.dir=C:/DSpace 
>
> Hope this helps 
>
> Claudia Jürgen 
>
>
>
> Am 22.02.2017 um 11:53 schrieb Mutowongi: 
> > error occurred after running ant fresh_install 
> > 
> > 
> >> BUILD FAILED 
> >> C:\dspace-6.0-src-release\dspace\target\dspace-installer\build.xml:780: 
> >> Failed to copy 
> >> 
> C:\dspace-6.0-src-release\dspace\target\dspace-installer\config\dspace.cfg 
> >> to C:\Dspace.  \config\dspace.cfg due to java.io.FileNotFoundException 
> >> C:\Dspace.  \config\dspace.cfg (The system cannot find the path 
> specified) 
> >> 
> >> Total time: 2 seconds 
> >> 
> >> 
> >> 
> C:\dspace-6.0-src-release\dspace\target\dspace-installer>C:\dspace-6.0-src-release\dspace\target\dspace-installerC:\dspace-6.0-src-release\dspace\target\dspace-installerC:\dspace-6.0-src-release\dspace\target\dspace-installer
>  
>
> >> 
>
> -- 
> Claudia Juergen 
> Eldorado 
>
> Technische Universität Dortmund 
> Universitätsbibliothek 
> Vogelpothsweg 76 
> 44227 Dortmund 
>
> Tel.: +49 231-755 40 43 
> Fax: +49 231-755 40 32 
> claudia...@tu-dortmund.de  
> www.ub.tu-dortmund.de 
>
> Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie 
> ist ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für 
> diese E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender 
> und vernichten Sie diese Mail. Vielen Dank. 
> Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen 
> ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher 
> Schriftform (mit eigenhändiger Unterschrift) oder durch Übermittlung eines 
> solchen Schriftstücks per Telefax erfolgen. 
>
> Important note: The information included in this e-mail is confidential. 
> It is solely intended for the recipient. If you are not the intended 
> recipient of this e-mail please contact the sender and delete this message. 
> Thank you. Without prejudice of e-mail correspondence, our statements are 
> only legally binding when they are made in the conventional written form 
> (with personal signature) or when such documents are sent by fax. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Build Fail after running ant fresh_install see attached

[Mutowongi]

Build Fail after running ant fresh_install see attached

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
#
# DSpace Configuration
#
# NOTE: The DSpace Configuration File is separated into several sections:

#  * General Configurations

#  * JSPUI & XMLUI Configurations

#  * JSPUI Specific Configurations

#  * XMLUI Specific Configurations
#


#--#

#--GENERAL CONFIGURATIONS--#

#--#

# These configs are used by underlying DSpace API, and are #

# therefore applicable to all interfaces   #

# Local configuration should be made in local.cfg (where possible) #

# Global or more complex configuration can be hardcoded here   #

#--#



# Basic information ##



# DSpace installation directory

# Windows note: Please remember to use forward slashes for all paths (e.g. 
C:/dspace)
dspace.dir = /dspace


dspace.dir = C:/dspace


# DSpace host name - should match base URL.  Do not include port number.

dspace.hostname = localhost




# DSpace base host URL.  Include port number etc.

dspace.baseUrl = http://localhost:8080



# The user interface you will be using for DSpace. Common usage is either xmlui 
or jspui

dspace.ui = xmlui




# Full link your end users will use to access DSpace. In most cases, this will 
be the baseurl followed by

# the context path to the UI you are using.

#

# Alternatively, you can use a url redirect or deploy the web application under 
the servlet container root.

# In this case, make sure to remove the /${dspace.ui} from the dspace.url 
property.

dspace.url = ${dspace.baseUrl}/${dspace.ui}





# Optional: DSpace URL for mobile access

# This

#dspace.mobileUrl = http://sapes.org.zw/ir/



# Name of the 
site
dspace.name = SAPES Trust IR



# Default language for metadata values
default.
language = en_US


# Solr server/webapp.

# DSpace uses Solr for all search/browse capability (and for usage statistics 
by default).

# The included 'solr' webapp MUST be deployed to Tomcat for DSpace to function.

# Usually it will be available via port 8080 and the 'solr' context path. But,

# But, you may need to modify this if you are running DSpace on a custom port, 
etc.
solr.server = http://localhost:8080/solr




# Database settings #
#

 DSpace only supports two database types: PostgreSQL or Oracle



# URL for connecting to database

#* Postgres template: jdbc:postgresql://localhost:5432/dspace

#* Oracle template: jdbc:oracle:thin:@//localhost:1521/xe
db.url = jdbc:postgresql://localhost:5432/dspace


db.url = jdbc:postgresql://localhost:5432/dspace

# JDBC Driver

#* For Postgres: org.postgresql.Driver

#* For Oracle:   oracle.jdbc.OracleDriver
db.
driver = org.postgresql.Driver



# Database Dialect (for Hibernate)

#* For Postgres: 
org.dspace.storage.rdbms.hibernate.postgres.DSpacePostgreSQL82Dialect

#* For Oracle:   org.hibernate.dialect.Oracle10gDialect

db.dialect = 
org.dspace.storage.rdbms.hibernate.postgres.DSpacePostgreSQL82Dialect


# Database username and password

db.username = dspace

db.password = dspace



# Database Schema name

#* For Postgres, this is often "public" (default schema)

#* For Oracle, schema is equivalent to the username of your database 
account,

#  so this may be set to ${db.username} in most scenarios.

db.schema = public


## Connection pool parameters


# Maximum number of DB connections in pool (default = 30)

db.maxconnections = 30



# Maximum time to wait before giving up if all connections in pool are busy 
(milliseconds)

# (default = 5000ms or 5 seconds)

db.maxwait = 5000



# Maximum number of idle connections in pool (-1 = unlimited)

# (default = -1, unlimited)

db.maxidle = -1



# Specify a configured database connection pool to be fetched from a

# directory.  This overrides the pool and driver settings above.  If

# none can be found, then DSpace will use the above settings to create a

# pool.

#db.jndi = jdbc/dspace



# Whether or not to allow for an entire 'clean' of the DSpace database.

# By default, this setting is 'true', which ensures that the 'dspace database 
clean' command

# does nothing (except return an error message saying clean is disabled)

# Setting this config to 'false' allows your database owner to destroy all 
DSpace data, tables, etc

# by running 'dspace database clean' from commandline. This is only useful for 

Re: [dspace-tech] access restriction by ip range not working for 6.0

[Miika Nurminen]

Wang, Yongming wrote:
We've just upgraded our DSpace from 5.1 to 6.0. We want to restrict 
the bitstream access to one collection to campus only. I enabled the 
IPAuthentication statement in /dspace/config/modules


Now the problem is that we cannot access the bitstream both off-campus 
and on-campus. Every item's bitstream has a lock and either we have to 
login or access, or request a copy by filling in an


After so many failed tries, I start to suspect that it's a program 
bug, because it worked for our previous version (5.1).


Does anyone encounter such problem for DSpace 6.0? Is there any 
workaround to solve this issue?


Hello,

I have reproduced (and possibly fixed) DS-3463 in our 6.0 test 
installation. The following edit to org.dspace.eperson.GroupServiceImpl 
seems to fix it - at least with regard the IP-based access for anonymous 
users, but not extensively tested. Add


  List specialGroups = context.getSpecialGrocups();
  for(Group specialGroup : specialGroups) {
if (StringUtils.equals(specialGroup.getName(), groupName)) {
  return true;
}
  }

to the latter block of isMember(context,groupname) method in (just 
before return false in line 188):


https://github.com/DSpace/DSpace/blob/269af71afb602808a14edf822ad658c3895e0a37/dspace-api/src/main/java/org/dspace/eperson/GroupServiceImpl.java#L188

Rationale: download problem is the same regardless of the format used in 
configuration files (e.g. authentication.ip.GROUP or 
authentication-ip.GROUP) and the result is the same with Mirage or 
Mirage2 themes. While checking the log, it seems that IP authentication 
itself is working. While trying to download the file, messages like


DEBUG org.dspace.authenticate.IPAuthentication @ 
user@university:session_id=...:special_groups=GROUP, group id

DEBUG org.dspace.app.xmlui.utils.ContextUtil @ Adding Special Group id=GROUP

appear, but right after that the "Request copy of the document" pop up 
instead of the file, so this seems to be some kind of 
authorization/group membership checking issue. GroupService.isMember is 
called at least from AuthorizeServiceImpl.authorize while trying to 
download.


While tracking down the cause I noticed that somewhat similar 
authorization error appears also with REST API (i.e. if trying to 
retrieve a bitstream that is protected by IP-based special group) 
unauthenticated - but the above fix does not affect the REST case.



Best regards,
Miika Nurminen

--
You received this message because you are subscribed to the Google Groups "DSpace 
Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] dspace not picking up Shibboleth attributes to authenticate

[Jbell KSU Gmail]

Great - some testing I have not done - I will let you know in the morning.  
Again, thank you!


> On Feb 22, 2017, at 2:57 PM, Tom Desair  wrote:
> 
> Can you enable debug logging for Shibboleth in DSpace by adding this line 
> "log4j.logger.org.dspace.authenticate.ShibAuthentication=DEBUG" to the 
> config/log4j.properties file and retry with the following settings:
> Use AJP
> Make sure to have attributePrefix="AJP_" in your ApplicationDefaults element
> Make sure to proxy to the AJP connector with a buffer that is large enough:
> We always use
> ProxyPass / ajp://localhost:8009/ retry=0
> ProxyPassReverse / ajp://localhost:8009/
> ProxyIOBufferSize 65536
> Make sure the connector is enabled in the Tomcat server.xml file and supports 
> UTF-8 encoding and large packages:
>  URIEncoding="UTF-8" packetSize="65536"/>
> Secure the correct location
> If you run DSpace under the root of your server, make sure this is
> 
> If you run DSpace under the the URL "/dspace", the location should be
> 
> Make sure there are no double slashes in the redirect URL your browser 
> receives (which is the case in your first example).
> Since you are using Apache 2.4 and Shibboleth 2.5, please replace the 
> following in your Apache configuration:
> Replace "ShibRequireSession On" by "ShibRequestSetting requireSession 1"
> Replace "ShibRequireSession Off" by "ShibRequestSetting requireSession 0"
> You can leave the values for lazysession.secure and the DSpace netid and 
> email header settings as you configured them.
> Can you also test this:
> Shutdown tomcat and visit /shibboleth-login after closing all 
> browser windows. This should take you to your IdP login page even if DSpace 
> is not running.
> Have you tried without AJP and using "ShibUseHeaders On" (note that this is 
> less secure and not recommended, but it would still be interesting to know if 
> this works).
> I'm interested to see what the DSpace logs show when you execute these tests. 
> Please also provide some information on the redirect URLs you are seeing.
> 
>  
>   Tom Desair
> 250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586
> Esperantolaan 4, Heverlee 3001, Belgium
> www.atmire.com 
> 
> 
> 2017-02-22 16:24 GMT+01:00 Jbell KSU Gmail  >:
> 
> Thank you for the reply - but that did not solve the problem.  I have the 
> same response in all the logs as prior to the change.  
> 
> I did try several variations on that theme but still have not hit the right 
> combination yet.  Further information that I missed last night:
> 
> Running dSpace 5.4
> 
> # Whether to use lazy sessions or active sessions.
> lazysession = true
> 
> Does this need to change?
> 
> # The url to start a shibboleth session (only for lazy sessions)
> lazysession.loginurl = /Shibboleth.sso/Login
> 
> # Force HTTPS when authenticating (only for lazy sessions)
> lazysession.secure = true
> 
> 
> and my question is this the correct netid-header for this configuration?  
> 
> #email-header = SHIB-MAIL
> netid-header = uid
> email-header = email
> email-use-tomcat-remote-user = false
> 
> 
> 
>> On Feb 22, 2017, at 2:16 AM, Tom Desair > > wrote:
>> 
>> Hi Julie,
>> 
>> The key here is the Apache configuration section
>>  
>>  AuthType shibboleth
>>  ShibRequireSession On
>>  Require valid-user
>> 
>> 
>> This tells the Apache Shibboleth daemon to require a Shibboleth session when 
>> visiting "/shibboleth-login" and to provide all mapped attributes to the 
>> Tomcat application server. For all other URL endpoints, Shibboleth will not 
>> forward the attributes.
>> 
>> However, your DSpace instance is not running under root but under "/dspace". 
>> I conclude this from the fact that you receive a redirect to 
>> "https://test-dspace.xxx.net//dspace/shibboleth-login 
>> ". This means you have 
>> to adjust the Apache configuration to secure that location instead. 
>> 
>> So your problem should be solved when you change "> "/shibboleth-login">" to "". Can you 
>> please try that and let me know if that works?
>> 
>> Best regards,
>> Tom
>>  
>>  Tom Desair
>> 250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586
>> Esperantolaan 4, Heverlee 3001, Belgium
>> www.atmire.com 
>> 
>> 
>> 2017-02-21 23:51 GMT+01:00 J Bell > >:
>> 
>> We are moving to Shibboleth and I am having a problem figuring out where my 
>> configuration is not set correctly to allow the actual authentication to 
>> occur.  This is working in other instances we have running - only dSpace  is 
>> not yet configured properly.   Would anyone have some input as to where 

Re: [dspace-tech] dspace not picking up Shibboleth attributes to authenticate

[Tom Desair]

Can you enable debug logging for Shibboleth in DSpace by adding this line
"log4j.logger.org.dspace.authenticate.ShibAuthentication=DEBUG" to
the config/log4j.properties file and retry with the following settings:

   - Use AJP
  - Make sure to have attributePrefix="AJP_" in your
  ApplicationDefaults element
  - Make sure to proxy to the AJP connector with a buffer that is large
  enough:
 - We always use
- ProxyPass / ajp://localhost:8009/ retry=0
- ProxyPassReverse / ajp://localhost:8009/
- ProxyIOBufferSize 65536
- Make sure the connector is enabled in the Tomcat server.xml
 file and supports UTF-8 encoding and large packages:
- 
- Secure the correct location
  - If you run DSpace under the root of your server, make sure this is
 - 
 - If you run DSpace under the the URL "/dspace", the location
  should be
 - 
 - Make sure there are no double slashes in the redirect URL your
  browser receives (which is the case in your first example).
   - Since you are using Apache 2.4 and Shibboleth 2.5, please replace the
   following in your Apache configuration:
  - Replace "ShibRequireSession On" by "ShibRequestSetting
  requireSession 1"
  - Replace "ShibRequireSession Off" by "ShibRequestSetting
  requireSession 0"
   - You can leave the values for lazysession.secure and the DSpace netid
   and email header settings as you configured them.

Can you also test this:

   - Shutdown tomcat and visit /shibboleth-login after closing
   all browser windows. This should take you to your IdP login page even if
   DSpace is not running.
   - Have you tried without AJP and using "ShibUseHeaders On" (note that
   this is less secure and not recommended, but it would still be interesting
   to know if this works).

I'm interested to see what the DSpace logs show when you execute these
tests. Please also provide some information on the redirect URLs you are
seeing.


[image: logo] Tom Desair
250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586
Esperantolaan 4, Heverlee 3001, Belgium
www.atmire.com


2017-02-22 16:24 GMT+01:00 Jbell KSU Gmail :

>
> Thank you for the reply - but that did not solve the problem.  I have the
> same response in all the logs as prior to the change.
>
> I did try several variations on that theme but still have not hit the
> right combination yet.  Further information that I missed last night:
>
> Running dSpace 5.4
>
> # Whether to use lazy sessions or active sessions.
> lazysession = true
>
> *Does this need to change?*
>
> # The url to start a shibboleth session (only for lazy sessions)
> lazysession.loginurl = /Shibboleth.sso/Login
>
> # Force HTTPS when authenticating (only for lazy sessions)
> lazysession.secure = true
>
>
> and my question is this the correct netid-header for this configuration?
>
> #email-header = SHIB-MAIL
> netid-header = uid
> email-header = email
> email-use-tomcat-remote-user = false
>
>
>
> On Feb 22, 2017, at 2:16 AM, Tom Desair  wrote:
>
> Hi Julie,
>
> The key here is the Apache configuration section
>
>> 
>>  AuthType shibboleth
>>  ShibRequireSession On
>>  Require valid-user
>> 
>
>
> This tells the Apache Shibboleth daemon to require a Shibboleth session
> when visiting "/shibboleth-login" and to provide all mapped attributes to
> the Tomcat application server. For all other URL endpoints, Shibboleth will
> not forward the attributes.
>
> However, your DSpace instance is not running under root but under
> "/dspace". I conclude this from the fact that you receive a redirect to "
> https://test-dspace.xxx.net//dspace/shibboleth-login;. This means you
> have to adjust the Apache configuration to secure that location instead.
>
> So your problem should be solved when you change " "/shibboleth-login">" to "". Can
> you please try that and let me know if that works?
>
> Best regards,
> Tom
>
> [image: logo] Tom Desair
> 250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586
> Esperantolaan 4, Heverlee 3001, Belgium
> www.atmire.com
> 
>
> 2017-02-21 23:51 GMT+01:00 J Bell :
>
>>
>> We are moving to Shibboleth and I am having a problem figuring out where
>> my configuration is not set correctly to allow the actual authentication to
>> occur.  This is working in other instances we have running - only dSpace
>>  is not yet configured properly.   Would anyone have some input as to where
>> I have wandered into the weeds?
>>
>> Notes about our configuration:
>>
>> I have the IDP and my local *SP  (shibboleth 2.5.2)  * configured and
>> talking as I would expect.
>>
>> We are using *mod_ajp*  for the proxy  (this did not work under 

[dspace-tech] Dspace embargo-lifter CHECK WARNING

[Margaret Vail]

Hi,

Has anyone seen a message like this before or have any idea what it is 
trying to tell me?

Thanks,

Margaret

Subject: Cron  /dspace/bin/./dspace 
embargo-lifter

 

CHECK WARNING: Item 12345678/24509, filename.pdf.jpg (in Bundle THUMBNAIL) 
allows READ by Group Anonymous CHECK WARNING: Item 12345678/24509, 
Bitstream filename.pdf.txt (in Bundle TEXT) allows READ by Group Anonymous 
CHECK WARNING: Item 12345678/24509, Bundle ORIGINAL allows READ by Group 
Anonymous CHECK WARNING: Item 12345678/24509, Bitstream filename.pdf (in 
Bundle ORIGINAL) allows READ by Group Anonymous

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Integrating LCSH as a controlled vocabulary for the subject field

[Long nam]

hi All,


Currently in our metadata schema, uploaders can input anything they want in 
the dc.subject field.  I would prefer to see this field reserved for LC 
Subject Headings, and I note that using this field for a controlled 
vocabulary is also recommended by Dublin core:


Can someone please point out an instruction on how to enable it in Dspace?


Many thanks

-LN


-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Error copie database production to test enviroment dspace 4.0

[christian criollo]

Hi all

in the last days I have problems with the database when the database is 
updated with the data of production, for some reason the structure some 
tables changed for example the table collection, metadatavalue has the 
structure of a database dspace version 5.0 the version of Dspace we use is 
the 4.0 I dont know why if in production the database the versioon is the 
4.0 when it copied this database in test enviroment this changed, thanks 
for the help 

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Re: Migrating from 3.x to 6.0: issues with stats

[Shawn Kiewel]

Is there any chance I can use the data in dspace-log-general-date.dat and 
dspace-log-monthly-date.dat to import the data? I don't have the old dspace 
logs. Space issues caused those to be removed and a short retain period of 
individual logs put in place. Regretfully, they were not backed up 
beforehand, as there was no space to put them. 

Shawn

On Tuesday, February 21, 2017 at 1:01:52 PM UTC-5, Shawn Kiewel wrote:
>
> I have an existing 3.x installation that is in desperate need of an 
> upgrade. However, an in-place upgrade is not doable, and stakeholders want 
> to see what 6.0 would look and feel like before ok'ing the upgrade. So I've 
> performed a clean install of DSpace 6.0 on a new VM and have started 
> migrating data and customizing the interface. I've managed to move the 
> database over, and it migrated just fine. After reindexing, I am able to 
> find all the expected records. I have not yet migrated over the assetstore, 
> so I can't confirm yet that I can access the digital objects themselves. 
>
> However, I have tried to migrate another section of necessary data and 
> have run into issues: statistics. I tried to fake an upgrade by copying 
> over the production [dspace]/solr/statistics folder. The ant upgrade task 
> noted the out of date solr indexes and said it successfully migrated them. 
> However when I tried to run [dspace]/bin/dspace solr-reindex-statistics, 
> I received the following error:
>
> Exception: SolrCore 'statistics' is not available due to init failure: 
> Error Instantiating Update Handler, solr.DirectUpdateHandler2 failed to 
> instantiate org.apache.solr.update.UpdateHandler
> org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException: 
> SolrCore 'statistics' is not available due to init failure: Error 
> Instantiating Update Handler, solr.DirectUpdateHandler2 failed to 
> instantiate org.apache.solr.update.UpdateHandler
> at 
> org.apache.solr.client.solrj.impl.HttpSolrServer.executeMethod(HttpSolrServer.java:552)
> at 
> org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:210)
> at 
> org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:206)
> at 
> org.apache.solr.client.solrj.request.CoreAdminRequest.process(CoreAdminRequest.java:510)
> at org.dspace.util.SolrImportExport.reindex(SolrImportExport.java:320)
> at org.dspace.util.SolrImportExport.main(SolrImportExport.java:184)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at 
> org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:229)
> at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:81)
>
> 3.x is old enough that [dspace]/bin/dspace solr-export-statistics does 
> not exist. Any other suggestions on how to move my stats data over to the 
> new server? Loss of stats data is a big deal to the stakeholders.
>
> Thanks,
> Shawn
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Re: REST API DSpace6.0 update bitstream contents (http 500)

[Tim Donohue]

Hi Elia,

Would you be willing to submit a Pull Request to fix this issue? Or log a
bug and attach a patch. We'd gladly work to get this resolved in the main
codebase, but we'd appreciate your help. As open source software, DSpace is
primarily developed and supported by its community of nearly 2,000
institutions worldwide. So, we encourage everyone to report bugs and fixes
back.

Here's our bug tracker: https://jira.duraspace.org/projects/DS/  (If you
need an account, please email sysad...@duraspace.org and we'll send you an
invite)
Here's how to contribute code to DSpace:
https://wiki.duraspace.org/display/DSPACE/Code+Contribution+Guidelines
(For a small fix, you are welcome to just submit a small Pull Request or
attach a patch to the ticket.

Submitting the bug fix back to us also means you'd no longer have to
maintain it locally (via overrides, etc).

Sincerely,

Tim

On Wed, Feb 22, 2017 at 8:15 AM Sebastijan Elbl 
wrote:

> Hi Elia,
>
> Thanks for the help.
>
> I hope that bug will be fixed in 6.1
>
> --
> You received this message because you are subscribed to the Google Groups
> "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dspace-tech+unsubscr...@googlegroups.com.
> To post to this group, send email to dspace-tech@googlegroups.com.
> Visit this group at https://groups.google.com/group/dspace-tech.
> For more options, visit https://groups.google.com/d/optout.
>
-- 

Tim Donohue
Technical Lead for DSpace & DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Re: REST API DSpace6.0 update bitstream contents (http 500)

[Sebastijan Elbl]

Hi Elia,

Thanks for the help.

I hope that bug will be fixed in 6.1 

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Re: No website display

[George Kozak]

Jeff:
 In general, in server.xml, is where you define what is the root for tomcat
and what webapps are activated and how to get to them.  I'm surprised that
nothing is showing up.  Maybe that's the problem, or the definitions could
be somewhere else, like /bin/setenv.sh.  Somewhere in tomcat the
path to the webapps and what is the root webapp and what the DSpace
instance is called has to be defined.  Anyway, here is how the pertinent
part of my server.xml is set up on my production server:

 

(my ip goes here)

(my DSpace site name goes here)

   (I am skipping a bunch of stuff that I didn't change, then further
in the definition, I added)

   

   
   

   

  

   

   

   


I hope this is of some help.
George Kozak
Cornell University

On Tue, Feb 21, 2017 at 12:41 PM, Jeff Mitchell 
wrote:

> Javier,
>
> Nothing in that file.
>
> Jeff
>
>
>
> On Tuesday, February 21, 2017 at 11:38:11 AM UTC-6, Javier Távara wrote:
>>
>> Jeff, take a look in /etc/tomcat7/conf/Catalina/localhost/
>>
>> El martes, 21 de febrero de 2017, 12:33:43 (UTC-5), Jeff Mitchell
>> escribió:
>>>
>>> I am running dspace 5.1 on Debian 7.
>>>
>>> If I look at /etc/tomcat7/server.xml - I don't see anything for context
>>> path. Am I not looking in the right location?
>>>
>>> Jeff
>>>
>>>
>>>
>>> On Tuesday, February 21, 2017 at 11:18:04 AM UTC-6, George Kozak wrote:

 Jeff:

 I don't know if this is helpful, but I had a similar problem when I
 moved our Test instance to a new Development server when I was planning on
 upgrading from DSpace 5.5 to DSpace 6.0.  The Development server was
 running a different version of Tomcat, and I discovered that I needed to
 change how I defined my site in the tomcat conf/server.xml file.

 On my test and production machines, I defined my tomcat root as:
 

 but on my development server that it did not work and created a blank
 page.  I discovered that I had to change the context path by adding a "/"
 on my development server:

 

 This may not be your problem, but you may want to check out how DSpace
 is defined in your tomcat's server.xml file.

 George Kozak
 Cornell University

 On Mon, Feb 20, 2017 at 2:55 PM, Jeff Mitchell  wrote:

> If I am looking at the output correctly Java is listening on 8080 but
> tomcat should be.  Is that right, or do I need to switch something?
>
> If I need to switch something, how would that get changed?
>
> Jeff
>
>
>
> On Monday, February 20, 2017 at 1:47:46 PM UTC-6, Jeff Mitchell wrote:
>>
>> Sorry - Running Debian 7
>>
>> Jeff
>>
>>
>>
>> On Monday, February 20, 2017 at 1:46:02 PM UTC-6, Jeff Mitchell wrote:
>>>
>>> Output:
>>>
>>> tcp6   0  0 127.0.0.1:8005  :::*
>>> LISTEN  2478/java
>>>
>>> tcp6   0  0 :::8009 :::*
>>> LISTEN  2478/java
>>>
>>> tcp6   0  0 :::80   :::*
>>> LISTEN  2573/apache2
>>>
>>> tcp6   0  0 :::8080 :::*
>>> LISTEN  2478/java
>>>
>>>
>>> So you are running Apache HTTP as a proxy? What OS are you running?
 Again, disable the OS firewall to discard it.

 Check if there is something running on port 80.

 You can do
 sudo netstat -plnt | grep ':80'

 You should see httpd.

 https://support.rackspace.com/how-to/checking-listening-port
 s-with-netstat/


 El lunes, 20 de febrero de 2017, 14:35:33 (UTC-5), Jeff Mitchell
 escribió:
>
> It is basically a 404 error but both tomcat and apache are running.
>
> http://essays.wls.wels.net
>
> Looking at the logs now.
>
>
>
> On Monday, February 20, 2017 at 1:31:22 PM UTC-6, Javier Távara
> wrote:
>>
>> What errors are you getting?
>>
>> Check your Tomcat and DSpace logs.
>>
>> El lunes, 20 de febrero de 2017, 14:28:06 (UTC-5), Jeff Mitchell
>> escribió:
>>>
>>> Restoring from backup didn't change anything.  Not sure what the
>>> issue is as it was working on Thursday for sure.
>>>
>> --


>>> --
> You received this message because you are subscribed to the Google
> Groups "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to dspace-tech...@googlegroups.com.
> To post to this group, send email to dspac...@googlegroups.com.
> Visit this group at https://groups.google.com/group/dspace-tech.
> For more options, visit 

Re: [dspace-tech] Re: d space BUILD FAILED see attached document

[Claudia Jürgen]

Hello Mutowongi,

you seem to have an error in
your local.cfg see
https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace/config/local.cfg.EXAMPLE#L31
check your settings of "dspace.dir".
Even for Windows you need to  use forward slashes. So assuming you
created an installation directory at C:\DSpace
the setting would be
dspace.dir=C:/DSpace

Hope this helps

Claudia Jürgen



Am 22.02.2017 um 11:53 schrieb Mutowongi:

error occurred after running ant fresh_install



BUILD FAILED
C:\dspace-6.0-src-release\dspace\target\dspace-installer\build.xml:780:
Failed to copy
C:\dspace-6.0-src-release\dspace\target\dspace-installer\config\dspace.cfg
to C:\Dspace.  \config\dspace.cfg due to java.io.FileNotFoundException
C:\Dspace.  \config\dspace.cfg (The system cannot find the path specified)

Total time: 2 seconds


C:\dspace-6.0-src-release\dspace\target\dspace-installer>C:\dspace-6.0-src-release\dspace\target\dspace-installerC:\dspace-6.0-src-release\dspace\target\dspace-installerC:\dspace-6.0-src-release\dspace\target\dspace-installer



--
Claudia Juergen
Eldorado

Technische Universität Dortmund
Universitätsbibliothek
Vogelpothsweg 76
44227 Dortmund

Tel.: +49 231-755 40 43
Fax: +49 231-755 40 32
claudia.juer...@tu-dortmund.de
www.ub.tu-dortmund.de

Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie ist 
ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für diese 
E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender und 
vernichten Sie diese Mail. Vielen Dank.
Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen 
ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher Schriftform 
(mit eigenhändiger Unterschrift) oder durch Übermittlung eines solchen 
Schriftstücks per Telefax erfolgen.

Important note: The information included in this e-mail is confidential. It is 
solely intended for the recipient. If you are not the intended recipient of 
this e-mail please contact the sender and delete this message. Thank you. 
Without prejudice of e-mail correspondence, our statements are only legally 
binding when they are made in the conventional written form (with personal 
signature) or when such documents are sent by fax.

--
You received this message because you are subscribed to the Google Groups "DSpace 
Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Re: d space i run ant fresh_install on cmd & BUILD FAILED see attached document

[Mutowongi]

On Wednesday, February 22, 2017 at 12:50:47 PM UTC+2, Mutowongi wrote:
>
> BUILD FAILED
> C:\dspace-6.0-src-release\dspace\target\dspace-installer\build.xml:780: 
> Failed to copy 
> C:\dspace-6.0-src-release\dspace\target\dspace-installer\config\dspace.cfg 
> to C:\Dspace.  \config\dspace.cfg due to java.io.FileNotFoundException 
> C:\Dspace.  \config\dspace.cfg (The system cannot find the path specified)
>
> Total time: 2 seconds
>
>
> C:\dspace-6.0-src-release\dspace\target\dspace-installer>C:\dspace-6.0-src-release\dspace\target\dspace-installerC:\dspace-6.0-src-release\dspace\target\dspace-installerC:\dspace-6.0-src-release\dspace\target\dspace-installer
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Re: d space BUILD FAILED see attached document

[Mutowongi]

error occurred after running ant fresh_install
 

> BUILD FAILED
> C:\dspace-6.0-src-release\dspace\target\dspace-installer\build.xml:780: 
> Failed to copy 
> C:\dspace-6.0-src-release\dspace\target\dspace-installer\config\dspace.cfg 
> to C:\Dspace.  \config\dspace.cfg due to java.io.FileNotFoundException 
> C:\Dspace.  \config\dspace.cfg (The system cannot find the path specified)
>
> Total time: 2 seconds
>
>
> C:\dspace-6.0-src-release\dspace\target\dspace-installer>C:\dspace-6.0-src-release\dspace\target\dspace-installerC:\dspace-6.0-src-release\dspace\target\dspace-installerC:\dspace-6.0-src-release\dspace\target\dspace-installer
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] d space BUILD FAILED see attached document

[Mutowongi]

BUILD FAILED
C:\dspace-6.0-src-release\dspace\target\dspace-installer\build.xml:780: 
Failed to copy 
C:\dspace-6.0-src-release\dspace\target\dspace-installer\config\dspace.cfg 
to C:\Dspace.  \config\dspace.cfg due to java.io.FileNotFoundException 
C:\Dspace.  \config\dspace.cfg (The system cannot find the path specified)

Total time: 2 seconds

C:\dspace-6.0-src-release\dspace\target\dspace-installer>C:\dspace-6.0-src-release\dspace\target\dspace-installerC:\dspace-6.0-src-release\dspace\target\dspace-installerC:\dspace-6.0-src-release\dspace\target\dspace-installer

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\Users\Sapes Library>cd 
C:\dspace-6.0-src-release\dspace\target\dspace-installer

C:\dspace-6.0-src-release\dspace\target\dspace-installer>ant fresh_install
Buildfile: C:\dspace-6.0-src-release\dspace\target\dspace-installer\build.xml

init_installation:
[mkdir] Created dir: C:\Dspace.  \bin
[mkdir] Created dir: C:\Dspace.  \config
[mkdir] Created dir: C:\Dspace.  \lib
[mkdir] Created dir: C:\Dspace.  \etc
[mkdir] Created dir: C:\Dspace.  \webapps
[mkdir] Created dir: C:\Dspace.  \triplestore
[mkdir] Created dir: C:\Dspace.  \exports
[mkdir] Created dir: C:\Dspace.  \exports\download
[mkdir] Created dir: C:\Dspace.  \handle-server
[mkdir] Created dir: C:\Dspace.  \log
[mkdir] Created dir: C:\Dspace.  \upload
[mkdir] Created dir: C:\Dspace.  \reports
[mkdir] Created dir: C:\Dspace.  \solr
[mkdir] Created dir: C:\Dspace.  \var
[mkdir] Created dir: C:\Dspace.  \var\oai

prepare_configs:
[mkdir] Created dir: 
C:\dspace-6.0-src-release\dspace\target\dspace-installer\config-temp
 [copy] Copying 157 files to 
C:\dspace-6.0-src-release\dspace\target\dspace-installer\config-temp
 [copy] Copying 1 file to 
C:\dspace-6.0-src-release\dspace\target\dspace-installer\config-temp
 [copy] Copying 1 file to 
C:\dspace-6.0-src-release\dspace\target\dspace-installer\config-temp
 [copy] Copying 16 files to 
C:\dspace-6.0-src-release\dspace\target\dspace-installer\config-temp

init_configs:
 [copy] Copying 159 files to C:\Dspace.  \config
Attempt to copy 
C:\dspace-6.0-src-release\dspace\target\dspace-installer\config-temp\ant.properties
 to C:\Dspace.  \config\ant.properties using NIO Channels failed due to 'failed 
to create the parent directory for C:\Dspace.  \config\ant.properties'.  
Falling back to streams.
 [copy] Failed to copy 
C:\dspace-6.0-src-release\dspace\target\dspace-installer\config-temp\ant.properties
 to C:\Dspace.  \config\ant.properties due to java.io.FileNotFoundException 
C:\Dspace.  \config\ant.properties (The system cannot find the path specified)
Attempt to copy 
C:\dspace-6.0-src-release\dspace\target\dspace-installer\config-temp\config-definition.xml
 to C:\Dspace.  \config\config-definition.xml using NIO Channels failed due to 
'failed to create the parent directory for C:\Dspace.  
\config\config-definition.xml'.  Falling back to streams.
 [copy] Failed to copy 
C:\dspace-6.0-src-release\dspace\target\dspace-installer\config-temp\config-definition.xml
 to C:\Dspace.  \config\config-definition.xml due to 
java.io.FileNotFoundException C:\Dspace.  \config\config-definition.xml (The 
system cannot find the path specified)
Attempt to copy 
C:\dspace-6.0-src-release\dspace\target\dspace-installer\config-temp\controlled-vocabularies\LICENCES
 to C:\Dspace.  \config\controlled-vocabularies\LICENCES using NIO Channels 
failed due to 'C:\Dspace.  \config\controlled-vocabularies\LICENCES (The system 
cannot find the path specified)'.  Falling back to streams.
 [copy] Failed to copy 
C:\dspace-6.0-src-release\dspace\target\dspace-installer\config-temp\controlled-vocabularies\LICENCES
 to C:\Dspace.  \config\controlled-vocabularies\LICENCES due to 
java.io.FileNotFoundException C:\Dspace.  
\config\controlled-vocabularies\LICENCES (The system cannot find the path 
specified)
Attempt to copy 
C:\dspace-6.0-src-release\dspace\target\dspace-installer\config-temp\controlled-vocabularies\controlledvocabulary.xsd
 to C:\Dspace.  \config\controlled-vocabularies\controlledvocabulary.xsd using 
NIO Channels failed due to 'failed to create the parent directory for 
C:\Dspace.  \config\controlled-vocabularies\controlledvocabulary.xsd'.  Falling 
back to streams.
 [copy] Failed to copy 
C:\dspace-6.0-src-release\dspace\target\dspace-installer\config-temp\controlled-vocabularies\controlledvocabulary.xsd
 to C:\Dspace.  

[dspace-tech] Re: REST API DSpace6.0 update bitstream contents (http 500)

[Elie Abu Haydar]

I faced the exact same issue and i think the problem is in the module 
dspace-rest, class org.dspace.rest.BitstreamResource, method 
updateBitstreamData which handles requests to update the bitstream data.

context.complete(); should be called 
after bitstreamStorageService.store(context, dspaceBitstream, is);

I think this is mistakenly removed and should be restored.

You can either do the change by overriding this particular class by using 
maven overlays or fix it in the module but don't forget to set the module 
to snapshot and update the related poms.
This change requires building dspace, updating it, and restarting the 
servlet container.

Hope this helps,
Elie Abu Haydar

On Monday, February 20, 2017 at 11:39:38 AM UTC+2, Sebastijan Elbl wrote:
>
> I'm trying to update the content of bitstream via REST API but I get : 
> HTTP 500 – Internal Server Error
>
>
> CURL:
>
> post new BITSTREAM:.
> curl --cookie "JSESSIONID=EDEC553C67C1AD18BDF4AC4A45EE6D0F" -H 
> "accept:application/json" -H "Content-Type: application/json" -X POST
>
> "localhost:8080/rest/items/d83bdd1c-553d-4529-9bcf-a783637befc9/bitstreams?name=test=testing"
>  
> -T "test.txt"
> result: http 200
>
>
> trying update previus BITSTREAM:
>
>
> curl --cookie "JSESSIONID=EDEC553C67C1AD18BDF4AC4A45EE6D0F" -H 
> "accept:application/json" -H "Content-Type: application/json" -X PUT
> "localhost:8080/rest/bitstreams/a8fbf6d5-9984-4b0d-8f76-cfa339e46f8d/data"
> -T "test2.txt
>
> result: http 500
>
>
> From dspace log:
> INFO org.dspace.content.BitstreamServiceImpl @ 
> *us...@example.com::update_bitstream:bitstream_id=a8fbf6d5-9984-4b0d-8f76-cfa339e46f8d*
>  
> 
>
> ERROR org.dspace.rest.Resource @ Something get wrong. Aborting context in 
> finally statement.
>
>
>
> From REST API documentation:
>
> PUT /bitstreams/{bitstream id}/data - Update the contents of the specified 
> bitstream.
>
>
> REST API is working otherwise, in DSpace 5.x there was no problem with 
> updating bitstream contents.
>
> Anyone can help me?
>
> Thanks
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Issue in PostgreSQL 9.6 Restore Data failed ('ascii' codec can't decode byte 0xfa in position 2: ordinal not in range(128))

[helix84]

OK, that confirms your issue is with PgAdmin, not with DSpace.

I suggest that you try unpacking the sql and feed it to PgAdmin unpacked,
but in general I can't help you with PgAdmin.


Regards,
~~helix84

Compulsory reading: DSpace Mailing List Etiquette
https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette



On Wed, Feb 22, 2017 at 10:44 AM, Bhavesh Patel 
wrote:

> Thanks for your email but while restore through pgAdmin it's shows error
> message (please see the attached screen sort)
>
>
>
> Thanks & Regards,
> *Bhavesh R. Patel*
>
> *"Learning is a never ending process"*
>
>
> On Wed, Feb 22, 2017 at 2:27 PM, helix84  wrote:
>
>> Which exact command is throwing that error message?
>>
>> That's a message that comes from a Python program, not a Java program. I
>> wouldn't expect to find it in DSpace.
>>
>>
>> Regards,
>> ~~helix84
>>
>> Compulsory reading: DSpace Mailing List Etiquette
>> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>>
>>
>>
>> On Wed, Feb 22, 2017 at 9:53 AM, Bhavesh Patel > > wrote:
>>
>>> Dear All,
>>>
>>> We have installed DSpace6 into CentOS7, It's installed successfully with
>>> default installation but when we are create new database and then import
>>> existing database (previous version database) it throw error like
>>>
>>>
>>> *"'ascii' codec can't decode byte 0xfa in position 2: ordinal not in
>>> range(128)"*
>>> we have exported .tar.gz file from pgAdmin3 and try to import that file
>>> into pgAdmin4.
>>>
>>> we have also try for pgcrypto for that new database.
>>>
>>> *dspace6=# CREATE EXTENSION pgcrypto;CREATE EXTENSION*
>>>
>>> Please help to resolve the issue.
>>>
>>>
>>> Thanks & Regards,
>>> *Bhavesh R. Patel*
>>>
>>> *"Learning is a never ending process"*
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "DSpace Technical Support" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to dspace-tech+unsubscr...@googlegroups.com.
>>> To post to this group, send email to dspace-tech@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/dspace-tech.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "DSpace Technical Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to dspace-tech+unsubscr...@googlegroups.com.
>> To post to this group, send email to dspace-tech@googlegroups.com.
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] dspace not picking up Shibboleth attributes to authenticate

[Tom Desair]

Hi Julie,

The key here is the Apache configuration section

> 
>  AuthType shibboleth
>  ShibRequireSession On
>  Require valid-user
> 


This tells the Apache Shibboleth daemon to require a Shibboleth session
when visiting "/shibboleth-login" and to provide all mapped attributes to
the Tomcat application server. For all other URL endpoints, Shibboleth will
not forward the attributes.

However, your DSpace instance is not running under root but under
"/dspace". I conclude this from the fact that you receive a redirect to "
https://test-dspace.xxx.net//dspace/shibboleth-login;. This means you have
to adjust the Apache configuration to secure that location instead.

So your problem should be solved when you change "" to "". Can you
please try that and let me know if that works?

Best regards,
Tom

[image: logo] Tom Desair
250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586
Esperantolaan 4, Heverlee 3001, Belgium
www.atmire.com


2017-02-21 23:51 GMT+01:00 J Bell :

>
> We are moving to Shibboleth and I am having a problem figuring out where
> my configuration is not set correctly to allow the actual authentication to
> occur.  This is working in other instances we have running - only dSpace
>  is not yet configured properly.   Would anyone have some input as to where
> I have wandered into the weeds?
>
> Notes about our configuration:
>
> I have the IDP and my local *SP  (shibboleth 2.5.2)  * configured and
> talking as I would expect.
>
> We are using *mod_ajp*  for the proxy  (this did not work under regular
> proxy either - I have tried both ways).  My *shibboleth2.xml* configuration
> looks like this:
>
> https://xxx.xxx.net/shibboleth;
>  id="default" policyId="default"
>  REMOTE_USER="eppn persistent-id targeted-id"
>  signing="false" encryption="false"
>  attributePrefix="AJP_">
>
>checkAddress="false" handlerSSL="false"
> cookieProps="https">
>
> https://alpha.signin.xxx.edu/idp/shibboleth;
> Location="/Login"
>  discoveryProtocol="SAMLDS" discoveryURL="https://ds.
> example.org/DS/WAYF">
>   SAML2 SAML1
> 
>
>
>
> My *attribute-map.xml*  has the following attributes mapped - which come
> back as expected:
>
>  
> 
> 
> 
> 
> 
>
>
>
> */Shibboleth.sso/Session *returns this:
>
>
> Miscellaneous
> Session Expiration (barring inactivity): 476 minute(s)
> Client Address: xxx.xxx.xxx.xxx
> SSO Protocol: urn:oasis:names:tc:SAML:2.0:protocol
> Identity Provider: https://alpha.signin.xxx.edu/idp/shibboleth
> Authentication Time: 2017-02-20T17:31:43.925Z
> Authentication Context Class: urn:oasis:names:tc:SAML:2.0:ac:classes:
> PasswordProtectedTransport
> Authentication Context Decl: (none)
>
> Attributes
> cn: jbell
> displayName: Julie Bell
> email: jb...@xxx.edu
> givenName: Julie
> ksuPersonWildcatId: 
> sn: Bell
> telephoneNumber: x
> uid: jbell
>
>
> After proper authentication the service is returned to:
>
> https://test-dspace.xxx.net//dspace/shibboleth-login
>
> and:
> Authentication Failed
>
> The* dspace log *responds with this:
>
> 2017-02-21 19:42:04,972 INFO  
> org.dspace.app.xmlui.aspect.artifactbrowser.CommunityBrowser
> @ anonymous:session_id=DDFBE06E3003021B702DF0A1310B48
> 16:ip_addr=xxx.xxx.xxx.xxx:view_community_list:
> 2017-02-21 19:42:04,973 INFO  
> org.dspace.app.xmlui.aspect.discovery.SidebarFacetsTransformer
> @ facets for scope, null: 3
> 2017-02-21 19:42:05,677 INFO  
> org.dspace.app.xmlui.aspect.artifactbrowser.CommunityBrowser
> @ anonymous:session_id=DDFBE06E3003021B702DF0A1310B48
> 16:ip_addr=xxx.xxx.xxx.xxx:view_community_list:
> 2017-02-21 19:42:05,678 INFO  
> org.dspace.app.xmlui.aspect.discovery.SidebarFacetsTransformer
> @ facets for scope, null: 3
> 2017-02-21 19:42:27,872 ERROR org.dspace.authenticate.ShibAuthentication
> @ Shibboleth authentication was not able to find a NetId, Email, or Tomcat
> Remote user for which to indentify a user from.
> 2017-02-21 19:42:27,872 ERROR org.dspace.authenticate.ShibAuthentication
> @ Unable to register new eperson because we are unable to find an email
> address along with first and last name for the user.
>   NetId Header: 'null'='null' (Optional)
>   Email Header: 'email'='null'
>   First Name Header: 'givenName'='null'
>   Last Name Header: 'sn'='null'
> 2017-02-21 19:42:27,872 INFO  org.dspace.app.xmlui.utils.AuthenticationUtil
> @ anonymous:session_id=01CF256229E776009AE83845CF4341
> A2:ip_addr=xxx.xxx.xxx.xxx:failed_login:email=null, realm=null, result=4
> 2017-02-21 19:42:28,444 INFO  
> org.dspace.app.xmlui.aspect.artifactbrowser.CommunityBrowser
> @ anonymous:session_id=01CF256229E776009AE83845CF4341
> A2:ip_addr=xxx.xxx.xxx.xxx:view_community_list:
> 2017-02-21