[dspace-tech] Re: Eperson.java Dspace 5.6

[Mark Wood]

The only cases where s="m.text_value" are 'case LANGUAGE' and 'default'.  
In each of those, 't' will be nonempty and so the first query() call should 
be used.  In that query, 'm' is defined.  I think we'll need to see some of 
the log surrounding the internal error, so that we know what kind of error 
we are looking at.  You should be more concerned about sending too little 
log, than too much.

-- 
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] Error running cleanup task in DSpace 5.x

[Mark Wood]

On Tuesday, April 25, 2017 at 11:28:05 AM UTC-4, Alan Orth wrote:
>
> Hello, a small update.
>
> It took me a few days, but I ran the cleanup task over and over and waited 
> for it to crash, each time adding the conflicting bitstream ID to a long 
> list of IDs to delete (70 in total, in a SQL query like in my previous mail 
> in this thread). Once the conflicts in the database were resolved, I was 
> finally able to run the task from start to finish successfully. I never 
> knew this task was failing, so I suspect it's been silently failing for 
> years—now that it finally ran, it cleared 30,000 files (7GB or so) from the 
> assetstore!
>
> To make a long story short: manually check your cron jobs (and add 
> logging) from time to time. Thanks for the help, Claudia.
>
>
You might find  https://jira.duraspace.org/browse/DS-3074 interesting.

-- 
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: Downloads.

[Mark Wood]

On Tuesday, April 4, 2017 at 11:10:58 PM UTC-4, Mark Lamont wrote:
>
> I'm am in the process of setting up an information repository with DSpace 
> and am wondering if there is a way to make files available to users without 
> them being downloadable? Most of what I've submitted needs to be downloaded 
> to be viewed-or listened to as the case may be. We would like to limit some 
> of the material to members of our organization so would like to be able to 
> make some files non-downloadable. Is there a way to do this with this 
> software even though it is open access. 
>


What you asked is not possible for any web service, since there is no way 
for the service to know what the client will do with a file that is sent to 
it.  As others have described, the only thing you can do is to grant READ 
permission to some logged-in users and deny any access by all others.

-- 
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: dspace 5.6 rest api

[Mark Wood]

On Monday, April 3, 2017 at 4:12:42 PM UTC-4, Ricardo Campos wrote:
>
> Hi.
>  
>
>> Some further information on the problem.
>>
>
> I configured DSpace to give me some debug information and I found some 
> errors, all related to same thing:
>
> 2017-04-03 16:54:57,749 ERROR org.dspace.statistics.SolrLogger @ Failed 
> DNS Lookup for IP:0:0:0:0:0:0:0:1
>
> I reckon if this error is responsible for the problems and I cannot figure 
> out what cause these messages.
>
>

0:0:0:0:0:0:0:1 (sometimes expressed as "::1") is the IPv6 loopback address 
of the local host. o.d.statistics.SolrLogger is the class which sends 
events to Solr for calculating usage statistics.  The first thing I would 
suppose is that your 'curl' command connected to localhost via IPv6 and 
that SolrLogger is trying to back-resolve that address to a name but 
cannot.  That would suggest incomplete configuration of IPv6 name 
resolution:  the host can map 'localhost' to '::1' (so 'curl' succeeded) 
but cannot map "::1' to 'localhost' (so SolrLogger failed).  This would 
cause DSpace to fail to record object usages requested by the local host 
through IPv6, but I doubt that that is the cause of the null 
parentCommunity.

-- 
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: Adding e-people into groups automatically

[Mark Wood]

On Tuesday, March 28, 2017 at 5:57:05 AM UTC-4, Layale Bassil wrote:
>
> I have seen this question on the forums and the answer to it was to use 
> LDAP authentication which we are already using and then edit the 
> authentication-ldap.cfg file and set the logins.specialgroup = A property 
> and give it the name of the group created (assume = A).
>
>  
>
> I did this and restarted tomcat but when I login I am not being added to 
> group A. If a user belongs to another group wont this apply to him when he 
> logs in?
>


How did you determine that this is not working?  You cannot make that 
determination by inspecting the list of members of group A.

