[dspace-tech] Re: Connection refused msg when attempting to reset password for another user.
On Tuesday, November 13, 2018 at 1:55:04 PM UTC-5, Chin U. Kim wrote: > > Connection refused (Connection refused) > Go to DSpace home > > Please contact the site administrator if you wish to report this error. If > possible, please provide details about what you were doing at the time this > error occurred. > > Contact site administrator || Show underlying error stack > > > Java stacktrace: > java.net.ConnectException: Connection refused (Connection refused) > 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 sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:673) > at sun.security.ssl.BaseSSLSocketImpl.connect(BaseSSLSocketImpl.java:173) > at com.sun.mail.util.SocketFetcher.createSocket(SocketFetcher.java:321) > at com.sun.mail.util.SocketFetcher.getSocket(SocketFetcher.java:211) > at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1927) > at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:654) > at javax.mail.Service.connect(Service.java:274) > at javax.mail.Service.connect(Service.java:91) > at javax.mail.Service.connect(Service.java:76) > at javax.mail.Transport.send(Transport.java:94) > at javax.mail.Transport.send(Transport.java:48) > at org.dspace.core.Email.send(Email.java:360) > > The error occurs when DSpace tries to send a password reset email. It cannot connect to the configured mail service. The configured host exists and is running but refused connection from your DSpace host on the configured port. I would check the values of mail.server, mail.server.port, and (if the mail service requires credentials) mail.server.username and mail.server.password. You may find 'bin/dspace test-email' useful for testing changes to these values. -- 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 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 sending emails through O365 / DSpace v5.5
Hi Evelthon. You certainly can. Just set your the SMTP settings in you dspace.cfg file (better in local.cfg if you are on version 6.x). These look like this: # SMTP mail server (allows DSpace to send email notifications) mail.server = smtp.example.com # SMTP mail server authentication username and password (if required) mail.server.username = mail.server.password = # SMTP mail server alternate port (defaults to 25) mail.server.port = 25 Change your mail.server to localhost, add username and password if you have smtp authentication configured in your postfix, and change the port as needed. If you have SPF configured for the domain of the email addresses that you are sending from, you will have to add the IP address of your server to the DNS SPF record. Otherwise, all should work and you should see the emails flow in you email log file (/var/log/maillog on Centos). Kind Regards. Shaun. On 2018/11/14 13:32, Evelthon Prodromou wrote: Dear all, Has anyone successfully sent emails through Office365? My problem occurs with the mail settings in dspace.cfg. The server itself uses postfix and has been successfully configured to send emails through O365. Can we configure email relaying through local postfix? Thank you, Evelthon Prodromou -- 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 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 sending emails through O365 / DSpace v5.5
Dear all, Has anyone successfully sent emails through Office365? My problem occurs with the mail settings in dspace.cfg. The server itself uses postfix and has been successfully configured to send emails through O365. Can we configure email relaying through local postfix? Thank you, Evelthon Prodromou -- 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 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] Enabling REST interface
The /var/log/tomcat7/localhost.2018-11.14.log has some interesting info: ... INFO: Marking servlet DSpace REST API as unavailable Nov 14, 2018 4:08:51 AM org.apache.catalina.core.StandardContext loadOnStartup SEVERE: Servlet [DSpace REST API] in web application [/rest] threw load() exception java.lang.ClassNotFoundException: com.sun.jersey.spi.spring.container.servlet.SpringServlet at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1859) at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1702) at org.apache.catalina.core.DefaultInstanceManager.loadClass(DefaultInstanceManager.java:504) at org.apache.catalina.core.DefaultInstanceManager.loadClassMaybePrivileged(DefaultInstanceManager.java:486) at org.apache.catalina.core.DefaultInstanceManager.newInstance(DefaultInstanceManager.java:113) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1146) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1085) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5318) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5610) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147) 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.deployDescriptor(HostConfig.java:677) at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1962) 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) Looks like I'm missing the SpringServlet class, but where would I get this? I'm using openjdk version "1.8.0_181", if that's at all relevant. On Wed, 14 Nov 2018 at 11:46, Alan Orth wrote: > Dear Sean, > > It's "good" that the /rest path doesn't work either. So something is wrong > with the loading of this application. Restart Tomcat and watch the logs as > it loads each application (xmlui, solr, rest, etc). On Ubuntu that would be > the general Tomcat Catalina logs[0] and localhost container logs[1]. > > Regards, > > [0] /var/log/tomcat7/catalina.out > [1] /var/log/tomcat7/localhost.2018-11-14.log > > On Wed, Nov 14, 2018 at 11:42 AM Sean Carte wrote: > >> Also, the permissions are the same as for all the other webapps, >> including sword2 and jspui, which do work. >> >> On Wed, 14 Nov 2018 at 11:40, Sean Carte wrote: >> >>> Thanks for responding, Alan. >>> >>> Yes, the path exists: >>> dspace@dev-ir:~$ ls /dspacecris-dut/webapps/rest/ >>> ametrics common css image index.jsp js META-INF static WEB-INF >>> >>> Same 404 for the root: >>> dspace@dev-ir:~$ curl -s -H "Accept: application/xml" >>> http://localhost:8080/restApache Tomcat/7.0.68 >>> (Ubuntu) - Error report...HTTP Status 404 - ... >>> >>> On Wed, 14 Nov 2018 at 11:30, Alan Orth wrote: >>> Dear Sean, Does the root path for the rest API work, ie /rest? Also, some basic sanity checking: make sure the path you gave as the context docBase exists: $ ls -l /dspacecris-dut/webapps/rest Cheers, On Tue, Nov 13, 2018 at 8:45 AM Sean Carte wrote: > I'm trying to enable the REST interface, but am just getting a 404: > curl -s -H "Accept: application/xml" > http://localhost:8080/rest/communities > Apache Tomcat/7.0.68 (Ubuntu) - Error >
Re: [dspace-tech] Enabling REST interface
Also, the permissions are the same as for all the other webapps, including sword2 and jspui, which do work. On Wed, 14 Nov 2018 at 11:40, Sean Carte wrote: > Thanks for responding, Alan. > > Yes, the path exists: > dspace@dev-ir:~$ ls /dspacecris-dut/webapps/rest/ > ametrics common css image index.jsp js META-INF static WEB-INF > > Same 404 for the root: > dspace@dev-ir:~$ curl -s -H "Accept: application/xml" > http://localhost:8080/restApache Tomcat/7.0.68 > (Ubuntu) - Error report...HTTP Status 404 - ... > > On Wed, 14 Nov 2018 at 11:30, Alan Orth wrote: > >> Dear Sean, >> >> Does the root path for the rest API work, ie /rest? Also, some basic >> sanity checking: make sure the path you gave as the context docBase exists: >> >> $ ls -l /dspacecris-dut/webapps/rest >> >> Cheers, >> >> On Tue, Nov 13, 2018 at 8:45 AM Sean Carte wrote: >> >>> I'm trying to enable the REST interface, but am just getting a 404: >>> curl -s -H "Accept: application/xml" >>> http://localhost:8080/rest/communities >>> Apache Tomcat/7.0.68 (Ubuntu) - Error >>>
Re: [dspace-tech] Enabling REST interface
Dear Sean, It's "good" that the /rest path doesn't work either. So something is wrong with the loading of this application. Restart Tomcat and watch the logs as it loads each application (xmlui, solr, rest, etc). On Ubuntu that would be the general Tomcat Catalina logs[0] and localhost container logs[1]. Regards, [0] /var/log/tomcat7/catalina.out [1] /var/log/tomcat7/localhost.2018-11-14.log On Wed, Nov 14, 2018 at 11:42 AM Sean Carte wrote: > Also, the permissions are the same as for all the other webapps, including > sword2 and jspui, which do work. > > On Wed, 14 Nov 2018 at 11:40, Sean Carte wrote: > >> Thanks for responding, Alan. >> >> Yes, the path exists: >> dspace@dev-ir:~$ ls /dspacecris-dut/webapps/rest/ >> ametrics common css image index.jsp js META-INF static WEB-INF >> >> Same 404 for the root: >> dspace@dev-ir:~$ curl -s -H "Accept: application/xml" >> http://localhost:8080/restApache Tomcat/7.0.68 >> (Ubuntu) - Error report...HTTP Status 404 - ... >> >> On Wed, 14 Nov 2018 at 11:30, Alan Orth wrote: >> >>> Dear Sean, >>> >>> Does the root path for the rest API work, ie /rest? Also, some basic >>> sanity checking: make sure the path you gave as the context docBase exists: >>> >>> $ ls -l /dspacecris-dut/webapps/rest >>> >>> Cheers, >>> >>> On Tue, Nov 13, 2018 at 8:45 AM Sean Carte wrote: >>> I'm trying to enable the REST interface, but am just getting a 404: curl -s -H "Accept: application/xml" http://localhost:8080/rest/communities Apache Tomcat/7.0.68 (Ubuntu) - Error
Re: [dspace-tech] Enabling REST interface
Dear Sean, Does the root path for the rest API work, ie /rest? Also, some basic sanity checking: make sure the path you gave as the context docBase exists: $ ls -l /dspacecris-dut/webapps/rest Cheers, On Tue, Nov 13, 2018 at 8:45 AM Sean Carte wrote: > I'm trying to enable the REST interface, but am just getting a 404: > curl -s -H "Accept: application/xml" > http://localhost:8080/rest/communities > Apache Tomcat/7.0.68 (Ubuntu) - Error >
