500 Internal Server Error after search

[Nicolas]

Hi,

When I use search in AtoM, I get a 500 internal server error, how can I fix that ? 

Thanks

[Jenny Mitcham]

Hi - this happened to us last week and it appeared it was a problem with Elasticsearch. I think Elasticsearch just needed to be restarted and it came back up pretty quick.

Cheers,

Jen

--
You received this message because you are subscribed to the Google Groups "ICA-AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To post to this group, send email to ica-ato...@googlegroups.com.
Visit this group at https://groups.google.com/group/ica-atom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/13b3e264-555b-498b-986c-7bb83c1b182e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Jenny Mitcham
Digital Archivist
Borthwick Institute for Archives

University of York
Heslington
York
YO10 5DD

Telephone: 01904 321170

Borthwick Institute website: http://www.york.ac.uk/borthwick/
Digital archiving blog: http://digital-archiving.blogspot.co.uk/

Twitter: @Jenny_Mitcham

Skype: jenny_mitcham

[Nicolas]

Hi,

It was that ! Thank you so much !

Nicolas

[Jenny Mitcham]

Great! - that is the first time I have ever been able to answer a technical question :-)

Happy to have been of help!

Jen

To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/25e8e1dc-5c50-420d-acf4-7e7af05b2d42%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Jesús García Crespo]

Thanks, Jenny! That was fast.

I'd like to add that in general it's a good practice to start troubleshooting errors like that looking at the logs. We have some docs here: https://www.accesstomemory.org/en/docs/2.0/admin-manual/maintenance/logging/#web-server-logs.

Also, the reason why Elasticsearch dies unexpectedly is mostly because the JVM has not enough memory assigned. The size of the heap is declared in /etc/default/elasticsearch, e.g. you could try "2g" if you have two GB of memory available. Once the value is changed you have to restart Elasticsearch. There are more details here: https://www.elastic.co/guide/en/elasticsearch/guide/current/heap-sizing.html.

To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/CAF8JE%3DpKF6Ok4d%3DiFekEJv5wGL3AnfgAz8EQUM1jBc0qCHCzrw%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Jesús García Crespo,
Software Engineer, Artefactual Systems Inc.
http://www.artefactual.com | +1.604.527.2056

[Dan Gillean]

Thanks so much for jumping in, Jen!

Nicolas, I'm glad to hear that your issue has been resolved! Just to supplement the response that Jesús provided - it may not be relevant for this particular problem, but  int the future, if you ever need to get a stack trace of an error encountered in the browser, you can do so by enabling Debug mode - see:

• https://www.accesstomemory.org/docs/2.2/admin-manual/maintenance/debug/

If you are not certain what the output of Debug mode or your webserver logs means, you are always welcome to post it here; our developers can offer some suggestions.

We've recently created a video tutorial series to help our users become more comfortable with using the command-line tools and tasks available in AtoM - video 4 covers accessing the webserver logs and debug mode, while video 5 covers some of the most common CLI tasks for maintenance and troubleshooting. See the full playlist here:

• https://www.youtube.com/playlist?list=PLZiwlG5eSMeyeETe15EsEBSu5htPLK-wm

Kind regards,

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056

@accesstomemory

On Mon, May 9, 2016 at 6:22 AM, Jenny Mitcham <jenny....@york.ac.uk> wrote:

To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/CAF8JE%3DpKF6Ok4d%3DiFekEJv5wGL3AnfgAz8EQUM1jBc0qCHCzrw%40mail.gmail.com.