Special groups are granted to user *sessions*, not user *accounts*.  
Special-group membership is not permanent and is not recorded anywhere in 
the database.  You can only discover it through the product's behavior or 
reading the authentication mechanism's configuration.  If you request 
access to an object, and access is granted, and access could only be 
granted to a member of group A, and you are not listed among the members of 
group A or any group that is a member of group A (directly or indirectly), 
then DSpace is configured to grant you special membership in group A.

-- 
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: i'm trying restore an community with dspace packager -r -s -k -a -t AIP

[Mark Wood]

I answered this in 
http://stackoverflow.com/questions/42982637/im-trying-restore-an-community-with-dspace-packager
 
but for the list, a quick summary:  PREMISCrosswalk can't deal with the 
number 2237780334 because it uses an int rather than a long to compare the 
declared size with the long returned by Bitstream.getSize(), and that 
number is greater than 2**31 - 1.  It's a bug.

-- 
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: Logout issue

[Mark Wood]

On Thursday, March 16, 2017 at 6:13:16 AM UTC-4, admin wrote:
>
> Hello,
>
> I use DSpace 6, tomcat 8.5.4, and experience http 302 issue upon logout.
> I found this entry: 
> https://groups.google.com/forum/#!topic/dspace-community/EHEpYhIcYCE but 
> the solution didn't help, or I am doing something wrong – I applied 
> "useRelativeRedirects" to xmlui context.
>
>  
I think this might be the same problem we had, which led to 
https://jira.duraspace.org/browse/DS-3505

-- 
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] Auto-assign e-person to a group upon registration

[Mark Wood]

But please note that "special groups" are assigned to *user sessions*, not 
to epersons.  Special group membership lasts until logout and is not 
recorded anywhere.  If you need for a new account to be permanently a 
member of a group, so that this membership affects what others do, a 
special group won't serve, and you'll have to manually assign permanent 
group membership.  We probably should have called them "session roles" 
rather than "special groups" since there is nothing special about the group.

One thing that isn't affected by special group membership is actions based 
on group membership which take place outside of a member's session, such as 
the emails that are sent to members of an editorial group during submission 
workflow.

If a user only needs group membership within the scope of his own sessions, 
then special groups should serve well.

-- 
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: delete on table "eperson" violates foreign key constraint

[Mark Wood]

Well, I would say that it's doing what it is supposed to, by preventing us 
from breaking one or more resource policies which would otherwise be 
referring to a nonexistent object.  But that's not very interesting if you 
need to delete an eperson.  DO you need to delete the account, or would it 
be sufficient to disable it?  An administrator can set an account unable to 
login.

