EPrints Technical Mailing List Archive

Message: #03845

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

[EP-tech] Re: [solved?] advanced search without subject list (3.3.13)

  • To: Thomas Lauke <th.lauke@arcor.de>
  • Subject: [EP-tech] Re: [solved?] advanced search without subject list (3.3.13)
  • From: "Field A.N." <af05v@ecs.soton.ac.uk>
  • Date: Mon, 26 Jan 2015 10:20:56 +0000
It's possible those errors occurred due to tables being missing.  What happens if you run epadmin update again?  What errors do you get?

Note that running epadmin ugrade should do this.  Are there any customisations in your code-base?  Which version were you upgrading from?

--
Adam Field
Business Relationship Manager and Community Lead
EPrints Services




On 26 Jan 2015, at 10:12, Thomas Lauke wrote:

> Hi Adam,
> 
>> What happens when you run <eprints_root>/bin/epadmin update <repositoryid>?
> I got the following:
> 
> Possible attempt to put comments in qw() list at (eval 188) line 29.
> [TL] BTW: How to find the file containing some unexpected comment?
> 
> Starting EPrints Repository.
> Connecting to DB ... Database execute debug: SET NAMES 'utf8'
> done.
> Use of uninitialized value $sql in concatenation (.) or string at /opt/eprints3/eprints-3.3.13/bin/../perl_lib/EPrints/Database.pm line 3208, <DATA> line 960.
> Database execute debug: 
> Use of uninitialized value $sql in concatenation (.) or string at /opt/eprints3/eprints-3.3.13/bin/../perl_lib/EPrints/Database.pm line 3208, <DATA> line 960.
> Database execute debug: 
> Use of uninitialized value $sql in concatenation (.) or string at /opt/eprints3/eprints-3.3.13/bin/../perl_lib/EPrints/Database.pm line 3208, <DATA> line 960.
> Database execute debug: 
> Use of uninitialized value $sql in concatenation (.) or string at /opt/eprints3/eprints-3.3.13/bin/../perl_lib/EPrints/Database.pm line 3208, <DATA> line 960.
> Database execute debug: 
> Database execute debug: CREATE INDEX `user_roles_roles_1` ON `user_roles` (`roles`)
> Added roles to dataset user
> Use of uninitialized value $sql in concatenation (.) or string at /opt/eprints3/eprints-3.3.13/bin/../perl_lib/EPrints/Database.pm line 3208, <DATA> line 960.
> Database execute debug: 
> Use of uninitialized value $sql in concatenation (.) or string at /opt/eprints3/eprints-3.3.13/bin/../perl_lib/EPrints/Database.pm line 3208, <DATA> line 960.
> Database execute debug: 
> Use of uninitialized value $sql in concatenation (.) or string at /opt/eprints3/eprints-3.3.13/bin/../perl_lib/EPrints/Database.pm line 3208, <DATA> line 960.
> Database execute debug: 
> Use of uninitialized value $sql in concatenation (.) or string at /opt/eprints3/eprints-3.3.13/bin/../perl_lib/EPrints/Database.pm line 3208, <DATA> line 960.
> Database execute debug: 
> Database execute debug: ALTER TABLE `request` ADD `expiry_date_year` smallint,ADD `expiry_date_month` smallint,ADD `expiry_date_day` smallint,ADD `expiry_date_hour` smallint,ADD `expiry_date_minute` smallint,ADD `expiry_date_second` smallint
> Database execute debug: CREATE INDEX `request_expiry_date_year_6` ON `request` (`expiry_date_year`,`expiry_date_month`,`expiry_date_day`,`expiry_date_hour`,`expiry_date_minute`,`expiry_date_second`)
> Database execute debug: ALTER TABLE `request__ordervalues_en` ADD `expiry_date` longtext CHARACTER SET utf8 COLLATE utf8_bin
> Added expiry_date to dataset request
> Database execute debug: ALTER TABLE `request` ADD `code` varchar(255) CHARACTER SET utf8 COLLATE utf8_bin
> Database execute debug: ALTER TABLE `request__ordervalues_en` ADD `code` longtext CHARACTER SET utf8 COLLATE utf8_bin
> Added code to dataset request
> Use of uninitialized value $sql in concatenation (.) or string at /opt/eprints3/eprints-3.3.13/bin/../perl_lib/EPrints/Database.pm line 3208, <DATA> line 960.
> Database execute debug: 
> Use of uninitialized value $sql in concatenation (.) or string at /opt/eprints3/eprints-3.3.13/bin/../perl_lib/EPrints/Database.pm line 3208, <DATA> line 960.
> Database execute debug: 
> Database execute debug: CREATE TABLE `subject_name_sortvalue` (`subjectid` varchar(128) CHARACTER SET utf8 COLLATE utf8_bin, `pos` integer, `name_sortvalue` varchar(255) CHARACTER SET utf8 COLLATE utf8_bin, PRIMARY KEY(`subjectid`, `pos`)) DEFAULT CHARSET=utf8
> Database execute debug: ALTER TABLE `subject__ordervalues_en` ADD `name_sortvalue` longtext CHARACTER SET utf8 COLLATE utf8_bin
> Added name to dataset subject
> Database execute debug: CREATE TABLE `subject_sortvalue_sortvalue` (`subjectid` varchar(128) CHARACTER SET utf8 COLLATE utf8_bin, `pos` integer, `sortvalue_sortvalue` varchar(255) CHARACTER SET utf8 COLLATE utf8_bin, PRIMARY KEY(`subjectid`, `pos`)) DEFAULT CHARSET=utf8
> Database execute debug: ALTER TABLE `subject__ordervalues_en` ADD `sortvalue_sortvalue` longtext CHARACTER SET utf8 COLLATE utf8_bin
> Database execute debug: CREATE TABLE `subject_sortvalue_lang` (`subjectid` varchar(128) CHARACTER SET utf8 COLLATE utf8_bin, `pos` integer, `sortvalue_lang` varchar(16) CHARACTER SET utf8 COLLATE utf8_bin, PRIMARY KEY(`subjectid`, `pos`)) DEFAULT CHARSET=utf8
> Database execute debug: ALTER TABLE `subject__ordervalues_en` ADD `sortvalue_lang` longtext CHARACTER SET utf8 COLLATE utf8_bin
> Database execute debug: CREATE INDEX `subject_sortvalue_lang_sortvalue_lang_1` ON `subject_sortvalue_lang` (`sortvalue_lang`)
> Database execute debug: ALTER TABLE `subject__ordervalues_en` ADD `sortvalue` longtext CHARACTER SET utf8 COLLATE utf8_bin
> Added sortvalue to dataset subject
> Use of uninitialized value $sql in concatenation (.) or string at /opt/eprints3/eprints-3.3.13/bin/../perl_lib/EPrints/Database.pm line 3208, <DATA> line 960.
> Database execute debug: 
> Database execute debug: ALTER TABLE `subject__rindex` CONVERT TO CHARACTER SET utf8 COLLATE utf8_bin
> DBD::mysql::db do failed: Specified key was too long; max key length is 1000 bytes at /opt/eprints3/eprints-3.3.13/bin/../perl_lib/EPrints/Database.pm line 3052, <DATA> line 960.
> SQL ERROR (do): ALTER TABLE `subject__rindex` CONVERT TO CHARACTER SET utf8 COLLATE utf8_bin
> SQL ERROR (do): Specified key was too long; max key length is 1000 bytes (#1071)
> Fixed subject__rindex.field collation
> 0 datasets added
> 5 fields added
> Database execute debug: SELECT 1 FROM `counters` WHERE `countername`='savedsearchid'
> Database execute debug: SELECT 1 FROM `counters` WHERE `countername`='documentid'
> Database execute debug: SELECT 1 FROM `counters` WHERE `countername`='fileid'
> Database execute debug: SELECT 1 FROM `counters` WHERE `countername`='userid'
> Database execute debug: SELECT 1 FROM `counters` WHERE `countername`='eprintid'
> Database execute debug: SELECT 1 FROM `counters` WHERE `countername`='requestid'
> Database execute debug: SELECT 1 FROM `counters` WHERE `countername`='historyid'
> Database execute debug: SELECT 1 FROM `counters` WHERE `countername`='accessid'
> Database execute debug: SELECT 1 FROM `counters` WHERE `countername`='messageid'
> Database execute debug: SELECT 1 FROM `counters` WHERE `countername`='importid'
> Database execute debug: SELECT 1 FROM `counters` WHERE `countername`='cachemapid'
> Database execute debug: SELECT 1 FROM `counters` WHERE `countername`='tripleid'
> Database execute debug: SELECT 1 FROM `counters` WHERE `countername`='bookmarkid'
> Database execute debug: SELECT 1 FROM `counters` WHERE `countername`='metafieldid'
> 0 counters were added
> 
> Afterwards the end of 'bin/generate_views <repositoryid> --verbose --verbose' reads now
> Warning! No values were found for eprint.view.document_tags [document_tags] - configuration may be wrong
> Undefined phrase: viewname_eprint_document_tags (en) at line 2215 in /opt/eprints3/eprints-3.3.13/bin/../perl_lib/EPrints/Update/Views.pm
> Writing: /opt/eprints3/eprints-3.3.13/archives/A401sandbox/html/en/view/document_tags/index
> Wrote: /opt/eprints3/eprints-3.3.13/archives/A401sandbox/html/en/view/document_tags
> Database execute debug: SELECT DISTINCT D0,D1 FROM (SELECT `distinctby_194181268`.`document_tags` AS D0,`distinctby_194181268`.`eprintid` AS D1 FROM `eprint`, `eprint_document_tags` AS `distinctby_194181268`, `eprint_document_tags` AS `eprint_document_tags` WHERE `eprint`.`eprintid`=`distinctby_194181268`.`eprintid` AND `eprint`.`eprintid`=`eprint_document_tags`.`eprintid` AND (`eprint`.`metadata_visibility` = 'show' AND `eprint`.`eprint_status` = 'archive' AND ( `eprint_document_tags`.`document_tags` != ''))) AS D
> Undefined phrase: viewname_eprint_document_tags (en) at line 2215 in /opt/eprints3/eprints-3.3.13/bin/../perl_lib/EPrints/Update/Views.pm
> Writing: /opt/eprints3/eprints-3.3.13/archives/A401sandbox/html/en/view/index
> Wrote: /opt/eprints3/eprints-3.3.13/archives/A401sandbox/html/en/view/index
> 
> Browse views and selection lists (in staff search) are back :)
> But what about the above warnings and failed actions? Any corrections still necessary (beside setting of some undefined phrases)?
> 
> Finally it seems imho, that closure of http://trac.eprints.org/eprints/ticket/3757 would be great :-)
> All the trouble could be caused by some failing/unavailable perl modules ...
> 
> What about to integrate such a check for availability of all needed modules/installations into 'epadmin test'?
> 
> Thanks
> Thomas