Re: [dspace-tech] Database connectivity Issue

2019-06-17 Thread Tony Brian Albers
What does getenforce say? This might be SELinux doing its job ;)

Check /var/log/audit/audit.log for stuff related to tomcat/catalina,
pgsql etc. 

Check the pgsql logs, they usually have some pointer as to where it
goes wrong. Also check the tomcat logs.

And an important thing:

The password stated in dspace.cfg or local.cfg must be entered as
follows:

db.password = un@b0mb3R?

make sure the spaces are there and be careful that your password
doesn't contain = or localized characters (german umlaut etc.)

also try to connect to pgsql directly from the CLI as the dspace user
like so:

[dspace@rigel config]$ psql -U dspace -W -d dspace
Password for user dspace: 
psql (9.5.14)
Type "help" for help.

dspace=>> \l
  List of databases
   Name|  Owner   | Encoding |   Collate   |Ctype|   Access
privileges   
---+--+--+-+-+-
--
 dspace| dspace   | UTF8 | C   | C   | 
 postgres  | postgres | UTF8 | en_GB.UTF-8 | en_GB.UTF-8 | 
 template0 | postgres | UTF8 | en_GB.UTF-8 | en_GB.UTF-8 |
=c/postgres  +
   |  |  | | |
postgres=CTc/postgres
 template1 | postgres | UTF8 | en_GB.UTF-8 | en_GB.UTF-8 |
=c/postgres  +
   |  |  | | |
postgres=CTc/postgres
(4 rows)

dspace=>

HTH

/tony

On Mon, 2019-06-17 at 09:35 -0400, Keith Jones wrote:
> Hi,
> I checked the dspace.cfg file and the information is correct.
> 
> I've run this:
> 
> -bash-4.2$ ../bin/dspace database test
> 
> Attempting to connect to database using these configurations:
>  - URL: jdbc:postgresql://localhost:5432/dspace
>  - Driver: org.postgresql.Driver
>  - Username: dspace
>  - Password: [hidden]
>  - Schema:
> 
> Testing connection...
> Connected successfully!
> 
> On Mon, Jun 17, 2019 at 9:26 AM Ayuka Phanuel  > wrote:
> > 
> > Confirm your database credentials (name, url, password, username)
> > added to your local.cfg or dspace.cfg
> > 
> > 
> > 
> > On Mon, Jun 17, 2019 at 4:21 PM Keith Jones 
> > wrote:
> > > 
> > > Hi All,
> > > 
> > > I'm trying to move an installation of Dspace 5.3 to a new Centos
> > > 7
> > > server. I've installed all the software required and have
> > > everything
> > > running. I'm able to compile the Dspace software, which goes
> > > without a
> > > problem. I test the database connection and it works fine. When I
> > > deploy the xmlui into the webapps area of Tomcat, I'm getting the
> > > following error:
> > > 
> > > SEVERE: Exception sending context destroyed event to listener
> > > instance
> > > of class org.dspace.app.util.DS
> > > paceContextListener
> > > java.lang.IllegalStateException: The connection attempt failed.
> > > at
> > > org.dspace.storage.rdbms.DatabaseManager.getDataSource(DatabaseMa
> > > nager.java:655)
> > > at
> > > org.dspace.storage.rdbms.DatabaseManager.getConnection(DatabaseMa
> > > nager.java:629)
> > > at org.dspace.core.Context.init(Context.java:121)
> > > at org.dspace.core.Context.(Context.java:95)
> > > at
> > > org.dspace.app.util.AbstractDSpaceWebapp.deregister(AbstractDSpac
> > > eWebapp.java:97)
> > > at
> > > org.dspace.app.util.DSpaceContextListener.contextDestroyed(DSpace
> > > ContextListener.java:146)
> > > at
> > > org.apache.catalina.core.StandardContext.listenerStop(StandardCon
> > > text.java:5165)
> > > at
> > > org.apache.catalina.core.StandardContext.stopInternal(StandardCon
> > > text.java:5829)
> > > at
> > > org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:22
> > > 1)
> > > at
> > > org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:1
> > > 49)
> > > at
> > > org.apache.catalina.core.ContainerBase.addChildInternal(Container
> > > Base.java:899)
> > > at
> > > org.apache.catalina.core.ContainerBase.addChild(ContainerBase.jav
> > > a:875)
> > > at
> > > org.apache.catalina.core.StandardHost.addChild(StandardHost.java:
> > > 652)
> > > at
> > > org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig
> > > .java:1260)
> > > at
> > > org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostCo
> > > nfig.java:2002)
> > > at
> > > java.util.concurrent.Executors$RunnableAdapter.call(Executors.jav
> > > a:511)
> > > at
> > > java.util.concurrent.FutureTask.run(FutureTask.java:266)
> > > at
> > > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecu
> > > tor.java:1149)
> > > at
> > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExec
> > > utor.java:624)
> > > at java.lang.Thread.run(Thread.java:748)
> > > Caused by: org.postgresql.util.PSQLException: The connection
> > > attempt failed.
> > > at
> > > org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(C
> > > 

[dspace-tech] HIJACKED SESSIONs Protection

2019-06-17 Thread Federico Yemurenko
Hi,

Has the IP address based session hijacking protection already been removed 
or made configurable in DSpace 6.3 ?
(Ref. DS-2030 ).

Please advise and provide more information.

Regards

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/66c7c43c-2602-45d3-83d2-1743452a5941%40googlegroups.com.


Re: [dspace-tech] Database connectivity Issue

2019-06-17 Thread Keith Jones
Hi,
I checked the dspace.cfg file and the information is correct.

I've run this:

-bash-4.2$ ../bin/dspace database test

Attempting to connect to database using these configurations:
 - URL: jdbc:postgresql://localhost:5432/dspace
 - Driver: org.postgresql.Driver
 - Username: dspace
 - Password: [hidden]
 - Schema:

Testing connection...
Connected successfully!

On Mon, Jun 17, 2019 at 9:26 AM Ayuka Phanuel  wrote:
>
> Confirm your database credentials (name, url, password, username) added to 
> your local.cfg or dspace.cfg
>
>
>
> On Mon, Jun 17, 2019 at 4:21 PM Keith Jones  wrote:
>>
>> Hi All,
>>
>> I'm trying to move an installation of Dspace 5.3 to a new Centos 7
>> server. I've installed all the software required and have everything
>> running. I'm able to compile the Dspace software, which goes without a
>> problem. I test the database connection and it works fine. When I
>> deploy the xmlui into the webapps area of Tomcat, I'm getting the
>> following error:
>>
>> SEVERE: Exception sending context destroyed event to listener instance
>> of class org.dspace.app.util.DS
>> paceContextListener
>> java.lang.IllegalStateException: The connection attempt failed.
>> at 
>> org.dspace.storage.rdbms.DatabaseManager.getDataSource(DatabaseManager.java:655)
>> at 
>> org.dspace.storage.rdbms.DatabaseManager.getConnection(DatabaseManager.java:629)
>> at org.dspace.core.Context.init(Context.java:121)
>> at org.dspace.core.Context.(Context.java:95)
>> at 
>> org.dspace.app.util.AbstractDSpaceWebapp.deregister(AbstractDSpaceWebapp.java:97)
>> at 
>> org.dspace.app.util.DSpaceContextListener.contextDestroyed(DSpaceContextListener.java:146)
>> at 
>> org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:5165)
>> at 
>> org.apache.catalina.core.StandardContext.stopInternal(StandardContext.java:5829)
>> at 
>> org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:221)
>> at 
>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:149)
>> at 
>> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:899)
>> at 
>> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:875)
>> at 
>> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:652)
>> at 
>> org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1260)
>> at 
>> org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:2002)
>> at 
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>> at 
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>> at 
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>> at java.lang.Thread.run(Thread.java:748)
>> Caused by: org.postgresql.util.PSQLException: The connection attempt failed.
>> at 
>> org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:
>> 152)
>> at 
>> org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:66)
>> at 
>> org.postgresql.jdbc2.AbstractJdbc2Connection.(AbstractJdbc2Connection.java:125)
>> at 
>> org.postgresql.jdbc3.AbstractJdbc3Connection.(AbstractJdbc3Connection.java:30)
>> at 
>> org.postgresql.jdbc3g.AbstractJdbc3gConnection.(AbstractJdbc3gConnection.java:22)
>> at 
>> org.postgresql.jdbc4.AbstractJdbc4Connection.(AbstractJdbc4Connection.java:32)
>> at 
>> org.postgresql.jdbc4.Jdbc4Connection.(Jdbc4Connection.java:24)
>> at org.postgresql.Driver.makeConnection(Driver.java:393)
>> at org.postgresql.Driver.connect(Driver.java:267)
>> at java.sql.DriverManager.getConnection(DriverManager.java:664)
>> at java.sql.DriverManager.getConnection(DriverManager.java:247)
>> at 
>> org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnec
>> tionFactory.java:75)
>> at 
>> org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java
>> :582)
>> at 
>> org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:974)
>> at 
>> org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:106)
>> at 
>> org.dspace.storage.rdbms.DatabaseManager.initialize(DatabaseManager.java:1336)
>> at 
>> org.dspace.storage.rdbms.DatabaseManager.getDataSource(DatabaseManager.java:650)
>> ... 19 more
>> Caused by: java.net.SocketException: Permission denied (connect failed)
>> at java.net.PlainSocketImpl.socketConnect(Native Method)
>> at 
>> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
>> at 
>> 

