EPrints Technical Mailing List Archive

See the EPrints wiki for instructions on how to join this mailing list and related information.

Message: #05074

< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

[EP-tech] Re: Problem updating eprints database schema from 3.3.3 to 3.3.4 - Users failing to log on

It looks like your upgrade process failed due to some problem.  Simply setting the version flag in the database will not have made this problem go away.  In fact, there may be parts of the database schema that have not been upgraded.

I would suggest setting the version flag back to what it was.  If you have a backup to restore to, that would be even better.  Then we should try to fix the problem with the database that's stopping the upgrade command from successfully running.  Have you checked for database corruption with your favourite database diagnostic tool (e.g mysqlcheck)?


--
Adam Field
Business Relationship Manager and Community Lead
EPrints Services
+44 (0)23 8059 8814





On 6 Nov 2015, at 17:24, Admire Mutsikiwa wrote:

> I have restored my  my eprints instance by installing a fresh version of eprints and then use the database dumb to restore the database and then run ./bin/epadmin upgrade <archive>. My database dumb is of the schema 3.3.3. Now when I run the upgrade command, I am getting the following
> Upgrading 3.3.3 to 3.3.4
> Fixing missing ordervalues in saved_search
> Fixing missing ordervalues in document
> Fixing missing ordervalues in file
> Fixing missing ordervalues in user
> Magic number checking on storable string failed at /usr/local/lib/perl/5.10.1/Storable.pm line 420, at /usr/share/eprints3/bin/../perl_lib/EPrints/MetaField/Storable.pm line 129.
>  
> Try to access the eprints repository gives the error “EPrints Database schema is out of date”
>  
> However, when I manual update the version to 3.3.4 by running
> update version set  version='3.3.4'
> The repository becomes accessible and other functionalities such as browing and searching works well. However, users even the admin cannot log on.   I them compared my database schema in terms of the number of tables with a freshly installed eprints whose database schema version is 3.3.4 and I noted that a freshly installed version has fewer tables (98 tables) whereas my 3.3.3 schema has  more(141). Below are the results of the show table command on the two databases. I want to believe that this is the source of my problems.  How do I go about it? Any Pointers?
>  
> Tables_in_researchdatabase (database schema 3.3.3)
> Tables_in_rczproject (3.3.4)
> access
> access__ordervalues_en
> cachemap
> cachemap__ordervalues_en
> counters
> document
> document__index
> document__index_grep
> document__ordervalues_en
> document__rindex
> document_relation_type
> document_relation_uri
> eprint
> eprint__index
> eprint__index_grep
> eprint__ordervalues_en
> eprint__rindex
> eprint_accompaniment
> eprint_conductors_id
> eprint_conductors_name
> eprint_contributors_id
> eprint_contributors_name
> eprint_contributors_type
> eprint_copyright_holders
> eprint_corp_creators
> eprint_creators_id
> eprint_creators_name
> eprint_divisions
> eprint_editors_id
> eprint_editors_name
> eprint_exhibitors_id
> eprint_exhibitors_name
> eprint_editors_id
> eprint_editors_name
> eprint_exhibitors_id
> eprint_exhibitors_name
> eprint_funders
> eprint_item_issues_comment
> eprint_item_issues_description
> eprint_item_issues_id
> eprint_item_issues_reported_by
> eprint_item_issues_resolved_by
> eprint_item_issues_status
> eprint_item_issues_timestamp
> eprint_item_issues_type
> eprint_lyricists_id
> eprint_lyricists_name
> eprint_producers_id
> eprint_producers_name
> eprint_projects
> eprint_related_url_type
> eprint_related_url_url
> eprint_relation_type
> eprint_relation_uri
> eprint_skill_areas
> eprint_subjects
> event_queue
> event_queue__ordervalues_en
> file
> file__ordervalues_en
> file_copies_pluginid
> file_copies_sourceid
> history
> history__ordervalues_en
> import
> import__ordervalues_en
> loginticket
> loginticket__ordervalues_en
> message
> message__ordervalues_en
> mf
> mf__ordervalues_en
> mf_fields_allow_null
> mf_fields_browse_link
> mf_fields_datasetid
> mf_fields_default_value
> mf_fields_export_as_xml
> mf_fields_family_first
> mf_fields_hide_honourific
> mf_fields_hide_lineage
> mf_fields_input_boxes
> mf_fields_input_cols
> mf_fields_input_ordered
> mf_fields_input_rows
> mf_fields_input_style
> mf_fields_maxlength
> mf_fields_mfremoved
> mf_fields_min_resolution
> mf_fields_options
> mf_fields_render_input
> mf_fields_render_order
> mf_fields_render_value
> mf_fields_required
> mf_fields_set_name
> mf_fields_sql_counter
> mf_fields_sql_index
> mf_fields_sub_name
> mf_fields_top
> mf_fields_type
> mf_fields_volatile
> mf_phrase_help_lang
> mf_phrase_help_text
> mf_phrase_name_lang
> mf_phrase_name_text
> request
> request__index
> request__index_grep
> request__ordervalues_en
> request__rindex
> saved_search
> saved_search__index
> saved_search__index_grep
> saved_search__ordervalues_en
> saved_search__rindex
> sneep
> sneep__index
> sneep__index_grep
> sneep__ordervalues_en
> sneep__rindex
> subject
> subject__index
> subject__index_grep
> subject__ordervalues_en
> subject__rindex
> subject_ancestors
> subject_name_lang
> subject_name_name
> subject_name_sortvalue
> subject_parents
> subject_sortvalue_lang
> subject_sortvalue_sortvalue
> triple
> triple__ordervalues_en
> upload_progress
> upload_progress__ordervalues_en
> user
> user__index
> user__index_grep
> user__ordervalues_en
> user__rindex
> user_editperms
> user_items_fields
> user_review_fields
> user_roles
> version
> access
> access__ordervalues_en
> cachemap
> cachemap__ordervalues_en
> counters
> document
> document__index
> document__index_grep
> document__ordervalues_en
> document__rindex
> document_relation_type
> document_relation_uri
> eprint
> eprint__index
> eprint__index_grep
> eprint__ordervalues_en
> eprint__rindex
> eprint_contributors_id
> eprint_contributors_name
> eprint_contributors_type
> eprint_copyright_holders
> eprint_corp_creators
> eprint_creators_id
> eprint_creators_name
> eprint_divisions
> eprint_editors_id
> eprint_editors_name
> eprint_funders
> eprint_item_issues_comment
> eprint_item_issues_description
> eprint_item_issues_id
> eprint_item_issues_reported_by
> eprint_item_issues_status
> eprint_item_issues_timestamp
> eprint_item_issues_type
> eprint_projects
> eprint_related_url_type
> eprint_related_url_url
> eprint_relation_type
> eprint_relation_uri
> eprint_skill_areas
> eprint_subjects
> event_queue
> event_queue__ordervalues_en
> file
> file__ordervalues_en
> file_copies_pluginid
> file_copies_sourceid
> history
> history__ordervalues_en
> import
> import__ordervalues_en
> loginticket
> loginticket__ordervalues_en
> message
> message__ordervalues_en
> mf
> mf__ordervalues_en
> mf_phrase_help_lang
> mf_phrase_help_text
> mf_phrase_name_lang
> mf_phrase_name_text
> request
> request__index
> request__index_grep
> request__ordervalues_en
> request__rindex
> saved_search
> saved_search__index
> saved_search__index_grep
> saved_search__ordervalues_en
> saved_search__rindex
> subject
> subject__index
> subject__index_grep
> subject__ordervalues_en
> subject__rindex
> subject_ancestors
> subject_name_lang
> subject_name_name
> subject_name_sortvalue
> subject_parents
> subject_sortvalue_lang
> subject_sortvalue_sortvalue
> triple
> triple__ordervalues_en
> upload_progress
> upload_progress__ordervalues_en
> user
> user__index
> user__index_grep
> user__ordervalues_en
> user__rindex
> user_editperms
> user_items_fields
> user_roles
> version
>  
>  
> Kind Regards,
>  
> Admire Mutsikiwa (Mr)
> ICT Manager
> Libraries
> University of Zimbabwe
> Tel:+263-4-303276
> Mob:+263771117777
>  
> “It is easy to dodge our responsibilities, but we cannot dodge the consequences of dodging our responsibilities.”  Josiah Charles Stamp
>  
> 
> UZ at 60: Celebrating our Past, Inspiring the Future. 
> *** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
> *** Archive: http://www.eprints.org/tech.php/
> *** EPrints community wiki: http://wiki.eprints.org/
> *** EPrints developers Forum: http://forum.eprints.org/