soedinglab / MMseqs2

MMseqs2: ultra fast and sensitive search and clustering suite
https://mmseqs.com
GNU General Public License v3.0
1.37k stars 193 forks source link

Error: msa2profile died when preparing eggNOG database #344

Open schmittel opened 4 years ago

schmittel commented 4 years ago

Expected Behavior

mmseqs databases eggNOG /mmseqs/eggnog tmp --threads 16 should prepare the eggNOG database.

Current Behavior

The following error is produced:

databases eggNOG /mmseqs/eggnog tmp --threads 16

MMseqs Version:                 11.e1a1c
Threads                         16

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   161  100   161    0     0   6192      0 --:--:-- --:--:-- --:--:--  6440
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   161  100   161    0     0   6192      0 --:--:-- --:--:-- --:--:--  6192
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   161  100   161    0     0   6440      0 --:--:-- --:--:-- --:--:--  6440
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   161  100   161    0     0   6192      0 --:--:-- --:--:-- --:--:--  6192
tar2db tmp/4327021748121712355/bacteria tmp/4327021748121712355/archea tmp/4327021748121712355/eukaryota tmp/4327021748121712355/viruses tmp/4327021748121712355/msa --output-dbtype 11 --tar-include \.raw_alg\.faa\.gz$ --compressed 0 -v 3

Cannot open file tmp/4327021748121712355/bacteria
Error: msa2profile died

mmseqs installed via Conda. All other databases can be prepared as expected, just not eggNOG.

milot-mirdita commented 4 years ago

Could you try using the latest git version? I think we already fixed the issue and the fix should be part of the next release (sorry for the delay).