Re: [dspace-tech] Best practice to modify existing classes

2019-06-17 Thread Claudia Jürgen

Hello Armin,

with which version of DSpace are you working and what are you trying to
overlay?

Depending on what you want to oververlay, you might be missing a
dependency in
[dspace-src]/dspace/modules/jspui/pom.xml
Most likely

javax.servlet
jsp-api
2.0
provided

as this is used in org.dspace.app.webui.jsptag and customizing the
ItemTag.java is a common use case.

Hope this helps

Claudia Jürgen


Am 17.06.2019 um 15:08 schrieb Wenz, Armin:

Hi all,

I want to modify existing class files in the dspace-api and dspace-
jspui tree, but keep the original files (the original source tree)
intact, so that I can still update Dspace without loosing my changes
with the next update. Therefore I copied the files I want to modify to
dspace/modules/additions (the api) and dspace/modules/jspui.

The problem (as you probably guess) is now, that I cannot compile my
classes due to missing import files.

Either my approach is wrong or I missed something. Searched the tech
group and the wiki but haven't found anything appropriate.

So, is there a HOWTO or Best Practice doc describing how to modify
existing files?

Thanks



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

--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/e55e6b57-ff6f-026a-28b4-e37bbc84aeee%40tu-dortmund.de.


Re: [dspace-tech] Database connectivity Issue

2019-06-17 Thread Ayuka Phanuel
Confirm your database credentials (name, url, password, username) added to
your local.cfg or dspace.cfg



On Mon, Jun 17, 2019 at 4:21 PM Keith Jones  wrote:

> Hi All,
>
> I'm trying to move an installation of Dspace 5.3 to a new Centos 7
> server. I've installed all the software required and have everything
> running. I'm able to compile the Dspace software, which goes without a
> problem. I test the database connection and it works fine. When I
> deploy the xmlui into the webapps area of Tomcat, I'm getting the
> following error:
>
> SEVERE: Exception sending context destroyed event to listener instance
> of class org.dspace.app.util.DS
> paceContextListener
> java.lang.IllegalStateException: The connection attempt failed.
> at
> org.dspace.storage.rdbms.DatabaseManager.getDataSource(DatabaseManager.java:655)
> at
> org.dspace.storage.rdbms.DatabaseManager.getConnection(DatabaseManager.java:629)
> at org.dspace.core.Context.init(Context.java:121)
> at org.dspace.core.Context.(Context.java:95)
> at
> org.dspace.app.util.AbstractDSpaceWebapp.deregister(AbstractDSpaceWebapp.java:97)
> at
> org.dspace.app.util.DSpaceContextListener.contextDestroyed(DSpaceContextListener.java:146)
> at
> org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:5165)
> at
> org.apache.catalina.core.StandardContext.stopInternal(StandardContext.java:5829)
> at
> org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:221)
> at
> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:149)
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:899)
> at
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:875)
> at
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:652)
> at
> org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1260)
> at
> org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:2002)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.postgresql.util.PSQLException: The connection attempt
> failed.
> at
> org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:
> 152)
> at
> org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:66)
> at
> org.postgresql.jdbc2.AbstractJdbc2Connection.(AbstractJdbc2Connection.java:125)
> at
> org.postgresql.jdbc3.AbstractJdbc3Connection.(AbstractJdbc3Connection.java:30)
> at
> org.postgresql.jdbc3g.AbstractJdbc3gConnection.(AbstractJdbc3gConnection.java:22)
> at
> org.postgresql.jdbc4.AbstractJdbc4Connection.(AbstractJdbc4Connection.java:32)
> at
> org.postgresql.jdbc4.Jdbc4Connection.(Jdbc4Connection.java:24)
> at org.postgresql.Driver.makeConnection(Driver.java:393)
> at org.postgresql.Driver.connect(Driver.java:267)
> at java.sql.DriverManager.getConnection(DriverManager.java:664)
> at java.sql.DriverManager.getConnection(DriverManager.java:247)
> at
> org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnec
> tionFactory.java:75)
> at
> org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java
> :582)
> at
> org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:974)
> at
> org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:106)
> at
> org.dspace.storage.rdbms.DatabaseManager.initialize(DatabaseManager.java:1336)
> at
> org.dspace.storage.rdbms.DatabaseManager.getDataSource(DatabaseManager.java:650)
> ... 19 more
> Caused by: java.net.SocketException: Permission denied (connect failed)
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net
> .AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
> at java.net
> .AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
> at java.net
> .AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:589)
> at java.net.Socket.connect(Socket.java:538)
> at java.net.Socket.(Socket.java:434)
> at java.net.Socket.(Socket.java:211)
> at org.postgresql.core.PGStream.(PGStream.java:62)
> at
> 

