Trouble with updating publication status through descendants

47 views
Skip to first unread message

FHYA

unread,
Jun 27, 2017, 1:31:38 PM6/27/17
to AtoM Users
Hi there

I am receiving an Error 500 message when I try to change the publication status from draft to published and click the box for update descendants. When I go through the descendants I can publish each individually, but I am confused as to why I am receiving the error when trying to update the descendants alongside the update of a higher level archival description. Does this make sense? I have AtoM version 2.3.1 - 138. I batch uploaded the material I am working with using the digital object path on a csv, and that upload went fine. everything nested correctly, etc. I really can't figure out what's wrong!

Thanks so much! 

Dan Gillean

unread,
Jun 27, 2017, 2:55:47 PM6/27/17
to ICA-AtoM Users
Hi Chloe,

In AtoM 2.3 and later, the publication status updates for descendants are handled asynchronously by AtoM's job scheduler. It sounds like it is possible that the AtoM worker is not running?

The first thing I would try would be to restart the AtoM worker. You can run the following command (depending on your installation operating system) from the root AtoM installation directory:
  • On Ubuntu 14.04: sudo restart atom-worker
  • On Ubuntu 16.04: sudo systemctl restart atom-worker

If that doesn't work, then we would want to see the output of the error logs. In general, whenever you encounter a 500 error, the first thing to check is the webserver error logs - these can help provide us more specific information about the nature of the error. If you have followed our default installation instructions (e.g. installing Nginx as you webserver), then the error logs should be accessible with the following command from the root AtoM installation directory:

You can also try putting the user interface into Debug mode to see if you can get a stack trace of the error. Once you enable debug mode, you can repeat the actions that lead to the error, and see if a stack trace provides further technical information about the error encountered. For more information on using Debug mode see:

This video will also help walk you through the process of setting up Debug mode and checking the Nginx error logs:

If you do get a stack trace, you can save it as HTML and attach it here. Please share any related messages you find in either the Nginx logs or when repeating the action that caused the 500 error while in Debug mode, and hopefully this will give us a better sense of the issue, so we can provide further recommendations.

Cheers,

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

--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-users+unsubscribe@googlegroups.com.
To post to this group, send email to ica-atom-users@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/bd4d8ec1-8f4b-4eaf-8c6a-a8e26aab2d45%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Chloe Rush

unread,
Jun 27, 2017, 4:06:07 PM6/27/17
to ica-ato...@googlegroups.com
Hi Dan

Thanks so much - I'll do some troubleshooting and get back to you if the issue persists! 

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.

--
You received this message because you are subscribed to a topic in the Google Groups "AtoM Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ica-atom-users/LgozdQwFop4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ica-atom-user...@googlegroups.com.
To post to this group, send email to ica-ato...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages