Page not found. "500 Internal Server Error" when move or save a edited file

[dan...@rebolledo.name]

Hello ICA-AtoM users:

I have a problem with ICA-AtoM 1.3.1, this problem appears from this friday, i'm worked with ICA-AtoM for 3 years without major problems.

I can reproduce the error:

When i try to "move" or saving a edited item appears the follow error: "Page not found" (The server returned a "500 Internal Server Error").
An example of URI returned with this error: http://www.museovillagrimaldi.info/icaatom/index.php/la3hn;default/move

Any suggestions or ideas?

I try to do:

[root@justicia icaatom]# php symfony search:populate QubitSearch

But appears:

File '/home/museo/public_html/icaatom/data/index/segments_ovt' is not readable.
                                                                               
I checked the chmod for file "segments_ovt" but isn't exist in the directory.

Thanks you.

[Dan Gillean]

Hello Daniel,

First, as you may know, ICA-AtoM 1.x is no longer being maintained, so if possible, I strongly urge you to consider upgrading to the 2.x version when you are able to.

Whenever you encounter a 500 error, it is useful to try to take a look at the webserver logs to see if there is more information. The instructions linked here are for our recommended 2.x installation, but it should give you an idea of where to look to find your Apache error logs (if you followed the recommended ICA-AtoM instructions). See:

• https://www.accesstomemory.org/docs/2.3/admin-manual/maintenance/logging/#web-server-logs
  

Please feel free to share any related error message that you find there if the following suggestions do not help to resolve the issue.

It sounds possible to me that there may be corrupted data in your database causing this issue. This can occur when a long-running operation (such as a move) is performed via the user interface, but the browser times out and aborts the operation before it is complete. This can lead to partial rows in the database which can cause errors.

We don't have all the same command-line tasks available in ICA-AToM, nor do we have documentation for this, so I am not sure that all the following suggestions will work for you. However, you can try them and see if they help:

First, I would suggest trying the solutions (build nested set, re-generate slugs) that I have mentioned in this other thread - this can often resolve issues. See:

• https://groups.google.com/d/msg/ica-atom-users/sZki6TtdX00/1LDNO_uLFAAJ

If those solutions don't work, the most common case for data corruption is when the publication status is missing in the database, or is strangely duplicated. You will have to add it directly via SQL queries in this case - see the following thread for some advice:

• https://groups.google.com/d/msg/ica-atom-users/Z8xPAMr0hiY/60L714l3EQAJ

For more details, and if the above solution doesn't work, please see this thread - it includes a query that should help you identify problem rows in the database, as well as a proposed query to resolve a much more rare issue. Again, I don't know if this query will be exactly the same in older ICA-AtoM versions or not, but it is worth a try:

• https://groups.google.com/d/msg/ica-atom-users/ZElzuHT_g40/z-XFsDFIFAAJ

Note that as of version 2.3, we have introduced the use of database 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.

I hope that helps!

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/220bbe08-9f58-43e9-8c82-da0b668cac9e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[dan...@rebolledo.name]

Hello Dan,

I've gone through the items you sent, and still the only error consistent to the problem is the missing file ending in _ovt.  To summarize efforts so far:

https://groups.google.com/forum/#!msg/ica-atom-users/sZki6TtdX00/1LDNO_uLFAAJ

Following the advice here, I regenerated slugs and nested sets:

root@justicia public_html]# cd icaatom/
[root@justicia icaatom]# php symfony propel:generate-slugs
>> propel    Generate actor slugs...
>> propel    Generate information_object slugs...
>> propel    Generate term slugs...
>> propel    Generate event slugs...
>> propel    Done!
[root@justicia icaatom]#

[root@justicia icaatom]# php symfony propel:build-nested-set
>> propel    Build nested set for information_object...
>> propel    Build nested set for actor...
>> propel    Build nested set for term...
>> propel    Done!
[root@justicia icaatom]# 

https://groups.google.com/forum/#!msg/ica-atom-users/Z8xPAMr0hiY/60L714l3EQAJ 

The advice here seemed to rely on having a specific item ID to check status on, so I skipped and instead went with the next reference:

https://groups.google.com/forum/#!msg/ica-atom-users/ZElzuHT_g40/z-XFsDFIFAAJ 

The advice here was much like the second URL, but not article-specific.  I ran the suggested queries and checked for empty columns, indicating a broken search index.  Each search returned no results, indicating there are no empty columns in the data:

[root@justicia ~]# mysql -Bse "use museo_icaatom; SELECT io.id as io_id, obj.id as obj_id, st.status_id as pub_status_id, slug.slug FROM information_object io LEFT JOIN object obj ON io.id=obj.id LEFT JOIN status st ON io.id=st.object_id AND st.type_id=158 LEFT JOIN slug ON slug.object_id=io.id;" > /home/temp/slugids.txt
[root@justicia ~]#
[root@justicia ~]# cat /home/temp/slugids.txt |wc -l
2448
[root@justicia ~]# head -n 5 /home/temp/slugids.txt
1    1    159    b9kns
316    316    160    fondo-historico-villa-grimaldi
319    319    160    previo-golpe-militar
328    328    160    documentos-generales
329    329    160    cartas
[root@justicia ~]#
[root@justicia ~]# cat /home/temp/slugids.txt |awk 'BEGIN {FS="\t"} $1=="" {print}'
[root@justicia ~]# cat /home/temp/slugids.txt |awk 'BEGIN {FS="\t"} $2=="" {print}'
[root@justicia ~]# cat /home/temp/slugids.txt |awk 'BEGIN {FS="\t"} $3=="" {print}'
[root@justicia ~]# cat /home/temp/slugids.txt |awk 'BEGIN {FS="\t"} $4=="" {print}'
[root@justicia ~]#

The error in the logs when I attempt to move an item is:

[06-Apr-2017 07:08:58 America/Vancouver] File '/home/museo/public_html/icaatom/data/index/segments_ovt' is not readable.

I did attempt to find the code which is calling segments_ovt, but my search came back empty.

[Dan Gillean]

Hi Daniel,

Thanks for trying to work through this, and for reporting back on your progress - sorry to hear that my initial suggestions didn't help. I confess that I have not seen this error before.

I think you could try manually deleting the index, and also explicitly running the reindex command as the www-data user, to make sure there is not some weird permissions issue going on. One of our developers recommended that, while you do this, you disable your webserver temporarily. So you could try the following to see if it will resolve this strange segments_ovt issue:

1. Disable your webserver
2. Manually delete the index: rm -rf data/index/*
3. Run the Repopulate command as the www-data user: sudo -u www-data php symfony search:populate QubitSearch

Hopefully manually removing the corrupted index first will allow the rebuild command to progress as expected.

Let us know how it goes!

Regards,

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/ad8ea1e6-eebc-4807-806e-b66d7a59fbe1%40googlegroups.com.