Payara startup timeout

[Péter Király]

Dear community,

I have the following problem: once Dataverse is deployed I can not restart Payara, because the startup process always run into a timeout issue, and it is stopped.

Here is what happens:

$ sudo journalctl --unit payara

Aug 22 09:38:30 vm18063 systemd[1]: Starting Payara Server v5.1...
Aug 22 09:41:30 vm18063 systemd[1]: payara.service: start operation timed out. Terminating.
Aug 22 09:41:30 vm18063 java[8046]: Waiting for domain1 to start ....................................................................................................>
Aug 22 09:41:30 vm18063 systemd[1]: payara.service: Control process exited, code=exited, status=143/n/a
Aug 22 09:43:01 vm18063 systemd[1]: payara.service: State 'stop-final-sigterm' timed out. Killing.

As you can see it happens after 3 minutes (180 sec). I found that some Payara commands have a --timeout parameters, but start-domain doesn't have. I can not find any parameter which seemed to be relevant in domain.xml.

Do you have an idea how to increase startup timeout?

Do you have an idea how to figure out what part of the Dataverse would require more resources to work faster?

Best and thanks any feedback or hint in advance,

Péter

--

Péter Király
software developer
GWDG, Göttingen - Europeana - eXtensible Catalog - The Code4Lib Journal
http://linkedin.com/in/peterkiraly

[Don Sizemore]

Hello,

If systemd is stopping Payara, you should be able to increase the timeout:
https://github.com/GlobalDataverseCommunityConsortium/dataverse-ansible/blob/develop/templates/payara.service.j2#L12

but 180 seconds sounds like a long launch time for Payara. Do you see anything interesting in server.log?

Don

--
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-commu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CABFhGtn0-gKDED0v4K4ACH0JjvXK-dfSiQ8_5kF-UuDbh2NsVQ%40mail.gmail.com.

[Péter Király]

Dear Don,

thanks! Increasing the TimeoutStartSec helped, but only if I also add "Type = forking". Without this later the timeout remains 3 mins (in Ubuntu 20.04).

Best,

Péter

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CAPfMOaye_rVCwi-QuCwzPZgOdujEpSPjxXB%3D7Pp1LDdJP9TVnQ%40mail.gmail.com.

[Philip Durbin]

Hi Péter,

You'd contributed so much to the guides (thanks!) that you should absolutely feel free to create a pull request for this!

Thanks,

Phil

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CABFhGtnPE7j%3DrYChFfyDnMmg6stiziY8aYw-6oTDHgHRdAhTXw%40mail.gmail.com.

--

Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin

[Péter Király]

OK, I will do that.

Best,

Péter

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CABbxx8FyajR0Berh6yapDv%2BaoyThD9wdKT9DRix0NgV1OB-y4Q%40mail.gmail.com.