[dspace-tech] Database connectivity Issue

2019-06-17 Thread Keith Jones
Hi All,

I'm trying to move an installation of Dspace 5.3 to a new Centos 7
server. I've installed all the software required and have everything
running. I'm able to compile the Dspace software, which goes without a
problem. I test the database connection and it works fine. When I
deploy the xmlui into the webapps area of Tomcat, I'm getting the
following error:

SEVERE: Exception sending context destroyed event to listener instance
of class org.dspace.app.util.DS
paceContextListener
java.lang.IllegalStateException: The connection attempt failed.
at 
org.dspace.storage.rdbms.DatabaseManager.getDataSource(DatabaseManager.java:655)
at 
org.dspace.storage.rdbms.DatabaseManager.getConnection(DatabaseManager.java:629)
at org.dspace.core.Context.init(Context.java:121)
at org.dspace.core.Context.(Context.java:95)
at 
org.dspace.app.util.AbstractDSpaceWebapp.deregister(AbstractDSpaceWebapp.java:97)
at 
org.dspace.app.util.DSpaceContextListener.contextDestroyed(DSpaceContextListener.java:146)
at 
org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:5165)
at 
org.apache.catalina.core.StandardContext.stopInternal(StandardContext.java:5829)
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:221)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:149)
at 
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:899)
at 
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:875)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:652)
at 
org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1260)
at 
org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:2002)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.postgresql.util.PSQLException: The connection attempt failed.
at 
org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:
152)
at 
org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:66)
at 
org.postgresql.jdbc2.AbstractJdbc2Connection.(AbstractJdbc2Connection.java:125)
at 
org.postgresql.jdbc3.AbstractJdbc3Connection.(AbstractJdbc3Connection.java:30)
at 
org.postgresql.jdbc3g.AbstractJdbc3gConnection.(AbstractJdbc3gConnection.java:22)
at 
org.postgresql.jdbc4.AbstractJdbc4Connection.(AbstractJdbc4Connection.java:32)
at org.postgresql.jdbc4.Jdbc4Connection.(Jdbc4Connection.java:24)
at org.postgresql.Driver.makeConnection(Driver.java:393)
at org.postgresql.Driver.connect(Driver.java:267)
at java.sql.DriverManager.getConnection(DriverManager.java:664)
at java.sql.DriverManager.getConnection(DriverManager.java:247)
at 
org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnec
tionFactory.java:75)
at 
org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java
:582)
at 
org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:974)
at 
org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:106)
at 
org.dspace.storage.rdbms.DatabaseManager.initialize(DatabaseManager.java:1336)
at 
org.dspace.storage.rdbms.DatabaseManager.getDataSource(DatabaseManager.java:650)
... 19 more
Caused by: java.net.SocketException: Permission denied (connect failed)
at java.net.PlainSocketImpl.socketConnect(Native Method)
at 
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at 
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at 
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at java.net.Socket.connect(Socket.java:538)
at java.net.Socket.(Socket.java:434)
at java.net.Socket.(Socket.java:211)
at org.postgresql.core.PGStream.(PGStream.java:62)
at 
org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:
76)
... 35 more

Any help would be appreciated.

Thanks
Keith

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" 

[dspace-tech] Best practice to modify existing classes

2019-06-17 Thread Wenz, Armin
Hi all,

