Since the upgrade to mga 6, mldonkey does not work anymore. The Deamon is started by the command mlnet Since the upgrade it is going back to prompt [~/Script]$ mlnet 2017/10/02 21:58:32 [cO] Starting MLDonkey 3.1.6 ... 2017/10/02 21:58:32 [cO] Language DE, locale UTF-8, ulimit for open files 1024 2017/10/02 21:58:32 [cO] raised ulimit for open files from 1024 to 4096 2017/10/02 21:58:32 [cO] MLDonkey is working in . 2017/10/02 21:58:32 [Gettext] Loading language resource mlnet_strings.de_DE.UTF-8 2017/10/02 21:58:32 [cO] loaded language resource file 2017/10/02 21:58:32 [DNS] Resolving [localhost.localdomain] ... 2017/10/02 21:58:32 [DNS] Resolving [www.mldonkey.org] ... 2017/10/02 21:58:32 [dMain] Libmagic file-type recognition database present 2017/10/02 21:58:32 [cO] Logging in ./mlnet.log [~/Script]$
Assigning to all packagers collectively, since there is no registered maintainer for this package. Also CC'ing some committers.
CC: (none) => eatdirt, lists.jjorge, luis.daniel.lucio, marja11Assignee: bugsquad => pkg-bugsSummary: mldonkey does not work => mldonkey does not work (mlnet command goes back to the prompt)
Works for me! Could you have a look to your ./mlnet.log and report what it says in there? thanks
There is not much in it 2017/10/03 18:31:09 [cO] Started logging... 2017/10/03 18:31:09 [dcCO] LETS reverse clients list NOW File searches.ini.tmp exists An error may have occurred during previous configuration save. Please, check your configurations files, and rename/remove this file before restarting
Thanks, yes there is enough :) mlnet has certainly crashed before, letting backup configuration files floating around. Remove the file "searches.ini.tmp" and start again. You may have another message like this, if there are other files *.ini.tmp. So keep removing the offending ones till mlnet starts! Let us know if this works! Cheers.
You was right. I works again, but i had to reboot. Great. I´m 100 % sure, though, that the bug emerged with the upgrade. Before, i experienced missed attempts in 10 % of the launch processes.
Yes, that's possible, the version of mldonkey changed on upgrade, so it may have caused a crash of the old one running! I am closing the bug then! Cheers.
Status: NEW => RESOLVEDResolution: (none) => INVALID