Skip to first unread message
Dan Gillean
Jun 21, 2019, 10:41:49 AM6/21/19
to ICA-AtoM Users
Hi Elizabeth,
Any time you encounter a 500 error, our first recommendation is always to have someone check the webserver error logs for more information. A 500 error is a general error message, and to learn more, we need to see what's in the logs, so we can better diagnose the issue. Instructions for accessing the webserver logs can be found here:
Now my guess is that the issue is that the job scheduler just needs to be restarted, but checking the logs will help us determine if that's correct or not. If they contain a message along the lines of "No worker available to complete the job," then you'll just need to restart the atom-worker, and then try again. See:
If that's not the case and/or it doesn't work, please share what you find in the logs, and that will help us offer better suggestions.
Cheers,
This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorised disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is prohibited. E-mails are not secure and cannot be guaranteed to be error-free as they can be intercepted, amended, or contain viruses. Anyone who communicates with us by e-mail is deemed to have accepted these risks. King's Christian College is not responsible for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent those of the College.
--
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-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/c3b88ec1-c882-4c69-aa5f-5f587618705d%40googlegroups.com.
Dan Gillean
Jun 24, 2019, 11:15:29 AM6/24/19
to ICA-AtoM Users
Hi again Elizabeth,
Thank you for forwarding your errog log message off-list. The key part of the error message, i.e.:
- 1 FastCGI sent in stderr: "PHP message: File upload path "/usr/share/nginx/atom/uploads/r/your-logo-name/conf" is not writable" while reading response header from upstream
...suggests to me that this might be a permissions issue. I would suggest that you try resetting the filesystem permissions, with the following command, run from AtoM's root installation directory (i.e. /usr/share/nginx/atom if you have followed our recommended installation instructions):
- sudo chown -R www-data:www-data /usr/share/nginx/atom
You may want to clear the application cache and restart PHP-FPM after. Once again, run all these commands from AtoM's root installation directory. I believe you are using PHP5.x, so the commands would be:
- php symfony cc
- sudo service php5-fpm restart
Just to be sure, let's also restart the atom-worker:
- sudo restart atom-worker
Let us know if that helps!
Elizabeth George
Jun 24, 2019, 8:47:05 PM6/24/19
to ica-ato...@googlegroups.com
Hi Dan,
Thank you very much Dan. I am able to upload photos.
I appreciate your help.
I have one more error message.
Go to Manage > Accession.
Message says Elasticsearch error: Elastica\Exception\ResponseException (SearchPhaseExecutionException).
I have attached the screenshot
Could you please look into this?
Thank you very much
Kind regards
Elizabeth George
Library Technician / Archivist
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/TDc9cg22uSs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ica-atom-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/CAC1FhZ%2B-aY7Y8HWH_TkDnCo3-GZkWjMdPHZSHrgCQ6ijMkcPLg%40mail.gmail.com.
Dan Gillean
Jun 25, 2019, 10:20:04 AM6/25/19
to ICA-AtoM Users
Hi Elizabeth,
Fortunately, in AtoM 2.4 there is also a setting that can help to resolve this. See:
Please read the section carefully, including the part in the IMPORTANT admonition, to get a full picture of how this setting works, and its gotchas.
If your issue is from trying to search for identifiers or accession numbers with slashes in them, note that another user has previously suggested a more permanent, code-based fix for this issue as well. We have not personally tested it, but another forum user has and reported success. See:
Did you perform a search on the Accessions browse page? Or did you just receive this message when first arriving there?
If you performed a search, it may be that you've used one of Elasticsearch's reserved characters. There are a number of special characters that are used as operators in Elasticsearch, and if used improperly in a query, these can cause errors. For example, the slash is a reserved character in Elasticsearch, so searching with it when it is not either in quotations or escaped will result in an Elasticsearch error. From the Elasticsearch 1.7 documentation (which is the version used in 2.4 and earlier):
See:
You can also see a list of other search operators and how they are used in AtoM here:
One simple solution is to search for the phrase exactly - i.e. in quotations.
Fortunately, in AtoM 2.4 there is also a setting that can help to resolve this. See:
Please read the section carefully, including the part in the IMPORTANT admonition, to get a full picture of how this setting works, and its gotchas.
If your issue is from trying to search for identifiers or accession numbers with slashes in them, note that another user has previously suggested a more permanent, code-based fix for this issue as well. We have not personally tested it, but another forum user has and reported success. See:
We've also changed the field type of AtoM's identifiers in the 2.5 release to make searching for identifiers and accession numbers easier. This doesn't automatically resolve the reserved character issue if you're trying to search for something with a slash in it, but it does make it easier to find matches when a slash is escaped. See:
Now, if the issue is NOT caused by a search you performed, then my next suggestion is to review the suggestions on our Troubleshooting page, here:
The second recommendation here (check the status of your search index) is a task that is not in AtoM 2.4.1 (it was added to 2.5), but the rest of the suggestions are still relevant. Let us know how it goes!
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/CAJh51806ptA38OQLC80JSvMMRKDxNYk_Q_Z77P8YHUvc-3mzXA%40mail.gmail.com.
Elizabeth George
Jun 25, 2019, 9:37:15 PM6/25/19
to ica-ato...@googlegroups.com
Hi Dan,
I have forwarded that to IT person.
I have another issue.
I have attached the screen shot
There are two logo which I created, third one I have not created.
How do I delete the third one.
Thank you very much
kind regards
Elizabeth George
Library Technician / Archivist
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/CAC1FhZJE_FFT7eCb8gUdcXMacKUck5Sq-Ee70mK2HfG2uqOnyg%40mail.gmail.com.
Dan Gillean
Jun 26, 2019, 10:26:33 AM6/26/19
to ICA-AtoM Users
Hi Elizabeth,
The documentation has the answers you seek!
One thing to check first: on the view page of the archival institution you want to delete, check the holdings listed on the left. If there are any descriptions there, I recommend opening them in a different tab - you will want to edit them to link them to the correct repository / archival institution after you have deleted this one.
Some further thoughts on how this record came to be, and how to avoid it in the future:
My guess is that this is a result of typing too fast in the autocomplete field to link a repository record, in the archival description edit page. When you want to link your descriptions to a repository, make sure you type a few letters in the autocomplete field, wait a second, and then select the correct record from the drop-down menu. If you type out the name too fast and then move out of the field, it is sometimes possible to create a duplicate record.
We've added some improvements in the 2.5 release to make this less likely to happen, but it's still possible.
Cheers,
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/CAJh5182K6Ev%3D6VRpR_E6gk8WrbWR3xk39n%2BDPhSCAYxGwEM-uw%40mail.gmail.com.
Reply all
Reply to author
Forward
0 new messages