To actually delete the account, you'll first need to find the policies 
which refer directly to this eperson #12, find the objects to which those 
policies apply, and adjust their policy sets so that they are accessible as 
needed but no longer refer to the eperson.  [Pokes around in a 5.2 
instance's database]  Actually I think it likely that a policy bound to an 
EPerson rather than a group indicates that it is associated with a 
workspace or workflow item, probably the latter.  I found such an eperson, 
and on the (XMLUI) Administrative | People | this-eperson page I see "This 
eperson is unable to be deleted because of the following constraint(s): 
eperson has submitted one or more items, and eperson has a workflow task 
awaiting their attention."  I haven't found a nice GUI way to track down 
pending submissions by user, but going into the database and executing 
"SELECT * FROM resourcepolicy WHERE eperson_id = 12" should give you a 
manageable list of objects to inspect.

"List pending submissions by this user" might be a welcome addition to the 
user interface

-- 
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: Batch uploading bitstreams before adding metadata

[Mark Wood]

The spreadsheet is not necessary; lots of people use that method because 
they are familiar with spreadsheet tools.  The important thing is that you 
somehow create the archive format that DSpace will try to read.

It shouldn't be too difficult to write a script that would, for example:  
walk a directory of PDFs, use pdftk to extract some minimal metadata, and 
lay out a tree of directories in Simple Archive Format that can be read 
with 'bin/dspace import'.  The content can be organized in any way you 
wish.  If you want each PDF to be a separate item, have your script create 
one subdirectory per PDF with one content file in it.

DSpace does demand a few metadata fields.  I think you'll need to provide 
at least a title.  If necessary, you should be able to edit those later. 
but you'll need to provide *some* value.  You could just generate serial 
numbers for temporary titles:  "Title 1", "Title 2"...; or use the filename 
as the title.

If you'd rather use one of the Packager formats, again it really doesn't 
matter how you proceed so long as you end up with a format that the 
Packager can read.  Again, if you describe each content file within a 
separate item, that's what you'll get.

-- 
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: Dspace Handle Server error

[Mark Wood]

It seems that the handle service is not opening sockets.  If it isn't 
logging any errors at startup, you may have to run it in a system call 
tracer (strace, truss, whatever you have) and see what happens when it 
tries to open these sockets.

Silly question:  the handle service *is* still configured to listen on 
those ports, yes?

-- 
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: PSA: Security issue in Ruby version manager (rvm)

[Mark Wood]

On Wednesday, February 15, 2017 at 8:03:06 AM UTC-5, Alan Orth wrote:
>
> Hello,
>
> I just thought I'd send word of several security issues in Ruby version 
> manager (rvm). If you're using Mirage 2 with DSpace 4, 5, or 6 you most 
> likely have rvm installed and should upgrade it at your soonest convenience 
> using the following command:
>
> $ rvm get stable
>
>
Here, I got errors saying "Could not download rvm-installer".  I had to 
install it as if I did not have RVM yet -- that worked.  BUT:  after 
verifying that I am now running 1.29, "rvm get stable" *still* fails in the 
same way.  There's something going on with replaced SSL certificates, but I 
haven't found a clear explanation yet. 

-- 
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: ant fresh_install vs postgres

[Mark Wood]

On Monday, January 30, 2017 at 7:16:53 PM UTC-5, Walter Rutherford wrote:
>
> I think that all makes sense. If I'm logging in from user 'dspace' to 
>  'dspace' in posgres it uses
> the peer rule and lets me in without a password. Any other user would have 
> to be accessing
> their own user/database.
> So, how should the pg_hba.conf file be configured to allow any user to 
> access the DSpace
> database via a webpage and Tomcat?
>
>
You need an entry that matches the db.* settings in dspace.cfg or 
local.cfg.  db.url specifies the DBMS hostname, db.username the database 
user, and db.password the database user's password.  If your db.url is 
'jdbc:postgresql://localhost:5432/dspace', db.username is 'dspace', and 
db.password is 'secret', then your existing 'host dspace dspace...' rule 
should work.  The DBMS cluster would have to be on the local host and have 
to have a user 'dspace' with the password 'secret' for this to work.

The PostgreSQL JDBC driver always uses a TCP connection, not a local 
socket, so only 'host' or 'hostssl' rules will apply to DSpace.  The 'psql' 
tool will by default use the local socket, so only 'local' rules will apply 
to it unless you tell it otherwise using the --host option.

-- 
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] 6.0 upgrade

[Mark Wood]

I've seen cases where the relevant information was in another Tomcat log.  
Here, I also get logs named localhost-$DATE.log.  (Not the same as 
localhost_access-$DATE.log)  I would look around in Tomcat's log directory 
to see if there is anything else covering the same time span, and what 
might be found in it.

-- 
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: SAF and Metadata Export Ordering

[Mark Wood]

It's probably ordered by whatever the DBMS finds convenient.  In that case 
it may not even be consistently ordered as items are added to a 
collection.  A relational query doesn't guarantee any particular order; the 
DBMS is free to arrange and re-arrange its own storage in 
implementation-dependent ways.  I imagine that nobody ever thought of a 
reason to pay the cost of sorting by adding ORDER BY to the query that 
produces the stream of items.

Are you asking out of sheer curiosity, or have you discovered a way in 
which the order of exports can be significant?

-- 
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: Question about DSpace code and version control of local mods

[Mark Wood]

We used to keep our local DSpace in SVN alongside a copy of stock code, to 
make it easy to keep our mod.s updated.  Some time ago we switched to git, 
and now keep local DSpace and stock in a local instance of GitHub 
Enterprise.  I find SCM tools to be much easier to work with than the 
overlay stuff.

