[ensembl-dev] Variant Effect predictor error message

Will McLaren wm2 at ebi.ac.uk
Wed Oct 26 09:52:31 BST 2011


Hi Mark,

Are you using the cache or connecting to the database?

In either case, is your API up to date and/or in sync with the version
number of the database/cache you are using?

Will

On 26 October 2011 08:51, Venturini Luca <vntlcu41 at univr.it> wrote:
> I would try using "human" as a species name, usually that functions. Also,
> set the verbose flag - if the connection to the database functions, you
> should see a list of all available species/dataset loaded from MySQL.
>
> - Luca
>
>
> Il 25/10/2011 16:38, Mark Aquino ha scritto:
>>
>> Hi,
>>
>> I'm getting this error:
>>
>> homo_sapiens is not a valid species name for this instance
>> homo_sapiens is not a valid species name for this instance
>> Use of uninitialized value $species in hash element at
>> /users/maquino/src/ensembl/modules/Bio/EnsEMBL/Registry.pm line 958.
>> Use of uninitialized value $species in hash element at
>> /users/maquino/src/ensembl/modules/Bio/EnsEMBL/Registry.pm line 969.
>> ERROR: Could not connect to core database
>>
>> When I try to run the variant effect predictor.
>>
>> Is the core database still down and that's what's causing this error or is
>> there something else going wrong here?
>>
>> -Mark
>>
>> _______________________________________________
>> Dev mailing list    Dev at ensembl.org
>> List admin (including subscribe/unsubscribe):
>> http://lists.ensembl.org/mailman/listinfo/dev
>> Ensembl Blog: http://www.ensembl.info/
>
>
> _______________________________________________
> Dev mailing list    Dev at ensembl.org
> List admin (including subscribe/unsubscribe):
> http://lists.ensembl.org/mailman/listinfo/dev
> Ensembl Blog: http://www.ensembl.info/
>




More information about the Dev mailing list