--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse-community@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/0b62d92a-d676-4102-a070-c92960584f66%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I've gotten the "EJB Timer" error before when the root problem was database connectivity. I bet you'll see SQL errors further up in the log.Not to ask a silly question, but did you verify that the password change worked via connecting with psql or another database client?I'll try this on a test machine and report back.Donald
On Fri, Jul 14, 2017 at 9:47 AM, Anders Conrad <a...@kb.dk> wrote:
Hi,
I tried to change the password in Postgres. Subsequently stopped Glassfish and changed the line
<property name="password" value="..."></property>
in config/domain.xml accordingly.
This resulted in the "EJB Timer Service is not available" error described in http://guides.dataverse.org/en/latest/admin/troubleshooting.html. I tried the workaround described here, but without succes. Changing the password back to the original resulted in everything loading correctly again.
What is the correct procedure if you want to change the Postgres password for Dataverse? Apologies if I have overlooked something in the doc or here in the Google group...
/Anders
--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.