-- 
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: Tomcat 8 versus Tomcat 7

[Mark Wood]

On my development box I'm currently using Tomcat 8.0 with 5x and 6.  We're 
still on 7.0 in production (5x) but I want to move to 8 when I can find the 
time.

The only issue I can recall is that Tomcat 8's classloader setup is much 
more finicky, and that collides with the way I like to deploy webapp.s.  I 
inject a ready-made database connection pool via JNDI, and if I'm not 
careful to delete the database driver JAR from each DSpace webapp. then 8 
will complain that it can't find the driver (because there's one in 
Tomcat's own classloader, which supplies the pool, and another in the 
webapp's classloader, and they aren't the same 'Class'es even though they 
are loaded from identical files).  I reckon that most sites won't have that 
problem.  When I have some time, I mean to create an option to leave the 
database driver JAR out of the webapps during assembly.

-- 
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: [dspace-community] Re: PostgreSQL question in upgrading to DSpace 6.0

[Mark Wood]

On Monday, November 28, 2016 at 8:43:12 AM UTC-5, wangyo wrote:
>
> Hi Mark,
>
> > You can change that last record from "md5" (which requires a password) 
> to "trust"...
>
> I did that.
>
> Then I restarted postgresql-9.5, and ran the cammond as follows:
>
> [root@dr data]# /usr/pgsql-9.5/bin/psql -U postgres -f 
> /dspace-backup/pg.out postgres
>
> The output as following:
>
> SET
> SET
> SET
> CREATE ROLE
> ALTER ROLE
> psql:/dspace-backup/pg.out:16: ERROR:  role "postgres" already exists 
> ALTER ROLE
> CREATE DATABASE
> REVOKE
> REVOKE
> GRANT
> GRANT
> You are now connected to database "dspace" as user "postgres".
> SET
> SET
> SET
> SET
> SET
> SET
> CREATE EXTENSION
> COMMENT
> ...
>
> ALTER TABLE
> COPY 1710
>  setval
> 
>1710
> (1 row)
>  ...
>
>
>
> It keeps going like this, and the last several lines:
>
> GRANT
> You are now connected to database "template1" as user "postgres".
> SET
> SET
> SET
> SET
> SET
> SET
> COMMENT
> CREATE EXTENSION
> COMMENT
> REVOKE
> REVOKE
> GRANT
> GRANT
>
>
> Does that mean the restore is successful?
>
>
Yes, that appears to be successful.  The error on line 16 is to be 
expected:  the DBMS already has a superuser account defined, so it cannot 
be created again.  That should not be a problem. 

-- 
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: Handle server in separate machine

[Mark Wood]

See https://github.com/DSpace/Remote-Handle-Resolver for one approach.

-- 
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: Sub-communities and collections not sorted alphabetically in the new version (6.0-rc2-SNAPSHOP)

[Mark Wood]

This was discussed today in the DSpace developers' meeting.  It looks like 
a bug, and the recommendation is to submit a Jira issue so that it stays on 
the radar.

-- 
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: PostgreSQL question in upgrading to DSpace 6.0

[Mark Wood]

On Wednesday, November 23, 2016 at 10:17:31 AM UTC-5, wangyo wrote:
>
> Dear all,
>
> One of the DSpace 6.0 pre-requisites is PostgreSQL 9.4 or above. My 
> current DSpace 5.1 installation has PostgreSQL 9.2. So I have to upgrade my 
> PostgreSQL first in order to upgrade to DSpace 6.0.  My OS is RHEL 7.
>
> I installed PostgreSQL 9.5 by using rpm and yum. The installed directory 
> is /usr/pgsql-9.5 (the default). My PostgreSQL 9.2 is at /usr/share/pgsql. 
>
> Before I installed PostgreSQL 9.5, I used pg_dumpall to backup the 
> PostgreSQL 9.2 to a file named pg.out. After I installed PostgreSQL 9.5, I 
> tried to restore my backup file by using psql like this:
>
> # /usr/pgsql-9.5/bin/psql -f /dspace-backup/pg.out postgres
> Password:
>
> I got the following error:
>
> psql: FATAL:  password authentication failed for user "root"
>
> I tried all different passwords, but the same error every time.
>
> What is the cause for this error? How do I solve it?
>