I want to modify existing class files in the dspace-api and dspace-
jspui tree, but keep the original files (the original source tree)
intact, so that I can still update Dspace without loosing my changes
with the next update. Therefore I copied the files I want to modify to
dspace/modules/additions (the api) and dspace/modules/jspui. 

The problem (as you probably guess) is now, that I cannot compile my
classes due to missing import files. 

Either my approach is wrong or I missed something. Searched the tech
group and the wiki but haven't found anything appropriate. 

So, is there a HOWTO or Best Practice doc describing how to modify
existing files? 

Thanks

-- 

Armin Wenz

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/1560776897.7252.11.camel%40ub.uni-mainz.de.


[dspace-tech] specify the size or number of downloads

2019-06-17 Thread muaz awed
Urgent : can we  specify the size or number of downloads  either for groups 
or individuals to prevent the download of content at random by any way.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/be9c7162-b0d5-438f-84e2-25a4a450046e%40googlegroups.com.


[dspace-tech] DSpace 7 accessibility (WCAG / section 508 / etc)

2019-06-17 Thread Jeremy Echols
Hi, I'm working with DSpace 6 and finding that remediation of accessibility 
failures is a huge chore just for our theme alone (requiring changes to 
core Java code and XSL files just to do things like add labels to form 
fields).  As we saw posts about accessibility in the past, we had been 
hoping the situation would have improved for DSpace 7, but looking over the 
demo site hosted by Atmire, it actually appears to have gotten 
significantly worse.

Is there a group dedicated to accessibility for DSpace 7?  Should I be 
filing tickets as I run into problems, or is the demo a very early 
prototype?  Are the core developers aware of the issues and simply haven't 
yet dealt with them?  Some issues are so trivial that it seems unlikely 
that there's widespread awareness, but I know nothing of Angular or how the 
core team operates, so maybe I'm jumping the gun here.

Detailed problems are listed below.  I found these in about fifteen 
minutes, so this is far from an in-depth audit.  Note that many of these 
are WCAG level A -- which means, essentially, that they are critical 
priority and block a large number of users from accessing the site.  It 
also means that under most jurisdictions, a university could be in legal 
trouble if they stood up the site as it exists today.

- The pages have no defined language, e.g., 
- Over a dozen fields have no labels, particularly within the search filter 
area
- There are images used as links which have no alt attribute (or other 
alternative text)
- The search page's filters are tab-accessible, despite being visually 
hidden, so keyboard focus just gets lost for several links
- There's no way I can figure out to open up the search filters with just a 
keyboard without actually clicking one of the hidden links
- There's at least one misuse of aria, where an  tag is given a role of 
"button", but its behavior isn't actually button behavior (spacebar doesn't 
activate it, for instance)
- Some links have a title but no text.  Depending on browser and screen 
reader combination, a user may have no idea what's being presented.
- I can't figure out how to use the date slider with just a keyboard.
- There are dozens of instances of low-contrast text

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/76940617-7756-4402-8e1d-4c3a56fd2efc%40googlegroups.com.


[dspace-tech] SolrCore Initialization Failures

2019-06-17 Thread Dyego Cavalieri
Hi all,

I have the following in the Solr after installing dspace 6.3

   - *search:* 
   org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: 
   Cannot create directory: /dspace/solr/search/data/index 
   - *oai:* 
   org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: 
   Cannot create directory: /dspace/solr/oai/data/index 
   - *authority:* 
   org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: 
   Cannot create directory: /dspace/solr/authority/data/index 
   - *statistics:* 
   org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: 
   Cannot create directory: /dspace/solr/statistics/data/index 

How do i fix this ?


thank you.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/742dfa1b-1d2f-4f2d-995a-af3827429470%40googlegroups.com.


[dspace-tech] Step installation Dspace-CRIS or step to upgrade Dspace to Dspace CRIS

2019-06-17 Thread Nur Maisari
Hi everyone. 

Right now, i'm trying to install upgrading dspace to dspace cris but 
unsucessfull. I'm try so many times and same issues are detect. Before 
this, i'm follow the step from Duraspace in upgrade the dspace cris and it 
still doesn't work. I didn't find the full step or documentation about the 
dspace cris. 

During installation dspace cris, i success install and the step below i 
can't understand. 

[image: Capture1.JPG]

[image: Capture.JPG]


If anyone are successful installed dspace cris, i really hope you willing 
to share the information or details to me and others. I'm really hope 
anyone notice my issue. 

Thank you for your cooperations...


-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/1039dd50-f143-4f83-bf5e-0d48a9c50711%40googlegroups.com.