500 Internal Server Error".
The error log has
[Sun Jan 22 16:56:41.203463 2017] [:error] [pid 20331] [client xxx.xxx.xxx.xxx:55999] arElasticSearchInformationObjectPdo: Couldn't find ancestors, please make sure lft and rgt values are correct, referer: http://archiv.abtei-muri.ch/index.php/altmann-und-bittner/actor/delete
What is wrong?
Beda
You can then try restarting your services - namely, PHP-FPM and Ngninx. This assumes you have followed our default installation instructions for Ubuntu 14.04:
Clear the application cache:
Repopulate the search index:
Try deleting your authority record again, and let us know if that has resolved the issue. If not, please let us know a bit more about your instance - what version of AtoM? What version of PHP? Did you follow our recommended installation instructions, or have you done anything differently? Etc.
Cheers,
--
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/0b8496eb-7c18-43cd-8ea9-bc773f5f48dc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
You can always take a look in the webserver error logs to see if
there is relevant information there. If you get an error, follow these
instructions to check the logs and share the relevant entry with us, so we can see what the messages associated with the 500 errors indicate:
Note
that we have some command-line tutorial videos that might be of use for
some of the above tasks. Video 4 covers using Debug mode and checking
the Nginx error logs; video 5 covers some of the troubleshooting CLI
tasks I've shared in previous messages:
In terms of dealing with data corruption, there can be a number of factors, and it can be difficult to troubleshoot. If you have a database backup from prior to the failed import, loading it may be the easiest solution. If not, you will have to do some digging.
One easy thing to check is whether or not all descriptions have slugs
- there is a task that will regenerate the permalinks (i.e. slugs) for
all of your descriptions:
Docs: https://www.accesstomemory.org/docs/2.3/admin-manual/maintenance/cli-tools/#generate-slugs
If there are still issues, then it gets more complicated to
troubleshoot. You can check first to see if all descriptions have a
publication status. Here are a couple user forum posts with some
instructions to try if you are still running into issues or errors that
you suspect are related to database corruption:
I don't know if it will work if there is database corruption, but there is a command-line task to delete descriptions - it's possible you can use this on the untitled descriptions:
php symfony tools:delete-description <slug>
Docs: https://www.accesstomemory.org/docs/2.3/admin-manual/maintenance/cli-tools/#delete-a-description
As I said, this may not work if there is corruption in the database, but it's worth a try.
Note that in AtoM 2.3, we have introduced the use of transactions,
to try to prevent data corruption - essentially, if a request times out
mid-process, AtoM will automatically roll back to the last database
state, instead of leaving corrupted data in the system. Hoipefully this might prevent such issues from arising in the future. We are hoping to release version 2.3.1 later this week.
Finally, the fact that you had to use sudo with the search:populate command suggests that your filesystem permissions may not be configured correctly, and/or you are not currently acting as the www-data user. You can try resetting the permissions in your site by running the following from AtoM's root directory:
Hope this helps! Let us know how it goes.
Regards,
--
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/65dbbc68-86f4-4750-8e34-75065974deba%40googlegroups.com.