That command does not specify a database user, so psql assumes that the 
database user has the same name as the OS user who is running it.  From the 
prompt, I assume that this was done as 'root' so psql tried to login *to 
the database* as 'root', which is probably not a known database user.  The 
DBMS user may be specified by adding '-U USER or '--username=USER' (where 
USER is some known DBMS username), but on a freshly installed instance you 
probably don't have any way of knowing the only defined user's password.

If you run the same command as the OS user which runs the DBMS (probably 
some variant of 'postgres') then you would be assuming the identity of the 
DBMS superuser and should be able to restore the dump without a DBMS 
password.  Supposing the DBMS owner account to be 'postgres', I would (as 
root) 'su postgres' and run the command.  (The dump file must be readable 
by that account.)  You can probably accomplish the same using 'sudo' but I 
don't know its specifics.
 

> I did two things before doing the above restore procedure: 
>
> 1. Edit /var/lib/pgsql/data/9.5/postgresql.conf 
> Uncomment the line: listen_addresses = ‘localhost’
>
> 2. Edit /var/lib/pgsql/data/9.5/pg_hba.conf
> Add the line: host dspace dspace 127.0.0.1 255.255.255.255 md5
> Change: “local all all  peer” to “local all all  md5” 
>

You can change that last record from "md5" (which requires a password) to 
"trust" (which does not require any sort of authentication).  DO NOT LEAVE 
IT SET TO "trust" AFTER RESTORING THE DUMP.  You will need to restart the 
DBMS instance after changing the configuration.  You will still have to 
connect to the DBMS as a known user, and a freshly installed instance 
should have only one:  the DBMS superuser.  You would need to specify -U or 
--username=.

I recommend reading at least some of 
https://www.postgresql.org/docs/9.5/static/admin.html to learn the basics 
of running PostgreSQL.
 

> My other questions are: 
>
> Do I have to backup my PostgreSQL 9.2 and restore it to PostgreSQL 9.5?
>

That is the safest way to upgrade PostgreSQL.
 
 | Or rather, do I have to upgrade to PostgreSQL 9.4 or above?

 An older version of PostgreSQL *may* be sufficient, but DSpace has not 
been tested with it.  According to 
https://www.postgresql.org/support/versioning/ support for 9.2 will end in 
about ten months, so it is about time to upgrade anyway.

-- 
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: Help with setting up virus scan curation task

[Mark Wood]

It's trying to send an email (UIUtil.sendAlert()), and it looks like there 
is something funny about the current user's EPerson, or at least the 
in-memory copy of it.  This code path definitely needs more logging.

-- 
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] problem user dspace

[Mark Wood]

On Monday, November 7, 2016 at 2:16:06 PM UTC-5, hoska...@gmail.com wrote:
>
> thanks for your reply
>
> in my system tomcat run under user tomcat8. i have not changed this.
> i set  the dspace's installation directory owner to user tomcat8. (Chown 
> -R tomcat8:tomcat8 /opt/dspace)
> i afraid for security problems: the database's password is present in 
> dspace.cfg file
> what are the rights permssions that should be set for dspace's 
> configuration directory.
>

You must trust your Servlet container (Tomcat):  it is the process that 
runs DSpace, and thus it must have access to DSpace's configuration.  No 
other user needs any access, so config/dspace.cfg's mode can be 400 or 600 
if you wish.  The DSpace configuration is outside of any webapp. directory 
tree and should not be visible, or even addressable, through Tomcat.

-- 
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] problem user dspace

[Mark Wood]

You should not have two users "dspace" and "tomcat"!

If Tomcat is run by a user named "fred" then the installed DSpace files and 
directories should be owned by user "fred".  It is that simple.  Whatever 
user owns Tomcat should own DSpace too.  They are not two separate 
processes.

If Tomcat is already installed for other purposes, just arrange for DSpace 
to be owned by the account that was already established for Tomcat.

The presence of this "dspace" user in our documentation is a source of 
endless confusion and I wish that it had never been mentioned.

-- 
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] DSpace 6.0 Release Candidate #4 is available now. 6.0 final coming soon.

[Mark Wood]

The fourth release candidate of 6.0 is now available for download and 
testing. 6.0-RC4 (Release Candidate #4) is a pre-release of 6.0, and we 
hope that the 6.0 final release will follow closely in its footsteps. 


We'd appreciate additional testers to help us verify no additional major 
bugs or issues exist in the 6.0 codebase. Over the last few months, our 
team of volunteer developers has been diligently resolving known major 
issues that stand in the way of a 6.0 final release. We believe the 6.0 
release is nearly production-ready, but could use your help in verifying 
there's nothing we've overlooked.

   - Download 6.0-RC4: 
   https://github.com/DSpace/DSpace/releases/tag/dspace-6.0-rc4 
   
   - You can also test this pre-release on our Demo site at 
   http://demo.dspace.org/
   - 6.0 Release Notes are available at: 
   https://wiki.duraspace.org/display/DSDOC6x/Release+Notes
   - Hints on testing this release are still available on our 6.0 Testathon 
   page: 
   https://wiki.duraspace.org/display/DSPACE/DSpace+Release+6.0+Testathon+Page
   - XMLUI Test Plan: http://bit.ly/xmlui-test-plan
  - JSPUI Test Plan: http://bit.ly/jspui-test-plan
  - A list of remaining 6.0 "known issues" is available at 
   
https://wiki.duraspace.org/display/DSPACE/DSpace+Release+6.0+Status#DSpaceRelease6.0Status-TicketstoResolve
   
Assuming our final tests validate the stability of 6.0-RC4, we anticipate 
that the 6.0 final release will be made available within the next week or 
so (i.e. mid-to-late October).

If you notice any bugs or issues with 6.0-RC4, please report them 
immediately to our issue tracker (https://jira.duraspace.org/browse/DS).  
As always, we are also available to answer questions on our DSpace Tech 
Support list (https://groups.google.com/d/forum/dspace-tech) or #dspace IRC 
(https://wiki.duraspace.org/display/DSPACE/IRC).

Thanks!


-- 

Mark H. Wood
Lead Technology Analyst

University Library
Indiana University - Purdue University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-0749
www.ulib.iupui.edu

-- 
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: Assetstore Size limitation

[Mark Wood]

The only limitation I can think of in DSpace itself is the size of the 
unique identifier by which a bitstream is retrieved.  In DSpace 6, that's a 
UUID, which is a 128-bit number.  In v5 and earlier it was a Java 'int', 
which is *only* 32 bits signed (so, can identify 2 billion bitstreams).

The OS filesystem that holds the bitstreams will have its own limits.  
Contemporary filesystem designs have limits on the order of exabytes, and 
billions to quintillions of files.  You may need to do some tuning of your 
assetstore filesystem(s) to even approach those limits, though.

I think it most likely that you'll first hit limits of filesystem 
*performance*, and particularly of backup performance.  And the answer to 
many performance questions is "keep measuring regularly and react to signs 
of significant deterioration."

I find backup of large services particularly worrisome.  We need ways to do 
backup smarter, not just faster.  That's true of everything, not just 
DSpace.

-- 
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: db password question

[Mark Wood]

In DSpace 6, local.cfg is read using Apache Commons Configuration, so see 
https://commons.apache.org/proper/commons-configuration/userguide/howto_properties.html.
  
In short:  you could escape the '#' as '\#', and might need to if this were 
read using java.util.Properties, but it appears that that may not be 
necessary when using PropertiesConfiguration.  What happens when you use a 
plain '#'?

-- 
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: IPV6?

[Mark Wood]

We've been running DSpace from v1.5x through v5.2 with both v4 and v6 
addresses for longer than I can recall.  It works well.  We run it behind 
Apache HTTPD 2.4 via mod-proxy-ajp, so Tomcat 7 only has to deal with the 
local HTTPD, but I'm not aware of any particular IPv6 problems in Tomcat.

>

-- 
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: Dspace on WebSphere

[Mark Wood]

I have never heard of anyone trying DSpace on WebSphere.  I can't think of 
any reason why it *cannot* work.  But JEE provides a lot more 
infrastructure than DSpace is used to, and you may see collisions between 
JARs provided by the container and those packaged with DSpace.  That was my 
experience when I very briefly experimented with running DSpace on 
Glassfish.

If you proceed, please let us know what problems you run into.

-- 
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: Request Copy of Document, but its too big for the mailserver...

[Mark Wood]

On Tuesday, August 9, 2016 at 5:34:13 PM UTC-4, Anton Angelo wrote:
>
> If a client wants to release a copy of a document, but it is too large for 
> our puny University mail server, they get the following error:
>
>  
>
> "552 5.3.4 Error writing message - message size exceeds the size limit of 
> 40960 blocks computed for this transaction".
>
>  
>
> I’d like to change that to something like “Please get in touch with the IR 
> admins”.  I can hunt this message down in the source, but is there anything 
> I should be aware of as I do that?
>
>
>
That looks like a message from the mail server itself.  DSpace is probably 
just passing it back as-is.  But you might find the place where the sending 
is done, detect failure, and wrap the MTA's message in something more 
helpful.

Probably you should wrap try/catch around the Transport.send(message) call 
at the end of org.dspace.core.Email.send(), catching MessagingException, 
and throw a new exception that wraps it, providing an appropriate message.

(The "552 5.3.4" bit is what makes me think that that is an MTA message.)

--
Mark H. Wood
Lead Technology Analyst
 
University Library
Indiana University - Purdue University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-0749
www.ulib.iupui.edu

-- 
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: installation failed of Dspace in Ubuntu

[Mark Wood]

On Friday, July 22, 2016 at 11:47:03 PM UTC-4, Souradip Banerjee wrote:
>
>  [java] 2016-07-23 09:15:09,647 INFO  
> org.dspace.services.caching.CachingServiceImpl @ destroy()
>

Notice that in this very first message that you report, DSpace is already 
shutting down.  The error had already happened.  We need to see further up 
the log in order to know what failed.  Ant logs hundreds of lines during an 
install, and the information needed is often nowhere near the end of the 
log.
 

>  [java] 2016-07-23 09:15:09,650 INFO  
> org.springframework.cache.ehcache.EhCacheManagerFactoryBean @ Shutting down 
> EhCache CacheManager
>  [java] 2016-07-23 09:15:09,651 INFO  
> org.dspace.services.sessions.SessionRequestServiceImpl @ shutdown
>  [java] 2016-07-23 09:15:09,652 WARN  
> org.dspace.services.sessions.SessionRequestServiceImpl @ Request 
> interceptor 
> (org.dspace.services.events.SystemEventService$EventRequestInterceptor@24a16b5)
>  
> failed to execute on end (request-114-1469245509252): null
>  [java] 2016-07-23 09:15:09,664 INFO  
> org.dspace.servicemanager.spring.SpringServiceManager @ Spring Service 
> Manager Shutdown...
>  [java] 2016-07-23 09:15:09,664 INFO  
> org.dspace.servicemanager.DSpaceServiceManager @ Shutdown DSpace core 
> service manager
>  [java] 2016-07-23 09:15:09,664 INFO  
> org.dspace.servicemanager.DSpaceKernelImpl @ DSpace kernel shutdown 
> completed and unregistered MBean: 
> org.dspace:name=b213b280-fd7f-443d-98dc-f921e369dc89,type=DSpaceKernel
>
> BUILD FAILED
> /dspace/Dspace/dspace/target/dspace-installer/build.xml:802: Java 
> returned: 1
>
 
This is helpful.  IF you are installing the current development version of 
DSpace, then that line is invoking the database schema migration tool.  
That would indicate some problem with the database.  It could be a mismatch 
of credentials between the DSpace configuration and the DBMS.  But it would 
be helpful if you would tell us what version of DSpace you are installing, 
so that we can be certain that we are reading the same version of the file 
that you are using.

Total time: 16 seconds
>

This short runtime indicates that the install failed very early, which also 
suggests problems with the database. 

-- 
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] HA Clustering Dspace

[Mark Wood]

On Thursday, July 21, 2016 at 3:13:35 PM UTC-4, Peter Dietz wrote:
>
> From my investigations into DSpace, the key element that I would like to 
> de-couple from DSpace is SOLR. 
>
> Say you were going to build a new frontend to DSpace that heavily used the 
> DSpace REST API. You could have multiple servers, each running tomcat and 
> the DSpace REST API deployed. With nginx outside of that proxying / load 
> balancing. No problems. Especially as you have postgres as an external 
> service (rds), the assetstore is located outside of DSpace (s3). However, I 
> don't see how you can run multiple instances of DSpace SOLR. SOLR stores 
> data, and it wouldn't be as simple as just adding another server running 
> the webapp. But you would need to coordinate the SOLR cluster, using 
> SolrCloud / ZooKeeper. Maybe its not as complicated as I think. But, I 
> thought that I read at one point that DSpace had some custom solr code 
> present, or the solr configs would have to be managed, and I'm not sure how 
> much work it would be to build up a solr cluster with that config.
>
> DSpace does include a tiny dab of custom code for Solr, which I think is 
not essential.  LocalHostRestrictionFilter can be replaced with fairly 
simple filtering by the Servlet container.  ConfigureLog4jListener only 
exists because for some reason we insist that Solr's logging configuration 
live with DSpace's instead of with the rest of Solr's configuration.  There 
is nothing else.  It should be simple to use DSpace with a stock Solr 4 
instance.  If and when DSpace moves to Solr 5+ this all will have to be 
revamped anyway due to significant changes in the way Solr must be deployed.

-- 
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: DSpace, JDBC PostgreSQL Connector and tcpKeepAlive

[Mark Wood]

You could try adding it to the db.url value:  "db.url = 
jdbc:postgresql://localhost:5432/DS-3176?tcpKeepAlive=true"

I'd be more inclined to configure the connection pool to test connections 
before use, but that is a bit more involved:  you'd need to explicitly 
declare to Tomcat a  for DSpace (if you are not already doing 
that) and enclose a  element which describes the connection 
pool.  Then you can configure the pool using the full range of its 
properties, including testOnBorrow and validationQuery.  If this all sounds 
completely new to you, I'd try the URL method first.

-- 
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] Recommended Testing Strategy

[Mark Wood]

On Tue, Jun 07, 2016 at 12:09:41PM -0500, Tim Donohue wrote:
> As far as I'm aware, that's just how a Maven test runs. It automatically
> will try to run tests in all modules, but it only will execute ones that
> it finds.  So, most modules will report that no tests were found.  I'm
> unaware of any way to change that behavior in Maven (if you know of one,
> let us know).

That's right: phases 'test' and 'integration-test' (and several other
test-related phases) are part of the standard Maven lifecycle and will
be run unless suppressed somehow.  I think that we could selectively
disable these phases for projects that currently have no tests, but I
would rather that we started writing good tests for those projects.

Some good work was started in dspace-api, which can be extended to
other projects without a lot of effort.  It just hasn't been done.
What we have now is frameworks with some quite useful tests included,
and a collection of newer tests that grows as individual developers
add to it for their own use.  I'm less familiar with the test setup in
dspace-services, which was developed separately.

We could use some more mocking to make some of our unit tests more
lightweight (and a lot faster).

> Also, be aware that we have Unit / Integration Tests disabled by default
> in our Maven POM settings.  So, to actually run tests, you need to apply
> a flag to enable them:
>
>   * "-Dmaven.test.skip=false" will enable Unit Tests to run (via Maven
> Surefire Plugin)
>   * "-DskipITs=false" will enable Integration Tests to run (via Maven
> Failsafe Plugin)

Just to make things *really* confusing, I have the following in my
~/.m2/settings.xml:

 
   
  defaults
  
 false
 false
  
   
 

 
defaults
 

-- 
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: No parameter substitution in ant when creating log.dir - DSpace 6 RC1

[Mark Wood]

This should have been corrected in 
https://github.com/DSpace/DSpace/pull/1364.  log.dir no longer exists in 
the DSpace configuration; it is only defined in the log4j configuration.  
If a property is not defined, no substitution is done.

-- 
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.